[Octave-bug-tracker] [bug #49348] Treat multi-byte characters as one character for char array

[HJW]

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

> I guess volunteers tend to work on the features that interest them.  If you
want to bump the priority, would you like to work on this feature or perhaps
pay someone to work on it?

Fair point. My problem is that I don't have enough passion for this to go and
learn C(++). With my Matlab background, I try to keep all my code compatible,
but I think that is where my prowess ends.

I'm afraid my financial means are restricted to the buymeacoffee-level. As I
understand it, rewriting char to be 16bit exceeds that by quite a lot.


> It *is* possible to use UTF-8 characters in Octave.
I was not aware this would work: fprintf('%s\n',uint8([226 140 154])); 
(although on my Windows machine that prints the emoji twice). I stand
corrected, I should have said 'chars with values above 255'. I will look into
the uint8 work-around for my use cases, thank you for the suggestion.
 
> What do you mean by "text reader"?
Out of what I described in bug#51707 grew my FileExchange submission 68780:
readfile() - a general purpose text file reader.

> Which ui elements don't work correctly with UTF-8 characters?
I haven't noticed something missing, hence the distinction between files and
UI elements.

    _______________________________________________________

Reply to this item at:

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

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