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 529318 - wrong autodetect windows1251 or koi8r encodings
wrong autodetect windows1251 or koi8r encodings
Status: RESOLVED DUPLICATE of bug 407659
Product: gedit
Classification: Applications
Component: general
2.20.x
Other All
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-22 03:15 UTC by Alexander Sashnov
Modified: 2008-04-25 20:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Alexander Sashnov 2008-04-22 03:15:48 UTC 
Please describe the problem:
Text in windows-1251 opens by double click as in koi8r encoding.

Steps to reproduce:
1. get samples in koi8r and windows-1251 encoding: http://sashnov.fanstvo.com/myfiles/test_readme.zip
2. /apps/gedit-2/preferences/encodings/auto_detected  value: list: UTF-8, CURRENT, KOI8R, WINDOWS-1251, ISO-8859-5
3. double-click to readme_koi.txt - encoding is ok
4. double-click to readme_cp1251.txt - encoding is broken.
5. exchange KOI8R and WINDOWS-1251 in gconf-editor
6. now readme_cp1251.txt ok, readme_koi.txt broken.

Actual results:
Now it is impossible to configure gedit for correct detect both koi8r and windows-1251 encodings.

Expected results:


Does this happen every time?


Other information:
May be use enca? It detect both encodings fine.
Comment 1 Pavel Šefránek 2008-04-25 20:56:49 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 407659 ***