Tata wrote:So maybe the translator might become a part od distribution?
IMO that's not the best idea. Each installed plugins causes at least a little overhead -- and Translator_XH is probably not of much use for typical end-users, even if they will adjust some language strings according to their personal preferences.
Of course I recommend using Translator_XH for any complete translations of plugins or the core.
Tata wrote:if plugin authors would respect the need to state the version number in the very first line under a variable, e.g. $plugin_version, then the translator could easily read it and include into the header-comment
Several (many?) plugins already have a version number stored as constant or available through a function. If we could find an agreement about the name, it would be used for other purposes too (an automated update availability check for example).
Another thing oldnema made me aware of: it would be very helpful for translators, if the developers will state somewhat about the stability of their original language files. E.g. to state, that no new languages will be introduced in the 1.5.x series as it's the case for CMSimple_XH.