After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619112 - internal-viewer by default display incorrect code pages
internal-viewer by default display incorrect code pages
Status: RESOLVED FIXED
Product: gnome-commander
Classification: Other
Component: internal-viewer
1.2.x
Other Linux
: Normal normal
: 1.6
Assigned To: Assaf Gordon
Assaf Gordon
Depends on:
Blocks:
 
 
Reported: 2010-05-19 18:02 UTC by Andrey Gankov
Modified: 2017-05-28 14:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andrey Gankov 2010-05-19 18:02:28 UTC 
If i open file with UTF-8 charset, internal-viewer display incorrect charset.
However, in menu text->charset-> by default selected UTF-8.
If i select UTF-8 again, file display correct.

p.s. sorry for my english
Comment 1 Uwe Scholz 2014-04-09 20:12:45 UTC 
Thank you for taking the time for this bug report. The internal viewer had ASCII as the default codepage, independent of what is selected in the menu.

I changed this behavior: Now UTF8 is the default, which will go into v1.4.2. The problem described above should be solved by this change.

Unfortunately, if another codepage has been stored as the default in ~/.gnome2/gnome-commander, lets say by "charset=ASCII", the radio button in the Encoding menu will still show that UTF8 is the selected codepage, which is not true in this case.

This happens because nowhere in the code the radiobutton is set accordingly. This should be fixed later and might be done in src/intviewer/viewer-window.cc. Therefore I'm leaving this bug open as a reminder.
Comment 2 Uwe Scholz 2017-05-28 14:00:27 UTC 
This bug is now fixed and will go into the next bugfix release of Gnome Commander.