Hi, can we get some information about the status of the Kurdish translations? There is issue 61400, which is "fixed", but we never heard what has become of it. Is there a Kurdish translation implemented? http://www.openoffice.org/issues/show_bug.cgi?id=61400
We are working hard on a far more complete translation for 2.0.4, so we'd love to hear what has become of the 2.0.3 translation. Regards, Erdal 2006/7/10, Vladimir Glazounov <[EMAIL PROTECTED]>:
Hi all, the OOo features frees for 2.0.4 is planned for July 13th 2006. In order to meet the deadlines, please start working up 20.07.2006 on your translation updates. The deadline for providing GSI / SDF files is August 3rd, 2006. Keep in mind that the timeline till last cws integration is very tight, so I have to reject all files delivered too late. 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.4" , Component "l10n" , Subcomponent "code" , Issue type "ENHANCEMENT" And as usual please: - File an issuezilla bug to "[EMAIL PROTECTED]" . Please don't attach your file directly to that issue, but provide an URL / link pointing to your file. Only attach if you don't have any web space 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. Best regards, Vladimir --------------------------------------------------------------------- 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]
