Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Hi André, André Schnabel wrote: Hi Aijin, * Aijin Kim schrieb: You can find the link of the result file of gsicheck in the issue description. Here is the list of the issue # for each language: German http://www.openoffice.org/issues/show_bug.cgi?id=87980 Just for the records: I had a look at the error file and none (but one) of the reported strings had been touched by us during translation. Thanks for reporting this. I'll also look into the file to see if any problem with oo2po/po2oo. Aijin This leaves the bad taste, that the workflow is unstable (if not broken). André - 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]
Re: [l10n-dev] Re: [documentation-dev] README for OOo 3.0 Beta
Hi Rafaella, Can you please confirm if readme can be uploaded to Pootle? And for this, existing translation in DB need to be extracted. Thanks, Aijin sophie wrote: Hi Martin, Martin Hollmichel wrote: Hi, I'm wondering if the README file on http://www.openoffice.org/welcome/readme.html and included in the installation set is still valid for the 3.0 release. I'd like to suggest that we create a wiki page to get a new readme for the upcomping beta release. deadline for this is April 17th to get it included into the beta. It was suggested at the last l10n irc meeting that the file be uploaded on Pootle for translation. Will we have the time to translate it? I'm adding l10n team in cc of your mail. Kind regards Sophie - 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]
Re: [l10n-dev] Re: [documentation-dev] README for OOo 3.0 Beta
I am sure is possible. On Mon, 07 Apr 2008 11:39:47 -0500, sophie <[EMAIL PROTECTED]> wrote: Hi Martin, Martin Hollmichel wrote: Hi, I'm wondering if the README file on http://www.openoffice.org/welcome/readme.html and included in the installation set is still valid for the 3.0 release. I'd like to suggest that we create a wiki page to get a new readme for the upcomping beta release. deadline for this is April 17th to get it included into the beta. It was suggested at the last l10n irc meeting that the file be uploaded on Pootle for translation. Will we have the time to translate it? I'm adding l10n team in cc of your mail. Kind regards Sophie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandro Colorado CoLeader of OpenOffice.org ES http://es.openoffice.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Unicode Consortium would like to invite the OpenOffice.org as a Liaison Member
Hello everyone, Thanks for your participation in this discussion. So far, the following folks participated in the discussion and voted (some in private emails and if I missed anyone, please let me know): Aiet Kolkhi Charles-H. Schulz Christof Pintaske Dieter Loeschky Eike Rathke Karl Hong Kazunari Hirano Louis Suarez-Potts Nakata Maho Matthias Huetsch Michael Meeks Pavel Janík Rafaella Braconi Sankarshan Mukhopadhyay Stephan Bergmann Vladimir Stefanov Wunna Ko Ko and reached the following consensus in my understanding: - ESC and L10N-Dev of OpenOffice.org support the idea of joining the Unicode Consortium as a Liaison Member. - Eike Rathke, a lead of L10N & I18N Project will be the first liaison to the Unicode Consortium. Please review and let me know if you have different opinion or comment by tomorrow 10PM UTC/GMT. Unless there will be objection by that time, I'd like to forward the consensus to Louis for additional discussion and possible approval also at the Community Council before we establish the formal liaison relationship. Ienup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Hi all, André Schnabel wrote: Hi, F Wolff schrieb: I don't know if I am stating the obvious, but just wanted to remind people that Pootle exposes many quality checks, which should stop gsierrors from entering the translations. The checks called 'variables', 'xmltags' and 'escapes' are the important ones. Not all of them might necessarily be problems, but should help you to avoid problems with gsicheck. This view is available with: Show editing functions -> Show checks. thanks for the hint. I never tried this function, as the translation in the German UI of pootle is missleading. But anyway - i tried it now, but the errors found within pootle do not match the errors reported by gsicheck. So it seems "nice" that the checks are there, but it does not ensure, that gsichek will be passed. Same for me and the bad news is that I corrected the .sdf file directly this morning, but didn't kept the gsicheck output, so no way for me to report the changes to Pootle now. Kind regards Sophie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: NL Issue 87986 Translation repairs submitted via IssueTracker
Aijin Kim schreef: > Here is the list of the issue # for each language: > Dutch translation of GSIcheck errors submitted to Issue 87986 - DiGro Windows XP Professional SP2 and OOo 2.3 Scanned with Multikabel Internet Security Plus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Hi, F Wolff schrieb: I don't know if I am stating the obvious, but just wanted to remind people that Pootle exposes many quality checks, which should stop gsierrors from entering the translations. The checks called 'variables', 'xmltags' and 'escapes' are the important ones. Not all of them might necessarily be problems, but should help you to avoid problems with gsicheck. This view is available with: Show editing functions -> Show checks. thanks for the hint. I never tried this function, as the translation in the German UI of pootle is missleading. But anyway - i tried it now, but the errors found within pootle do not match the errors reported by gsicheck. So it seems "nice" that the checks are there, but it does not ensure, that gsichek will be passed. André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Hi Aijin, * Aijin Kim schrieb: You can find the link of the result file of gsicheck in the issue description. Here is the list of the issue # for each language: German http://www.openoffice.org/issues/show_bug.cgi?id=87980 Just for the records: I had a look at the error file and none (but one) of the reported strings had been touched by us during translation. This leaves the bad taste, that the workflow is unstable (if not broken). André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] Re: [documentation-dev] README for OOo 3.0 Beta
Hi Martin, Martin Hollmichel wrote: Hi, I'm wondering if the README file on http://www.openoffice.org/welcome/readme.html and included in the installation set is still valid for the 3.0 release. I'd like to suggest that we create a wiki page to get a new readme for the upcomping beta release. deadline for this is April 17th to get it included into the beta. It was suggested at the last l10n irc meeting that the file be uploaded on Pootle for translation. Will we have the time to translate it? I'm adding l10n team in cc of your mail. Kind regards Sophie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Op Maandag 2008-04-07 skryf Aijin Kim: > Hi Pootle translation lead, > > All the Pootle translation was submitted via IssueTracker. You can add > yourself as cc to the issue to track the progress. > > However, several languages still have gsicheck errors to be fixed and > the strings have format errors won't be imported to the database. So > please **check the issue of your language and have the strings fixed > ASAP**. > You can find the link of the result file of gsicheck in the issue > description. > > > Here is the list of the issue # for each language: > > Arabic http://www.openoffice.org/issues/show_bug.cgi?id=87973 > Bengali http://www.openoffice.org/issues/show_bug.cgi?id=87975 ... > Thanks, > Aijin I don't know if I am stating the obvious, but just wanted to remind people that Pootle exposes many quality checks, which should stop gsierrors from entering the translations. Check this URL for example: http://www.sunvirtuallab.com:32300/bn/openoffice_org/index.html?editing=1&showchecks=1 I picked Bengali (bn) as the first language in the list with gsicheck errors mentioned in the bug. The checks called 'variables', 'xmltags' and 'escapes' are the important ones. Not all of them might necessarily be problems, but should help you to avoid problems with gsicheck. This view is available with: Show editing functions -> Show checks. Keep well Friedel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Aijin Kim schreef: > But > please make sure the fixing err.sdf is more urgent on this stage. > Will take care of that first -- DiGro Windows XP Professional SP2 and OOo 2.3 Scanned with Multikabel Internet Security Plus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Hi Dick, Dick Groskamp 쓴 글: > Aijin Kim schreef: > >> Hi Pootle translation lead, >> >> All the Pootle translation was submitted via IssueTracker. You can add >> yourself as cc to the issue to track the progress. >> >> However, several languages still have gsicheck errors to be fixed and >> the strings have format errors won't be imported to the database. So >> please **check the issue of your language and have the strings fixed >> ASAP**. >> You can find the link of the result file of gsicheck in the issue >> description. >> >> > Aijin, > > just to be sure: > Do I fix the errors in the err.sdf file or in Pootle ? > Or even both ? > Please enlighten me ;-) > If you can apply fix to both err.sdf and Pootle, it'll be great. But please make sure the fixing err.sdf is more urgent on this stage. Thanks, Aijin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Aijin Kim schreef: > Hi Pootle translation lead, > > All the Pootle translation was submitted via IssueTracker. You can add > yourself as cc to the issue to track the progress. > > However, several languages still have gsicheck errors to be fixed and > the strings have format errors won't be imported to the database. So > please **check the issue of your language and have the strings fixed > ASAP**. > You can find the link of the result file of gsicheck in the issue > description. > Aijin, just to be sure: Do I fix the errors in the err.sdf file or in Pootle ? Or even both ? Please enlighten me ;-) -- DiGro Windows XP Professional SP2 and OOo 2.3 Scanned with Multikabel Internet Security Plus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Hi Pootle translation lead, All the Pootle translation was submitted via IssueTracker. You can add yourself as cc to the issue to track the progress. However, several languages still have gsicheck errors to be fixed and the strings have format errors won't be imported to the database. So please **check the issue of your language and have the strings fixed ASAP**. You can find the link of the result file of gsicheck in the issue description. Here is the list of the issue # for each language: Arabic http://www.openoffice.org/issues/show_bug.cgi?id=87973 Bengali http://www.openoffice.org/issues/show_bug.cgi?id=87975 Catalan http://www.openoffice.org/issues/show_bug.cgi?id=87976 Chinese (Simplified) http://www.openoffice.org/issues/show_bug.cgi?id=87996 Chinese (Traditional) http://www.openoffice.org/issues/show_bug.cgi?id=87997 Dutch http://www.openoffice.org/issues/show_bug.cgi?id=87986 French http://www.openoffice.org/issues/show_bug.cgi?id=87982 German http://www.openoffice.org/issues/show_bug.cgi?id=87980 Italian http://www.openoffice.org/issues/show_bug.cgi?id=87983 Japanese http://www.openoffice.org/issues/show_bug.cgi?id=88000 Klingon http://www.openoffice.org/issues/show_bug.cgi?id=87992 Korean http://www.openoffice.org/issues/show_bug.cgi?id=87984 Kurdish http://www.openoffice.org/issues/show_bug.cgi?id=87985 Occitan-Lengadocian http://www.openoffice.org/issues/show_bug.cgi?id=87987 Portuguese (Brazil) http://www.openoffice.org/issues/show_bug.cgi?id=87988 Russian http://www.openoffice.org/issues/show_bug.cgi?id=879819 Spanish http://www.openoffice.org/issues/show_bug.cgi?id=87981 Swedish http://www.openoffice.org/issues/show_bug.cgi?id=87990 Turkish http://www.openoffice.org/issues/show_bug.cgi?id=87993 Ukrainian http://www.openoffice.org/issues/show_bug.cgi?id=87994 Vietnamese http://www.openoffice.org/issues/show_bug.cgi?id=87995 Thanks, Aijin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] Re: l10n TCM (Re: [l10n-dev] REMINDER: OpenOffice.org 3.0 Translation Delivery for BETA)
André Schnabel wrote: Hi Rafaella, L10n CWS builds/language packs will be ready approx. on Monday 10th. As soon as ready I'll post it to the list. we won't have a Monday 10th for several months ;) Can you tele the correct date, as I'd like to prepare l10n testing within the germanophone team. André sorry, April 10th Thursday, April 10th Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
