Hi Nguyen Vu Hung,

On 02/12/09 06:23, Nguyen Vu Hung wrote:
Hello all,

12 of our Vietnamese team members will do a cross review against
the entire Vietnamese translation which is available on pootle.

The target is 3.1 so we have one month until the deadline.
Not really. The last date for l10n fixes is actually February 26th. What you can fix by then will be integrated into the 3.1 release - which is the content that is available on Pootle. All other improvements will be for 3.2. The review process is a very long task ... so the earlier you start the better :-) .

There are many ways of approaching review. So depending on the time and resources you have at your disposal you may want to review in one way or the other. Of course it also depends on the current language quality of the translation.

Going through one strings after the other in Pootle may be very good from the translation perspective, but it is very time consuming.... If I may suggest something .... I would first of all review the GUI and define the GUI terminology. Once the GUI terminology is well defined, I would go and fix it first in the GUI and then in the Help.

How can this be done?
With the testtool there is the possibility of automatically creating screen shots of all GUI dialogs. Once the screen shots are generated, you/your team can start reviewing them. What needs to be changed should then be reported in table in a wiki. Once you/the team agrees on the changes and on the terminology, you can then go ahead and carry out the changes in Pootle. IMHO, the advantage of starting with this approach is that you fix the errors in the context and to fix the major issues that a user would see at first. Also you get screeshots of dialogs which you would not usually sere if you are not familiar which a particular OOo function.

Just let me know if this approach would work for you.

Kind Regards,
Rafaella

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to