Why not translate one word "Version" at price of one-week-work? ;)

Hi L¨¹bbe,

2007/7/10, L¨¹bbe Onken <l.onken@rac.de> in "Spellchecking of manuals" thread:

> Are you talking about the condition="pot" stuff in the appendix? It prevents
> the strings from getting extracted into the .pot file. It does not do
> anything concerning spellchecking.

Preamble: I would like word "Version" on the title page in Russian :)

There is the condition="pot" in version.in file (thus in version.xml
also), so "Version x.x.x" is not translated (however version.xml is
present in "translate" target).
I understand why version.xml is excluded from up-to-date check, but I
don't understand why it's excluded from translation :)
If the rationale is "don't touch translated files in case of version
number change", then we can:
 - replace "en\version.xml" with "en\version.in" before generating
.pot file ( -> "Version $..$.$..$.$..$" entry in .po file)
-- (translation) --
 - prepare all needed version numbers in prepare.custom
 - replace contents "en\version.xml" with "en\version.in" before
translation (-> "Version $..$.$..$.$..$" translated correctly)
 - update version number in {$lang.target}\version.xml _after_
translation, but before producing output files (right before
spellchecking is OK) (-> we get "Version x.x.x" or "§£§Ö§â§ã§Ú§ñ x.x.x" or
... in output)

Am I missing something obvious here?

I can try to implement this (see preamble :).

Stan
Received on Tue Jul 17 17:21:29 2007