[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49685] Change default codepage of text editor

From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #49685] Change default codepage of text editor to UTF-8 on Windows
Date: Tue, 5 Mar 2019 00:11:34 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Safari/537.36

Follow-up Comment #3, bug #49685 (project octave):

Here's an alternative, if more complicated, idea that could support both use

How about adding support for an explicit encoding indicator stored in a
".encoding" file in source code directories? For source files under dirs with
an explicit encoding, that encoding would always be used for those files,
regardless of what the Text Editor default encoding is. Then leave the Text
Editor default encoding as System on Windows. (This would affect both the Text
Editor and Octave's M-code interprerter.)

That way Windows Octave and Windows Matlab projects without explicit encodings
would be compatible (as long as they're used on machines with the same system
locale). And Octave-only projects that needed cross-OS or cross-locale
portability could be given .encoding files (and use UTF-8).

Octave's core files and Octave Forge packages would all get UTF-8 .encoding
files so they're portable.

See my big long post at

It's a bummer that this approach requires explicit action on the part of the
user to achieve portability. But I think this might be necessary if you want
both cross-OS/locale and with-Matlab compatibility.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]