A Gedit annoyance and even worth situation in Ubuntu
Ma Xiaojun
damage3025 at gmail.com
Sun Apr 14 16:35:10 UTC 2013
Hi,
As you may know, evil Microsoft Windows save plain text using a local,
non-Unicode, encoding by default. For example, Simplified Chinese
version of Windows uses CP936 or GBK encoding by default.
Sometimes plain text files created that way getting around in
Internet. GNOME users may download such files. Open such files in
Gedit, results in garbage display as Gedit has no automatic encoding
detection feature as Kate. Compare the following two screenshots
should give you an idea.
Gedit: http://img.vim-cn.com/c7/d8ef36f00f9294b968b00848872eb1c83b9eda
Kate: http://img.vim-cn.com/8c/7e5c24d961298391b23975d8e8c989faa42ec4
Gedit only allows a (configurable) static list possible encodings.
When open a file, Gedit try the encoding one by one until it finds a
valid one. But valid for computer doesn't mean valid for human, text
encoded in many encodings are valid in ISO-8859-15 encoding.
This problem is mitigated, through the translation of the default
static list. An example of such translation can be seen in GNOME's git
repo.
https://git.gnome.org/browse/gedit/tree/po/zh_CN.po#n424
I also verified that the translation is included in Gedit 3.6.1's tarball.
However, the Gedit in Ubuntu 12.10, which claim itself as 3.6.1,
doesn't have the expected behavior after such translation take
effects. It seems that Gedit in Ubuntu doesn't keep up with upstream
translation.
More information about the Ubuntu-GNOME
mailing list