> > xxx yyy
> > xxx yyy
> >
> > xxx yyy
> > xxx yyy
>
> Sorry, I'm not seeing a problem here. As long as both tables have
> left-aligned problems, what's the issue?
The latter version looks worse IMHO; at least there are high chances
that it doesn't reflect the author's orig
> I'm wondering, though, if it might make more sense to use:
>
> .ds eL \&.\|.\|.\&
This would be the right definition for a string.
> Whether the .ds is worth the trouble depends on how many times you
> use the ellipsis in a file versus the need to remember another
> string definition. B
Zvezdan Petkovic wrote:
.ds eL \|.\|.\|.\&
sentence goes on\*(eL
where the first \| provides that extra spacing between the last word and
the first dot. Yet, the spacing is smaller than a full space which is a
little unseemly.
I'm not sure from Werner's explanation whether h
Werner LEMBERG <[EMAIL PROTECTED]>:
> > But trailing spaces should be safe with 'l' justification (and
> > leading spaces with 'r') except in the odd circumstance that
> > the spaces happen to extend past the tab point due to some
> > wacky point-size change. I think.
>
> Well, it can make the
> But trailing spaces should be safe with 'l' justification (and
> leading spaces with 'r') except in the odd circumstance that
> the spaces happen to extend past the tab point due to some
> wacky point-size change. I think.
Well, it can make the results uglier. For example, this
.TS
ta
> This implies the full space before the ellipsis, right?
>
> .ds eL .\|.\|.
> 1, 2, \*(eL
>
> instead of what I thought looks less asymmetric
>
> .ds eL \|.\|.\|.
> 1, 2,\*(eL
Yep.
> I might be quite wrong on this, of course. Well, we never stop
> learning. I guess you
On Sat, Feb 03, 2007 at 12:13:40AM +0100, Werner LEMBERG wrote:
> > > Doesn't it look typographically even better as `\|.\|.\|.\&'.
> > > I think this is what eqn sequence `. . .' gets translated into.
> >
> > In general, this depends on language and style guide.
>
> Indeed. Within groff, James
On Sat, Feb 03, 2007 at 12:01:45AM +0100, Gunnar Ritter wrote:
> Zvezdan Petkovic <[EMAIL PROTECTED]> wrote:
>
> > On Fri, Feb 02, 2007 at 07:44:10PM +0100, Werner LEMBERG wrote:
> > > . The proper way to write an ellipsis is `.\|.\|.\&', optionally
> > > starting with `\&'. Please don't om
Werner LEMBERG <[EMAIL PROTECTED]>:
>
> > You are right about the long names. I clean forgot about this, for
> > reasons I'll explain in a moment. I can undo that step easily
> > enough if you want.
>
> Well, in case it's really *easy* I would like to have the old forms
> back. However, this i
Werner LEMBERG <[EMAIL PROTECTED]>:
> Just look at this example:
>
> .TS
> tab (@);
> r r.
> [EMAIL PROTECTED]
> xxx @yyy
> .TE
>
> this gives
>
> xxx yyy
> xxx yyy
That's clear enough. The trailing spaces interact badly with 'r'
justification. Similarly, leading spac
> > Doesn't it look typographically even better as `\|.\|.\|.\&'.
> > I think this is what eqn sequence `. . .' gets translated into.
>
> In general, this depends on language and style guide.
Indeed. Within groff, James always has used .\|.\|. for situations
like
1, 2, ...
(and this is basic
> > (b) it works with old troff also (which has a limit
> > of 9 macro arguments)
> >
> Actually the limit was 6 macro arguments for man macros
> in the 1980s.
Old troff had a general limit of 9 macro arguments. The
limit of 6 arguments you're referring to came about because
the particul
Zvezdan Petkovic <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 02, 2007 at 07:44:10PM +0100, Werner LEMBERG wrote:
> > . The proper way to write an ellipsis is `.\|.\|.\&', optionally
> > starting with `\&'. Please don't omit the `\|' -- it looks quite
> > ugly in PostScript output if the do
> Not exactly, it should be
>
> '\" t
Thanks! I'll fix up the groff man pages accordingly.
Werner
> You are right about the long names. I clean forgot about this, for
> reasons I'll explain in a moment. I can undo that step easily
> enough if you want.
Well, in case it's really *easy* I would like to have the old forms
back. However, this isn't an urgent issue.
[about virtualization]
I'l
> OK. Do you think it's worth adding an ellipsis definition to
> an-ext.tmac?
I don't object. What do others think?
> > . Don't use real tabs in tables; use the `tab' keyword to
> > substitute them with, say, `@'.
>
> Can do. Is there any technical reason for this, other than the
> "fut
On Fri, Feb 02, 2007 at 07:44:10PM +0100, Werner LEMBERG wrote:
> . The proper way to write an ellipsis is `.\|.\|.\&', optionally
> starting with `\&'. Please don't omit the `\|' -- it looks quite
> ugly in PostScript output if the dots don't have enough horizontal
> separation.
Do
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> . If you use a table within a man page, the first line should be
>
> .\" t
Not exactly, it should be
'\" t
At least this is the convention on SunOS, and, following that,
on SVR4 derivatives. (The first reference I can find is in a
SunO
Werner LEMBERG <[EMAIL PROTECTED]>:
> Some other observations:
>
> . The proper way to write an ellipsis is `.\|.\|.\&', optionally
> starting with `\&'. Please don't omit the `\|' -- it looks quite
> ugly in PostScript output if the dots don't have enough horizontal
> separation.
Werner LEMBERG <[EMAIL PROTECTED]>:
> I see that you are going to replace \[..] with \(.. -- do we really
> need that? (a) It makes the code more difficult to read. (b) I
> thought that we've agreed on staying with long macros/variables/glyph
> names, and that we currently only `normalize' the ma
Werner LEMBERG wrote:
. It's better to say
.B "foo bar baz"
instead of
.B foo bar baz
Reasons:
(a) it's processed faster (no issue today, but...)
(b) it works with old troff also (which has a limit of
9 macro arguments)
Actually the limit was
> The above sounds like it should be added to a README or TESTING file
> in the tmac directory, if for no other reason than that the
> usefulness of -ww is not elsewhere documented that I have seen. I
> think I'll make that happen.
Thanks.
> I have been applying the eyeball test to .SY/.OP/.YS
> I have been applying the eyeball test to .SY/.OP/.YS conversions of
> chem.man, grog.man, and the roff2.man pages, and it looks like I
> have managed not to screw the pooch this time. [...]
Some other observations:
. The proper way to write an ellipsis is `.\|.\|.\&', optionally
startin
Werner LEMBERG <[EMAIL PROTECTED]>:
> > The previous stuff on my agenda is done, [...]
>
> Please add a ChangeLog entry! I insist on having entries for
> everything which isn't trivial (e.g., fixing typos in comments or
> documentation).
A catchup entry is done, and will be in my next commit.
> The previous stuff on my agenda is done, [...]
Please add a ChangeLog entry! I insist on having entries for
everything which isn't trivial (e.g., fixing typos in comments or
documentation).
> When I go back to trying to make the man pages portable, I'm
> wondering what the appropriate test pr
The previous stuff on my agenda is done, but I'm not going to commit the
MathML patch yet; nobody has had time to review it.
When I go back to trying to make the man pages portable, I'm wondering what
the appropriate test protocol is. Is an eyeball check that it looks right
under both man in a t
26 matches
Mail list logo
