[Top][All Lists]

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

Re: New Issue with makeinfo

From: Patrice Dumas
Subject: Re: New Issue with makeinfo
Date: Mon, 25 Aug 2014 10:17:34 +0200
User-agent: Mutt/1.5.20 (2009-12-10)

On Sat, Aug 23, 2014 at 01:28:14PM +0800, Mahlon Smith ( 马伦 ) wrote:
> Hi again, bug squashers,
> When a '@w{TEXT}' packet extends beyond the 'fill-column' limit, then if
> there is a word break ahead of the packet on that line, then logically, the
> entire packet should wrap to the next line. This was the case in makeinfo
> v:4.13, but not in v:5.1.
> The documentation says that “'@w{TEXT}' outputs TEXT, while prohibiting
> line breaks *within* TEXT.”
> To me, this means that the entire packet should be processed as if it were
> a single word.
> What do you think?

Both could be ok in my opinion, but it is not ok to have something
inconsistent.  I agree that the best would be to process the entire
packet as if it was a single word.  It seems to me that it is also what
TeX does.

> What might give a clue is that there is an inconsistency in parsing a
> '@w{TEXT}' packet at the end of a line, as shown in the example with plain
> text contents. This could indicate that the same parsing sequence is
> happening in more than one place, and that they don't match, OR that a
> search for a word break is (inappropriately) happening within the @w{}.

It seems to me that it happens for the first @w{} in a paragraph.  I'll
have a look.


reply via email to

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