[Octave-bug-tracker] [bug #65546] m-files (scripts) created with 6.4.0 and 8.3.0 lead to encoding error when opening in 9.1.0

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?65546>

                 Summary: m-files (scripts) created with 6.4.0 and 8.3.0 lead
to encoding error when opening in 9.1.0
                   Group: GNU Octave
               Submitter: None
               Submitted: Mon 01 Apr 2024 04:36:16 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: Matthias Schagginger
        Originator Email: matthias.schagginger@vol.at
             Open/Closed: Open
                 Release: 9.1.0
         Discussion Lock: Any
        Operating System: Microsoft Windows
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 01 Apr 2024 04:36:16 PM UTC By: Anonymous
This is about Octave 9.1.0 64-Bit GUI (German) that runs on Windows 10 64-Bit.
Several script files created originally with v6.4.0 or v8.3.0 can not be
opened in the script editor of 9.1.0 -> the OPEN FILE procedure is aborted
with error dialog (UI) "Die Datei <filenameandpath> kann mit der
Zeichenkodierung SYSTEM (CP1252):Illegal byte sequence nicht geöffnet werden"
(sometimes complaining about UTF-8 as mentioned encoding) - Stands for "File
<filenameandpath> can not be opened with coding SYSTEM....". The editor window
tab is then labled "unbekannt" ("unknown"), no content visibla at all and
(empty) first line is highlighted in yellow. (no crash).

I get different coding errors on different files, but all of them have been
created with the German GUI version of Octaves script editors of previous
versions.

I did neither find an incompatibility warning in the release notes nor
something similiar. 9.1.0 releasenotes even say "Text encoding for non-UTF-8
generally made more robust. File editor now lists available encodings".  

I can not find any way to manipulate the files in an external editor to make
them accepted by Octave again (after Reading article
https://lists.gnu.org/archive/html/octave-maintainers/2019-11/msg00017.html; I
tried to remove all ö, ü, ä, µ but even without german umlauts, it does
not work).

And many other files work.... I upload an example "field.m"

 






    _______________________________________________________
File Attachments:


-------------------------------------------------------
Name: field.m  Size: 4KiB
<https://file.savannah.gnu.org/file/field.m?file_id=55913>

    AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-3a3eac0100c1af30944362b400ee562149bc6d7a.tar.gz

    _______________________________________________________

Reply to this item at:

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

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