📅 Original date posted:2011-08-31
🗒️ Summary of this message: Qt translations can be reused for Bitcoin Core, but files need to be converted from Wx's line-based format to Qt's XML-based format. Translations can be added later.
📝 Original message: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110901/e5fb7740/attachment.html>;
John Smith [ARCHIVE] /
npub1e4…4jafl
2023-06-07 02:19:54
in reply to nevent1q…qtdj
Author Public Key
npub1e4lupyw4vuuhfsmt726ud69555re66pph90kwx0afpt346e9k7zsd4jaflSeen on
wss://relay.noswhere.comPublished at
2023-06-07 02:19:54Event JSON
{
"id": "3fc817db1aed11bde9f6154d410644c1141bf663eca8b39ba51779d05e8f3631",
"pubkey": "cd7fc091d5673974c36bf2b5c6e8b4a5079d6821b95f6719fd48571aeb25b785",
"created_at": 1686104394,
"kind": 1,
"tags": [
[
"e",
"ae205b1e3dc9858e8c5287dab16a9d15c248143003d13a23e95b51e3687a0e4a",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2011-08-31\n🗒️ Summary of this message: Qt translations can be reused for Bitcoin Core, but files need to be converted from Wx's line-based format to Qt's XML-based format. Translations can be added later.\n📝 Original message:Would it be possible to port some of the existing translations?\n\u003e\n\nWell, the strings in the core can be reused one-on-one as the _ function is\nmapped to the Qt translation function.\n\nAnd some of the UI texts probably can be reused as well, at least for a\nrough approximation.\n\nThe files will have to be converted, as Qt uses an XML-based format whereas\nWx uses a line-based one. Also, Qt translations have a \"context\"\n(file/object) defined whereas in Wx the \"msgid\" is only the English text.\nNah, nothing that a bit of Python hacking can't solve.\n\nThough IMHO its not a huge deal if qt is merged without all the\n\u003e translations as IMHO it should be merged soon and then not the default\n\u003e release GUI until its in tree for a bit (like one release) and some\n\u003e translations can be built up.\n\u003e\n\nExactly... if there is some time between Qt being merged and Wx being phased\nout, translations can be added. The Qt translation tool (Qt Linguist) is\nuser friendly enough to be used by anyone.\n\n\u003e\n\u003e \u003e So IMO, it is ready to be merged.\n\u003e IMHO it should be merged right after 0.4 is pushed.\n\u003e\n\nSounds fine with me,\n\nJS\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110901/e5fb7740/attachment.html\u003e",
"sig": "546d8fc249f789292ca013c02b41afc41c1fe9d4b4c35c22be5508c5e669f204b16bba6b8ebe1e775682f02b0a624849a5e1740fb134fc2cb24e0354931385bb"
}