Bug 354731

Summary: Error in Norwegian translation
Product: [Fedora] Fedora Localization Reporter: Ingvar Hagelund <ingvar>
Component: Other languageAssignee: Dimitris Glezos <dimitris>
Status: CLOSED NEXTRELEASE QA Contact: A S Alam <aalam>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: mshao, trans
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-26 14:15:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ingvar Hagelund 2007-10-26 19:44:50 UTC
Description of problem:
In the screen where one selects installation profile and software repositories,
there is two typos in the Norwegian translation, and the text could be clearer.

Version-Release number of selected component (if applicable):
Today's boot.iso, probably 11.3.0.45-1

How reproducible:
Every time

Steps to Reproduce:
1. Boot the installer. Select Norwegian language.
2. Walk the installation onto the installation profile and software repo screen
3. Watch the error on that screen
  
Actual results:
Two typos and unclear language

"Vennligst velg hvile ekstra lagere du vil bruke for å installere programmer fra"

Expected results:
No typos and easier language, for example:

"Vennligst velg hvilke ekstra lagre du vil installere programmer fra"

Additional info:
None

Comment 1 Espen Stefansen 2007-10-29 00:12:17 UTC
I've fixed this in CVS now. But I'm not sure if it makes it into F8. It might be
to late.



If you like to help out with the Norwegian translation, let me know. We (I)
could always need more help. :)

Comment 2 Dimitris Glezos 2007-10-29 06:30:51 UTC
Thanks Espen! If this is fixed/tested in CVS, can you please go ahead and close
the bug?

Comment 3 Dimitris Glezos 2008-01-26 14:15:05 UTC
Haven't heard any update, so I assume this was fixed.

Closing bug report.