octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #54310] Synchronize file encoding used in edit


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #54310] Synchronize file encoding used in editor with the one used for executing m files
Date: Sat, 28 Jul 2018 06:11:55 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0

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

Thanks Torsten!
Changing the setting with __mfile_encoding__ also successfully changes the
editor setting in the preferences for me on Ubuntu Linux. I'll try with a
Windows cross-build later.
Changing the encoding setting in the preferences dialog doesn't change the
__mfile_encoding__ for me. But I guess that isn't implemented yet.

I didn't realize that iconv and Qt used different names to identify the
encodings. That might complicate things as there is no way of querying a list
of all valid encodings from iconv (as of now).
However, iconv seems to be more "forgiving" when it comes to using alternative
character codec identifiers: *__mfile_encoding__ ("cp1252")* seems to work as
does *__mfile_encoding__ ("windows-1252")*. At least on Ubuntu 18.04.
So we might be able to just set whatever Qt uses as an identifier for iconv as
well.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54310>

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




reply via email to

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