Bug 113797

Summary: SL10_LOC - Linux - pt-BR - Beta3 050826: LinuxRC: Add Driver: untranslated text
Product: [openSUSE] SUSE Linux 10.1 Reporter: John-Carl Kullmann <johnk>
Component: InstallationAssignee: Karl Eichwalder <ke>
Status: VERIFIED WONTFIX QA Contact: Klaus Kämpf <kkaempf>
Severity: Enhancement    
Priority: P5 - None CC: davidbo, emmetw, sineadk
Version: unspecifiedKeywords: L10N, Portuguese
Target Milestone: ---   
Hardware: x86   
OS: SUSE Other   
Whiteboard:
Found By: Localization Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description John-Carl Kullmann 2005-08-29 10:54:46 UTC
Detailed description: Add Driver: untranslated text
Configuration: Suse 10
Build: Beta3 050826
Steps to reproduce:
1. Insert the SUSE Linux Professional 10.0 CD1 CD-ROM. Reboot the machine.
2. Select the F2 option and select Brazilian Portuguese.
3. Hit Enter.
4. After the initial processes have completed The YaST2 'Installation and 
System Administration Program' initializes. Click 'Cancel'
5. A main menu appears. This is the Linuxrc module. Select 'Modulos Kernel 
(Drivers de Hardware)' (Kernel Modules)
6. Select ' Adicionar Atualizacao de Driver' (Add Driver?)

Expected result: all text should be localised.
Actual result: the "Searching for Storage Devices" message that briefly appears 
is untranslated.
Comment 1 mary hearne 2005-08-30 15:22:31 UTC
We cannot find this string in our resources.  Seems to be  LINUX RC 
reassigning to snwint@suse.de
Comment 2 Steffen Winterfeldt 2005-09-02 09:48:52 UTC
just look away :) 
Comment 3 Shane Wims 2006-02-02 10:55:50 UTC
Kerry, can you take a look at this bug please?
Comment 4 Kerry OConnor 2006-02-07 12:13:35 UTC
Hi Karl, I can't locate the source of this string. Possibly a kernel string. It would need to be resourced for translation. 
Comment 5 Steffen Winterfeldt 2006-02-07 15:06:35 UTC
Sorry, I will not make this string translatable. It's just not worth the
trouble.
Comment 6 Dmitri Sarin 2007-03-05 16:42:04 UTC
*** Bug 251188 has been marked as a duplicate of this bug. ***