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

[Andrey Aleshin Igorevich]

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

Thank you. Is I correct try to use a patch? Please, see a attached screen.

I found in Internet next instructions:
#! /bin/sh
#
# To apply this patch, cd to the top level Octave source directory and
# run this file through /bin/sh.  It will first remove any files that
# have been deleted from the source distribution since the last
# release and then update the sources with patch(1)...

Is same actions need in Windows?
I use: bin\sh.exe bug51203_xls_unicode.patch
I added "#" in line 7.

Is need to run via Windows Octave-editor? I'm sorry for this simple question.

(file #40912)
    _______________________________________________________

Additional Item Attachment:

File name: is I corr use a patch.jpg      Size:294 KB


    _______________________________________________________

Reply to this item at:

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

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