octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #49348] Treat multi-byte characters as one cha


From: HJW
Subject: [Octave-bug-tracker] [bug #49348] Treat multi-byte characters as one character for char array
Date: Wed, 28 Oct 2020 16:17:33 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36

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

Characters beyond 255 are (surprisingly?) common. It isn't just accented
characters, it is also Greek symbols. The vast majority of the internet is
UTF-8, and while most files will not make use of the full gamut, some will.
(especially if you consider emoji, it would be nice if those wouldn't break a
text reader)

When dealing with UI elements you can generally make those with the (La)TeX
controls, but for file interactions you are forced to hack your way there by
writing raw bytes.

I understand this would take a lot of work, but I don't see why this isn't
something that has already happened. There are many more herculean tasks that
have been done, so I don't see why this one seems to be on the backburner.

My fear is that this is causing stagnation: the case has already been open for
so long people have either moved on, or have written their own int16-derived
class.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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