9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Ligatures in Plan 9 troff
Date: Sat, 20 Jul 2013 10:03:48 +0200	[thread overview]
Message-ID: <CAOEdRO1owydb9wK2Af1gkxVNdQ+Y2g7SL4xpSnNO_nV=pSmj0w@mail.gmail.com> (raw)
In-Reply-To: <605920755.134257.1374157112614.JavaMail.sas1@172.29.249.242>

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



       reply	other threads:[~2013-07-20  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <605920755.134257.1374157112614.JavaMail.sas1@172.29.249.242>
2013-07-20  8:03 ` Rudolf Sykora [this message]
2013-07-18 14:18 benjamin.purcell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOEdRO1owydb9wK2Af1gkxVNdQ+Y2g7SL4xpSnNO_nV=pSmj0w@mail.gmail.com' \
    --to=rudolf.sykora@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).