[Octave-bug-tracker] [bug #57304] Error message for non-UTF-8 encoded *.m files

[Markus Mützel]

Update of bug #57304 (project octave):

                  Status:          Ready For Test => Fixed                  
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

Thanks for testing.
Closing as fixed.

If you want to use files that are encoded in another encoding (not UTF-8) and
expect non-ASCII characters in strings to work (e.g. as labels on axes), you
would have to set the mfile encoding first - either via the drop down list in
the editor preferences or with a command, e.g.:

__mfile_encoding__ ("iso-8859-1");
clear functions  # If the file was parsed before, this is necessary to parse
it again with the new encoding.


That should already be working with Octave 5.1.

If you don't set the correct encoding, the results might be unexpected. That
could be gibberish or errors when the strings are used.

The difference for Octave 6 will be that the default encoding will match the
system locale independent of the platform (i.e. not only on Windows). This is
"UTF-8" for most modern Linux and OS X anyway. Hence, there shouldn't be any
noticeable changes for the huge majority of Linux or Mac users.

Files only containing ASCII characters aren't affected in any case.

    _______________________________________________________

Reply to this item at:

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

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