1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <witchspace81@gmail.com>) id 1Qywks-0000VY-Ue
for bitcoin-development@lists.sourceforge.net;
Thu, 01 Sep 2011 02:11:46 +0000
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;
Received: from mail-gy0-f175.google.com ([209.85.160.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128)
(Exim 4.76) id 1Qywks-00010l-7W
for bitcoin-development@lists.sourceforge.net;
Thu, 01 Sep 2011 02:11:46 +0000
Received: by gyg4 with SMTP id 4so1325402gyg.34
for <bitcoin-development@lists.sourceforge.net>;
Wed, 31 Aug 2011 19:11:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.206.9 with SMTP id d9mr862852ybg.427.1314843100824; Wed,
31 Aug 2011 19:11:40 -0700 (PDT)
Received: by 10.150.146.2 with HTTP; Wed, 31 Aug 2011 19:11:40 -0700 (PDT)
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
X-Spam-Score: -0.1 (/)
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
(witchspace81[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (witchspace81[at]gmail.com)
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
0.4 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1Qywks-00010l-7W
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2011 02:11:47 -0000
--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 "context"=
(file/object) defined whereas in Wx the "msgid" is only the Engl=
ish text. Nah, nothing that a bit of Python hacking can'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">><br>
> 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--
|
