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

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

[Octave-bug-tracker] [bug #45597] GUI Editor should use ANSI text encodi


From: Hartmut
Subject: [Octave-bug-tracker] [bug #45597] GUI Editor should use ANSI text encoding under Windows
Date: Mon, 23 Nov 2015 20:05:45 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0

Follow-up Comment #4, bug #45597 (project octave):

Yes, I see the same behavior unter Ubuntu Linux (14.04):
* When I open an ISO8859-1 file with umlauts, those characters are just
omitted with Octave 4.0.1+ (default encoding setting = "system default")
currently.
* When I open an ISO8859-1 file with umlauts, I get funny diamond shaped
question marks instead of the umlauts with Octave 4.0.1+ (explicit encoding
setting to "UTF-8") currently.
* Wen I open the samme ISO8859-1file with umlauts in Octave 4.0.0 release,
then I also get funny diamond shaped question marks instead of the umlauts.

note: I just now realise, have I misunderstood you? Do you maybe suggest to
set the default encoding ONLY for Linux to UTF-8? In this case I would fully
agree :) It's better so see funny diamond shaped question marks (then at least
you know that some encoding error just destroyed your umlauts), instead of
silently dropping several text characters.

...The following text was written when I still thought that you wanted to
change the default encoding to UTF-8 BOTH for Linux and Windows:...

Nevertheless I DO like the current behavior a lot - not the funny (but exotic)
behavior described above, but the fact that:
* Under Linux OS I can open any m file that was created (under Linux) with
Octave 3.8.2 release and Octave 4.0.0 release, and I do see all umlauts
displayed properly.
* Under Windows OS I can open any mm file that was created (under Windows)
with Matlab, with Octave 3.8.2 [with Octave 4.0.0 I am not sure at the moment,
but I could check], and I do see all umlauts displayed properly.

I think the use case that someone save an m file under one operating system,
and then opens the saved m file under a different operating system is quite
rare and exotic. Whereas I think that the use case that someone under Windows
wants to open an m file that was created under Matlab happens (hopefully!)
quite often. 

This is why I do NOT like the idea of setting the default encoding for Ubuntu
AND windows back to UTF8.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/




reply via email to

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