Hi,
Erdal Ronahi wrote:
Hi,
since Kurdish will be in 2.0.3 for the first time, there are still some
open issue left (43217, 44766 and especially 61400). Probably some
Please assign issue i61400 till 2006 / 04 / 20 to me (
[EMAIL PROTECTED] ! ). Add a link to you latest / final updated sdf
file in the issue and take care that I am able to access it. Please use
the gsicheck tool to ensure format correctness( see below ).
i44766 and i43217 are i18n relatd, possible Eike can give a statement
here. Both issues have the correct target, but please ask in the issues
again if there are any problems to get your i18n stuff into the OOo
2.0.3 release.
testing is required whether the new locale works at all. So:
1. does this deadline apply to us, too?
I would suggest to get the localisation into OOo 2.0.3
2. what additional steps are required of us?
Please provide language dependend patches to introduce your language to
the build system, see
http://www.khmeros.info/tools/localization_of_openoffice_2.0.html
Cheers,
Ivo
Regards,
Erdal
2006/4/3, Ivo Hinkelmann <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
Hi all,
the OOo 2.0.3 UI freeze is planned for 2006 / 04 / 06 , thus
*** the deadline for providing GSI / SDF files for the OOo 2.0.3 release
is 2006 / 04 / 20 ***
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] <mailto:[EMAIL PROTECTED]>" , Target
milestone to "2.0.3" , Component
"l10n" , Subcomponent "code" , Issue type "ENHANCEMENT"
And as usual please:
- File an issuezilla bug to "[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>" . Please don't attach
your file directly to that issue, better provide an 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 us 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]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
