[Top][All Lists]

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

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

From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #53842] Handle m-files with UTF-16 and UTF-32 character encoding
Date: Tue, 5 Mar 2019 00:21:19 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.109 Safari/537.36

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:


  Message sent via Savannah

reply via email to

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