Am Mittwoch, 19. November 2014, 18:46:28 schrieben Sie: > So again, what is necessary to get this done?
First step is to make kdevelop in kf5 translatable using the "normal" po files, then let's talk about json translation: * KDevelop has 20 translation catalogs, but none of them is used (no setApplicationDomain call, no TRANSLATION_DOMAIN defintion) * KDevelop uses ki18n (XGETTEXT) and qt5_wrap_ui. That is broken, a ki18n based system has to use ki18n_wrap_ui * KDevelop has 9 .rc files, 6 of them do not belong to an application with a KLocalizedString::setApplicationDomain call, therefore these 6 rc files need a translationDomain definition of the corresponding translation catalog in the header. * KDevplatform has 32 translation catalogs, but only one add_definitions(- DTRANSLATION_DOMAIN=\"kdevplatform\") line in the top level CMakeLists file -> translations in 31 catalogs are not used. * KDevplatform uses ki18n (XGETTEXT) and qt5_wrap_ui. That is broken, a ki18n based system has to use ki18n_wrap_ui * KDevplatform has 21 .rc files, none of them belongs to an application with a KLocalizedString::setApplicationDomain call, therefore all of them need a translationDomain definition of the corresponding translation catalog in the header. -- Burkhard Lück