[Octave-bug-tracker] [bug #64331] unicode2native demands codepage input on Windows

[Markus Mützel]

Follow-up Comment #6, bug #64331 (project octave):

Btw, using `unicode2native` without specifying the output encoding might give
"unexpected" results even if the input is ASCII-only. If the system locale is,
e.g., IBM-037 (EBCDIC), you'd get the following (even without the second
argument):

>> unicode2native('abc', 'ibm-037')
ans =

  129  130  131


Whereas on an ASCII-compatible locale, you'd expect:

>> unicode2native('abc', 'latin1')
ans =

  97  98  99




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64331>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/