octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues
Date: Tue, 20 Jun 2017 10:51:30 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0

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

Those files aren't really strange. That is what the more recent MS Office
files are: zip-files with a certain structure.

It would be easier to follow if you post the errors and warning directly as
text.

@Philip: There indeed seem to be two instances of "return" in
__OCT_spsh_open__ (and at least in __COM_spsh_open__, too) where the last
output argument "lastintf" is not yet set. I will leave that error to you
because I am not sure what that argument is used for and what should be
returned in those cases.

There seems to already be a manual pause after unpack in line 63:

      unpack (templ, tmpdir, "unzip");
      ## Allow unpack dust to settle down (lazy write file I/O)
      pause (0.2);


It might be that this pause is too short on Andrey's system and the file I/O
needs more time to flush. Maybe waiting some time whilst checking for the last
file in the return value of unpack to be available might be necessary? Any
better ideas?

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]