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 79717 - Localized category names in gnome-file-types-properties.
Localized category names in gnome-file-types-properties.
Status: RESOLVED DUPLICATE of bug 79389
Product: gnome-control-center
Classification: Core
Component: [obsolete] File types and programs
1.99
Other other
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks: 75718
 
 
Reported: 2002-04-24 07:43 UTC by Xavier Cho
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Xavier Cho 2002-04-24 07:43:08 UTC 
Using localized name as a file type category, causes duplicate entry in the
category list.

To reproduce the problem, set the system locale to non-english one(like
"ko_KR.eucKR") and follow the steps below :

(1) Launch gnome-file-types-properties.
(2) Select "Add file type(or its localized name)" button.
(3) Enter the localized name of an already existing category name shown in
the file types list to the category field.
(4) Fill out the other necessary fields and close the window.

You will see the duplicated category name created instead of the new entry
being registered below the pre-existing one.

Could you please fix this problem?

Thanks

=================================================
Korean GNOME Community - http://gnome.or.kr
Comment 1 kz 2002-04-24 12:00:37 UTC 
the real problem is that, ko.po has some translation for default category:
    like Video, or so. (mime-type-info.c:743)
the Video, for example, does present as translated string, while saved
literal 'Video'.
so if I type in native string of meaning Video, I cannot point the
Video category correctly.
it's just a new category.
Comment 2 Kjartan Maraas 2002-05-01 10:00:28 UTC 

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