Re: [l10n-dev] L10n mailing list for translation tools
Hi Rafaella, I second this good proposal. Joy Rafaella Braconi wrote: Dear All, despite my initial assumption that the traffic on Pootle and various tools would decrease, I must admit that this hasn't happened. I take it as a sign that there is a a great need to share best practices and to propose features, work flows and tools which can make the localizer's life much easier. I'm still convinced that we do not need a *Pootle* only mailing list, and this because Pootle is not the only tool we are using to localize OOo. What I am proposing here is actually what Olivier Hallot suggested during our last l10n meeting on IRC: to set up a translation tool list where to discuss all tool related topics. Just to clarify: translation schedules and deadlines will still be posted to the [EMAIL PROTECTED] list which is to be considered the main discussion list of the l10n project. But information and discussion on Pootle and its functionality will be moved there (I am quite sure some people will be happy about that). If I get your support, I will go ahead and set up a [EMAIL PROTECTED] list - discussion list on translation tools and workflows. Kind Regards, Rafaella - 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] L10n mailing list for translation tools
Hi Rafaella, I support your idea. To be honest, I really want the place to share and discuss the translation tools and process as soon as possible. Now I am holding my post about Pootle until the discussion is finished. Going through the Pootle process first time, I have a lot of findings, feedback, suggestion I want to share. Regards, -Reiko Rafaella Braconi wrote: Dear All, despite my initial assumption that the traffic on Pootle and various tools would decrease, I must admit that this hasn't happened. I take it as a sign that there is a a great need to share best practices and to propose features, work flows and tools which can make the localizer's life much easier. I'm still convinced that we do not need a *Pootle* only mailing list, and this because Pootle is not the only tool we are using to localize OOo. What I am proposing here is actually what Olivier Hallot suggested during our last l10n meeting on IRC: to set up a translation tool list where to discuss all tool related topics. Just to clarify: translation schedules and deadlines will still be posted to the [EMAIL PROTECTED] list which is to be considered the main discussion list of the l10n project. But information and discussion on Pootle and its functionality will be moved there (I am quite sure some people will be happy about that). If I get your support, I will go ahead and set up a [EMAIL PROTECTED] list - discussion list on translation tools and workflows. Kind Regards, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Reiko Saito Japanese Language Lead Translation Language and Information Services (TLIS) Globalization Services Sun Microsystems, Inc. Email: [EMAIL PROTECTED] Phone: +81 3 5962 4912 Blog: http://blogs.sun.com/reiko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] L10n mailing list for translation tools
On Tue, Apr 8, 2008 at 6:20 PM, Rafaella Braconi <[EMAIL PROTECTED]> wrote: > Dear All, > > despite my initial assumption that the traffic on Pootle and various tools > would decrease, I must admit that this hasn't happened. I take it as a sign > that there is a a great need to share best practices and to propose > features, work flows and tools which can make the localizer's life much > easier. > > I'm still convinced that we do not need a *Pootle* only mailing list, and > this because Pootle is not the only tool we are using to localize OOo. What > I am proposing here is actually what Olivier Hallot suggested during our > last l10n meeting on IRC: to set up a translation tool list where to discuss > all tool related topics. Just to clarify: translation schedules and > deadlines will still be posted to the [EMAIL PROTECTED] list which is to be > considered the main discussion list of the l10n project. But information and > discussion on Pootle and its functionality will be moved there (I am quite > sure some people will be happy about that). > > If I get your support, I will go ahead and set up a > [EMAIL PROTECTED] list - discussion list on translation tools and > workflows. > It is easy to put all possible problems under term 'workflow(s)'. e.g when I'm announcing about new pot-files, it's a workflow related thing, because using po-files is just one of thousands workflows? (just to be sure what is this I'm voting for) :) ain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] L10n mailing list for translation tools
+1, too much issues with KBabel, Pootle and OmegaT wrt to OpenOffice. (yes I'm changing my previous vote) Olivier Rafaella Braconi escreveu: Dear All, despite my initial assumption that the traffic on Pootle and various tools would decrease, I must admit that this hasn't happened. I take it as a sign that there is a a great need to share best practices and to propose features, work flows and tools which can make the localizer's life much easier. I'm still convinced that we do not need a *Pootle* only mailing list, and this because Pootle is not the only tool we are using to localize OOo. What I am proposing here is actually what Olivier Hallot suggested during our last l10n meeting on IRC: to set up a translation tool list where to discuss all tool related topics. Just to clarify: translation schedules and deadlines will still be posted to the [EMAIL PROTECTED] list which is to be considered the main discussion list of the l10n project. But information and discussion on Pootle and its functionality will be moved there (I am quite sure some people will be happy about that). If I get your support, I will go ahead and set up a [EMAIL PROTECTED] list - discussion list on translation tools and workflows. Kind Regards, Rafaella - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Olivier Hallot Scinergy Consulting Tel (021) 2224-3224, (021) 8822-8812 Rio de Janeiro, Brasil http://www.scinergy.com.br OpenOffice.org L10N project leader for Brazil - 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)
Hi, Rafaella Braconi schrieb: L10n CWS builds/language packs will be ready approx. on Monday 10th. As soon as ready I'll post it to the list. sorry, April 10th Thursday, April 10th According to EIS, cws localisation28 has a Estimated integration date of 2008-04-17. This would mean, TCM tests should be finished until 2008-04-16? This is avery short time, given the fact that we have - a lot of new functionality - a lot of new help strings - new testcases in TCM - a base milestone of low quality ( DEV300m5 seems to have several issues that will cause TCM tests to fail - at least the version from pavel that I use) We surely will do our best, but this won't be much more than rushing through the tests. André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [l10n-dev] L10n mailing list for translation tools
Hi, Rafaella Braconi schrieb: If I get your support, I will go ahead and set up a [EMAIL PROTECTED] list - discussion list on translation tools and workflows. +1 (as I hope, this will lead to a working process with a recommended toolset that does not feel like "patchwork") André - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[l10n-dev] L10n mailing list for translation tools
Dear All, despite my initial assumption that the traffic on Pootle and various tools would decrease, I must admit that this hasn't happened. I take it as a sign that there is a a great need to share best practices and to propose features, work flows and tools which can make the localizer's life much easier. I'm still convinced that we do not need a *Pootle* only mailing list, and this because Pootle is not the only tool we are using to localize OOo. What I am proposing here is actually what Olivier Hallot suggested during our last l10n meeting on IRC: to set up a translation tool list where to discuss all tool related topics. Just to clarify: translation schedules and deadlines will still be posted to the [EMAIL PROTECTED] list which is to be considered the main discussion list of the l10n project. But information and discussion on Pootle and its functionality will be moved there (I am quite sure some people will be happy about that). If I get your support, I will go ahead and set up a [EMAIL PROTECTED] list - discussion list on translation tools and workflows. Kind Regards, Rafaella - 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 Gregor, Gregor Hartmann wrote: > Hi, just to be sure: are these errors detected by the gsicheck tool > which I maintain or is it some other tool(s). > I used the gsicheck 1.8.7 which was downloaded from OO.o web page and ran below command: gsicheck -f -we -wc [sdf] > > Would it be possible to add an automatic check with gsicheck and have > the errorfiles along with the errormessages ready for download > somewhere? That might help some translators. > It'd be helpful to recognize issues. Thanks for your comment. Regards, Aijin > Just my 2c > Gregor > > > Aijin Kim schrieb: > >> 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] >> >> > > > - > 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]
[l10n-dev] Re: [qa-dev] Re: [l10n-dev] Re: [documentation-dev] README for OOo 3.0 Beta
Can you please confirm if readme can be uploaded to Pootle? And for this, existing translation in DB need to be extracted. yes, I confirm that the oooreadme can be uploaded to Pootle. However, we need first to clarify if the README content will be available only on a wiki page or if it gets back into the oooreadme file and if yes by when. Adding the readme to Pootle now means - as far as I understand - that we add content which still needs to be finalized and not yet ready to be translated. Before we add the ooreadme module to Pootle, I would like to get clarifications on the above. Here is an update on the above. On April 17th/18th the updated readme for OOo 3.0 Beta will be available for translation. Translation delivery date is April 22nd. Not much time, but at least a chance to get it translated and integrated into the Beta release Regards, Rafaella - 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, just to be sure: are these errors detected by the gsicheck tool which I maintain or is it some other tool(s). if it is some other tool, so it would be good to pick a different name to avoid confusion. I had a look at some of the errors and to me it seems as if there are quite a lot of false positives. meaning errors are detected where there are no errors. Would it be possible to add an automatic check with gsicheck and have the errorfiles along with the errormessages ready for download somewhere? That might help some translators. Just my 2c Gregor Aijin Kim schrieb: > 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] > - 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, On Tue, Apr 8, 2008 at 11:50 AM, F Wolff <[EMAIL PROTECTED]> wrote: > > > > 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. > These checks give a lot of false positives, which lowers the trust in them. For instance the translation of strings like [none] always produces an error in the category "variables". Erdal
Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors
Op Maandag 2008-04-07 skryf André Schnabel: > 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. Thanks for the feedback, André. The translations of the Pootle interface is maintained at http://pootle.locamotion.org - perhaps you can contribute there, since you understand the context of that message better. Also feel free to help us add good comments to the translation to help translators understand it better. > > 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é I would really like to know these details, since it is definitely our intention to report at least all the errors that gsicheck reports. Please help us if there are any errors that we missed - perhaps they were added to gsicheck more recently, or there is a bug in our error detection around this. I believe the quality checks is a powerful way for translators to review possibly problematic strings. Friedel - 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 Aijin and all, Aijin Kim wrote: Hi Rafaella, Can you please confirm if readme can be uploaded to Pootle? And for this, existing translation in DB need to be extracted. yes, I confirm that the oooreadme can be uploaded to Pootle. However, we need first to clarify if the README content will be available only on a wiki page or if it gets back into the oooreadme file and if yes by when. Adding the readme to Pootle now means - as far as I understand - that we add content which still needs to be finalized and not yet ready to be translated. Before we add the ooreadme module to Pootle, I would like to get clarifications on the above. Thanks, Rafaella 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]
