[Top][All Lists]

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

Re: Standalone Info reader cannot read Info files with CR-LF EOLs

From: Eli Zaretskii
Subject: Re: Standalone Info reader cannot read Info files with CR-LF EOLs
Date: Fri, 26 Dec 2014 18:45:37 +0200

> Date: Thu, 25 Dec 2014 18:05:25 +0000
> From: Gavin Smith <address@hidden>
> Cc: Texinfo <address@hidden>
> On Thu, Dec 25, 2014 at 3:51 PM, Eli Zaretskii <address@hidden> wrote:
> > Today I discovered that the Info reader built from the current trunk
> > cannot display any Info file that was produced natively on Windows (as
> > opposed to Info files that come from distribution tarballs, which were
> > produced on Unix).  The reader says it cannot find the Top node in any
> > such Info file.
> I've commited a change that seemed to fix the problem on a small test
> file I made.

Thanks, it mostly did work for me too, although I did only limited
testing with --strict-node-location.  I say "mostly" because I did
find a few glitches:

 . Info still cannot find the Top node in a split manual (a manual
   produced with --no-split does work).

 . A cross-reference whose target node crosses a newline cannot be
   followed.  The example I have is in the Emacs Lisp manual, node
   "Lisp Data Types".  There's a cross-reference there to "Editing
   Types" which has a newline between the two words.  When I try
   following it, Info shows me this:

      File: *manpages*,  Node: Editing
       Types,  Up: (dir)

      No manual entry for Editing.
      No manual entry for Types.

 . The file's encoding is not recognized when the file has CR-LF EOLs

I looked through the sources, and saw a few additional places where \r
before \n might need to be handled (some of them might be the reason
for the above-mentioned problems):

  'avoid_see_see', where it skips whitespace
  'scan_reference_label', where it turns off underlining at EOL
  'get_file_character_encoding', in the call to 'search_forward'

There might be more places, I'm not sure.

> I'll comment more in coming days.

Thanks, I hope we will be able to discuss the broader picture then.
As things stand, I don't see how fixing Info to skip/ignore CR will
solve the fundamental issue of incompatibility between the Emacs and
the stand-alone Info readers wrt byte offsets in tag tables.

reply via email to

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