From: Eero T. <ee...@us...> - 2006-12-29 20:34:29
|
Hi, On Thursday 28 December 2006 23:49, Kees Bakker wrote: > > It would also be nice if "check_po" would support checking also that > > following numeric format stuff matches: > > msgid "Generation %d has 1 individual. (%3.2f%%)\n" > > msgid "Generation %d has %d individuals. (%3.2f%%)\n" > > msgid "Total ancestors in generations 2 to %d is %d. (%3.2f%%)\n" > > msgid "%(genders)s born %(year_from)04d-%(year_to)04d: %(chart_title)s" > > msgid "Persons born %(year_from)04d-%(year_to)04d: %(chart_title)s" > > Matches what? Can you give me a hint? check_po didn't notice (at least earlier) that I had a mismatch in this parameter: "%3.2f" (and that mismatch would have resulted in Python exeption). I guess it didn't check for int/float format parameters that had digits between the % character and the parameter type character. > > It also seems to miss this: > > #: ../src/plugins/IndivComplete.py:131 > > #, fuzzy, python-format > > msgid "%(date)s in %(place)s. " > > msgstr "%(date)s, paikka %(place)s." > > > > If the string has format parameters or keywords, doesn't check_po check > > the last character anymore? It could check the first character also; > > whether it's space and whether its capitalization matches. > > Well, that's my choice. If it's a fuzzy, then it won't check the last > character. There were quite a few (still are?) translations with a lot of > fuzzies and last character messages. For a fuzzy it is not really > interesting (I thought). Let me know if you think otherwise. Note, a > fuzzy is not used by gramps as far as I know, so you better fix that > fuzzy first. I think it's good to skip these for fuzzies (sorry, I didn't know that it skipped that check for fuzzies). Does check_po check yet the capitalization of the first character (for non-fuzzies :))? - Eero |