[Octave-bug-tracker] [bug #44186] print command gives incorrect postscript file

[Dan Sebald]

Follow-up Comment #32, bug #44186 (project octave):

Yes binary open with write() could be the issue.  Let's look at what that
"garbage" data is.  I extracted that hunk of 16 bytes, then read it into
Octave.  Here is what that 16 bytes of data is:


octave:210> reshape(data, 4, 4)'
ans =

     5   162   117   128
    10    35     1   144
     0     0     0   128
    10    35     1   135


Thinking that write() might be displaying 4 characters as 32-bit float, or 8
characters as 16-bit unsinged, I tried reading in the data with all
combinations of float/int/32-bit/16-bit/big-endian/little-endian.  Nothing
seems to make sense.  There is some repetition, for sure.

    _______________________________________________________

Reply to this item at:

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

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