|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #53842] Handle m-files with arbitrary character encoding |
Date: | Wed, 9 May 2018 21:27:19 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Follow-up Comment #6, bug #53842 (project octave): This works for me on Debian with an m-file encoded in iso8859-1 or latin1. This does not work for me on Debian with an m-file encoded in utf-16. Should that be possible with this change so far? Also, I think functions that take a string argument setting usually return the previous value, not the new value. So for example >> enc = __mfile_encoding__ () enc = utf-8 >> enc = __mfile_encoding__ ('utf-16') enc = utf-16 both of these return values should be 'utf-8'. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53842> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |