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

List:       kde-i18n-doc
Subject:    Re: KGeography needs your help
From:       Michal Rudolf <mrudolf () kdewebdev ! org>
Date:       2005-08-04 17:13:31
Message-ID: 200508041913.31715.mrudolf () kdewebdev ! org
[Download RAW message or body]

Nicolas Goutte,  czwartek, 4 sierpnia 2005 19:02:
>> Of course, multiplying messages is not a good solution either.
>However it seems to be the only exact solution without a script that is run
> at runtime.
Right, just it has to be used with care. We don't want to add 1.000 messages x 
50 languages just to solve some very subtle problem which is not really 
important.

>Perhaps a middle way is to have a (non-runtime) script to fill the
>translation. However the script must be adapted to the application. (We had
>already that problem with the "fuzzy clock"; I do not know how this problem
>has evolved.)
Me too, but it seemed unsolvable.

>> I think the best we can do is to avoid such construction if it is
>> possible, and if it is not, trying to formulate the sentence and arguments
>> in a way that will cause as little problems as possible.
>I suppose that this will always have limits, either in what the developer
>wants to implement or of what a translator needs to translate to his
>language.
Right.

>The problem that I see here is that we have already "forbidden" constructs
> and that they are still used. (And in the past I was at least two times
> "flamed" for reminding a developer about them with a bug report.)
The problem is that there is a lot of (well, at least some) simple messages 
that can be fixed very easily, without breaking anything.

Maybe providing (or even committing) a patch by some "i18n supervisor" will be 
better then reporting bugs?

-- 
Michal Rudolf
[prev in list] [next in list] [prev in thread] [next in thread]