Am Sonntag 28 Juli 2013, 13:53:33 schrieb James Cloos: > >>>>> "HO" == Heinz-Jürgen Oertel <[email protected]> writes: > > HO> If not absolutely necessary, I like to stay with my ISO 8859-1 (-15) > environment. > > In a utf-8 locale, nroff defaults to the utf8 device, which is why the > nroff example as written did not work for you. > > It seems that you need support for u0075_030A in the groff font file if > you want to use the unicode combining sequence. > > This: > > :; grep u0075_030A /usr/share/groff/1.22.2/font/*/R > /usr/share/groff/1.22.2/font/devhtml/R:u0075_030A 24 0 0x016F > /usr/share/groff/1.22.2/font/devutf8/R:u0075_030A 24 0 0x016F
OK, than this will be the way for me as next step. > > shows that only those two devices have it by default. > > The aring example worked because the font/devps/TR file has explicit > support for the type1 /aring glyph. It also support the /ring glyph, > so maybe something like: > > \o'u\C\'ao\'' > > is the way to go? \o'' overstrikes up to nine glyphs; \C'ao' is the ring > glyph. This works. > > It works here for ps, dvi and pdf devices. But only for troff; nroff > only show the last glyph from the \o'' set. > > (I used http://cm.bell-labs.com/sys/doc/troff.pdf to learn \o'' and \C'' > and looked at /usr/share/groff/1.22.2/font/devps/TR to find the roff > name (ao) for the ring glyph.) > > -JimC Thanks Jim, -- mit freundlichen Grüßen Heinz-Jürgen Oertel
signature.asc
Description: This is a digitally signed message part.
