Werner LEMBERG napisał(a):
First of all, which groff version?
I have started to use groff some time ago. I use it to generate
document in Polish language. I have installed Polish font Quasi
Times and I use to generate documents macro latin2. But as you can
see in attached document that the
> - If there's a reference to page N in the text, you need to add viii
> to it. What's more: you have to remember to add ... That'
> difficult, you know.
Well, there are clickable links everywhere: table of contents,
indices, etc.. Where exactly have you encountered problems?
>The simp
> How much work would it be to hook into whatever system-wide printer
> drivers there may be?
Uh, I've no idea.
> This is something I've been pondering for a while, and I don't even
> have a clue how gtroff figures out glyph widths (is there some
> communication between gtroff & the postproces
> Here comes the patch that makes it possible to process manual pages
> with Unicode characters without declaring them first in advance.
Thanks a lot! I've applied your changes, but I'm stumbling across the
following problems.
. What shall we do with `charXXX' glyph names, with 128 <= `XXX' <=
On 27/02/2006, at 7:33 AM, Werner LEMBERG wrote:
- If there's a reference to page N in the text, you need to add viii
to it. What's more: you have to remember to add ... That'
difficult, you know.
Well, there are clickable links everywhere: table of contents,
indices, etc.. Where exac
Werner LEMBERG wrote:
... how gtroff figures out glyph widths ...
gtroff reads the metric files (in the devXXX directories) for the
given device and positions the glyphs accordingly. The postprocessor
just translates the intermediate output file into device-specific
data -- no need to access
