Red Hat Bugzilla – Bug 472919
Listing languages for release notes
Last modified: 2008-12-16 14:45:55 EST
Description of problem:
The release notes available in various languages are listed in abbrevation instead of full language names here,
For a novice, no techy user, these abbrevations is very very confusing and barely helpful.
I'd suggest a list like,
US English (en_US)
Version-Release number of selected component (if applicable):
Fedora 10 Release notes
Steps to Reproduce:
1. Click on the link http://docs.fedoraproject.org/release-notes/f10/
Abbrevations that don't make any sense to non techy users.
Language name and it's abbrevation
I used to spell these language names out in their native language and, if I recall correctly, it was criticized as a bug because the names would generate erroneous "missing character" boxes for people without the required fonts installed. It would be wrong, in my opinion, to either spell these out in English only, or to spell out only those names we can represent with a Latin character set.
*** Bug 473323 has been marked as a duplicate of this bug. ***
So ... is there a good solution? What about:
Native_lang (English_ver, short_code)
Español (Spanish, es)
Of course, now the hard part is getting the native language characters and spelling all worked out. Perhaps we can have a single wiki page that has all of this for reference and future use?
Pulling the list from gdm should be simple enough. By default on the desktop, we install fonts for most character sets.
Sorry, I've been crawling through the gdm files and cannot find one that specifically has the language name in the native character set and language. The closest I've seen is 'Login Window' in all languages:
Oh, fun. It generates them on the fly now. In F-8 and earlier, it was in gui/gdmlanguages.c
Can we just reference a wiki page with the information?
Sorry, I haven't been updating the bug with the status. I got most of this done, it is live here:
I was leaving this open while discussing (via f-websites-l) how to present that information better. But the essence of this bug is finished, what's there is good enough, time to move on. :)