Bug 77087 - Norwegian translation of balsa package information incorrect
Norwegian translation of balsa package information incorrect
Product: Red Hat Linux
Classification: Retired
Component: specspo (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Paul Cormier
Depends On:
  Show dependency treegraph
Reported: 2002-10-31 17:48 EST by Trond Varslot
Modified: 2013-01-10 16:29 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-01 20:57:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Trond Varslot 2002-10-31 17:48:40 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
The description for the package balsa under category for graphical internet
applications is incorrectly translated to Norwegian-bokmel.

English description:
'balsa - An email client for GNOME'
Norwegian description:
'balsa - Et grafisk grensesnitt for RPM, for GNOME'
This roughly translates to:
'balsa - A graphical interface to RPM, for GNOME.', which indicates that you are
installing an application for package management, not an email client.

The Norwegian translation should be:
'balsa - Et epostprogram for GNOME.'

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Choose language Norwegian for a GNOME session
2.Start redhat-config-packages
3.Find package description for balsa under category 'Grafisk Internet' 

Additional info:
Comment 1 Paul Gampe 2003-01-01 20:57:20 EST
Norwegian is not a language we officially support and do not have the resources internally to  
verify the issues raised in this bug.    
We do however accept community translations and would welcome any bug fixes.   
You can request an account to submit translations/bugfixes via the website:  

Note You need to log in before you can comment on or make changes to this bug.