What have folks been generally using to produce PDF from their docbook
SGML?
I have typically been using docbook2pdf on my linux box. Now that I spend
more writing time on OSX I managed to port the docbook-utils and jadetex
over to fink manually with a little bit of tweaking. The
docbook-utils
Thomas,
Well, the "quick" answer is that pdftex/pdflatex have been under heavy
development in the past few years, and things haven't always been backwards
compatible.
The good news is that now that the new version of teTeX (which was the
basis for both the new Fink package and Gerben Wierda's new
Thomas,
This particular problem is caused by fancyhdr.sty, which has changed
the way it does footrulewidth (see comments in that file).
I think you should replace
\setlength{\footrulewidth}{0.4pt}
with
\def\footrulewideth{0.4pt}
I'm not sure this is right, because I haven't been able to TeX
On Tuesday, February 4, 2003, at 07:12 PM, Max Horn wrote:
At 18:43 Uhr -0500 04.02.2003, Jeremy Erwin wrote:
I am porting a number of libraries that have extensive example code.
I have been
putting
DocFiles: examples/hello/* examples/testgrid/*
and the like in my info files, but flattening
From my point of view, portable software just means
that it should work well in regards to platform-specific
features (or bugs).
yves
Le Mardi, 4 févr 2003, à 00:59 Canada/Eastern, Robert Boehne a écrit :
Hello,
Maybe I don't understand OS X, but as I see it, any library
that needs a two level
I have some reports that the package doxygen doesn't work with gerben's
distro and with the newest tex distribution in fink unstable.
the problem is the tex-file included in the .tar-file of doxygen in the
/latex directory. it gets processed with "pdflatex doxygen_manual.tex"
and gives the fol
At 18:43 Uhr -0500 04.02.2003, Jeremy Erwin wrote:
I am porting a number of libraries that have extensive example code.
I have been
putting
DocFiles: examples/hello/* examples/testgrid/*
and the like in my info files, but flattening the directory
structure might not be such a great idea. Is the
I am porting a number of libraries that have extensive example code. I
have been
putting
DocFiles: examples/hello/* examples/testgrid/*
and the like in my info files, but flattening the directory structure
might not be such a great idea. Is there any reason why this behavior
is the default, and
Today, I split-off orbit package because it does not compliant to
Fink's packaging policy about shared library. BuildDepends field
of many packages in unstable tree are updated, but they are not
synced with stable tree because new orbit is not in stable yet.
Please help me test this, so as to move
I fixed dependency list of libxml, which previously contained readline,
declares 'BuildDepndsOnly: True'.
At the same time, I added readline as a BuildDepends in following
packages:
[unstable]
eroaster
flac
glunarclock
gtkhtml1.1
gtranslator
visualos
xmms-normalize
xmms-pm
xmms-status
[stable]
g
10 matches
Mail list logo