Menu spec: .desktop filename encoding issue

Daniel Veillard veillard at
Wed Jul 20 22:47:53 EEST 2005

On Wed, Jul 20, 2005 at 02:28:07PM -0500, Travis Watkins wrote:
> On 7/20/05, Daniel Veillard <veillard at> wrote:
> >    XML solved that problem the following way:
> >      - the file has an encoding (with UTF-8 and UTF-16 being the
> >        only default encoding, i.e. guessed/assumed if not indicated
> >        in the instance)
> >      - unknown encoding are fatal error the file can't be read
> >      - if the file does not follow that encoding it's a fatal error
> >        the file cannot be read
> >     - never ever depend on a locale for processing
> > 
> > IMHO XML solved the problem for good that way. Making encoding errors
> > fatal also ensured that problems are detected immediately, not on the
> > client in the majority of the cases.
> At the moment PyXDG bombs out when the DesktopFileID isn't valid
> utf-8. Are you saying this should be the way to go? I have a feeling,
> just like XML, you'll have most people choose to either ignore the
> error and go on or try to autofix the error and go on (users will be
> pissed if their menu entries don't show up).

  I'm suggesting to be inflexible when parsing the description file
(thought the localization of the name may just make that irrealistic
with current practice), but as Fred pointed out the problem is somewhere 
else (Unix legacy, sigh ...)


Daniel Veillard      | Red Hat Desktop team
veillard at  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine

More information about the xdg mailing list