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 115250 - Default charset for Western languages shall be UTF-8
Default charset for Western languages shall be UTF-8
Status: VERIFIED FIXED
Product: gtranslator
Classification: Other
Component: Generally bug'd
HEAD
Other Linux
: Normal normal
: 1.0
Assigned To: Ross Golder
Fatih Demir
Depends on:
Blocks:
 
 
Reported: 2003-06-15 20:40 UTC by Fatih Demir
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Fatih Demir 2003-06-15 20:40:03 UTC 
We should set the default charset of all Western languages to UTF-8 as it's
now so for the GNOME 2.x platform - and offer (like Peeter did write to the
gtranslator-devel list) an "export to [charset/Non-UTF8]" menu entry like
the current one for Exporting/Importing to UTF-8.

Hmm...
Comment 1 Ross Golder 2003-06-16 09:50:16 UTC 
I've already started removing the existing 'import/export from/to
UTF8' code. Everything internal to gtranslator will be UTF-8. The next
step, once that has been proven, is to have it read the header record
first, take the Content-Type 'charset' attribute, and if it's not
UTF8, use g_convert when reading/writing lines to the file. Currently,
I don't think gtranslator deals with non-UTF8 files, so you'll need to
manually iconv them in the meantime.
Comment 2 Fatih Demir 2003-06-16 14:41:16 UTC 
Well, it can deal with them but the display of the chars and messages
is totally wrong then and the usage of gtranslator would be useless :-(

One way would be to convert all your files to UTF-8 before editing
(which is the standard charset for GNOME 2.x po files btw...) until we
can snatch out some more intelligent ways of parsing/reading/writing
other charsets.
Comment 3 Fatih Demir 2003-08-10 17:10:31 UTC 
Ross, any work in the field of charset handling done lately?! This
should be also done before a R 1.0 as it could be a very important point
to have also support for non-UTf8 files.
Comment 4 Fatih Demir 2003-09-05 07:21:26 UTC 
Charset conversion is done already and the UTF-8/non-UTF-8 cases ain't
gonna be a problem any further I guess, so closing this bug.