From: Gerry K. <ge...@fa...> - 2005-05-25 13:19:23
|
Filip Miletic wrote: > Gerry Kirk wrote: > >>I see that as a problem with the .po file, but not the .pot file. > > > There are some problems with putting the original English text in the > msgstrs of the .pot, as opposed to putting it in the comment: > > 1) As the msgstr's are already filled when you begin, you cannot > automate counting the number of translated and fuzzy strings. > 2) The only reference to the English text is that of the msgstr, which > you _overwrite_ when translating. It is not possible to revert to an > already translated string and improve, without referring somewhere else. > Note there are the "#." comments, but they often contain more text than > what you need to translate, so they are not straightforward. > 3) As all the strings are 'translated', you cannot use msgmerge to fetch > canned translations from your database. > > Introducing the "##" comment fixes these three, at the expense of not > being able to 'clone' the translation from the English original. > > While this tradeoff might be annoying for the translators to varieties > of English (-uk, -ca etc.) since they would like to make only minimal > changes to the text, it does not matter to anyone else as the > translations will be much different from the English original anyway. > > >>I don't see this new comment in the latest plone.pot or in, say >>plone-fr.po. >>These should get copied to the .po files then, so that you don't need to >>refer to the .pot file when translating. That would be nice. > > > I have recently completed a translation based upon the .pot file with > the "## English translation:" comments. It worked fine. So if you cannot > see it, you might be looking at the old pot files. > Ah, they weren't showing on the first few translations of the pot file. Now I see them. :) - Gerry |