There are different problems combined here:

- New strings vs old strings in maintenance mode vs old-old strings. The solution is that English strings go as soon as possible to enable localization, followed probably by the rest of official translations as soon as they have gone through the internal revision.

- New system strings that could come together with SDK pre-releases vs new applications strings that at least now would need to be treated differently since they would come no sooner than a new release launch.

- Localization testing taking into account bugs.maemo.org and getting the feedback in the best time to implement the changes.



Agreed. However, I also think that the way to give feedback about the official languages should be filing bugs. Those texts have gone through internal revisions already, are tied to a Nokia terminology and any changes go through a revision equivalent to a pacth submitted (only simpler to test). Offering a e.g. web interface to modify those strings and propose changes would give the impression that anybody can get changes committed easily. This has the potential of creating a lot of unproductive noise and discussion, just as if you would offer an easy way to submit changes to the icons and design layout.