Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.47 as permitted sender)
	client-ip=209.85.215.47; envelope-from=laanwj@gmail.com;
	helo=mail-lpp01m010-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <50268BB0.8080001@bitminter.com>
References: <CA+8xBpfeoNOte=GFGqAT7+4U+JCa4DP8CkEupe+oKdJL1dMFFQ@mail.gmail.com>
	<50268BB0.8080001@bitminter.com>
Date: Sat, 11 Aug 2012 20:56:09 +0200
Message-ID: <CA+s+GJDU8Y8TuDVwt6S91Eppps5d_NfbKGgMiFB6ktNHPSHpcw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Geir Harald Hansen <operator@bitminter.com>
Content-Type: multipart/alternative; boundary=f46d040839197ad79804c70203a5
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.7 release planning
Precedence: list

--f46d040839197ad79804c70203a5
Content-Type: text/plain; charset=UTF-8

Geir,

There were a lot of subtle changes to the English base messages such as
capitalization or punctuation, I know this is pretty annoying for
translators. It is a pity that there is no way to update all translations
when the English base message changes but not significantly enough to
trigger re-translation. I've looked but Transifex does not have that option.

Also there were new duplicated strings:
>
> "Verify a message to ensure it was signed with a specified Bitcoin address"
> "Sign a message to prove you own a Bitcoin address"
> "Clear &All"
>

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.

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.


>
> These two seem odd:
> 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.

Let's do this after 0.7.0 release though, otherwise all the translations
for those messages will be broken again. There should be no more message
changes before the release unless there is a very good reason.

Wladimir

--f46d040839197ad79804c70203a5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Geir,<br><br>There were a lot of subtle changes to the English base message=
s such as capitalization or punctuation, I know this is pretty annoying for=
 translators. It is a pity that there is no way to update all translations =
when the English base message changes but not significantly enough to trigg=
er re-translation. I&#39;ve looked but Transifex does not have that option.=
<br>
<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also there were new duplicated strings:<br>
<br>
&quot;Verify a message to ensure it was signed with a specified Bitcoin add=
ress&quot;<br>
&quot;Sign a message to prove you own a Bitcoin address&quot;<br>
&quot;Clear &amp;All&quot;<br></blockquote><div><br>Duplicate strings are n=
ot 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.<br>
<br>At least Qt translator fills duplicates in automatically, with the opti=
on to change them if desired. I&#39;m not sure about Transifex but I&#39;ve=
 heard it&#39;s the same there.<br>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">

<br>
These two seem odd:<br>
Use UPnP to map the listening port (default: 0)<br>
Use UPnP to map the listening port (default: 1 when listening)<br></blockqu=
ote><div><br>The default depends on compiler flags, hence the two messages.=
 I suppose the message could be split up, so that &quot;Use UPnP to map the=
 listening port&quot; is factored out. <br>
<br>Let&#39;s do this after 0.7.0 release though, otherwise all the transla=
tions for those messages will be broken again. There should be no more mess=
age changes before the release unless there is a very good reason.<br><br>
</div>Wladimir<br><br></div>

--f46d040839197ad79804c70203a5--