Re: [9fans] Ligatures in Plan 9 troff

Re: [9fans] Ligatures in Plan 9 troff

[Rudolf Sykora]

Hello,

On 18 July 2013 16:18, benjamin.purcell <benjamin.purcell@zoho.com> wrote:
> when I attempt to convert the troff output with dpost. Does anyone know
how to get ligatures using Plan 9 troff?

I also have been unable to typeset ligatures.
I think I once asked the same question here, with no answer.
So, perhaps, if you are in a hurry, use heirloom troff instead, or you may
try and ask Ali Gholami Rudi <aligrudi@gmail.com>, who recently
wrote to me:

# I had not yet publicly announced it and I am just fighting with the
# temptation to start a new pic clone but in any case, neatroff, i.e. my
# new troff implementation, is now usable (http://litcave.rudi.ir/).
# There are some features (the ones that I rarely use myself) missing.
# It comes with its own postscript postprocessor (neatpost) and it can
# use the preprocessors and the macros of the original troff (available
# in my linux port of plan9 troff).  I hope to add some of the missing
# features and document the differences between neatroff and groff or
# the original troff in future.

Ruda

[9fans] Ligatures in Plan 9 troff

[benjamin.purcell]

I can't find any support for ligatures (suchas fi, ffi, fl) in the Plan 9 version of troff. The ligature tokens Fi and fi are not defined in the DESC file for troff fonts and no sizing data is given for those ligatures in the R font file for example. When I try to manually typeset a ligature (with the code "\(fi" or "\(Fi" ) I get the error

"cannot find glyph, rune=0x46 stoken <Fi> troff font R"

when I attempt to convert the troff output with dpost. Does anyone know how to get ligatures using Plan 9 troff?

Thank you!
bsp