FYI.
Charles.

-------- Original Message --------
Subject:        [l10n-dev] Deadline for OOo 2.0.1 translations
Date:   Mon, 17 Oct 2005 16:28:23 +0200
From:   Ivo Hinkelmann <[EMAIL PROTECTED]>
Reply-To:       [email protected]
Organization:   StarOffice / Sun Microsystems, Inc.
To:     [email protected]
Newsgroups:     openoffice.l10n.dev



Hi all,

the last cws integration for OOo 2.0.1 is near, thus please provide your 
translation updates for integration:

The deadline for providing GSI / SDF files is 2005/11/03

Keep in mind that the timeline till last cws integration is very tight, 
so I have to reject all files coming too late.

Please update to the latest milestone m134.

As the integration cause a lot of work do not provide sdf files that 
cover less then 80 % ( UI only ) translation done. Also please add the 
en-US translation to your sdf file.

Important: To prevent confusion and big mess please ensure that your 
issue has the following properties set:

Assign to "[EMAIL PROTECTED]" , Target milestone to "2.0.1" , Component 
"l10n" , Subcomponent "ui" , Issue type "ENHANCEMENT"


And as usual please:

- File an issuezilla bug to "[EMAIL PROTECTED]" . Please don't attach 
your file directly to that issue, better provide a URL / link pointing 
to your file. Only attach if you don't have any webspace available.
( http://qa.openoffice.org/issue_handling/project_issues.html )

- Please take care that the GSI / SDF file format is not violated ( 
format errors like wrong amount of tabs, shifted columns, ... ). You can 
use the tool "gsicheck" to perform basic checks on your file. "gsicheck" 
is located in the transex3 module.

usage: gsicheck -c -l "" myfile.sdf

- We try to correctly update our database status information which would 
later help to improve the overall quality of the translation. Please 
provide a GSI / SDF file containing both, your language and the 
corresponding en-US source string. Please note that the en-US string 
have to be the same milestone like your translation.

Cheers,
Ivo

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to