GNOME Bugzilla – Bug 325053
Some typos in the PO file
Last modified: 2005-12-29 19:48:42 UTC
Gnome Schedule bugs 1. Firstly, thankyou for using named variables, which make it possible for translators to re-order variables in the python-format translation string, if necessary. :) 2. It would save translators time if you would use the plurals facility in gettext. For example, the file contains: po:53 reference: ⑤ ../src/crontabEditorHelper.py:223 ../src/gnome-schedule.glade.h:42 Original: ⌘0 Minute: Việt: Phút: po:63 reference: ⑤ ../src/crontabEditorHelper.py:246 ../src/gnome-schedule.glade.h:43 Original: ⌘0 Minutes: Việt: Phút: .po:129 reference: ⑤ ../src/gnome-schedule.glade.h:65 Original: ⌘0 _Hour: Việt: _Giờ : .po:130 reference: ⑤ ../src/gnome-schedule.glade.h:66 Original: ⌘0 _Hours: Việt: _Giờ : My language has no plurals in that sense, so I have to input the same translation twice,. 3. po:34 reference: ⑤ ../src/crontabEditor.py:266 flag: ⑤ python-format Original: ⌘0 This is an invalid record! The problem could be at the %(field)s field. Reason: %(reason)s - at the field + in the field 4. .po:56 auto: ⑤ day reference: ⑤ ../src/crontabEditorHelper.py:230 Original: ⌘0 At an exact day - at a day + on a day also po:60 auto: ⑤ weekday reference: ⑤ ../src/crontabEditorHelper.py:238 Original: ⌘0 At an exact weekday - at a weekday + on a weekday 5. po:58 auto: ⑤ month reference: ⑤ ../src/crontabEditorHelper.py:234 Original: ⌘0 At an exact month - at a month + in a month 6. .po:117 reference: ⑤ ../src/gnome-schedule.glade.h:51 Original: ⌘0 See \"man 5 crontab\" for informations about the crontab format. - informations + information ("information" is a mass noun, like "rice", "paper" and "software". You can have "some information", or "a kilo of rice", or "a piece of paper" or "a package of software", but these mass nouns on their own are not countable, so they do not take the plural indicator "s".) Clytie Siddall, Vietnamese translator
Thanks, are we going to fix this in this release? This will probably just result in 6 strings marked fuzzy.
+1 for fixing. Some are my fault... ;) Comment on point 2: It's not possible to use ngettext here. These are two different labels and the plurals are an unspecified amount of days/hours/minutes. But anyway, it's probably better to replace plural labels with a common "Step size:".
There are so many similar strings, I did wonder how many of them you could combine, using plurals or variables. However, you know what you can do! If there's something you can't do because of limitations in the current python support in gettext, please mention it on the gettext list or Translation Project list, where the gettext developers hang out. They're aware (partly because of my dumb, um, helpful questions ;) ) that there are more and more python-format strings coming in for translation, and that there needs to be more work on python support in gettext (and possibly on gettext support in python?). One of the issues I had to take there was the one of reordering variables. In C-format strings, you can reorder the variables, usually printf, by doing this: %s %s becomes %$2s %$1s if the translation grammar requires reordering, as it often does. Python-format strings using these printf-style variables can _not_ (yet?) be reordered. We are trying to encourage developers to use named variables. You saved me a lot of hassle by using them anyway, and I appreciate that very much. As an open-source translator, I'm happy to support more work on python in gettext. I'll certainly support any queries you post to translation-i18n@lists.sourceforge.net (TP list). from Clytie, Vietnamese translator in more open-source projects than you could shake a stick at, assuming you had a stick and felt like shaking it
Ok, lets fix the typos. But not point 2.
Fixed, i added a note in the TODO about the limitations of python gettext, I don't really feel like shaking the stick here, but i would be happy if somebody else shaked it and felt like testing this out on gnome-schedule. But not for this release of course.