qt-locales should be resynced with transifex #919

nomnombtc opened this Issue Mar 5, 2012 · 12 comments


None yet
5 participants

nomnombtc commented Mar 5, 2012

The german bitcoin-qt translation is currently incomplete (missing translation for sign message for example)
and it contains some garbage characters. The translation on transifex seems to be much more complete.

Diapolo commented Mar 14, 2012

I worked on the german translation recently and it would be great to get it pulled into the next official release. One thing that is pretty hard to translate is this here: "Be careful to only sign statement you agree to with full details, as phishing attacks may try to trick you into signing access to them." I don't get it's meaning ... so german translation needs an update here (perhaps a native english speaking person can explain what is meant here). And I think the message displayed in RC2 is much longer, than what can be translated via Transifex!?


sipa commented Mar 14, 2012

@Diapolo: compare it to putting your signature (in ink) on a text document. The feature can be used to send a message to a merchant, while proving you are the one who paid him. It could also be used to get access to a site by signing some text they send you with a key that was used to pay them.

The general message here is: pay attention to what you sign.

Diapolo commented Mar 14, 2012

Thanks sipa, I'm sure the current translation is much better than before for the signing feature now. I'll keep thinking about it and will update the translation as needed :).


TheBlueMatt commented Mar 15, 2012

@tcatm usually does the pulls right before full releases (not maintenance releases like 0.5.2 and 0.5.3, though 0.5.1 was not a maintenance release). Expect the new translations to show up in 0.6.

Diapolo commented Mar 15, 2012

I would like to propose a change for translation handling and think it would be a good idead to pull translations even into RC versions. It's easier to read (and update) a translation in the BC client itself, because only there you see the full context of the translation and it's meanings.

tcatm commented Mar 15, 2012

@Diapolo: Are you willing to do that or create a script that will aid with fetching new translations, figuring out whether they are ready to be merged (i.e. not too many phrases left untranslated) and resolve conflicts?

Diapolo commented Mar 15, 2012

I did not want to offend anyone as I simply don't know how much work needs to be done to prepare the translations. But if it's achievable in a defined period of time, I would be glad to help (at least for the german translation).

Diapolo commented Mar 15, 2012

I worked with Github before (I'm the diakgcn kernel writer), but I'm really no expert and don't want to mess up things, so as I said I can help but I can't take over that whole process. I had a hard time learning that git stuff and trying to resolve merge conflicts, which did not always work like it should ;).

Diapolo commented Mar 16, 2012

I read through https://github.com/bitcoin/bitcoin/blob/master/doc/translation_process.md, but I can't start working with this. I'm on Windows and have no clue how to do an lupdate. I saw that there is a Transifex client for Windows, but that comes after the lupdate. I definately need more help, before I can start helping the whole project ... a more detailed how-to would be really a great thing!

I guess I need to fork bitcoin, setup a local repo and all that stuff. Afterwards I need to put the Transifex client somewhere on my system so that I can pull the translations into my local repo, but that's unclear to me ...

Diapolo commented Mar 16, 2012

This one can be closed now, as the latest Transifex translations got merged into the project. At least I'm now able to contribute to the german translation and can create pull-requests for it, so that's a good starting point :).

Diapolo commented Apr 1, 2012

The current translations are in 0.6 final so this can be closed.

@sipa sipa closed this Apr 1, 2012

suprnurd pushed a commit to chaincoin-legacy/chaincoin that referenced this issue Dec 5, 2017

Merge #919: Add option to hide warning about low keys
b4647b5 Add option to hide warning about low keys before creating autobackup (but still warn if backup fails)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment