Hi Jonathon,
Jonathon Blake wrote:
Ivo wrote:
specific _why_ OOo is such a wall for translation teams ?
i) The number of files that are required to be translated;
ii) The number of strings that are required to be translated;
Those two point can not be avoided in my point of view.
iii) The lack of a comprehensive and complete OOo glossary, with
definitions as used within OOo.
Please see my answer in Alberto's mail
iv) String context. The English word can be translated two or more
ways in the target language. [OOo 1.0.0 through 1.1.4 French has some
interesting examples of the English being incorrectly translated.]
This is a common problem in string based translation, any suggestion how
to solve this ?
v) Converting the material to be translated into a format that the
translation tools that a team is familiar with can use.
IMHO there is a bunch of formats supported now ? sdf, xliff, po, ...
What is your preferend format ?
QA for translations can not be done by running one or two tools. It
requires several people to read everything two or three times, to
catch the types, mis-translations and other errors.
I can not give an answer because I am not familar with QA
xan
jonathon
Cheers,
Ivo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
