[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues

[Markus Mützel]

Follow-up Comment #23, bug #51203 (project octave):

Andrey, the behavior that you are describing is due to the fact that Excel
needs the text encoded in UTF-8. If you save your file in UTF-8 and do not
mangle with the strings, Excel is happy.
However as you wrote, that does not match Octave's nor Matlab's default
encoding (and you might hit other bugs like bug #51210). 
As of Octave version 4.2, there is no Octave function to manually convert
between arbitrary encodings. Octave 4.4 will contain "native2unicode" and
"unicode2native" which could be used for this. Unfortunately, there is no way
I can think of to solve your issues at the moment (other than manually writing
a function that converts strings between your local encoding "Windows-1251"
and UTF-8).

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/