Comment 7 for bug 1104462

I partly agree with you Tino. (In case we need a bug tracker item for keeping track about "untranslateable strings" - which I am not yet convinced of), point 1 and 2 seem like a good idea.

However points 3 to 5 do not make sense for me:

1st) this bug report is about "is something translateable" - and I think that's the only thing we should keep track of, because:
2nd) if we take care about if something is translated, we would need a bug tracker item for every possible language Widelands could be translated to - during the time of development (so to say 365days a year ;) ) almost all of those bug reports would be "In Progress" or even just "Confirmed". However to see whether a translation is complete, you can just take a look at the list of translations of Widelands on launchpad.

So my point of view is:

* If new strings are created that are either not translateable at all or that need a catalog update that is not done for some days, a bug report should be created so the issue is kept in mind and hopefully handled soon.
* As soon as the strings are translateable the tracker item should be set to fix released, as again all strings are translateable again (keep point 2nd from above in mind).