Ciao Enrico,
Ciao Rafaella,
we need the italian files only as reference during translation. Davide
Dozza suggested us to translate the english files directly...
I agree. Translating from English which is the source is better because
you can better find the new and changed strings from milestone to
milestone or from release to release.
We want to translate the 2.2 release, and for the moment we want to
start from the Writer user interface, in order to understand the
translation process.
That's a very good approach.
- start from the UI strings
create a glossary based on the most important Writer terminology,
then move to another UI application,
add terminology to the glossary, review the glossary, then move to the
next application...
once you have approx. 80% of the UI translated start verifying the
langauge quality in the build itself.
There are some testtool scripts which enable you to verify the main menu
entries adn some others which can automatically create screenshots of
most of the OOo dialogs ... so that even unexperienced users can see
dialogs of a function they would not even know they exist....
I have found also this guide:
http://translate.sourceforge.net/wiki/openoffice.org?DokuWiki=eeecb7319622a9c49fa390d7456ac2bc
:what do you think about?
There are some information on the OOo localization project page:
please visit: http://l10n.openoffice.org/localization/translation.html
Also, please look at the HowTo document created recently at:
http://wiki.services.openoffice.org/wiki/NLC:ReleaseChecklist
As for the Italian most recent files ... just received the inforamtion
that they will be uploaded next Monday. I'll keep you posted.
Thank you very much for Your help!
You're welcome.
Excuse me if my english is not perfect!
mine is not perfect as well...
Bye
Ciao
Rafaella
Enrico Di Lenarda
P.S.: Do you speak Italian? ;-)
certo!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
