[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a
From: |
Andrey Aleshin Igorevich |
Subject: |
[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues |
Date: |
Tue, 13 Jun 2017 11:15:55 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #22, bug #51203 (project octave):
Good day.
I found next:
Linux & Oct work ideal - plots, xls-es.
If in Windows in Octave to set editor encoding UTF-8 and to write script, It
will be in UTF-8. And it do output in xlsx (...'oct') fine as said Markus
Mützel. Thanks. But this script incompatible with default users.
----
But. If to write script in UTF-8, for example in Notepad++, to convert, to
save in UTF-8 and to open in Windows Octave, then file will be not readable by
me, but it correctly do output in Excel w/o flag "convert_utf". Text is
readable.
But if you to run UTF-8-script in Windows-Matlab, then you can see in Excel
same characters as in Matlab/Octave editor.
I don't can to understand it now. I see, that Matlab to do output this
character, that view.
But Octave to do output character that it load. But it don't display it. That
is: There are a script in UTF-8. Octave with 1251's editor don't may to
display it correctly. But It do output exactly as scriptt saved.
Although, it must to do output that it display. In my opinion.
I'm sorry for my long comments and my write style. I will think further.
(file #40909)
_______________________________________________________
Additional Item Attachment:
File name: scr20170613.jpg Size:148 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?51203>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [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, (continued)
- [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, Aleshin Andrey Igorevich, 2017/06/08
- [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, Aleshin Andrey Igorevich, 2017/06/08
- [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, Markus Mützel, 2017/06/08
- [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, Philip Nienhuis, 2017/06/08
- [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, 2017/06/09
- [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, 2017/06/09
- [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, Philip Nienhuis, 2017/06/09
- [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, 2017/06/09
- [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, Markus Mützel, 2017/06/09
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Philip Nienhuis, 2017/06/11
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues,
Andrey Aleshin Igorevich <=
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Markus Mützel, 2017/06/13
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Andrey Aleshin Igorevich, 2017/06/13
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Markus Mützel, 2017/06/13
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Andrey Aleshin Igorevich, 2017/06/14
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Markus Mützel, 2017/06/14
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Andrey Aleshin Igorevich, 2017/06/14
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Philip Nienhuis, 2017/06/14
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Andrey Aleshin Igorevich, 2017/06/15
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Andrey Aleshin Igorevich, 2017/06/20
- [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues, Andrey Aleshin Igorevich, 2017/06/20