[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output in a corrupted .xlsx. 'oct' output Russian in a non-readable xlsx. 'oct' need to execute twice

[Andrey Aleshin Igorevich]

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

Good morning.

Very thanks, that you are discussing about them. I don't carefully understand
all information, that you wrote to each other with 49222, I've read it, but I
understand a common idea and I will understand it.

Do I understand correctly, that future (and being developed now) Octave 4.4
will contain native2unicode and unicode2native functions?

In Matlab they work non ideal with all characters but work.

If Octave will contain their, I think it will be good. Although how binary
data in unicode write in cell when transfer to xls/xlsx? But it will be good
in any case.

I found 'UTF-8' encoding in Octave. It's one of solutions. Although this code
is not readable by Matlab users. Well.

Thanks very much you both.
It about encoding.
----
How about this no stable output with 'oct', when other files or/and folders
are exist? It's interested by me first. And I think, that this is not small
inaccuracy, but this is a more important bug. Both: xlswrite and
xlsopen-oct2xls-xlsclose don't do a guaranteed output, when another
folders/files are.





(file #40890)
    _______________________________________________________

Additional Item Attachment:

File name: screenshots OctEditorUTF8.7z   Size:115 KB


    _______________________________________________________

Reply to this item at:

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

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