From: John Smith <witchspace81@gmail•com>
To: Matt Corallo <matt@bluematt•me>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin-qt ready for merging
Date: Thu, 1 Sep 2011 02:11:40 +0000 [thread overview]
Message-ID: <CAJNQ0stejgAjXaap-ZKqYn6YH0QpReei5_-W_rtZK6_G=Pq=Lw@mail.gmail.com> (raw)
In-Reply-To: <1314803146.2601.5.camel@BMThinkPad.lan.bluematt.me>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1733 bytes --]
next prev parent reply other threads:[~2011-09-01 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 14:20 John Smith
2011-08-31 15:07 ` Matt Corallo
2011-09-01 2:11 ` John Smith [this message]
2011-09-01 2:13 ` Luke-Jr
2011-09-01 2:32 ` John Smith
2011-09-22 20:11 ` Luke-Jr
2011-09-11 0:20 Alex Waters
2011-09-11 7:37 ` John Smith
[not found] ` <CAL0fb62M9=vKM4kag9rdQ=1bAbKdnoXD+7XR3eyKWY_Q4WEZXA@mail.gmail.com>
2011-09-11 9:54 ` John Smith
2011-09-11 17:12 ` Gavin Andresen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJNQ0stejgAjXaap-ZKqYn6YH0QpReei5_-W_rtZK6_G=Pq=Lw@mail.gmail.com' \
--to=witchspace81@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=matt@bluematt$(echo .)me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox