[Octave-bug-tracker] [bug #57235] Document that startup file .octaverc is always read in the system encoding

[Markus Mützel]

Update of bug #57235 (project octave):

              Item Group:                    None => Documentation          
        Operating System:       Microsoft Windows => Any                    
                 Summary: Startup file .octaverc is always read in the system
encoding => Document that startup file .octaverc is always read in the system
encoding

    _______________________________________________________

Follow-up Comment #13:

If I recall correctly, when this bug was created, Octave ignored the system's
locale charset on non-Windows platforms. That has been fixed in the meantime.

One drawback might be that is is not possible (at least not without breaking a
lot of other programs) to set a UTF-8 locale on Windows. But that is not
Octave's fault and I'm not sure if it is worth trying to implement a
workaround for that shortcoming.

It's probably good enough to document somewhere that the startup files are
interpreted (initially) in the locale charset. That is until a user manually
changes the .m file encoding and triggers re-parsing the .m files (see comment
#4) or the GUI sets the .m file encoding from the saved GUI options.

    _______________________________________________________

Reply to this item at:

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

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