Bug 84727 - Broken translations for german gdm
Broken translations for german gdm
Status: CLOSED UPSTREAM
Product: Red Hat Linux
Classification: Retired
Component: gdm (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Paul Cormier
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-20 16:45 EST by Bernd Bartmann
Modified: 2013-01-10 16:39 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-04-02 21:42:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bernd Bartmann 2003-02-20 16:45:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
After doing a fresh install of Phoebe3 with german as default language I notice
that some gdm menu entries are not correct. This is probably related to wrong
keyboard shortcut definitions:
Sprache [L]
Herunterfahren [d]


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


How reproducible:
Always

Steps to Reproduce:
1. Install Phoebe3 with german as default language
2. Look at the menu bar of gdm for broken translations/keyboard shortcuts
3.
    

Additional info:
Comment 1 Bernd Groh 2003-02-20 19:37:41 EST
> After doing a fresh install of Phoebe3 with german as default language I
> notice that some gdm menu entries are not correct. This is probably
> related to wrong keyboard shortcut definitions:
> Sprache [L]
> Herunterfahren [d]

gdm is, so I believe, part of gnome. Does anyone know who currently maintains
the translations for this package?

Thank you,
Bernd
Comment 2 Bernd Bartmann 2003-04-02 11:33:36 EST
The bug is still present in Red Hat 9.
Comment 3 Bernd Bartmann 2003-04-03 14:51:31 EST
Do you mean it is fixed in Rawhide or is an errata coming up?

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