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 694316 - Syntax errors in the desktop file
Syntax errors in the desktop file
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: general
3.7.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2013-02-20 22:26 UTC by Kalev Lember
Modified: 2013-02-21 21:14 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix syntax errors in desktop file translations (1.34 KB, patch)
2013-02-20 22:27 UTC, Kalev Lember 		none Details | Review

Description Kalev Lember 2013-02-20 22:26:43 UTC 
desktop-file-validate complains:

gnome-system-monitor.desktop: error: value "Monitor;S?steem;Protsess;Protsessor;CPU;M?lu;V?rk;Ajalugu;Kasutus" for locale string list key "Keywords[et]" in group "Desktop Entry" does not have a semicolon (';') as trailing character
gnome-system-monitor.desktop: error: value "Pemantauan;Sistem;Proses;CPU;Memori;Jaringan;Riwayat;Pemakaian;Monitor" for locale string list key "Keywords[id]" in group "Desktop Entry" does not have a semicolon (';') as trailing character
gnome-system-monitor.desktop: error: value "???????????? ???????? ???????? ??????? ?????????? ?????? ???????? ??????????????" for locale string list key "Keywords[km]" in group "Desktop Entry" does not have a semicolon (';') as trailing character

Attaching a patch that fixes the first two, but I've no idea how to fix the km translation.
Comment 1 Kalev Lember 2013-02-20 22:27:53 UTC 
Created attachment 236990 [details] [review]
Fix syntax errors in desktop file translations
Comment 2 Robert Roth 2013-02-21 21:14:29 UTC 
Thanks for the patch, committed.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.