Bug 102880 - desktop-create-kmenu doesn't handle @MODIFIER locale syntax
Summary: desktop-create-kmenu doesn't handle @MODIFIER locale syntax
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: desktop-file-utils
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-22 09:35 UTC by Dave Shield
Modified: 2007-04-18 16:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-10-04 05:28:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Dave Shield 2003-08-22 09:35:39 UTC
Description of problem:  The 'desktop-create-kmenu' tool does not
   understand the full range of locale syntax, as described in
   http://www.freedesktop.org/standards/desktop-entry-spec/0.9.4-onehtml/
   In particular, an entry of the form
              key[lang@modifer]=value
   is rejected with an error, and the corresponding entry does not appear
   in the menu structure.


Version-Release number of selected component (if applicable):  3.1-13


How reproducible: Very


Steps to Reproduce:
1. cp /usr/share/application/konsole.desktop /usr/share/application/TEST.desktop
2. insert line "Name[en@Latn]=Terminal"
3. desktop-create-kmenu 2>&1| grep TEST
    
Actual results:
    Warning: failed to load /usr/share/applications/TEST.desktop:
        Error in section Desktop Entry at line 15:
        Invalid characters in locale name

Expected results:
    No error, and an extra Terminal entry in the menu structure

Additional info:
    desktop-create-menu also appears to choke on a space in this locale
section which appears in the examples in the above specification (though
isn't described explicitly).

Comment 1 Than Ngo 2003-08-28 13:47:10 UTC
it should be in desktop-file-utils. i assign it to correct component

Comment 2 Havoc Pennington 2003-10-04 05:28:36 UTC
I believe Jonathan fixed this.


Note You need to log in before you can comment on or make changes to this bug.