Sometimes, l10n bugs are not always l10n bugs!
January 5th, 2007
On wednesday, I reopened the bug 206439 when Aman pointed the following to us…
Okay, this seemed a translation bug. Down to the debugging & I found that Comment 12 was where the bug coming from. Giving it a round of translation was the first thing on my mind… which was not very well received by the code. The code was parsing the translation & separating it for day names on the basis of length… not a good thing.
Ankit then suggested to keep the day names in separate strings, so they can be separately be translated. This would bring sanity to both the code & the translations. But however, this induced another problem… Since the day names were being used as “MTWTFSS” (initials!), marking Saturday’s S and Sunday’s S separately was another issue. Gettext has a rule to mark duplicate strings as a single translatable string. Carlos at #i18n (irc.gnome.org) suggested to use contexts in strings which are to be marked for translation… which led to this patch.
…now Evo rests in peace… atleast for two days of this weekend - during which I plan to hack m17n-db for bug 198325 to move my Mapper from a pre-pre-alpha+buggy version to a alpha version atleast!
It looks like this in its current state…
Posted in Fedora-i18n, Red Hat | Comments (2)
January 5th, 2007 at 3:54 pm
Is this a keymap for Hindu or other language?
January 8th, 2007 at 2:01 am
Pete, this is a keymap loader – something which will aid user to understand that what keymappings are there in the keymap
Have a look at RH bug 198325 for more info. BTW, yes, its the Hindi inscript keymap