bugGNU Octave - Bugs: bug #58860, [octave forge] (tsa) Use UTF-8...


bug #58860: [octave forge] (tsa) Use UTF-8 encoding

Submitter:  Rafael Laboissière <rlaboiss>
Submitted:  Fri 31 Jul 2020 07:35:57 AM UTC
Category:  Octave Forge Package Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  None Assigned to:  None
Originator Name:  Open/Closed:  * Open
Release:  * other Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup

Jump to the original submission

Fri 18 Sep 2020 11:05:39 AM UTC, comment #6: 

D'oh! That's been too close in front of my face. :-D

Markus Mützel <mmuetzel>
Group Member
Fri 18 Sep 2020 10:52:35 AM UTC, comment #5: 

> The report of which I was thinking is probably bug #49685

Ah, yes: that's totally relevant to exactly this patch. It's also the same one I linked in my first comment. ;)

Andrew Janke <apjanke>
Fri 18 Sep 2020 10:48:58 AM UTC, comment #4: 

The report of which I was thinking is probably bug #49685 (which admittedly could have a better title).

Markus Mützel <mmuetzel>
Group Member
Fri 18 Sep 2020 09:10:15 AM UTC, comment #3: 

Variables of type "char" are expected to be UTF-8 encoded inside Octave. Missing conversions at the interfaces are bugs.
This seems to be one of those bugs.

You are right: Currently, the default .m file encoding is the "native" encoding configured for the system Octave is running on. This is probably a good choice imho.

However, there is currently no way of setting a file encoding on a per-directory basis (like proposed in the thread to which you linked). I agree that it would make sense to make that possible.

I believe there was a bug report about this. But I can't find it at the moment.
If there is none, it would probably be best to open one and discuss the general issue there.

Markus Mützel <mmuetzel>
Group Member
Fri 18 Sep 2020 08:38:44 AM UTC, comment #2: 

Here's the big ol' thread on the mailing list about this I was thinking of: https://lists.gnu.org/archive/html/octave-maintainers/2019-03/msg00019.html

Andrew Janke <apjanke>
Fri 18 Sep 2020 08:35:15 AM UTC, comment #1: 

Has Octave actually settled on using UTF-8 for its source code file encodings? There's been some discussion of it - see https://savannah.gnu.org/bugs/?49685 - but I don't know if it was settled, and my impression is that Octave source code files still use "native" encoding by default, which is the legacy system code page on Windows.

Andrew Janke <apjanke>
Fri 31 Jul 2020 07:35:57 AM UTC, original submission:  

File inst/sinvest1.m uses the IO-8859-1 encoding of the character "²". It should be converted to UTF-8.

The patch attached to this bug report fixes the issue.

Rafael Laboissière <rlaboiss>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files
file #49589:  utf8-encoding.patch added by rlaboiss (992B - text/x-patch)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by apjanke (Posted a comment)
  • -email is unavailable- added by rlaboiss (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only project members can vote.


    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-07-31 rlaboiss Attached File- Added utf8-encoding.patch, #49589

    Back to the top

    Powered by Savane 3.12