I am seeing the same problem as Kenneth for my Yiddish strings: > "Kenneth J. Davis" <[EMAIL PROTECTED]>, Jan 23, said > > We have a .po file that ended up with this: > > #. MSG_SpellSelectionDone > #. " Do you want to continue checking the remainder of the document?"); > #. /* DLG_FR_FinishedReplace > #: po/tmp/ap_String_Id.h.h:329 > msgid "AbiWord finished checking the selection." > msgstr "" > > #: po/tmp/ap_String_Id.h.h:331 > #, c-format > msgid "AbiWord has finished its search of the document and has made %d replacements." > msgstr "" > > Note that DLG_FR_FinishedReplace should be the message id for string 331 > here, but it is instead stuck inside the section for string 329 above. The > resulting strings file ended up having a duplicate ID (both translated > messages had MSG_SpellSelectionDone as their id, hence the strings file > aborted loading. My question for those with access and some knowledge of > perl, is this just a weird quirk that happened somehow, or if the update.pl > (as indicated on abisource's webpage for translations) is ran, does it > produce a correct .po[t] file?
I always have to manually go into the resulting strings file (user/wp/strings/yi.strings) and remove one of the MSG_SpellSelectionDone strings. I will try to track down why the update.pl script is giving us this bogus entry. Raphael
