Description of problem: Under keyboard preferences, second tab (layout ?. agencements in French), all keyboard descriptions in French incorrectly identify all canadian keyboard as English ("Anglais") There is one without latin caracters, but otherwise there is only one Canadian keyboard not adapted for canadian French users. (That one is essentially identical to the U.S. keyboard.) Most use a typical canadian French rearrangement of a few keys from the U.S. keyboard, in addition to accent keys. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Use the fr localisation. (It could be any fr-*) The file in question is /usr/share/locale/fr/LC_MESSAGES/xkeyboard-config.mo 2. Open keyboard preferences 3. select layout tab (2nd tab) 4. select by country, Canada 5. open the scroll list at versions (variantes in French) The only one that is essentially an English-language keyboard has English ("Anglais") twice. (It is essentially identical to U.S. keyboard.) The descriptions in French would all be corrected by removing the leading "Anglais ". Note : This error may exist in other locales.
You didn't say what tool you used, xkeyboard-config itself doesn't provide any GUI's. (Also if you're sure it's a problem with the .mo file, you better file a bug upstream, since we didn't manually edit the content of the .mo files).
Source RPM: xkeyboard-config-2.2.1-1.mga1.src.rpm => ,-2.2.1-1.mga1.src.rpm
Using search tools and a hex editor, I traced the offending text to the file indicated. (/usr/share/locale/fr/LC_MESSAGES/xkeyboard-config.mo). This file belongs to the package x11-data-xkbdata, which is generated by the srcrpm package indicated. (I restored the package name above.) Sorry about not specifying that I was running on Gnome -- although the info below makes it a moot point. Thanks for the suggestion about upstream -- I found : 1) 2.2 was released 2011 April (it has the errors) - It contains many rewrites of keyboard descriptions. (Correctly designating one canadian keyboard as obsolete.) 2) 2.3 was released 2011 May - a bugfix version fixing these descriptions and other errors. 2.3 is already in cauldron -- updated by tv. It would be a good candidate for an update to mga1.
Source RPM: ,-2.2.1-1.mga1.src.rpm => xkeyboard-config-2.2.1-1.mga1.src.rpm
CC: (none) => andre999mga
(In reply to comment #2) > Using search tools and a hex editor, I traced the offending text to the file > indicated. > (/usr/share/locale/fr/LC_MESSAGES/xkeyboard-config.mo). > > This file belongs to the package x11-data-xkbdata, which is generated by the > srcrpm package indicated. > (I restored the package name above.) > > Sorry about not specifying that I was running on Gnome -- although the info > below makes it a moot point. > > Thanks for the suggestion about upstream -- I found : > 1) 2.2 was released 2011 April (it has the errors) > - It contains many rewrites of keyboard descriptions. > (Correctly designating one canadian keyboard as obsolete.) > > 2) 2.3 was released 2011 May > - a bugfix version fixing these descriptions and other errors. > > 2.3 is already in cauldron -- updated by tv. > It would be a good candidate for an update to mga1. Thierry, yes, no ? :)
CC: (none) => thierry.vignaud
(In reply to comment #3) > (In reply to comment #2) > > > > 2.3 is already in cauldron -- updated by tv. > > It would be a good candidate for an update to mga1. > Thierry, yes, no ? :) Anyway, still no maintainer for xkeyboard-config
CC: (none) => marja11
I'm looking into it
CC: (none) => oliver.bgrAssignee: bugsquad => oliver.bgr
As I see it, 2.3 is not a pure bugfix release, but also adds further keyboards and removes some things. So I'd rather prefer to patch xkeyboard-config-2.2.1 in Mga1 for this special bug.
3-monthly ping
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
(reporter -- note that my email as reporter is incorrect, due to a bug which truncates email adresses containing ".") It was already fixed in Cauldron when I reported the bug, so it is fixed for Mga2. Installing the mga2 version in mga1 solves the problem for the French descriptions. (Although generally that is not a recommended practice.)
Whiteboard: (none) => MGA1 only
thx for putting that on the whiteboard, good idea :) I removed the space, so it is MGA1only now, to make searching for bugs with this string on the whitheboard easier
Whiteboard: MGA1 only => MGA1only
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
The mga2 version fixes the bug and works on mga1
Status: NEW => RESOLVEDResolution: (none) => FIXED