public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Geir Harald Hansen <operator@bitminter.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Help wanted: translations
Date: Sat, 22 Oct 2011 18:14:04 +0200	[thread overview]
Message-ID: <4EA2EBCC.9000207@bitminter.com> (raw)
In-Reply-To: <4EA2C4FE.2020609@nilsschneider.net>

What do you know, it worked. Finished.

Once again Norway finishes ahead of Sweden. :P

By the way, I had to translate some of the exact same strings 2-3 times.
That's something you may want to improve on.

On 22.10.2011 15:28, Nils Schneider wrote:
> I think it's possible to add it yourself. Just click on "add translation"
> 
> On 22.10.2011 14:26, Geir Harald Hansen wrote:
>> On 22.10.2011 12:51, Nils Schneider wrote:
>>>> 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?
>>>
>>> I have exported all .ts to transifex.
>>>
>>> https://www.transifex.net/projects/p/bitcoin/resource/tx/
>>
>> If you add Norwegian Bokmål, I can do that one. Language code "nb".
>>
>> Regards,
>> Geir Harald Hansen
>>
>>
>> ------------------------------------------------------------------------------
>> The demand for IT networking professionals continues to grow, and the
>> demand for specialized networking skills is growing even more rapidly.
>> Take a complimentary Learning@Cisco Self-Assessment and learn 
>> about Cisco certifications, training, and career opportunities. 
>> http://p.sf.net/sfu/cisco-dev2dev
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
> 
> 
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn 
> about Cisco certifications, training, and career opportunities. 
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> 





  reply	other threads:[~2011-10-22 16:14 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
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 [this message]
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=4EA2EBCC.9000207@bitminter.com \
    --to=operator@bitminter.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