[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TortoiseSVN GUI translation status for trunk (r12729)

From: Matjaz <mc1607slo_at_gmail.com>
Date: Mon, 21 Apr 2008 16:05:52 +0200

On Mon, Apr 21, 2008 at 3:34 PM, Lübbe Onken | RA Consulting
<l.onken_at_rac.de> wrote:
> Maybe... Could be worth a try. OTOH I'm afraid that some ppl will start from zero again if they don't see their language pack on SF, so we get three Magahursy translations with 200 strings translated, each of them less than the current translation and all of them combined still not good enough.

Why couldn't you just remove the install packages and leave the page
with the translations as it is? I mean, whoever chooses to start
translating would have to get the .pot file to start from and would
see that there's already a partially translated version available.
Maybe an additional warning to check the list of unmaintained
translations could be added.

I agree with Stefan that 60% is not enough and the GUI would look
really clumsy. The recently added/changed features (merging is a good
example) that really need to be understood are probably not
translated. Plus there's probably a lot of 'fuzzy' translations that
aren't really fuzzy but completely incorrect.

I don't want to sound too negative but I don't think it's fair to
advertise the product as translated in a particular language when in
fact it's only half way there. It's a free product, I know, but
still... I'd send additional 'please help translate...' emails to both
dev & users mailing lists and hope someone continues the work.

Just my opinion.

Matjaz

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-04-22 07:18:37 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.