[self-follow-up]
At 2024-01-30T20:06:51-0600, G. Branden Robinson wrote:
> I find that while the link text gets appropriately colored when
> viewing gropdf(1)-generated PDFs in both Evince and Okular (which I
> have handy), only in Evince do the links _work_.
I figured out the trouble
Follow-up Comment #33, bug #63354 (group groff):
Bjarni's proposed \[u2012] definition in comment #26 has two problems.
* It relies on a register (lfiguredash) that calculates the width of a zero
and a hair space based on the font size at the time the register is defined.
This value will thus be
Follow-up Comment #17, bug #63332 (group groff):
[comment #3 comment #3:]
> However maybe we need a new ".if g" conditional operator that _really_
> does check to see if a glyph is available in the current font.
This (and some related proposed conditionals) is the subject of bug #64004.
Thank you very much and nice to see that you are still active. :-)
søn. 3. mar. 2024 19.35 skrev Peter Schaffter :
> On Sun, Mar 03, 2024, Mikkel Meinike Nielsen wrote:
> > Now I am in a situation where I want to use the font called
> > Palatino which is in the ghost script package fonts. What
On Sun, Mar 03, 2024, Mikkel Meinike Nielsen wrote:
> Now I am in a situation where I want to use the font called
> Palatino which is in the ghost script package fonts. What would
> be the easiest step for me to get Palatino working in my groff ms
> document?
groff already ships with Palatino
The manual pages for gropdf and grops should gave you enough
information.
Looking at "fonts_x.ps" and "fonts_n.ps" shows you how the
glyphs look like
in the groff package hdtbl,
residing in the build directory ".../contrib/hdtbl/examples" in
the git repository and
in Debian
Hey fellow gruff users
Actually writing this makes me wonder how many we are around the world that
actually uses groff/troff on a regular basis.
What do you think a hundred?
Well I do use groff on a regular basis and have done that since I guess
2008. I've been playing with fonts every now and
