Hello Burkhard,<br>thanks for your effort.<br><br><div class="gmail_quote">On Wed, Sep 16, 2009 at 4:13 AM, Burkhard Lück <span dir="ltr"><<a href="mailto:lueck@hube-lueck.de">lueck@hube-lueck.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hallo,<br>
<br>
I found some buggy i18n calls in mymoneygncreader.cpp with missing arguments,<br>
relevant lines as attachment.<br>
<br>
There is "#define i18n QObject::tr" in mymoneygncreader.cpp, I hope this will<br>
never be used, cause it does not works with translations from the kde svn<br>
archiv and will explode the i18n system, reason see<br>
<a href="http://techbase.kde.org/Localization/Concepts/Transcript" target="_blank">http://techbase.kde.org/Localization/Concepts/Transcript</a>.<br>
Qt's "tr" and KDE's "i18n" have to be strictly seperated and need to be<br>
extracted to different catalogs. The catalog with the "tr" - messages needs a<br>
trailing "_qt", e.g. kmymoney_qt.pot<br>
<br></blockquote><div>Tony, this being the gnc reader, can you take a look at it?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The text in the startup screen is not localized, a possible solution you find<br>
here:<br>
<a href="http://techbase.kde.org/Localization/Concepts/Non_Text_Resources" target="_blank">http://techbase.kde.org/Localization/Concepts/Non_Text_Resources</a><br>
<br></blockquote><div>I will look into it, and coordinate with whoever is need.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There is a manpage in kmymoney/doc/kmymoney2.1, but it is not included in the<br>
kde i18n tool chain.<br>
Do you want me to do that?<br></blockquote><div><br>Thanks, but not yet, because it is really outdated. I will look into it first. Can I get in touch with you to get it into the i18n tool chain later?<br> <br>Again, thanks a lot.</div>
</div>I keep an eye on the docs and I noticed you have been fixing a lot of bugs there.<br><br>Regards,<br>Alvaro<br>