Hello Neil, On Sun, May 20, 2007 at 09:51:34PM +0100, Neil Williams wrote: > On Sun, 20 May 2007 21:53:29 +0200 > Helge Kreutzmann <[EMAIL PROTECTED]> wrote: > > While translating your po file to German, the German translation team > > noticed some minor errors which are listed in the following pseudo > > patch format: > > -msgid "Query the QSF XML data in <filename>" > > +msgid "Query the QOF XML data in <filename>" > > The XML format is QSF - QOF Serialisation Format, not QOF. The message > string is correct. (I wrote and designed the format, I think I can say > with some certainty that the correct name is QSF.) > :-)
Ok, it looked as if this was a typo as well. To be hones, I don't know
much about the program, I just read the request for translation on
debian-i18n, so all these details are new to me.
> > -" Use exactly one of -i -l --gui or --explain;\n"
> > +" Use exactly one of -i, -l. --gui or --explain;\n"
>
> The comma and fullstop are misplaced. Any one of those four options is
> valid. The message string is correct.
Yes, the full stop is my mistake. Usually (and you do this later in
the po file, see below) listing options are separated by commas, and
especially since the "or" indicates that this is a listing. Why are
the commas incorrect?
> Please do not include the changed msgid in your translation - the patch
> is likely to be rejected.
I will not change anything in your template. I just report things
which look like errors to me and it is *completely* up to you to
incorporate the changes. Experience has simply shown that translation
teams find many (small) errors which are overlooked otherwise. But the
final decision is always up to you the package maintainer (or
upstream, depending who wrote the strings).
> > -" options are -c -t -w, -s or -f.\n"
> > +" options are -c -t -w, -s and -f.\n"
>
> The options are "or" not "and", using -s precludes -f. The message
> string is, again, correct. I do require that your translation specifies
> 'or' here, not 'and' - please ensure that it is translated in that
> manner.
Ok. It was not obvious to me, which options are grouped or how they
relate together. I assumed that you could use any of the ones listed
above (or several together). Maybe you can add notes to the po file to
help translators understand. Also I was not sure what "-i -l --gui or
--explain" are. Do you call them options as well?
> > -msgid "%s: ERROR: specify only one of-i, -l, --gui or --explain.\n"
> > +msgid "%s: ERROR: specify only one of -i, -l, --gui or --explain.\n"
You did not comment this one. Is there indeed no space between "of"
and "-i"?
> > -msgid " Expenses applet for GPE on iPAQ .\n"
> > +msgid " Expenses applet for GPE on iPAQ.\n"
>
> OK, that's minor. I'll change that for the next upload.
>
> > -"%s: Error: please specify which database you would like explained.
> > \n"
> > +"%s: ERROR: please specify which database you would like
> > explained.\n"
>
> Where is it mandated that "Error" needs to be uppercase? The message
> string is correct. There is no need to shout about this error, it's a
> minor error message, not a critical or even serious error.
Ok, often capitalization is used consistently across a programm, I was
not aware that you used this to distinguish between minor and major
errors.
If you provide me with the updated template before your next upload,
I'll update the translation and check all the issues you explained to
me in the translation as well.
Greetings
Helge
--
Dr. Helge Kreutzmann [EMAIL PROTECTED]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
