Re: Bug#779885: info: Does not display a info-file from the start, if it contains (some) multibyte characters

[Gavin Smith]

On 6 June 2015 at 08:24, Norbert Preining <address@hidden> wrote:
> We are updating the dir file by looping over all info files and call
>         install-info "$file" "$INFODIR/dir"
>
> I attach the gzipped version of the dir file on my system.

Please have a look at coreutils.info (or coreutils.info-1) and look
for a line starting "INFO-DIR-SECTION" followed by
"START-INFO-DIR-ENTRY", and look up until "END-INFO-DIR-ENTY". There
may be several extents of lines like this. These contain the lines
that should be copied into "dir".

Looking at the dir file you attached, there are the following entries:

* Coreutils: (coreutils).       Core GNU (file, text, shell) utilities.
* coreutils: (coreutils)coreutils invocation.   Multi-call program.

The two labels are "Coreutils" and "coreutils". Info prefers an exact
case match, so it will display "(coreutils)coreutils invocation".

Info is operating as expected here. The problem is with the Info file
- it was a bad idea to add that dir entry.

>>   Display is normal, if the info-files have been transformed to latin-1 (8
>> bit single byte) encoding before they are used.
>>
>>   Using "info coreutils | iconv -f utf-8 -t latin1//TRANSLIT" does only
>> show chapter 2.14.

I don't think that "iconv" in particular is the issue here: piping the
output of info into any program causes it only to output the node it
finds and any other nodes below it in the document structure. Try
"info coreutils | less" and see if you have the same thing.