[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]

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

Is my English so bad? I'm sorry. I tell only in forums and shops. I try to
speak better. I'm very sorry again.
--
I understood about Linux and utf8. Thanks. I will remember it feature. I will
try to solve an encoding problem later.
('com'-interface in windows correct do output in xls file, but don't do in
xlsx. In Linux com interface don't work as I think, and oct don't output in
xls.)
--
I don't touch this xlsx file during running script. I understand it.

I solve this task by using 'oct'-interface and repeating output again and
again while file is not exist or counter t<=3.
--
I try to use xlsopen->oct2xls->xlsclose, but result is same as xlswrite:

When work folder with script(which contain oct2xls or xlswrite) is empty. The
script work ideal.
When I create 9 folders (for example:)

system('mkdir 1 2 3 4 5 6 7 8 9')

a result is not guaranteed. After 1 times, after 2-5 times, my script don't
output xlsx-file, displays warnings or errors and create strange xml-folders
and files.

If I continue and I press F5 to run script. It will be work and do output to
xlsx.
--
Thank you very much for answer. You can say me any words.

    _______________________________________________________

Reply to this item at:

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

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