Re: [Groff] Groff Digest, Vol 106, Issue 3

[Robert Marks]

So, how is neatroff pronounced?
Neet-roff?  Nia-troff? Nia-T-roff?
Actually, how is troff pronounced? Troff? T-roff?
And groff?  Hardly G-roff but possible. 

Inquiring minds want to know. 

Robert Marks

My web page is http://www.agsm.edu.au/bobm

On 28/07/2013, at 2:01 AM, <address@hidden> wrote:

> Send Groff mailing list submissions to
>    address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    https://lists.gnu.org/mailman/listinfo/groff
> or, via email, send a message with subject or body 'help' to
>    address@hidden
> 
> You can reach the person managing the list at
>    address@hidden
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Groff digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Announcing Neatroff (Ali Gholami Rudi)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 26 Jul 2013 23:05:06 +0430
> From: Ali Gholami Rudi <address@hidden>
> To: Heinz-Jürgen Oertel <address@hidden>
> Cc: address@hidden
> Subject: Re: [Groff] Announcing Neatroff
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=utf-8
> 
> Heinz-J?rgen Oertel <address@hidden> wrote:
>>>> * Assumes UTF-8 encoding
>>>> * Named environments
>>>> * Long macro, register and environment names
>>>> * Color support
>>>> * Font pairwise kerning and arbitrary font ligatures
>>>> * Text direction for right-to-left languages
>>>> 
>>>> Links:
>>>> * A brief introduction: http://litcave.rudi.ir/neatroff.pdf
>>>> * Neatroff's Git repository: git://repo.or.cz/neatroff.git
>>>> * Neatpost's Git repository: git://repo.or.cz/neatpost.git
>>>>  (neatroff's postscript postprocessor)
>>>> 
>>>>    Ali
>>> 
>>> May I ask for the reasons to start a new development?
>>> Regards
>>>   Heinz
>> 
>> OK, i read the introduction at http://litcave.rudi.ir/neatroff.pdf.
> 
> Actually I was long contemplating starting a modern pure C
> implementation of troff; Plan 9 troff, Open Solaris troff, and
> Heirloom troff are all derived from the original troff; very short and
> difficult to decipher global variable and function names make their
> source code very difficult to follow.
> 
> When I needed a fully UTF-8 compatible troff clone with features such
> as text direction, I naturally decided to modify one of the available
> implementations.  After some examination, I decided to extend Plan
> 9 troff, which was already UTF-8 compatible; I ported it to Linux
> (git://repo.or.cz/troff.git), changed its font handling to make it
> more similar to the original troff or Groff, included a few fixes, and
> implemented text direction.
> 
> However, the difficulty of changing this implementation for some of my
> needs and importing some of the features absent in Plan9 troff
> convinced me to start neatroff.
> 
>    Ali
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Groff mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/groff
> 
> 
> End of Groff Digest, Vol 106, Issue 3
> *************************************