Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-09 Thread André Schnabel
Hi Friedel, F Wolff schrieb: I would really like to know these details, since it is definitely our intention to report at least all the errors that gsicheck reports. Speaking of all the tools, I am just a user. Speaking of the workflow - I am a beginner. So - I can report some of my findi

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-09 Thread Gregor Hartmann
Hi Aijin, Aijin Kim schrieb: > 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: > gsic

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-08 Thread Aijin Kim
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

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-08 Thread Gregor Hartmann
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 p

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-08 Thread Erdal Ronahi
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

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-08 Thread F Wolff
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',

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread Aijin Kim
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 l

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread sophie
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 impo

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread 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 mig

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread André Schnabel
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 (bu

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread F Wolff
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

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread Dick Groskamp
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 -

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread Aijin Kim
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

Re: [l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread 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 import

[l10n-dev] POOTLE: Translation was submitted via IssueTracker;Please fix gsicheck errors

2008-04-07 Thread 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 *