GNOME Bugzilla – Bug 348173
charging status message is nonsense
Last modified: 2008-02-25 15:49:36 UTC
Incorrect translation Application: gnome-power-manager Incorrect text: Charging status message is a sequence of words withou understandable meaning in Czech: "Baterie laptopu 14 minut dokud nedobito (85%)" Should be: Not sure. Probably "Zbývá 14 minut do plného nabití baterií laptopu (" "nyní nabito" or "zbývá nabít" " 85%)".
Thanks for the report. The problem here is that the string is not a single string, but it is concatenated from "Laptop battery", "%i minute", and "until charged". This makes the translation little bit tricky. The problem will probably occur in other combinations too. I will look deeper into it but I am afraid that changing the original string and the way it is generated will be necessary.
Then it is a I18N support programming bug and should be fixed in a program code. Translating sentence in parts and expecting, that all languages have English syntax, is a bad practice. For more see: http://www.gnu.org/software/gettext/manual/html_chapter/gettext_3.html#SEC15
It seems, that another message is affected by the same problem: "Baterie laptopu 2 hodiny, 15 minut zbývající (68%)"
Filled a bug asking for providing whole sentences.
so can this be closed as fixed now that bug 350415 has been fixed?
Překládám gnome-power-manager, podívám se na to.
cs_CZ: Hm, v SVN je prelozeno 100% ale me se zda, ze chyba pretrvava, opravoval si to? en_US: Hm, there's 100% of czech translation done in SVN but I think this "bug" is still present, did you fix that?
Neopravoval, překlad jsem posílal někdy před dvěma týdny, kdy jsem o této chybě ještě nevěděl.
Created attachment 105807 [details] [review] patched czech translation of gpm Tak jsem to upravil, posílám patch. Opravena tato chyba + další 4 řetězce (změna rodu z mužského na ženský (jedná se o TU kapacitu).
Pavel's patch committed to SVN (cf. <http://svn.gnome.org/viewvc/gnome-power-manager?view=revision&revision=2686>), thanks! Can the bug be closed now?
Yes.
That was a clear and plain answer, so finally closing the bug.