From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Help wanted: translations
Date: Sat, 8 Oct 2011 17:13:28 -0400 [thread overview]
Message-ID: <CABsx9T2eCpxqzbd0PmWJxCDFLHwOix2BOYp+APQGMZYh_O+R4g@mail.gmail.com> (raw)
Reposting here from the forums:
Good news: I'm just about to get a Bitcoin-Qt version 0.5 Release
Candidate 1 out, with a much-improved GUI.
Bad news: all the translations for the old wxWidgets Bitcoin are
obsolete, and the process for making translations is different.
Is anybody willing to write new translations? Here's what you'll need to know:
Three translations already exist: de nl and ru.
Translations are stored in ".ts" files in the src/qt/locale folder
The 'QT Linguist' tool can be used to create translations
... or maybe an online tool like Transifex could/should be used to
crowd-source the work
And is anybody willing to take the job of coordinating translation
efforts, figuring out if Transifex is a good tool to use, and writing
some documentation to make it easy for people to create and submit new
translations?
References:
https://github.com/bitcoin/bitcoin/blob/master/src/qt/locale
http://doc.qt.nokia.com/latest/linguist-manual.html
http://www.transifex.net/
--
--
Gavin Andresen
next reply other threads:[~2011-10-08 21:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 21:13 Gavin Andresen [this message]
2011-10-08 21:25 ` [Bitcoin-development] Help wanted: translations Christian Decker
2011-10-08 23:06 ` Martinx - ジェームズ
2011-10-08 23:12 ` Luke-Jr
2011-10-10 4:02 ` Luke-Jr
2011-10-10 9:22 ` Mike Hearn
2011-10-10 13:05 ` Luke-Jr
2011-10-10 13:18 ` Mike Hearn
2011-10-10 14:11 ` Luke-Jr
2011-10-22 10:51 ` Nils Schneider
2011-10-22 12:26 ` Geir Harald Hansen
2011-10-22 13:28 ` Nils Schneider
2011-10-22 16:14 ` Geir Harald Hansen
2011-10-24 11:24 ` Christian Decker
2011-10-24 18:10 ` John Smith
2011-10-24 18:55 ` Geir Harald Hansen
2011-10-25 5:02 ` John Smith
2011-10-29 21:16 ` John Smith
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=CABsx9T2eCpxqzbd0PmWJxCDFLHwOix2BOYp+APQGMZYh_O+R4g@mail.gmail.com \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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