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

List:       kde-i18n-doc
Subject:    Re: Translation of application.desktop files
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2014-10-08 20:21:55
Message-ID: 1858537.H5clYfGgQU () xps
[Download RAW message or body]

El Dimecres, 8 d'octubre de 2014, a les 14:53:09, Burkhard Lück va escriure:
> Am Mittwoch, 8. Oktober 2014, 11:55:23 schrieb Aleix Pol:
> > Hi,
> > I've received this bug report [1]. It's about how some languages have
> > translated the ;separed values in the category with coma instead of
> > semi-colon.
> 
> This is about translations of msgids with msgctxt = X-KDE-Keywords|Keywords
> ?
> 
> Searching for msgids in l10n-kde4/templates/messages/ shows:
> X-KDE-Keywords + comma separator = 92x
> X-KDE-Keywords + semicolon separator = 1x
> Keywords + comma separator = 1x
> Keywords + semicolon separator = 7x
> 
> muon-discover.desktop and muon-installer.desktop use semicolon as separator
> and have a trailing semicolon for "Keywords" entries
> muon.desktop has comma as separator and missing trailing semicolon for
> "X-KDE- Keywords" entries
> 
> desktop-file-validate apparently does check only missing for missing
> trailing semicolon in app desktop files with "Keywords", not for the kind
> of separator
> 
> desktop-entry-spec-1.1.html says:
> "multiple values should be separated by a semicolon"
> and
> "KDE also used the Keywords key before it was standardized, using commas
> instead of semi-colons as separators. At the time of standardization, the
> field had been prefixed with a X-KDE prefix, but the Trinity fork still
> used the non- prefixed variant."
> 
> > How can we do to fix this?
> > Also maybe it's a problem in other places, maybe we can have a check or
> > something, for desktop files...
> 
> A check is obviously needed, but what is the correct separator and trailing
> char to be used?

Right i see, this is a bit confusing, maybe it's , for X-KDE-Keywords and ; 
for Keywords?

Aleix can you read the code that parses that and confirm?

Cheers,
  Albert
[prev in list] [next in list] [prev in thread] [next in thread]