[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: README files or messages for translators? (Re: still kdeedu)
From:       Thomas Diehl <thd () kde ! org>
Date:       2002-04-27 7:55:27
[Download RAW message or body]

Am Samstag, 27. April 2002 09:10 schrieb Éric Bischoff:
> On Friday 26 April 2002 23:31, Erik Kjær Pedersen wrote:
> > Three strings in ktuberling would be wonderful
> > 1. Saying this is where you should place the wav files.
> > 2. You have to add a section with the names of the wav-files
> > 3. You have to make sure your language is in this file.
>
> A pointer to these explanations somewhere else is enough, no need to put
> the details in the po file itself. It is enough to *know* that something
> special has to be done.

I'm more with Erik Pedersen on this one. It would be nice to know 
immediately what is required and if it can be done in the same translation 
session or not. At least some vague idea would be nice. If the process is 
so elaborate that it can't be properly described in a PO message it can of 
course refer to a README (but maybe the author should rather think about a 
way to  simplify the procedure in this case).

Judging from the experience with the PluralForms string in kdelibs.po we 
also need a (standardized) wording of the notes which make it _absolutely_ 
clear to people working on those files that they should NOT translate them 
but follow the instructions in there. (Believe it or not, there are still 
folks who translate the whole PluralForms comment instead of setting the 
variable described there.)

> > And the translation would be either DONE or NOT DONE, or DONE, but the
> > sounds stink.
>
> ????

This one made me also pause for a moment. ;-) I guess it means something 
like "Sound translations are done but not so good as they should be".

Thomas



-- 
KDE translation: http://i18n.kde.org/
Deutsche KDE-Uebersetzung: http://i18n.kde.org/teams/de/
[prev in list] [next in list] [prev in thread] [next in thread]