From: Carsten Kunze <carsten.kunze@arcor.de>
To: 9fans@9fans.net
Subject: Re: [9fans] Many bugs in eqn(1)
Date: Wed, 13 Aug 2014 14:22:00 +0200 [thread overview]
Message-ID: <2021410182.1376266.1407932520506.JavaMail.ngmail@webmail06.arcor-online.net> (raw)
In-Reply-To: <20140813104336.GA1172@polynum.com>
> Does anyone know if there has been any effort to use TeX and al. for the
> system typesetting i.e. the manpages and docs? (Translation of the troff
> macros to TeX ones etc.---not to mention that for TeX (kerTeX), it needs
> to be converted for utf-8 input; that's on my TODO list but I need to
> finish the rewrite of the T1 lib for dvips(1) first, and the display for
> METAFONT.)
Is this really necessary for the system documentation? AFAIK P9 nroff/troff
can handle utf-8. If there are problems with *roff they should be solved.
*roff is a Bell Labs documentation system--it should be used for P9--IMO.
next prev parent reply other threads:[~2014-08-13 12:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1209878384.1371392.1407919054269.JavaMail.ngmail@webmail06.arcor-online.net>
2014-08-13 9:52 ` Rudolf Sykora
2014-08-13 10:30 ` cam
2014-08-13 10:43 ` tlaronde
2014-08-13 12:22 ` Carsten Kunze [this message]
2014-08-13 13:36 ` tlaronde
2014-08-13 10:57 Carsten Kunze
2014-08-13 11:34 ` Rudolf Sykora
2014-08-13 12:16 ` Carsten Kunze
2014-08-13 13:13 ` Rudolf Sykora
2014-08-13 13:46 ` tlaronde
2014-08-13 13:31 ` Carsten Kunze
2014-08-13 18:11 ` Steve Simon
2014-08-13 18:47 ` Carsten Kunze
2014-08-13 19:37 ` Steve Simon
2014-08-13 20:09 ` Carsten Kunze
2014-08-14 6:53 ` Steve Simon
2014-08-14 15:01 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 15:41 Carsten Kunze
2014-08-12 20:46 ` Steve Simon
2014-08-12 21:02 ` Carsten Kunze
2014-08-12 21:08 ` Steve Simon
2014-08-13 7:56 ` Rudolf Sykora
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=2021410182.1376266.1407932520506.JavaMail.ngmail@webmail06.arcor-online.net \
--to=carsten.kunze@arcor.de \
--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).