Re: L10n Testing: OpenOffice.org 3.3 - August 25th - September 2nd

Rafaella Braconi <[email protected]>
Newsgroups gmane.comp.openoffice.devel.localization
Message-ID <[email protected]>
Hi Jordi,

On 25.08.10 22:01, Jordi Serratosa wrote:
>  El 25/08/2010 17:58, en/na Santiago Bosio ha escrit:
>> Rafaella Braconi escribió:
>>> Dear All,
>>>
>>> this is a reminder that builds are available at the below location, 
>>> as announced by Vladimir. Deadline for providing fixes is September 
>>> 2nd. Please make sure to inform the list immediately in case of 
>>> critical issues. In case of possible show stoppers, don't hesitate 
>>> to nominate your issue to the releases list.
>>>
>>> For all the ones who would like to test the new features, please 
>>> note that TCM has a special scenario with latest test cases to test 
>>> the new features (thanks Joost!).
>>>
>>> Kind Regards,
>>> Rafaella
>> Rafaella:
>>
>> I just need a clarification here. The fixes that we can provide until 
>> september 2nd. need to be notified by entering issues, or can we just 
>> correct the errors on the Pootle server and after the deadline you 
>> will capture a new snapshot for the final translation?
> I'm wondering the same.
> In case of Catalan, we rushed to get to the 100% translated in ordre 
> to meet the deadline.
> I have a looong list of changes to do, including correcting 
> mistranslations, spell&grammar mistakes, ensuring translation 
> consistency throughout the product, etc.
>
> To make things worse: in the previous 3.2.1 release I was correcting 
> hundreds of the aforementioned mistakes. When the strings were updated 
> in Pootle for 3.3, I found to my dispair that LOTS of my corrections 
> were rolled back. My take is that the obsolete strings in .po (marked 
> with #~) were to blame. In my global QA for 3.2.1, obviously I didn't 
> take into account the obsolete strings. Apparently, when updating the 
> strings, Pootle (well, I guess it was Translate Toolkit) preferred to 
> take the obsolete strings as translation instead of the actual newer 
> reviewed string. It probably has to do with the update process not 
> "reusing" the strings (even with the same string ID) when they have 
> been moved to another file (which I seem to remember it was reported 
> here not long ago).
> Anyway, for whatever reason it happened and it adds to the things in 
> my list to correct for 3.3.
>
> Getting back to the topic: If you tell us that the Pootle files will 
> be all "picked up" again for the upcoming 3.3 release, I'd take the 
> time to try to fix as many errors as possible within the deadline. In 
> this case, please specify if this deadline is the latest opportunity 
> we have to change files in pootle or there will be other builds in the 
> future.
> If you tell us that only major fixes (though issues) will be 
> addressed, I'll leave it for the next release.
The very, very last deadline to provide corrections is September 30th. 
This should give you the possibility to correct as many errors as 
possible. Please do let us know via Issue and/or mailing list to 
download complete files from Pootle.

Hope this helps!

Rafaella
-- 

<http://www.oracle.com/>
Rafaella Braconi | Program Manager
Phone: +49 40 23646-0
Oracle Open Office Global Business Unit

ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven

<http://www.oracle.com/commitment>

	

Oracle is committed to developing practices and products that help 
protect the environment
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.