CVSROOT:/cvsroot/groff
Module name:groff
Changes by: Werner LEMBERG wl 12/12/27 21:55:19
Modified files:
. : ChangeLog
man: ditroff.man
Log message:
* man/ditroff.man: Typographical improvements and typos.
CVSWeb URLs:
CVSROOT:/cvsroot/groff
Module name:groff
Changes by: Werner LEMBERG wl 12/12/27 22:06:35
Modified files:
. : ChangeLog
man: ditroff.man groff_diff.man groff_font.man
Log message:
* man/groff_font.man: Typographical
This bug appears in GNU groff version 1.21.
In the -me reference manual, the description for .(b says:
If the block will not fit on the current page a new page is begun,
unless that would leave more than \n(bt [0] white space at the bottom
of the text. If \n(bt is zero, the threshold
\~\c is removed as it is not needed (any more).
This is a bad idea. I don't want to read
... and for each font
F a font file called
F.
Instead, I want the single letter `F' bound to its associated word:
... and for each font F
a font file called F.
Besides this, I've
Hi,
I need to put double quotes within string arguments, for example a HEADING.
According to the documentation, inline escapes \(lq and \(rq should be used.
However I found out that using (two double-quotes) works fine too, and I
find it more convenient.
Is that just by chance or can I
Yes, you can use a double quote in a macro argument (it is documented
and has been there forever).
But it gives you the ASCII quote mark, not the typographical open and
close quotes which are use in typesetting English (\[lq] and \[rq]).
What special symbols you use would depend on the language,
On Thu, Dec 27, 2012, Denis M. Wilson wrote:
Yes, you can use a double quote in a macro argument (it is documented
and has been there forever).
But it gives you the ASCII quote mark, not the typographical open and
close quotes which are use in typesetting English (\[lq] and \[rq]).
If
