[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Broken UTF-8 in KDE desktop files (fwd)
From:       Bernhard Rosenkraenzer <bero () redhat ! de>
Date:       2001-08-02 10:36:49
[Download RAW message or body]

Can anyone with a clue about i18n take a look at this one?
I'd rather not just remove all characters I can't read. ;)

---------- Forwarded message ----------
Date: 01 Aug 2001 18:38:49 -0400
From: Owen Taylor <otaylor@redhat.com>
To: bero@redhat.com
Subject: Broken UTF-8 in KDE desktop files


Some of the KDE .desktop files have invalid UTF-8 in them. Running

 for i in `find . -type f` ; do
   iconv -f UTF-8 -t UTF-16 $i > /dev/null || echo $i
 done

I found the following:

 System/hanterm.desktop [ko]
 System/kpm.desktop [cs]
 Settings/Network/kcmktalkd.desktop [es/pt/pt_BR/cs - SwallowTitle]
 Development/kdevelop.desktop [de/fr]
 Games/Arcade/ksmiletris.desktop [cs]
 Games/TacticStrategy/konquest.desktop [cs]

Any files with invalid UTF-8 in them will not be translated for
any language in the GNOME menus.

Basically, there are two encodings for desktop files:

 UTF-8: Entire files is UTF-8
 Legacy-Mixed: Each line is encoded according to the language tag

GNOME uses the second, KDE is supposed to (and mostly does) use
the first.

The way we are auto-detecting between them is checking if the
entire file is valid UTF-8 or not; KDE files with junk in them will
not be correctly detected.

System/hanterm.desktop, and Development/kdevelop.desktop actually
don't cause problems for GNOME since they are "proper" Legacy-Mixed,
but probably don't work for KDE.

Regards,
                                        Owen

(Note: according to the desktop file standard on freedesktop.org all
desktop files are actually supposed to include an Encoding: line, but
very few or none do currently, and I don't either the GNOME or
KDE parsers pays any attention.)


Chances of this message being spam: 0

[prev in list] [next in list] [prev in thread] [next in thread]