From: Wladimir <laanwj@gmail•com>
To: Geir Harald Hansen <operator@bitminter•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.7 release planning
Date: Sat, 11 Aug 2012 20:56:09 +0200 [thread overview]
Message-ID: <CA+s+GJDU8Y8TuDVwt6S91Eppps5d_NfbKGgMiFB6ktNHPSHpcw@mail.gmail.com> (raw)
In-Reply-To: <50268BB0.8080001@bitminter.com>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Geir,
There were a lot of subtle changes to the English base messages such as
capitalization or punctuation, I know this is pretty annoying for
translators. It is a pity that there is no way to update all translations
when the English base message changes but not significantly enough to
trigger re-translation. I've looked but Transifex does not have that option.
Also there were new duplicated strings:
>
> "Verify a message to ensure it was signed with a specified Bitcoin address"
> "Sign a message to prove you own a Bitcoin address"
> "Clear &All"
>
Duplicate strings are not a problem. Some strings are used multiple times
in the program, and thus appear multiple times in the translation. This is
because there are cases in which a string that is the same in English is
translated differently in another language based on the context.
At least Qt translator fills duplicates in automatically, with the option
to change them if desired. I'm not sure about Transifex but I've heard it's
the same there.
>
> These two seem odd:
> Use UPnP to map the listening port (default: 0)
> Use UPnP to map the listening port (default: 1 when listening)
>
The default depends on compiler flags, hence the two messages. I suppose
the message could be split up, so that "Use UPnP to map the listening port"
is factored out.
Let's do this after 0.7.0 release though, otherwise all the translations
for those messages will be broken again. There should be no more message
changes before the release unless there is a very good reason.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1976 bytes --]
next prev parent reply other threads:[~2012-08-11 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 16:43 Jeff Garzik
2012-08-02 16:45 ` Jeff Garzik
2012-08-02 18:00 ` Gavin
2012-08-02 17:17 ` Luke-Jr
2012-08-11 16:43 ` Geir Harald Hansen
2012-08-11 18:05 ` Luke-Jr
2012-08-11 18:32 ` Wladimir
2012-08-11 18:56 ` Wladimir [this message]
2012-08-12 7:59 ` Geir Harald Hansen
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=CA+s+GJDU8Y8TuDVwt6S91Eppps5d_NfbKGgMiFB6ktNHPSHpcw@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=operator@bitminter$(echo .)com \
/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