今回対象は、ドイツ語、チェコ語、フランス語、イタリア語、オランダ語で、日本語は対象からはずされています。
でもこのテストプロセスはえらくおもしろい。エラリーさん、これ、おもしろいぞー。
:)
翻訳されたい方はどうぞ。
Suggested Exercises
====================
[1] Note the untranslated wordcount for you language on the Translation
Status pages. Identify a file with untranslated content using the pages.
Check that file out of CVS. Translated all or some of the untranslated
content (you can grep or find for OO-TRANSLATABLE-MSG in the file to
get to the untranslated messages). Once you have translated the messages
commit the file back to CVS. Check the untranslated wordcount for you
language the next day. It should be lower reflecting your translation
work. Recheck the file out of CVS. Note now that the messages you have
translated are commented OO-REVIEWABLE-MESSAGE.
[2] Deliberately break a PO file that you have checked out in some way.
Commit the file back to CVS. Check the next day to see whether the
file appears in the Broken Files list. If you check the directory which
contained the file out of CVS you will note that there is also a file
present called <your filename>.po.broken. Fix the file and commit it
back to CVS. THe file should disappear off the Broken Files list the
next day.
Note: I am particularly interested to get peoples thoughts on treatment
of broken files. At the moment a copy of any broken files is copied into
CVS when found by the server side scripts. THe copy has the suffix file
suffix .broken. The thought behind this is that it allows contributors
to quickly and easily identify broken files and fix them but should the
PO file be removed to just leave the .broken file?
[3] If using Linux and you have msgfmt installed then do a
test compile on all the PO files for your language as follows using a
terminal :
for pofile in `find HEAD/<your language> -name "*.po" -print`
do
msgfmt --check --strict -o /tmp/out $pofile
done >compile-output.txt 2>&1
Read the newly generated compile-output.txt file to check for errors.
Do the same as above, substituting the msgmft with the following if
you have pofilter installed :
pofilter --openoffice $pofile
[4] Add a new PO file to the PO CVS server giving it any name you like.
If this file has no equivalent in the extracted OO.org sources then it
will appear in the last section of the Broken Files list the next day.
Note : This is a methodology for identifying obsolete PO files in CVS that no
longer have an equivalent in the OO.org sources. You might ask why not
automatically remove such files? The answer is that a file might not
have an equivalent in the OO sources not because it is obsolete but because
the source code has been restructured and the source code simly moved. In
such instances the translations are still needed and this is why we dont
want to automatically delete the PO thereby losing them.
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
