Bug 112627 - SL10_LOC - Linux - DE - Beta2 050819 - YaST Bootloader: Add Section: untranslated text
Summary: SL10_LOC - Linux - DE - Beta2 050819 - YaST Bootloader: Add Section: untransl...
Status: VERIFIED 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: Kerry OConnor
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords: German, L10N
Depends on:
Blocks:
 
Reported: 2005-08-24 08:00 UTC by John-Carl Kullmann
Modified: 2005-09-02 09:30 UTC (History)
2 users (show)

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

Attachments
YaST Bootloader Kernel Section (102.77 KB, image/pjpeg)
2005-08-24 08:03 UTC, John-Carl Kullmann 		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 John-Carl Kullmann 2005-08-24 08:00:31 UTC 
Detailed description: YaST Bootloader: Add Section: untranslated text
Configuration: Suse 10
Build: Beta2 050819
Steps to reproduce:
1. Click Start/System/YaST to launch YaST Control Center
2. Click the "System" option in the left navigational panel.
3. Click the "Bootloader" option in the right-hand panel.
4. Click "Add" in the Section managment tab.
5. Select 'Clone Selected Section' radio button & click 'Next'

Expected result: all text should be localised.
Actual result: some strings and part of the side panel are untranslated.
Comment 1 John-Carl Kullmann 2005-08-24 08:03:42 UTC 
Created attachment 47309 [details]
YaST Bootloader Kernel Section

Attachment: 112627_DE.jpg


Duplicate of Chinese bug 106231
Comment 2 mary hearne 2005-08-24 16:21:09 UTC 
Strings are coming from  from Bootloader.xx.po which is in translation. Should 
be back in for build Beta 4 or 5 so please verify then.
Comment 3 Emmet Wildes 2005-09-02 09:30:50 UTC 
Checked on Beta 4 050901 for German and its now fixed.

Closing issue.