Bug 112697 - SL10_LOC-Linux-FR-Beta2 050819 - '&' appearing in front of System/LVM option
Summary: SL10_LOC-Linux-FR-Beta2 050819 - '&' appearing in front of System/LVM option
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: x86 SUSE Other
: P5 - None : Normal
Target Milestone: Beta 4
Assignee: Shane Wims
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords: French, L10N
Depends on:
Blocks:
 
Reported: 2005-08-24 13:07 UTC by Emmet Wildes
Modified: 2005-09-13 10:10 UTC (History)
1 user (show)

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

Attachments
'&' symbol appeaing in front of Heading name. (56.24 KB, image/pjpeg)
2005-08-24 13:09 UTC, Emmet Wildes 		Details
View All 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 Emmet Wildes 2005-08-24 13:07:12 UTC 
'&' appearing in front of System/LVM option

SUSE10
Beta2

Steps:
Click Start/System/YaST to launch YaST Control Center
Click the "System" option in the left navigational panel. 

Expected Result:
All options on right hand side should appear correctly.

Actual Result:
'&' symbol appearing before the 'LVM' option.
Comment 1 Emmet Wildes 2005-08-24 13:09:59 UTC 
Created attachment 47375 [details]
'&' symbol appeaing in front of Heading name.
Comment 2 mary hearne 2005-08-31 14:35:31 UTC 
LCN\trunk\update-desktop-files\xx\entries.6.po

msgid "Name(lvm_config.desktop): LVM"
msgstr "Partitionnement"

Removed & from Partitionnement

Issue should be resolved in BETA5
Comment 3 John-Carl Kullmann 2005-09-13 09:50:28 UTC 
Still a bug in French build RC1 050909.
Comment 4 Kerry OConnor 2005-09-13 10:06:50 UTC 
Desktop files (lvm_config.desktop) need to be updated from
\LCN\trunk\update-desktop-files\fr\entries.6.po as this is fixed in our fileset.
Comment 5 Craig Jeffares 2005-09-13 10:10:24 UTC 
Menu's have been updated for RC 3 so this maybe fixed now