groff
[Top][All Lists]
Advanced

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

Re: [Groff] `groff_char.7' works only for `man', but not for `groff'


From: Bernd Warken
Subject: Re: [Groff] `groff_char.7' works only for `man', but not for `groff'
Date: Tue, 27 May 2014 11:04:55 +0200

> Von: "Werner LEMBERG" <address@hidden>
> Betreff: Re: [Groff] `groff_char.7' works only for `man', but not for `groff'
>
> >> I changed grog, such that lines starting with . (period) or '
> >> (apostrophe) are both regarded as equal (only within `grog').
> > 
> > Why?  I guess users are more likely rely on man(1), rather than on
> > grog, for reading man pages.  The convention is dictated by man, and
> > that convention stipulates that the keyword line should begin with
> > an apostrophe.  Since the maintenance of man(1) lies beyond our
> > remit, groff's manpage sources should be corrected, to conform with
> > the prescribed convention.
> 
> I suggest that grog accepts
> 
>   .\" t
> 
> under protest only, this is, it emits a warning that the line should
> be changed to
> 
>   '\" t
> 
> Bernd, can you implement that?

The 1st line of groff_char.man is changed now, I will check other man pages
later on.

The protest of grog will come later.  Now grog accepts not only the 4 
characters,
but all 8 from groff's options.  That will not hurt anything.

How about handling this feature also for other roff files?

Bernd Warken



reply via email to

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