https://bugs.kde.org/show_bug.cgi?id=375385
--- Comment #4 from Burkhard Lueck <lu...@hube-lueck.de> --- (In reply to Wolfgang Rohdewald from comment #2) > Maybe using the Qt translations path might help. If you apply the following > patch to master and start kajongg from shell, it will print that path. For > me, that is > > Qt translation path:/usr/share/qt5/translations > Here it is (local installation of 5.6.1) /home/kdeframeworks/Qt5.6.1/5.6/Src/qttranslations/translations/ Use the dirs you get with "$ qtpaths --paths GenericDataLocation /home/kdeframeworks/.local5:/home/kdeframeworks/kf5/share:/usr/share" to search for locale/[LANG]/LC_MESSAGES/kajongg.po (or kajongg_qt.qm for qt translation system) and you will pick up the correct catalog - first user install, second system install > Is there a formal method to compute the correct KF5 .mo path from this one? > But that will probably only help if you also build qt5 in the same local > install folder. Is that the standard case when building kf5? > No, see above -- You are receiving this mail because: You are watching all bug changes.
