This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin manpages clobbered
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Mon, 13 May 2013 16:04:04 -0600
- Subject: Re: Cygwin manpages clobbered
- References: <5F8AAC04F9616747BC4CC0E803D5907D0AF787B3 at MLBXv04 dot nih dot gov> <518C55BD dot 7020807 at etr-usa dot com> <20130510041245 dot GA3019 at ednor dot casa dot cgf dot cx> <518CC275 dot 2060207 at etr-usa dot com> <518D8085 dot 8020203 at tlinx dot org>
On 5/10/2013 17:19, Linda Walsh wrote:
the PDF code font is less than optimal..
The current doco PDFs are generated through dblatex, via xmlto. I don't
know if it's possible to reach through two generators to affect final
I suspect part of this is due to the weirdness of fonts on *ix systems
in general. You wouldn't expect dblatex to be able to go and grab, say,
the native Consolas font from Windows. And even if someone did the work
to make that happen, it would fail when you built the manuals on Linux.
I know how to fix this when you generate PDF from DocBook via XSL-FO
(e.g. xsltproc and Apache FOP) but that brings in its own bag of
problems. For one biggie, all the XSL-FO processors depend on Java.
I've added an item to look into this to the new winsup/doc/Wishlist file.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple