bugGNU Octave - Bugs: bug #55689, Wrong display of non-ASCII...

 
 

bug #55689: Wrong display of non-ASCII characters (e.g. é, ö) with legacy console

Submitted by:  Charles Praplan <charprap>
Submitted on:  Sun 10 Feb 2019 10:39:15 AM UTC  
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  None Assigned to:  None
Originator Name:  Charles Praplan Open/Closed:  Open
Release:  dev Operating System:  Microsoft Windows

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Tue 18 Feb 2020 08:28:59 AM UTC, comment #11: 

Thanks for reporting back.

Re-titling accordingly. But I don't know if it is possible to fix this without changing the console widget completely which is probably out of scope of this bug.

Markus Mützel <mmuetzel>
Project Member
Tue 18 Feb 2020 08:20:07 AM UTC, comment #10: 

YES! Thank you for the tip!

I had the legacy console activated. Deselecting it solves the issue.

If I remember well, I activated the legacy console because of a scrolling problem in Octave, that I solved with the following workaround:

   https://savannah.gnu.org/bugs/?func=detailitem&item_id=52496#comment13

  

But I see now that this is fixed and that the workaround is no more needed.

Charles Praplan <charprap>
Mon 17 Feb 2020 04:49:56 PM UTC, comment #9: 

This is only blind guessing: Does it change if you use the Legacy console?
Open a Windows command window. In the properties, select the "Options" tab and tick/untick the last checkbox (legacy console). Close the command window. Re-start Octave.
See also e.g.: https://www.tenforums.com/tutorials/94146-enable-disable-legacy-console-mode-all-consoles-windows-10-a.html

Markus Mützel <mmuetzel>
Project Member
Mon 17 Feb 2020 04:32:44 PM UTC, comment #8: 

The settings for _mfile_encoding_ are the same for both computer (system) and match the settings in the Editor preferences.

Changing _mfile_encoding_ to Windows-1252 does not help.

Concerning the user independent GUI settings, I made following trials:
- I copied the settings from the other computer
- I copied the settings from the admin account
- I deleted the settings

No effect!

Charles Praplan <charprap>
Sat 15 Feb 2020 10:05:29 AM UTC, comment #7: 

The problem with not being able to enter non-ASCII characters at the command line in Windows is bug #47571.

Do the settings for "__mfile_encoding__" differ on the two computers you tested on? Does it work if you correctly match the encoding of the test file (i.e. Windows-1252)?
Also check in the Editor preferences which text encoding you selected for reading and saving files. (It should match "__mfile_encoding__".)

AFAIK, the GUI settings are stored for each user. This could explain the different behavior and the different interface language if you run as user or administrator.

Markus Mützel <mmuetzel>
Project Member
Sat 15 Feb 2020 09:50:30 AM UTC, comment #6: 

Point of the situation with Octave 5.2.0

I tested the demo script (file #46226) on two computers running Windows 10.

On the first one the display is correct.

On the second one the display is NOT CORRECT in the console.
However, I saw by accident, that when I run Octave as administrator,
the display is correct again.

Note that typing a special character in the console still does not work.

 

I compared the language settings and code page. I tried many different settings.
But, I couldn't manage to get a correct display for a standard user.

Which setting is used by octave that can be different when running as administrator.

I also observed this:

In admin the buttons are in english. for example :  Ok - Cancel
In sdt user the buttons are in mixed language    :  Ok - Annuler

Strange, isn't it?

Charles Praplan <charprap>
Tue 12 Feb 2019 06:32:18 PM UTC, comment #5: 

That last part is due to gnu readline not properly supporting utf-8 on Windows, see bug #47571.

Markus Mützel <mmuetzel>
Project Member
Tue 12 Feb 2019 04:15:02 PM UTC, comment #4: 

Today I tried on a window 7 PC. The situation is the same except that the display in the command window is:
Résistances

I also noticed that when selecting   disp('Résistances') in the editor and pressing F9, the following is displayed in the command windows:

>> disp('R\303\251sistances');


Maybe this can help debugging.

Charles Praplan <charprap>
Mon 11 Feb 2019 10:16:24 PM UTC, comment #3: 

Yes, well. The heading is misleading. Just noting that the original submission, points 4) and 5) cover the command line as well.
https://savannah.gnu.org/bugs/?42036#comment0
Five years ago, I didn't have an idea how protracted and widely ramified this UTF-8 topic would be. I really would like to see UTF-8 working in Octave 5

Armin Müller <arm_in>
Mon 11 Feb 2019 04:02:32 PM UTC, comment #2: 

Bug #42036 was about files and directories with Unicode characters.
This is about the Windows console and UTF-8.

Similar, but not a duplicate.

Markus Mützel <mmuetzel>
Project Member
Mon 11 Feb 2019 11:56:27 AM UTC, comment #1: 

Reminds me to #42036

Armin Müller <arm_in>
Sun 10 Feb 2019 10:39:15 AM UTC, original submission:  

Characters  as é, ö ... are not displayed correctly in the console.

Fore example Résistances are displayed as R��sistances !

Test file is appended : Octave_ANSI_files_test_case.m

For more information, have a look at

   https://savannah.gnu.org/bugs/index.php?53646

which was the original post and has been partially solved.

Charles Praplan <charprap>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #46226:  Octave_ANSI_files_test_case.m added by charprap (136B - application/octet-stream)

 

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 arm_in (Posted a comment)
  • -email is unavailable- added by charprap (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-02-18 mmuetzel Release5.1.0 => dev
        SummaryWrong display in console of characters as é, ö => Wrong display of non-ASCII characters (e.g. é, ö) with legacy console
    2019-02-26 mtmiller Release5.0.91 => 5.1.0
    2019-02-10 charprap Attached File- => Added Octave_ANSI_files_test_case.m, #46226

    Back to the top


    Powered by Savane 3.5