|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #56805] Using unrecognized char in text results in infinite warning loop |
Date: | Tue, 3 Sep 2019 12:11:44 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0 |
Follow-up Comment #4, bug #56805 (project octave): @Rik: I was trying with Octave 5.1.0 installed on Windows 10 and the result for "native2unicode(169, 'latin1')" was a column vector. (Hence the transpose operator in comment #2.) You are right. It would be better to use the transpose operator in the code you cited. And the condition in this code is probably what causes the problem. Both isrow and iscolumn are true for a scalar input. The transpose should only be done for "true" column vectors. Maybe we could use something like: if (numel (native_bytes) > 1 && iscolumn (native_bytes)) utf8_str = utf8_str.'; endif or maybe easier: if (! isrow (native_bytes)) utf8_str = utf8_str.'; endif _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?56805> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |