Re: generate_html breaks documentation encoding

[Julien Bect]

Le 17/01/2015 09:16, Oliver Heimlich a écrit :
> I debugged into the __makeinfo__ function and found the error: The 
> temporary file that is parsed by the system (cmd) should definitely 
> carry a @documentencoding utf-8 line at the beginning.
>
> I am going to post a patch in the bug tracker...

I think there several issues there (at least two).


Issue #1: which encoding is supposed to be used in the texinfo 
documentation of help functions ?

__makeinfo__.m just adds a minimal header (\input texinfo) and footer 
(@bye), letting makeinfo decide.

In other words, currently, Octave doesn't enforce any specific encoding.

My opinion: if you use any "non-standard" character (say, anything 
outside the range 0x20-0x7E), you should insert a @documentencoding 
statement in your texinfo documentation to be safe.

If I understand correctly, you intend to enforce "@documentencoding 
utf-8" for all m-files. I don't know about that, but certainly other 
people on this list will have an opinion. The discussion will probably 
continue on the bug tracker if you propose a patch. An option would be 
to add "@documentencoding utf-8" only if another @documentencoding 
statement is not already present.


Issue #2: generate_package_html() does not honor the "charset=utf-8" in 
the output of makeinfo

I think this is a bug: generate_package_html() should honor whichever 
encoding comes out of makeinfo.

I will fix this in the generate_html package.


@++
Julien