On Mon, 7 Jul 2008, Martijn van Oosterhout wrote:
In other words, you want to remove the force option? The use case I
have is where I know some packages I want to translated but havn't
checked if they're translated. I can just type in the package name and
nothing happens if its already done.
Well, hmmmm, yes. Somehow I think what you call "force" is nothing
like force - it's rather asking for a review.
The practical problem is that when a package is requested to be
translated it is loaded into the DDTSS database (which is seperate
from the DDTP) and once there is has to be edited, and checked by two
people before it can be resubmitted as a new translation and removed
from the DDTSS. If you look at the DDTSS you can see many packages
which have been requested to be translated and then never actually
done. I'm worried that just blindly assuming "force" will make the
problem worse.
Yes, I can understand your doubt - but what is a reasonable solution?
I have detected broken translations and want to fix it.
In other words, I want to have a way of making your links work,
without putting unnessesary work on the translation teams that have to
review and check the result.
BTW, are there any experiences how long it might take until a fixed
description is available. I think I worked on either med-imaging
or med-imaging-dev (which had a wrong spelling for the German word
Paket (=package)) but now there is no translation at all (neither
the old with spelling error nor the new one).
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
