-
Friedrich W. H. Kossebau authored
Summary: To understand these changes best read the section "Connecting Calls to Catalogs" at http://api.kde.org/frameworks-api/frameworks5-apidocs/ki18n/html/prg_guide.html#link_cat Instead of adding #define TRANSLATION_DOMAIN "foolib" to lots of files, many projects simply use -DTRANSLATION_DOMAIN="foolib" with all sources, this seems most simple here as well at the respective places in the hierarchy, usually at the same place as the respective Message.sh script. While for the actual app it is recommended to call KLocalizedString::setApplicationDomain("fooapp"); instead of using the TRANSLATION_DOMAIN var, Calligra code has source files for plugins/parts and apps not cleanly separated. So using TRANSLATION_DOMAIN for all code, including app code, again seems most simple. Exceptions from this rule done for the few simple util apps though. Projects: #calligra:_3.0 Maniphest Tasks: T449 Differential Revision: https://phabricator.kde.org/D131
1776abc3