9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Carsten Kunze <carsten.kunze@arcor.de>
To: 9fans@9fans.net
Subject: Re: [9fans] Many bugs in eqn(1)
Date: Wed, 13 Aug 2014 12:57:13 +0200	[thread overview]
Message-ID: <1179414908.1374571.1407927433550.JavaMail.ngmail@webmail06.arcor-online.net> (raw)

> first, I don't understand German (I am Czech), but I used google translate,
> hopefully getting the meaning.

Sorry for that!

> Second, it's generally better (unless it's really personal or highly
> technical)
> to keep the discussion within the mailing list, since then other people
> can also contribute; I am far from an expert. Thus I have brought the
> discussion back to the list.

Since nobody seems to use troff on P9 I regarded it as off-topic.

> http://9fans.net/archive/2011/11/106

Thank you!

> some more ...
> http://9fans.net/archive/?q=sykora+eqn&go=Grep

I can't believe that TeX should not produce better results, but
thats really OT...

> I would say that groff is *much, much* more tested software.
> P9 troff is basically dead.

Not dead ... lets call it freezed or so ...

> I'd rather say that p9p software is the source these days.

Really?  Ok, if I compare the sources it looks like this.  Is this
true for troff only or for p9p in general?

So p9 troff posts may be better done on the p9p list?

> troff is a macro language.

This I completely don't understand.  If someone has much time
and uses only low level requests than the word "macro" should
be improper?

What is not a macro language, i.e. what do you suggest to use instead?

> Page makeup by postprocessing text formatter output
> by Kernighan & Wyk

I also do not understand that.  It is possible to write very good macro
packages for troff.  Also TeX can produce very good documents.  Ok,
this is OT again.

Carsten



             reply	other threads:[~2014-08-13 10:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13 10:57 Carsten Kunze [this message]
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
     [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
2014-08-13 13:36       ` tlaronde
  -- 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=1179414908.1374571.1407927433550.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).