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
On Thu, Sep 20, 2007 at 12:19:29PM +0200, Werner LEMBERG wrote:
>
> > > >From HP's "Text Formatting User's Guide" (ca. 1991):
> >
> > [...]
> >
> > This was already there in the "PWB/MM Programmer's Workbench
> > Memorandom Macros", D.W. Smith and J.R. Mashey, October 1977.
> >
> > So there only
On Thu, Sep 20, 2007 at 02:10:04PM +0200, Gunnar Ritter wrote:
> Bob Diertens <[EMAIL PROTECTED]> wrote:
>
> > This was already there in the "PWB/MM Programmer's Workbench Memorandom
> > Macros", D.W. Smith and J.R. Mashey, October 1977.
> >
> > So there only a bug in the groff_mm manual page.
> >
On Mon, Sep 17, 2007 at 05:50:28PM +0200, Gunnar Ritter wrote:
> M Bianchi <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Sep 17, 2007 at 01:52:04AM +0200, Gunnar Ritter wrote:
> > > :
> > > All variants of the original -mm which I have seen so far
> > > h
On Mon, Sep 17, 2007 at 01:52:04AM +0200, Gunnar Ritter wrote:
> :
> All variants of the original -mm which I have seen so far
> have been very similar. It is likely that they all use the
> :p register in the same way.
One definition of backward compatibility is "All Bugs Are Preserv
On Mon, Sep 17, 2007 at 12:25:20AM +0100, Ted Harding wrote:
> On 16-Sep-07 22:15:55, Werner LEMBERG wrote:
> >> > I don't think classic troff mm's ":p" has ever been in groff's mm,
> >> > which has used "ft*nr" as long as I've known it (about 1990)!
> >>
> >> The obvious "solution" to that "probl
On Sat, Jul 07, 2007 at 08:45:23PM +0200, Werner LEMBERG wrote:
> > May I complement you and your colleagues and thank you all for the
> > GNU troff suite. It is obviously excellently done. [...]
> Thanks for the praise. However, we lack an active maintainer for the
> mm macros (which I've nev
On Thu, Jan 25, 2007 at 02:51:07PM +0100, Gunnar Ritter wrote:
> Stephen Holland <[EMAIL PROTECTED]> wrote:
>
> > So, with all that, is there an option to get groff to stop adjusting
> > withing words? For my needs, adjusting whitespace size is all that
> > is needed.
>
> .kern 0
>
> > Or s
On Fri, Jan 05, 2007 at 03:04:08PM +0100, Gunnar Ritter wrote:
> M Bianchi <[EMAIL PROTECTED]> wrote:
> > If it is always created in groff tbl(1), can we get this documented in the
> > man
> > page? As part of GNU TBL ENHANCEMENTS ?
> But \n(TW is not a GNU tbl enh
On Thu, Jan 04, 2007 at 03:11:38PM -, Ted Harding wrote:
> On 03-Jan-07 T. Kurt Bond wrote:
> > Is there any way to find out the width of the most recent table?
> :
> The following should work. Indeed, it may always work!
>
> When 'tbl' is invoked on groff code with ".TS"/".TE" blocks,
>
> On Mon, Jan 01, 2007 at 11:32:11AM -0500, Eric S. Raymond wrote:
> > Gunnar Ritter <[EMAIL PROTECTED]>:
> > > Eric S. Raymond wrote:
> > > ... and "don't write multiple description lines".
> > Multiple description lines?
> I'm talking about name sections like this:
>
> NAME
>bzip2, bunzi
On Fri, Dec 29, 2006 at 10:38:39AM -0500, Larry Kollar wrote:
> :
> When you're writing a
> document (like a manpage) that can be displayed in a large number of ways
> -- text on a console, PDF/print (allowing the user to choose the point size
> with the -S option, remember), or HTML... or
On Sun, Dec 24, 2006 at 04:48:50PM -0500, Eric S. Raymond wrote:
> Enclosed version of groff.1 uses only standard man macros and .de;
> I've inserted .in and .br macros to make the Synopis pretty again.
Woops!
I apologize. I've been looking at _very_ old versions of the man page source.
I think
On Sun, Dec 24, 2006 at 01:35:09AM -0500, Eric S. Raymond wrote:
> :
> This is a much richer ontology than HTML, so man -> DocBook -> HTML
> produces best possible HTML. man -> HTML, on the other hand, ends up
> translating man pages into a sort of least-common-denominator ontology
> between
On Sat, Dec 23, 2006 at 10:26:43PM -0500, Larry Kollar wrote:
> :
> The problem with using XML for documentation is that it was
> designed specifically for machine processing -- and *people*
> write documents for *other* people.
I agree and think this is _very_ important. groff -mm and -ms
On Sat, Dec 23, 2006 at 12:56:47AM -0500, Eric S. Raymond wrote:
> M Bianchi <[EMAIL PROTECTED]>:
> > On Fri, Dec 22, 2006 at 06:19:15PM -0500, Eric S. Raymond wrote:
> > > :
> I think you'll see from my previous reply to Ted Harding that
> I agree with thi
On Fri, Dec 22, 2006 at 06:19:15PM -0500, Eric S. Raymond wrote:
> :
> But I hear you asking "Why fix what ain't broken?".
> :
> The philosophical issue this raises about groff's place in the world
> is simple: are we willing to accept that it's a legacy rather than
> a primary format
On Tue, Aug 22, 2006 at 02:42:47PM +0100, Keith MARSHALL wrote:
> Mike Bianchi wrote:
> >>> (it just would be nice if the `.so' request _could_ interpolate the
> >>> string register value)
> >>
> >> Indeed, but I don't see how to do that properly.
> >
> > Maybe soelim(1) could recognize that the ar
On Tue, Aug 22, 2006 at 07:30:54AM +0200, Werner LEMBERG wrote:
> > (it just would be nice if the `.so' request _could_ interpolate the
> > string register value)
>
> Indeed, but I don't see how to do that properly.
Maybe soelim(1) could recognize that the argument is not a file name ( \ being
a
generated from some WP program which supported Avery labels.
There is a labels macro package listed at
http://www.troff.org/macros.html
Maybe you could add to that and contribute.
> On Thu, Aug 10, 2006 at 10:05:27AM -0400, M Bianchi wrote:
> > On Tue, A
On Tue, Aug 08, 2006 at 12:20:25PM -0600, Clarke Echols wrote:
> I haven't done labels, but I wrote a package to print business cards
> on pre-perforated business-card stock.
> :
On the basis that 0x01 example is worth 1K words,
here is a test sheet for Avery 5163 2 x 4 inch Mailing Labels
On Wed, Jul 12, 2006 at 02:52:02PM +0200, Joerg van den Hoff wrote:
> :
> and while I'm writing anyway: does anybody know how to handle the
> following situation:
>
> source:
>
> Miller et al.
> .[
> miller01
> .]
> did it wrong and John Doe, too.
> .[
> Doe02
> .]
>
> result:
> =
On Tue, Jul 04, 2006 at 04:25:32PM +0200, Werner LEMBERG wrote:
> Here's the administrator's answer.
> :
> From: Sylvain Beucler <[EMAIL PROTECTED]>
> To: Werner LEMBERG <[EMAIL PROTECTED]>
> Cc: savannah-hackers@gnu.org
> Subject: Re: [Savannah-help-public] Fw: [Groff] Spam
>
> Well, Mailma
On Tue, Jul 04, 2006 at 12:02:02PM +0100, Ted Harding wrote:
> On 04-Jul-06 Gabriel Diaz wrote:
> > Hello,
> >
> > I wonder what kind tricks you use to make big tables that goes beyond
> > the paper defined boundaries fit on the paper.
> >
> > How you mangae to fit them? Just changin the point si
On Fri, Jun 16, 2006 at 10:49:05AM -0400, Larry Kollar wrote:
> Werner LEMBERG wrote:
>
> >> What started that was my early experiences with unix where I went
> >> to the permuted index and looked for "rename a file". I was not
> >> plesed when the only thing I could find is the rename(2) system
It was great to read the interview with Werner (our Fearless Leader?).
What an interesting story! It is good to "meet" you, Werner.
Now all we need is a Groff Anthem to be sung at the next International Groff
Confernece ;)
--
Mike Bianchi
Foveal Systems
973 822-2085 call to arrange Fax
On Sun, Apr 16, 2006 at 01:39:59AM +1000, Miklos Somogyi wrote:
> Hello all,
>
> I try to use a diversion to determine the height of a block of text, so
> that I can paint something underneath this block in PostScript.
> The following simplified example works nicely if no-fill is turned on.
>
> H
On Sat, Mar 11, 2006 at 07:58:04AM +0300, Michail Vidiassov wrote:
> And the real question behind the poll is what version of the Adobe metrics
> to use - PostScript 2 or PostScript 3.
>
> If a considerable part of the grops output is handled by hardware,
> then we have to be conservative and use
On Sat, Mar 11, 2006 at 08:12:30PM +0100, Werner LEMBERG wrote:
> > An approach is to do a groff release where the PS 3 fonts are there,
> > but not used by default, with a notice that in time (say in one
> > year) the default will change. Then in the next major release have
> > the PS 2 fonts the
On Sat, Mar 11, 2006 at 05:41:55PM +0300, Michail Vidiassov wrote:
> On Sat, 11 Mar 2006, M Bianchi wrote:
>
> >> And the real question behind the poll is what version of the Adobe metrics
> >> to use - PostScript 2 or PostScript 3.
> >>
> > does the def
> Do you print groff PS output for any purposes but test?
I use groff for all my documentation (since I know the MM macros in my spine).
> But, on the other hand, may be you are printing more pages created
> with grops then the rest of humanity.
The PostScript output is what I send t
On Tue, Jan 31, 2006 at 08:37:32PM +0100, Werner LEMBERG wrote:
>
> > Has there been any movement on the groff wiki? Yet more interesting
> > snippets and tips have been posted recently - it would be nice to
> > preserve them somewhere accessible!
>
> Unfortunately, the great enthusiasm a few we
On Tue, Jan 31, 2006 at 07:38:54AM +0100, Werner LEMBERG wrote:
> > Is anyone aware of a means by which floating point arithmetic and
> > formating can be computed either within groff or in a preprocessor
> > (ala eqn, tbl, etc.)?
>
> Not that I know of. Why do you need it?
I use groff -mm for
> > Is anyone aware of a means by which floating point arithmetic
> > and formating can be computed either within groff or in a
> > preprocessor (ala eqn, tbl, etc.)?
Several people have contributed ideas that point to possible approaches.
I won't have time to think about them for a couple of days
Is anyone aware of a means by which floating point arithmetic and formating can
be computed either within groff or in a preprocessor (ala eqn, tbl, etc.)?
--
Mike Bianchi
Foveal Systems
973 822-2085 call to arrange Fax
[EMAIL PROTECTED]
http://www.AutoAuditorium.com
http://www.FovealMou
On Mon, Oct 24, 2005 at 09:26:51PM +0100, Deri James wrote:
> :
> Groff is used
> in the final stage to actually typeset the report, including a barcode on
> each page to control the "finishing" at the printers, ...
Deri,
Are the barcodes generated by troff? (A special font?)
Or are the
On Thu, Oct 20, 2005 at 10:34:05AM -0600, Clarke Echols wrote:
> :
> If any of you have trouble with tendonitis or carpal tunnel
> syndrome, take a look at the Kinesis keyboards. They are
> WONDERFUL!!! It takes about 3 weeks to get used to one, and
> it totally ruins you for "normal" keybo
On Fri, Oct 21, 2005 at 02:02:15AM +1000, Robert Marks wrote:
> I've been using *roff since the days of nroff and
> daisywheel printers, i.e., 1978. Am I alone?
No, Mark. I wrote my first nroff documents at Bell Labs, in 1974 or 1975, on
what were called Programmers' Workbench UNIX systems. The
On Thu, Oct 20, 2005 at 07:52:50AM -0400, M Bianchi wrote:
> Which is the *best* editor?
> The one I know in I know my spine.
Take 2:
Which is the *best* editor?
The one I know in my spine.
--
Mike who cannot proofread his own email B
Which is the *best* editor?
The one I know in I know my spine.
Which is the second best editor?
The one used by most of the folks around me,
because that means they can help me and I can help them and
deep shared knowledge is an exponential function.
On Fri, Sep 30, 2005 at 12:20:40PM +0200, Tadziu Hoffmann wrote:
> > :
> > BTW, I *never* have *any* user writeable directory before the
> > system binary directories, in *my* PATH; but, I guess it would
> > be naive to expect everybody to follow that piece of simple
> > security advice.
>
>
On Thu, Sep 29, 2005 at 10:53:59AM +0100, Keith MARSHALL wrote:
> :
> Not a big deal, I know, but `unsafe' is a rather unfortunate choice
> of name for this `extended functionality' mode of groff's.
The problem is you have to think like a nasty person.
If I can convince you to run groff i
On Wed, Sep 28, 2005 at 10:37:45AM +0800, Lei Ming wrote:
> I encountered a strange problem with page header.
> Following is a small test case. Please process it
> with groff and see the PostScript output.
>
> .\"__
> .de H
> .tl 'X'Y'Z'
> \l'\n(.lu\(rn'
Forgive me, but I'm going to toss by two-bytes into this discussion.
It seems to me that this thread has been largely conducted in the "solution
space", where this and that solution is thrown in and reactions are generated.
It might be better to discuss the wide-character and escape sequence probl
Keith,
On Thu, Jun 16, 2005 at 02:55:24PM +0100, Keith MARSHALL wrote:
> :
> I beg to differ here. While POSIX defines the $( ... ) syntax for
> embedded command invocation, we have to deal with many legacy systems
> which are not POSIX compliant. As you say, Mike, the syntax used in
> pdf
On Thu, Jun 16, 2005 at 08:46:01AM +0200, Werner LEMBERG wrote:
> :
> I think that the offending line is
>
> MATCH="$MATCH`echo --$OPT | $GREP "^$OPTNAME"`"
>
> I suspect that the
>
> "...`..."..."`"
>
> combination causes the problem.
The `command` shell escape has been known to b
On Thu, Mar 31, 2005 at 09:22:23PM -0500, Larry Kollar wrote:
> :
> I seem to remember
> a paper by Brian Kernighan
> that suggested putting each phrase
> on its own line
> :
That's most probably where I got the idea.
Speaking of Brian, the man I want to be when I grow up, he is speak
On Thu, Mar 31, 2005 at 12:23:32AM +0200, Jorgen Grahn wrote:
> On Wed Mar 30 13:09:40 2005, [EMAIL PROTECTED] wrote:
> > Coming from a version control background I happen to love the roff requests
> > because they have a natural tendency to break things up. When people
> > create really long lin
Regarding the animation-using-groff idea presented in
A System for Algorithm Animation Tutorial and User Manual
Computing Science Technical Report No. 132
http://cm.bell-labs.com/cm/cs/cstr/132.ps.gz
The code for the programs mentioned in the paper are available at
49 matches
Mail list logo
