[Octave-bug-tracker] [bug #54170] java.lang.String.toCharArray result incorrect conversion to char matrix

[Andrew Janke]

Follow-up Comment #10, bug #54170 (project octave):

Here's a concrete example that might help discussion.

Consider the case of `cs = {'foo', 'föö', 'foobar'}'`, and how it looks in
2-D char form.

>From Matlab R2018a:


>> cs = {'foo', 'föö', 'foobar'}'
cs =
  3×1 cell array
    {'foo'   }
    {'föö'   }
    {'foobar'}
>> char(cs)
ans =
  3×6 char array
    'foo   '
    'föö   '
    'foobar'


In Matlab, this can be round-tripped through java.lang.String and produce the
same results.


>> cs2 = cs; for i = 1:numel(cs); cs2{i} =
java.lang.String(cs{i}).toCharArray'; end
>> char(cs2)
ans =
  3×6 char array
    'foo   '
    'föö   '
    'foobar'
>> isequal(cs, cs2)
ans =
  logical
   1


If the individual char[] results of that operation were transcoded to UTF-8
before being returned as Octave values, you might end up with different values
for cs/cs2, or not be able to produce that 2-D array.

    _______________________________________________________

Reply to this item at:

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

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