Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread John Gardner
> Use .in \\nWu (capital "W"). Your "W" is the address width in device units. Uh... yeah, you're 100% right. I'm an idiot, haha. I must've been randomly trying different divisions before I knew to append the "u", heh. Thank you!!! On 4 August 2016 at 01:27, Tadziu Hoffmann wrote: > > > Hrm,

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Damian McGuckin
On Wed, 3 Aug 2016, Larry Kollar wrote: Is there some reason you can?t use device-independent units like inches or ens? .in 1i \? One inch indent on all devices .in 6n \? Six ens, (1 en is roughly the current text size) Sadly, I was under the 35 year impression you could. But in my letterhea

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Larry Kollar
> John Gardner wrote: > > I'm using the dl register to set page indent with .in, which works fine in > nroff, but generates absurdly large sizes in groff. For instance, a > diversion with a width of 624 in TTY output becomes 286946 in PostScript. > > I'm aware this is connected to the matter of

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Tadziu Hoffmann
> Hrm, well, adding the `u` suffix to `.in` *did* change the > indentation, but it's suddenly too small. Use .in \\nWu (capital "W"). Your "W" is the address width in device units. Your "w" (lowercase "w") is address width in device units divided by font size in points, which is probably no

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Carsten Kunze
> > http://troff.org/54.pdf It is recommended to study this document carefully. groff has useful extensions, but it's best to learn them when you know about the portable subset of the roff language. You e.g. often use requests with register contents as arguments without using a unit. I hope

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Ted Harding
Regarding your "72000", this will refer to 72000 "millipoints". In current standard orthograhy, 1 point is 1/72 of an inch, amd what I call a "millipoint" is of course 1/1000 of a point. It is ths standard unit (groff "u") for PostScript output ("devps" output device). So "72000" in \n[.o] denotes

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Ralph Corderoy
Hi John, > > > If you use .in with a register value you have to set the unit to > > > u, > > Hrm, well, adding the `u` suffix to `.in` *did* change the > indentation, but it's suddenly too small. Carsten means if the register holds a value that's already been converted to base units then append a

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread John Gardner
Hey guys, Hrm, well, adding the `u` suffix to `.in` *did* change the indentation, but it's suddenly too small. If you're curious, the code may be found here . Be aware this was written strictly as a personal challenge; no macros or GNU extensions were us

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Ralph Corderoy
Hi John, Carsten wrote: > If you use .in with a register value you have to set the unit to u, > e.g.: > .in \n(dlu > else the default unit of .in is multiplied with the dl register value. Also, see the Notes column for .in on page 4 of CSTR 54, http://troff.org/54.pdf, and sections 1.3 and 1.

Re: [Groff] Converting basic units to inches in PostScript

2016-08-03 Thread Carsten Kunze
John Gardner wrote: > I'm using the dl register to set page indent with .in, which works fine in > nroff, but generates absurdly large sizes in groff. For instance, a > diversion with a width of 624 in TTY output becomes 286946 in PostScript. If you use .in with a register value you have to set

[Groff] Converting basic units to inches in PostScript

2016-08-03 Thread John Gardner
I'm using the dl register to set page indent with .in, which works fine in nroff, but generates absurdly large sizes in groff. For instance, a diversion with a width of 624 in TTY output becomes 286946 in PostScript. I'm aware this is connected to the matter of device resolution, but is there any