Untranslated strings in GUI #8900

I'm using the pt-br interface and some texts are appearing in English. v 0.13

According to the release process we are only syncing translation from transifex before every rc.

But these texts alread translated

@FabioCarpi Can you give us some example strings, or screenshots?

I think he refers to the recent translations on transifex, which are not yet fetched: https://www.transifex.com/user/profile/FabioCarpi/#activity

They are going to be included in https://github.com/bitcoin/bitcoin/releases/tag/v0.13.1rc1 which is not out yet, so closing the issue for now.

No @MarcoFalke. Are windows that always have translation, but are not showing translated after the last updates

Hmm, in this case I am going to quote @fanquake

@FabioCarpi Can you give us some example strings, or screenshots?

@MarcoFalke as requested

I can confirm the issue. Somehow the tr()-strings in AddressBookPage are not getting translated.

Confirmed: The tr() strings in addressbookpage.cpp don't even end up in the translation - not even the English one.

$ git grep "Choose the address to send coins to"
src/qt/addressbookpage.cpp:        case SendingTab: setWindowTitle(tr("Choose the address to send coins to")); break;

The reason for this is that that cpp file does not end up on the command line to lupdate in make translate.

Many of the cpp's don't, because of:

if ENABLE_WALLET
BITCOIN_QT_CPP += \
  qt/addressbookpage.cpp \
  ...
endif

Wallet was disabled. Maybe that is the problem: make translate still works when you build without wallet support, however the strings from the .cpp files will not be included.

It is possible that the system I use for generating the translations to upload doesn't have the wallet enabled. I had some issues here on Xenial and had to fall back to a Trusty VM. This could be the cause of the issue.

Should be fixed by #8911

Yes - I've just pushed a commit to 0.13, 633c4a1f3690152bdda4b0ac7bcfde22c237183e, which when picked up by Transifex will enable the wallet messages to be translated again. Sorry for the mess.

I am wondering if it is possible to "translate" those "new" string on transifex by a script.

Just saying, in version 0.13.1rc2, the problem continues...

@FabioCarpi Unfortunately the translated string "fell out" of the transifex translation system. There may be a way to read them from the transifex cache and submit them via the api in an automated manner.

I am not sure if @luke-jr has some script for the transifex api. (I remember this was up for discussion when changing the product name to as few places as possible, but I don't recall if a script emerged from that...)