Re: [l10n-dev] Deadline for OOo 2.0.4 translations
Vladimir Glazounov pravi: - 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 Maybe you should outline that the latest gsicheck can be downloaded from http://ooo.services.openoffice.org/gsicheck/ Bye Robert Ludvik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] L10n Status page !
Ankit Patel wrote: > Hi all, > > I have made one web application for openoffice.org > localization status page automation. > > FEATURES IT PROVIDES :- > 1. Get the latest tarball of .pot from Openoffice.org > server and merge it with your current .po translation. > 2. All .po files are secure and stored in the CVS > server of sourceforge. > 3. You can see the status page of your language on > web. > 4. Your translated .po files will be automatically > converted to .sdf daily. > 5. You can download tarballs of your language > translation files & .sdf files also. > > You can see the demo of the web application on > sourceforge webserver. > http://indianoss.sf.net/Openoffice.org/index.php > > CVS:- > 1. Create an account on sourceforge.net. > 2. Let me know the account ID. > 3. I will give you CVS access to the openoffice > translation repository > 4. You can checkout, update, commit your translation > into CVS. > ---> After getting CVS account working >I. export > CVSROOT=:ext:@indianoss.cvs.sourceforge.net:/cvsroot/indianoss >II. export CVS_RSH=ssh >III. cvs co locales >IV. Your language directory will be there in your > locales folder. Start translating. > > > Above information would be very helpful for the > localizers who are working for openoffice > localization. > > Still, i need inputs from the openoffice l10n > community to make this tool better. > Hi This is nice... one little recommendation - it takes a lot of effort to reload so many images per page to do the bar charts showing progress - why not just adjust the widths and the browser should resize them? or use them as background images to table cells... Cheers David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Deadline for OOo 2.0.4 translations
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]
