Topic: Transifex Translation Memory Fill-Up

Can we get some statistics how much it would fill without actually doing it? Does transifex mark these auto filled translations? (I once uploaded some offline translations with such draft translator remarks, and transifex just ignored them.) Between different source files it may be less risky, but IMO different contexts should be respected and manually reviewed.

I think a bigger issue is when there is a minor fix in the English text, especially if it's just punctuation, typo or English specific grammar that don't need changing the translations that were done properly. These are handled by gettext and transifex as if they were completely new strings and the translation is lost, and must be manually restored from translation memory. But of course these are better checked manually as well because there's no automatic way to tell if a small change requires change in a given translation. Again, ideally these should be marked as minor changes that need reexamination.

Top

Quote

Using this option would be problematich with all soldier related translations. In Englisch they are all soldiers. but in German for example we have "Soldat" for Empire and Atlanteans, "Krieger" for Barbarians and Frisians and "Kriegerin" for Amazons.
I really would prefer top stick for manual check and use the suggested memory strings in these cases.
IIRC we made these Soldier Strings translatable in different fashions by using Pgetttext and they were treated as the same string before, with multiple occurences.
So AFAIK 100% matching strings are translated the same as long as they are not excluded by some function like Pgettext.

Top

Quote