Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1T0Gr4-0004Jl-Ej for bitcoin-development@lists.sourceforge.net; Sat, 11 Aug 2012 18:56:10 +0000 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; Received: from mail-lpp01m010-f47.google.com ([209.85.215.47]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1T0Gr3-0005mk-Jv for bitcoin-development@lists.sourceforge.net; Sat, 11 Aug 2012 18:56:10 +0000 Received: by mail-lpp01m010-f47.google.com with SMTP id v3so1332752lag.34 for ; Sat, 11 Aug 2012 11:56:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.112.234 with SMTP id it10mr6732700lab.36.1344711369086; Sat, 11 Aug 2012 11:56:09 -0700 (PDT) Received: by 10.112.83.161 with HTTP; Sat, 11 Aug 2012 11:56:09 -0700 (PDT) In-Reply-To: <50268BB0.8080001@bitminter.com> References: <50268BB0.8080001@bitminter.com> Date: Sat, 11 Aug 2012 20:56:09 +0200 Message-ID: From: Wladimir To: Geir Harald Hansen Content-Type: multipart/alternative; boundary=f46d040839197ad79804c70203a5 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1T0Gr3-0005mk-Jv Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Version 0.7 release planning X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Aug 2012 18:56:10 -0000 --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,

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'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 add= ress"
"Sign a message to prove you own a Bitcoin address"
"Clear &All"

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.

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

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 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.

Wladimir

--f46d040839197ad79804c70203a5--