BTW, I can't send mail directly to you, Greg -- it is blocked by your
email system. Sigh.
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
Werner Lemberg wrote, quoting Greg Lehey:
>> I have a design document that I need to output in two forms: as a
>> properly typeset PostScript file (troff) and in plain text (nroff).
>> I want the latter not to have page breaks.
>
> Have a look how this problem is solved in an-old.tmac.
Hmm. Is th
> Hmm. Is this completely solved within an-old.tmac?
AFAIK, yes. Of course, there may be bugs, but...
> Man itself does:
>
> (echo ".pl 1100i"; cat manpage-source; echo ".pl \n(nlu+10") |
> nroff -man
With groff, this is unnecessary (since a few years).
Werner
> When my LANG environment variable is set to en_US.UTF-8 which it
> generally is as I work in unicode I get very weird groff outputted
> postscript files.
This should be fixed in more recent versions of groff (which
internally sets the locale to `C').
Werner
__
Greg Lehey wrote, quoting Clarke Echols:
>> Have you tried ".ifn" and ".ift" (if nroff and if troff)?
>
> Yes, though I write it '.if t' and '.if n'. '.ifn' doesn't work;
> possibly this is a contracted form that no longer works.
".ifn" is AT&T syntax; since AT&T troff allows only two characters
> ".ifn" is AT&T syntax; since AT&T troff allows only two characters
> in a request name, this is interpreted as ".if n", with the missing
> space implicitly understood. To support arbitrary long request
> names, groff *never* allows this space to be omitted.
Except in compatibility mode.
On Wed, May 31, 2006 at 11:32:00AM +0930, Greg 'groggy' Lehey wrote:
> I have a design document that I need to output in two forms: as a
> properly typeset PostScript file (troff) and in plain text (nroff). I
> want the latter not to have page breaks. I've tried a number of
> things, but I have t
>> Man itself does:
>>
>> (echo ".pl 1100i"; cat manpage-source; echo ".pl \n(nlu+10") |
>> nroff -man
>
> With groff, this is unnecessary (since a few years).
Ok, but I guess man needs to keep this construct; the nroff deployed
may not be groff, on some supported platforms.
Regards,
Keit
Werner Lemberg wrote, quoting me:
>> ".ifn" is AT&T syntax; since AT&T troff allows only two characters
>> in a request name, this is interpreted as ".if n", with the missing
>> space implicitly understood. To support arbitrary long request
>> names, groff *never* allows this space to be omitted.
On Wed, May 31, 2006 at 08:27:29AM -0400, Jon Snader wrote:
> On Wed, May 31, 2006 at 11:32:00AM +0930, Greg 'groggy' Lehey wrote:
> > I have a design document that I need to output in two forms: as a
> > properly typeset PostScript file (troff) and in plain text (nroff). I
> > want the latter not
Dear Werner,
Thank you very much for your advice, after upgrading groff to
1.19.3 I no longer have this problem. I would have liked to stay
with the packaged version for Fedora Core 5 to keep things
easier. But since they won't be bundling a newer version of
groff for a while, I compiled it and
11 matches
Mail list logo
