[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Groff] Fw: We need a new maintainer for groff

From: Werner LEMBERG
Subject: [Groff] Fw: We need a new maintainer for groff
Date: Fri, 15 Nov 2013 09:00:22 +0100 (CET)

Here's my e-mail sent to

--- Begin Message --- Subject: We need a new maintainer for groff Date: Fri, 15 Nov 2013 08:59:29 +0100 (CET)

we need a new maintainer for GNU troff.  While I still apply critical
patches here and there, I no longer have the impetus to do active
development of the package.

Note that Ted Harding, my co-maintainer, doesn't do any coding; he is
rather the helpful soul who takes care of user requests on the mailing
list (and I'm very glad that he does so).

The software package itself is in a rather good state, I think; it
compiles just fine on most (if not all) platforms, as far as I know.

Here's a short list of the most necessary improvements which quickly
came to my mind.


  . Move the groff CVS repository to a modern DVCS (I prefer git).

  . Update infrastructure to use gnulib.  Right now, it has a hybrid
    approach to use gnulib for a single module only, which is a waste
    of resources and a pain to maintain.

  . Make groff use automake.


  . Implement TeX's paragraph formatting or something similar – I
    consider groff's line-oriented paragraph formatting as its weakest
    point.  See heirloom troff for an example how this could be

  . Update to today's font world.  What groff currently supports
    natively (PostScript Type 1) is out of date since 15 years.
    Again, heirloom troff has support for this.

  . Apply zillions of small bug fixes sent to the groff mailing list.

  . Better support of Unicode.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]