[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53842] Handle m-files with arbitrary characte
|
From: |
Markus Mützel |
|
Subject: |
[Octave-bug-tracker] [bug #53842] Handle m-files with arbitrary character encoding |
|
Date: |
Wed, 27 Jun 2018 06:25:54 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 |
Follow-up Comment #14, bug #53842 (project octave):
@Andrew: As a first step, being able to read UTF-16 (or at least UCS-2) and
UTF-32 encoded files at all would be an improvement. We could worry later
about some heuristics to detect which flavour of UTF is actually used.
To be honest, I personally rarely stumbled upon UTF-16 encoded files myself
apart from some Windows system files (and never knowingly upon UTF-32 encoded
files).
But if you want to start working on that, I could try and give some feedback.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53842>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/