public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christian Decker <decker.christian@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Help wanted: translations
Date: Sat, 8 Oct 2011 23:25:17 +0200	[thread overview]
Message-ID: <CALxbBHVatfdVeZ=gLm6Fd1nN3gPA-f_NwcuQz8_ym-5Wrha6GA@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T2eCpxqzbd0PmWJxCDFLHwOix2BOYp+APQGMZYh_O+R4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

Damn, german is already contributed :-)
Well I can still do the italian one and check german then.

On Sat, Oct 8, 2011 at 11:13 PM, Gavin Andresen <gavinandresen@gmail.com>wrote:

> 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
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

[-- Attachment #2: Type: text/html, Size: 2699 bytes --]

  reply	other threads:[~2011-10-08 21:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 21:13 [Bitcoin-development] Help wanted: translations Gavin Andresen
2011-10-08 21:25 ` Christian Decker [this message]
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='CALxbBHVatfdVeZ=gLm6Fd1nN3gPA-f_NwcuQz8_ym-5Wrha6GA@mail.gmail.com' \
    --to=decker.christian@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gavinandresen@gmail.com \
    /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