[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [help-texinfo] Consecutive spaces in node titles?

From: Dumas Patrice
Subject: Re: [help-texinfo] Consecutive spaces in node titles?
Date: Sat, 10 Mar 2012 12:37:47 +0100
User-agent: Mutt/1.5.20 (2009-12-10)

On Thu, Mar 08, 2012 at 04:02:53PM -0800, Karl Berry wrote:
>     * should spaces in menu entries not be transformed in one space,
>       although it is what is setup in the `HTML Cross References' spec?
> No, why should it be different in @menu?

Because the rendering is different in Info, as spaces are kept in menu 
but not in @node lines.  Though I agree that it is better to normalize
nodes in menu the same as on @node line, even if spaces are not rendered
the same.

> In @w, no, it should be one space.


> In @verb, I'm not sure.  I expect the TeX output is two spaces, although
> I haven't tried it.

I have tried, but TeX has trouble with this construct.  This is weird
because I was persuaded that TeX had been fixed to accept @verb in @node
and @anchor.  I'll report some issues on bug-texinfo.

>     * shoud @ @ follow the rule on normal spaces, and therefore be 
>       transformed in one space?
> Here the user has explicitly given the space command twice.  I think the
> result should be two spaces, as you say it is now.  And I think the
> output should be that way in texinfo.tex, though I haven't tried.

It is also that way in texinfo.tex.  However there is a problem with the 
cross reference, like
l.19: Undefined cross reference `a.@ @ b-snt'. and in the resulting
pdf one get 
  See undefined [a. b], page undefined

>     The error for `a.@ @ b' looks wrong.  
> I think it's ok.  The menu entry should be written the same way:
> * a.@ @ b::
> Does that work (no warning)?

It works without warning and I agree with you that it is better as it is 

>     c.texi:6: warning: Node expansion `c. d' in menu differs from normal node 
> expansion `c.  d'
>     c.texi:7: warning: Node expansion `e. f' in menu differs from normal node 
> expansion `e.  f'
> I think those warnings are fine too.  People should fix their input
> files, and it is trivial to do.

I tend to disagree on that one, because that means that one cannot have
a different spacing on menu entry and @node line which I think should be
ok.  It is not a big deal either, and I could try to have this warning
removed when the 2 expansions only differ in the spaces, as Info rightly
do not care about the number of spaces.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]