From: Geir Harald Hansen <operator@bitminter•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Help wanted: translations
Date: Mon, 24 Oct 2011 20:55:01 +0200 [thread overview]
Message-ID: <4EA5B485.9090300@bitminter.com> (raw)
In-Reply-To: <CAJNQ0svAPqPdr_oWL-D-y3Om2dzFQ+0DS=K=ZEi+7+VVMDHtLw@mail.gmail.com>
Three quick examples of duplicated strings. There are many more. Some of
the smaller ones may make sense to have duplicated several times in
english as their translated versions may differ in other languages. But
with these below I don't see the point.
Twice, with a small difference (<b> vs. none):
WARNING: If you encrypt your wallet and lose your passphrase, you will
<b>LOSE ALL OF YOUR BITCOINS</b>! Are you sure you wish to encrypt your
wallet?
WARNING: If you encrypt your wallet and lose your passphrase, you will
LOSE ALL OF YOUR BITCOINS! Are you sure you wish to encrypt your wallet?
Again twice, with a small difference (%s vs %1):
This transaction is over the size limit. You can still send it for a fee
of %1, which goes to the nodes that process your transaction and helps
to support the network. Do you want to pay the fee?
This transaction is over the size limit. You can still send it for a fee
of %s, which goes to the nodes that process your transaction and helps
to support the network. Do you want to pay the fee?
Twice, looks exactly the same:
Generated coins must wait 120 blocks before they can be spent. When you
generated this block, it was broadcast to the network to be added to the
block chain. If it fails to get into the chain, it will change to "not
accepted" and not be spendable. This may occasionally happen if another
node generates a block within a few seconds of yours.
Generated coins must wait 120 blocks before they can be spent. When you
generated this block, it was broadcast to the network to be added to the
block chain. If it fails to get into the chain, it will change to "not
accepted" and not be spendable. This may occasionally happen if another
node generates a block within a few seconds of yours.
Regards,
Geir Harald Hansen
On 24.10.2011 20:10, John Smith wrote:
>
> Indeed. It could make sense. That's the reason why Qt distinguishes
> strings based on context as well as content.
>
> But it could also be nonsense. Can you be more specific as to which strings?
>
> JS
>
> On Mon, Oct 24, 2011 at 1:24 PM, Christian Decker
> <decker.christian@gmail•com <mailto:decker.christian@gmail•com>> wrote:
>
> Actually no, the same string may have to be translated in different
> ways depending on the context they appear in. That sometimes happens
> for italian, and I'm sure it happens in other cases too. Not sure
> whether this is the cause for duplicate strings for now, but it might.
>
> Regards,
> Chris
>
>
> On Sat, Oct 22, 2011 at 6:14 PM, Geir Harald Hansen
> <operator@bitminter•com <mailto:operator@bitminter•com>> wrote:
>
> 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
next prev parent reply other threads:[~2011-10-24 18:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-08 21:13 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
2011-10-24 11:24 ` Christian Decker
2011-10-24 18:10 ` John Smith
2011-10-24 18:55 ` Geir Harald Hansen [this message]
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=4EA5B485.9090300@bitminter.com \
--to=operator@bitminter$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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