[Top][All Lists]

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

[Octave-bug-tracker] [bug #56805] Using unrecognized char in text result

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 14:13:56 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Follow-up Comment #8, bug #56805 (project octave):

@Rik: You are right. I didn't read the sources before commenting.

The two attached patches fix the orientation of the output vector of
native2unicode and remove the duplicate input checks from the internal

AKAIK, Matlab uses only the BMP of UTF-16 (i.e. UCS-2). So there is probably
no example where a single character in any encoding would lead to a two
element result of native2unicode in Matlab.
We decided we want to use UTF-8 instead. If I remember correctly the reasoning
was that most third party libraries are using 8bit chars as their strings.
Thus, if our strings are of 8bit chars as well we would need to convert them
at less interfaces.

This still leaves the original issue.

(file #47443, file #47444)

Additional Item Attachment:

File name: bug56805_native2unicode_row_vector.patch Size:0 KB

File name: bug56805_native2unicode_input_checks.patch Size:1 KB


Reply to this item at:


  Message sent via Savannah

reply via email to

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