[Octave-bug-tracker] [bug #55974] Octave hangs on plotting text object with invalid UTF-8 byte sequence

[Pantxo Diribarne]

Follow-up Comment #5, bug #55974 (project octave):

@ies: I like the proposed fix for the infinite loop (and FWIW Matlab also uses
a replacement character in this situation). Can you produce a proper patch? 

>> But I must admit at this point that I am not sure why we ended up calling
it like this.

We want to use UTF-8 as Octave's internal string encoding, hence the
assumption that the string that is passed to the text renderer is UTF-8
encoded. 
Octave can make sure a string typed in a terminal, or read from a file
(provided the file is loaded with the proper encoding) is translated to UTF-8
before being passed to internal functions. But it can't prevent you from
loading files with wrong encodings or building foreign non UTF-8 strings, so
the replacement character looks like the best approach.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via Savannah
  https://savannah.gnu.org/