Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.175 as permitted sender)
	client-ip=209.85.160.175; envelope-from=witchspace81@gmail.com;
	helo=mail-gy0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <1314803146.2601.5.camel@BMThinkPad.lan.bluematt.me>
References: <CAJNQ0su7iRsQ2zPhXcd774TTqYzJGT+E9ss4D=6Ja3QSrpLdkw@mail.gmail.com>
	<1314803146.2601.5.camel@BMThinkPad.lan.bluematt.me>
Date: Thu, 1 Sep 2011 02:11:40 +0000
Message-ID: <CAJNQ0stejgAjXaap-ZKqYn6YH0QpReei5_-W_rtZK6_G=Pq=Lw@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Matt Corallo <matt@bluematt.me>
Content-Type: multipart/alternative; boundary=000e0cd404e0f5c6bb04abd7c368
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
Precedence: list

--000e0cd404e0f5c6bb04abd7c368
Content-Type: text/plain; charset=ISO-8859-1

Would it be possible to port some of the existing translations?
>

Well, the strings in the core can be reused one-on-one as the _ function is
mapped to the Qt translation function.

And some of the UI texts probably can be reused as well, at least for a
rough approximation.

The files will have to be converted, as Qt uses an XML-based format whereas
Wx uses a line-based one. Also, Qt translations have a "context"
(file/object) defined whereas in Wx the "msgid" is only the English text.
Nah, nothing that a bit of Python hacking can't solve.

Though IMHO its not a huge deal if qt is merged without all the
> translations as IMHO it should be merged soon and then not the default
> release GUI until its in tree for a bit (like one release) and some
> translations can be built up.
>

Exactly... if there is some time between Qt being merged and Wx being phased
out, translations can be added. The Qt translation tool (Qt Linguist) is
user friendly enough to be used by anyone.

>
> > So IMO, it is ready to be merged.
> IMHO it should be merged right after 0.4 is pushed.
>

Sounds fine with me,

JS

--000e0cd404e0f5c6bb04abd7c368
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"h5"><br>
</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Would it b=
e possible to port some of the existing translations?<br></blockquote><div>=
<br>
Well, the strings in the core can be reused one-on-one as the _ function is=
 mapped to the Qt translation function.<br><br>And some of the UI texts pro=
bably can be reused as well, at least for a rough approximation.<br><br>
The files will have to be converted, as Qt uses an XML-based format whereas=
 Wx uses a line-based one. Also, Qt translations have a &quot;context&quot;=
 (file/object) defined whereas in Wx the &quot;msgid&quot; is only the Engl=
ish text. Nah, nothing that a bit of Python hacking can&#39;t solve. <br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.=
8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Though IMHO its not a huge deal if qt is merged without all the<br>
translations as IMHO it should be merged soon and then not the default<br>
release GUI until its in tree for a bit (like one release) and some<br>
translations can be built up.<br></blockquote><div><br>Exactly... if there =
is some time between Qt being merged and Wx being phased out, translations =
can be added. The Qt translation tool (Qt Linguist) is user friendly enough=
 to be used by anyone.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.=
8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class=3D"im">&gt;<br>
&gt; So IMO, it is ready to be merged.<br>
</div>IMHO it should be merged right after 0.4 is pushed.<br></blockquote><=
div><br>Sounds fine with me,<br><br>JS<br><br></div></div>

--000e0cd404e0f5c6bb04abd7c368--