[Octave-bug-tracker] [bug #53842] Handle m-files with UTF-16 and UTF-32 character encoding

[Andrew Janke]

Follow-up Comment #16, bug #53842 (project octave):

>  I personally rarely stumbled upon UTF-16 encoded files myself apart from
some Windows system files (and never knowingly upon UTF-32 encoded files)

Same here. I don't think I've ever seen UTF-16 or UTF-32 source code files in
the wild. I think we should defer UTF-16 and UTF-32 support until the broader
source code encoding issues are sorted out, like: bug #49685, bug #35910, bug
#50409, and bug #55826.



    _______________________________________________________

Reply to this item at:

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

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