... HelpMessageBox class, as tr() does not work that early in the code
I was wondering, why for example the translation for "Usage:" did not work, althoug it was in the (in my example) de language file. I found out that using the _() function does it's job and so I added 2 new functions in init.cpp to be able to get the strings translated and the translations used.
This needs an additional bitcoinstrings.cpp update!
This is not the right way to solve it. I moved the ui-specific stuff out of init.cpp for a reason. This bounces strings around all over the place.
As this is a ui-only problem, please solve this without changes to the core.
Note that _ is defined in ui code, you can call it from there. However, it simply calls tr, so if _ works, so does tr!
tr() did not work, please try it. Even if the fix is not what it needs to be, there is a problem. And tr() vs. _() is for sure a difference, because _() shows up in bitcoinstrings.cpp, while this is not true for tr().
Strings that are defined in src/qt/bitcoin.cpp should not show up in bitcoinstrings.cpp but end up in the .ts through the normal translation path.
Did you try to verify the problem? Before we start a discussion battle I would like to know if I found a bug or did something wrong in my local build ;).
Try to change tr("Usage:") into something stupid like tr("Pig:"), what I say is that even after a translation the word "Usage:" is used in it's untranslated form.
I think I know why tr doesn't work in our new class: Q_OBJECT is missing.
It's all fine, I seem to have missunderstood what you were trying to say :). I'm glad it's fixed!