[Top][All Lists]

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

Re: [PATCH] ignoring Info extensions

From: Karl Berry
Subject: Re: [PATCH] ignoring Info extensions
Date: Fri, 2 Apr 2004 19:19:39 -0500

    juri> I guess you actually meant *Note[^:*] vs. *Note\s.  Anyway,

Yes, sorry.

    eliz> But if we use *Note[^:*], 

That won't fix all of the cases Juri found:
>       8 *NOTEBOOK,
>       1 *Notes:*
>       1 *Note2:
>       1 *note'

These would still be misidentified as references.  So according to these
findings, it would have to be *Note[^:*Bs2'], and obviously some day
there will be some other character.  Let's fix it for real, right now,
by saying *Note is followed by whitespace.

    we remain compatible to whatever Info files
    are out there that don't have a whitespace after "*Note:", right?

But there aren't any, I feel more sure than ever.  Every Info writer
writes "*Note " for references.  So let's reflect that in the Info readers.
I see no problem here.

    Isn't that better to solve a problem without breaking what previously

As a general rule, I of course agree with you.  As you know, I am a bear
for compatibility, and we have tried our utmost never to break old Info
readers with new Info files.  I think the last time we did was with
@anchor, umpteen years ago.

However, in this particular case, it seems to me that the proposed
change (a) would not break old Info files that would break, and (b) it
fixes the original problem, of references being misidentified, for good
(as well as we can, anyway), whereas the alternative does not.

Therefore, I believe that
  \*[Nn]ote[ \t\n]
is preferable to

Let's do it.  I will change the Info reader.


reply via email to

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