MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Message-id: <5027627C.3020303@bitminter.com>
Date: Sun, 12 Aug 2012 09:59:56 +0200
From: Geir Harald Hansen <operator@bitminter.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.6esrpre) Gecko/20120713
	Thunderbird/10.0.6
To: bitcoin-development@lists.sourceforge.net
References: <CA+8xBpfeoNOte=GFGqAT7+4U+JCa4DP8CkEupe+oKdJL1dMFFQ@mail.gmail.com>
	<50268BB0.8080001@bitminter.com>
	<CA+s+GJDU8Y8TuDVwt6S91Eppps5d_NfbKGgMiFB6ktNHPSHpcw@mail.gmail.com>
In-reply-to: <CA+s+GJDU8Y8TuDVwt6S91Eppps5d_NfbKGgMiFB6ktNHPSHpcw@mail.gmail.com>
Subject: Re: [Bitcoin-development] Version 0.7 release planning
Precedence: list

On 11.08.2012 20:56, Wladimir wrote:
> Duplicate strings are not a problem. Some strings are used multiple
> times in the program, and thus appear multiple times in the translation.
> This is because there are cases in which a string that is the same in
> English is translated differently in another language based on the context.

That makes sense. But it's hard to translate when you just see the same
string twice and don't know the context where it will be used.

> At least Qt translator fills duplicates in automatically, with the
> option to change them if desired. I'm not sure about Transifex but I've
> heard it's the same there.

No, I just use copy and paste.

>     Use UPnP to map the listening port (default: 0)
>     Use UPnP to map the listening port (default: 1 when listening)
> 
> The default depends on compiler flags, hence the two messages. I suppose
> the message could be split up, so that "Use UPnP to map the listening
> port" is factored out.

Sorry, forgot there was a compiler flag for this. No need to split this
up. As long as there is no explanation or description for each string I
think it's easier to translate whole sentences.

On 11.08.2012 20:32, Wladimir wrote:
> By the way, by far the most common support request I have at my pool is
>
>     users withdrawing coins and not seeing it in their wallet because it's
>     not up-to-date with the block chain. Might be worth adding
something in
>     the bitcoin-qt GUI to make it more obvious that users can't see new
>     transactions and why.
>
> For 0.7 we've added a red "(out of sync)" warning to the balances when
> the block chain is out of date.

Perfect. This will prevent a lot of confusion. Thanks!

Regards,
Geir H. Hansen, bitminter.com