Bug 151509 - translations in appamor yast desktop file are broken
Summary: translations in appamor yast desktop file are broken
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: AppArmor (show other bugs)
Version: Beta 3.5internal
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Dominic W Reynolds
QA Contact: Dominic W Reynolds
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-16 14:59 UTC by Uwe Gansert
Modified: 2006-03-13 08:48 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Gansert 2006-02-16 14:59:16 UTC 
the translations in the desktop file are broken.
The "Name=Novell AppArmor" is correct but all other Name[..} entries are translated wrong to "Security and Users" - maybe a copy and paste bug.
Comment 1 Uwe Gansert 2006-03-02 15:00:15 UTC 
sorry Thorsten
Comment 2 Dominic W Reynolds 2006-03-08 23:02:09 UTC 
Yes this is a problem. Karl I think that we stopped handling the content in the desktop files and that this is done by the localization group. Do you know who I should assign this to?
Comment 3 Karl Eichwalder 2006-03-10 20:31:48 UTC 
If you add the update-desktop-files magic to the .spec file, we can translate it together with all the other .desktop files.
Comment 4 Dominic W Reynolds 2006-03-10 20:57:39 UTC 
We use the macro:

  %suse_update_desktop_file -d ycc_${d%.desktop} ${d%.desktop}

In the yast2-apparmor spec file. Is this the update-desktop-files magic? (it does look mystical :)

Looking at our package we still are including the localized "Name[XX]=I8tn text" tags for the desktop file /usr/share/applications/YaST2/group/apparmor.desktop

I will remove and recheck in for beta8.
Comment 5 Karl Eichwalder 2006-03-10 21:25:19 UTC 
Yes, that's it.  I have to check, why this does not seem to be sufficient.
Comment 6 Dominic W Reynolds 2006-03-13 08:48:32 UTC 
Checked in for beta8. This should eliminate the problem.