[Octave-bug-tracker] [bug #57341] iso-8859-1 encoding triggers error in get_first_help_sentence.m

[Juan Pablo Carbajal]

Follow-up Comment #8, bug #57341 (project octave):

Indeed it is heuristics, details are here

https://linux.die.net/man/1/file

Then I guess your solution was correct. It also doesn't sound reasonable to me
to assume unknown encoding means iso-8859-1

However, if this fix was present when I was working with the iso-8859-1
encoded file:

1. I wouldn't have got an error

2. The docstring will not be readable

So in my situation it seems that the error is better than the patch (maybe a
more clear error message), because I could then go an identify the files with
the funny encoding, and get the right docstrings. 
This patch would have silently avoided the error but produced the wrong
docstrings. The latter is undesirable.

How does, e.g. gedit, handles this encoding issue? Both files are correctly
shown in gedit when I open them. Are they also re-encodig?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57341>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/