Re: [Groff] It is time to modernise "groff"

2017-09-02 Thread Ralph Corderoy
Hi Bjarni, You present too long a list, and that may be putting off people from attempting to reply, but I think the general answer is "no". > an-old.tmac:.tm `R' is a string (producing the registered sign), not a > macro. > devices/grodvi/dvi.cpp:error("unrecognised drawing command `%1'

Re: [Groff] It is time to modernise "groff"

2017-09-02 Thread Larry Kollar
Modernizing is all well and good, but many people use groff to typeset legacy documents. Indeed, one could argue that groff has done an excellent job of walking that line between modernizing and backward compatibility. We have long names, HTML output (however crude), and a lot of people on this

Re: [Groff] It is time to modernise "groff"

2017-09-02 Thread Blake McBride
On Thu, Aug 31, 2017 at 3:54 PM, Bjarni Ingi Gislason wrote: > > it is time to modernize "groff" and > get rid of Americanism, old, obsolete, deprecated, bad, and worse > decisions. > > . First, I love troff. In my 35+ years in the software industry, I've never seen a better ba

Re: [Groff] git-repository: Adjustments not yet completed after transfer

2017-09-02 Thread Bertrand Garrigues
Hi Bjarni, On Wed, Jul 26 2017 at 11:55:24 PM, Bjarni Ingi Gislason wrote: > The git repository is not yet fully functional as the bug #51415 has yet to > be committed. > My master branch shows me in read the names of manual pages, that are > created and should therefore not be tracked. I'v

Re: [Groff] It is time to modernise "groff"

2017-09-02 Thread Peter Schaffter
On Sat, Sep 02, 2017, Blake McBride wrote: > Second, I don't think troff is gaining in popularity. The contrary is, > Lastly, as stated by others, troff has a substantial history. Significant > changes in troff could invalidate most of the old documents leaving troff > with no usage base, and a p