Hi all,
The `make pdfdocs' target still fails for me on the
`writing_usb_drivers' document. There's one small bug in it, and one
problem I haven't figured out yet.
There is a malformed <literal>blah<literal> sequence, where the
closing tag is instead an opening tag. Patch for that below.
Also, when the TeX back-end runs, for some reason, ConTeX seems
to get referenced and I get this (trimmed):
loading : Context Support Macros / Missing
)
loading : Context Support Macros / PDF
) (/usr/share/texmf/tex/latex/hyperref/nameref.sty) (./writing_usb_driver.out
! Missing $ inserted.
[snippity]
LaTeX Font Warning: Font shape `\\\OT1/cmr/m/n' @undefined
(Font) using `\\OT1/cmr/m/n' instead on input line 2.
LaTeX Font Warning: Font shape `\\\\OT1/cmr/m/n' @undefined
(Font) using `\\\OT1/cmr/m/n' instead on input line 2.
[snip]
LaTeX Font Warning: Font shape `[LOTS of \'s]\\\OT1/cmr/m/n' @undefined
(Font) using `\[LOTS of \s']\OT1/cmr/m/n' instead on input line 2.
[snip]
! TeX capacity exceeded, sorry [save size=5000].
But when I generate it manually from the sgml file that was generated, i.e.:
jade -t tex -d /usr/share/sgml/docbook/utils-0.6.9/docbook-utils.dsl
-i print -o foo.tex ../Documentation/DocBook/writing_usb_driver.sgml
jadetex foo.tex
I get a proper dvi file.
Converting to RTF also works:
jade -t rtf -d /usr/share/sgml/docbook/utils-0.6.9/docbook-utils.dsl
-i print -o foo.rtf Documentation/DocBook/writing_usb_driver.sgml
Anyone have ideas?
-- DN
Daniel
===== Documentation/DocBook/writing_usb_driver.tmpl 1.4 vs edited =====
--- 1.4/Documentation/DocBook/writing_usb_driver.tmpl Wed Aug 20 09:40:22 2003
+++ edited/Documentation/DocBook/writing_usb_driver.tmpl Mon Sep 15 03:45:26 2003
@@ -209,7 +209,7 @@
The driver now needs to verify that this device is actually one that it
can accept. If so, it returns 0.
If not, or if any error occurs during initialization, an errorcode
- (such as <literal>-ENOMEM<literal> or <literal>-ENODEV<literal>)
+ (such as <literal>-ENOMEM</literal> or <literal>-ENODEV</literal>)
is returned from the probe function.
</para>
<para>
On Mon, Sep 15, 2003 at 03:57:29AM -0700, carbonated beverage wrote:
> Hi all,
> ...
> LaTeX Font Warning: Font shape `[LOTS of \'s]\\\OT1/cmr/m/n' @undefined
> (Font) using `\[LOTS of \s']\OT1/cmr/m/n' instead on input line 2.
> [snip]
> ! TeX capacity exceeded, sorry [save size=5000].
Try to increase the capacities. You just need to
edit the file
/etc/texmf/texmf.cnf
Juergen.
On Mon, Sep 15, 2003 at 06:11:57PM +0200, Juergen Quade wrote:
> Try to increase the capacities. You just need to
> edit the file
> /etc/texmf/texmf.cnf
Sorry, I wasn't clear. Every time it fails to find a font, it slaps
a backslash on the beginning of it and tries again, and keeps going
until it consumes all of TeX's memory pool. So something either in the
DocBook utilities in Debian's broken, or the DocBook-related material
in the kernel.
-- DN
Daniel
On Mon, Sep 15, 2003 at 03:57:29AM -0700, carbonated beverage wrote:
> Hi all,
>
> The `make pdfdocs' target still fails for me on the
> `writing_usb_drivers' document. There's one small bug in it, and one
> problem I haven't figured out yet.
>
> There is a malformed <literal>blah<literal> sequence, where the
> closing tag is instead an opening tag. Patch for that below.
Thanks, I've applied this patch, and fixed up a missing </para> tag in
that file too.
greg k-h