On Tue, Dec 29, 2009 at 2:37 PM, Sophie <[email protected]> wrote:
Hi Alexandro, [email protected] wrote:During the TCM process we discover that the Spanish localization lacks a lot of a quality that has had before. Seems that this round of localization it was a complete mess. We will be trying to see what solution can we address by doing this that could solve the bigger issue of coherence with the context of the GUI. We are hoping to use pootle to debug the most possible before RC2 and ask Pavel for help to update the architectures with the patched localization, unfortunately Pavel doesn't build for Windows (AFAIK) so the Windows version might be unpatched unless Sun engineers provide an updated build for the Windows version.This is sad to ear. How can we help with the process? is there something you see that we have to change to get an earlier feedback for your team? Is it for new functionalities only, may be we have to better highlight/document them for l10n teams?
Biggest issue has to do with the need of context and translation memory. Basically users have no idea about the context of what they are translating resulting on very bad translations. However last cycle we didnt get enough people to translate which make us skip some QA we do resulting on very rushed translations. This combined with SunGloss which is stalled and nobody can contribute or updated it or even have access to it without a cumbersome process. The style guide is also a bit incomplete compared to other ones from Gnome and KDE which are also incomplete to a degree. Finally is the issue of traceability, we don't know who translated what, and when, yes we know who can do it because of permissions but we can't tell from those people who actually was the one that translated that string on that branch of the PO. This is very frustrating when situations like this happens, and we can't identify people that shouldnt be translating or just can't assure quality of their work.
However I think all this could be resolved with a bigger window of localization and also be able to generate new builds at any time of the development process. Localization bugs are real bugs and we should be able to update the build whenever we feel is important.
Kind regards Sophie--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- Alexandro Colorado OpenOffice.org Español IM: [email protected]
signature.asc
Description: OpenPGP digital signature
