[Groff] man-page fixes

2007-09-21 Thread Axel Kielhorn
Hi! I'm currently adding a section about further literature to my short guide. While reading the man-pages I stumbled over a few things: groff_char.man the Latin-1 (ISO-8859-1) code. groff.man (7) linkt to http://cm.bell-labs.com/cm/cs/54.ps but the actual file is at http://cm.bell-labs.com/

[Groff] Fw: sqrt troubles with eqn

2007-09-21 Thread Werner LEMBERG
This mail might be of interest to the groff community. Is there someone willing to explore how the PS version of cmex10 could be integrated into groff to get better scalable delimiters and radical signs? Werner --- Begin Message --- > For -Tdvi, I was not able to find a standalone DVI to Po

Re: [Groff] man-page fixes

2007-09-21 Thread M Bianchi
On Fri, Sep 21, 2007 at 08:32:54PM +0200, Axel Kielhorn wrote: > : > groff.man (7) linkt to http://cm.bell-labs.com/cm/cs/54.ps but the > actual file is at > http://cm.bell-labs.com/cm/cs/cstr/54.ps.gz (Which is actually a ps > file, unless my browser ungziped it on the fly.) It is a gzip

Re: [Groff] man-page fixes

2007-09-21 Thread Werner LEMBERG
> Do you want patches? Yes, please. > If yes, which format? diff -u Werner

Re: [Groff] -Txhtml

2007-09-21 Thread Gaius Mulley
Werner LEMBERG <[EMAIL PROTECTED]> writes: > > finally I've managed to track down some more bugs in -Txhtml and > > I think I've addressed all the issues above. The compressed > > file consists of the patches and ChangeLog entry, > > Excellent! I've applied it (with minor improvements). > Hoewe

[Groff] Question on string registers and requests

2007-09-21 Thread andlabs
Hello. I noticed, that given .ds U \\s-2UNIX\\s0 in a troff file after -ms, and neither -ms nor that file define a macro .U, I could do .U and it would be replaced with the contents of that string. Is that a feature of groff? I'd like to clear things up. Thanks. -- View this message in contex

Re: [Groff] Question on string registers and requests

2007-09-21 Thread Clarke Echols
Doesn't work that way. If you use: .de U .\" troff/groff requests and other stuff here .. to define macro U, then use .ds U \\s-1UNIX\\s0 to define a string named U, the namespace conflict causes macro U to be overwritten by the defined string. Executing .U does nothing because macro U was

Re: [Groff] Question on string registers and requests

2007-09-21 Thread andlabs
Here is what I did: .ds U \\s-1UNIX\\s0 .U Here is the command line (pstopdf is the Mac OS X equivalent of ps2pdf): troff utest | grops | tee utest.ps | pstopdf -i -o utest.pdf I attached the utest files and the two output files to show you; you may need to view them in Nabble. http://www.nabb

Re: [Groff] LL Usage in an-old.tmac Incompatible with man Program on GNU/Linux

2007-09-21 Thread Keith Marshall
On Thu, 2007-09-20 at 04:16 +0100, Colin Watson wrote: > > > groff_man.man says this: > > > > > > -rLL=line-length > > > Set line length. If this option is not given, the line > > > length defaults to 78n in nroff mode and 6.5i in troff mode. > > > > And, of course I *could* add that

Re: [Groff] Question on string registers and requests

2007-09-21 Thread Larry Jones
Clarke Echols writes: > > andlabs wrote: > > Hello. I noticed, that given > > > > .ds U \\s-2UNIX\\s0 > > > > in a troff file after -ms, and neither -ms nor that file define a macro .U, > > I could do > > > > .U > > > > and it would be replaced with the contents of that string. Is that a featu

Re: [Groff] Question on string registers and requests

2007-09-21 Thread brian m. carlson
On Fri, Sep 21, 2007 at 01:38:41PM -0700, andlabs wrote: > > Hello. I noticed, that given > > .ds U \\s-2UNIX\\s0 > > in a troff file after -ms, and neither -ms nor that file define a macro .U, > I could do > > .U > > and it would be replaced with the contents of that string. Is that a feature

Re: [Groff] Question on string registers and requests

2007-09-21 Thread Clarke Echols
I stand corrected. I put together a text file as follows. The first excerpt incorrectly uses the defined string as a macro call. The second interpolates the string. The only difference lies in how the "macro" is interpreted. There is no white space after "interpolating" the macro, and thus no