Support translation domain in 'kde' translation system

In applications translations can be looked up in the globally set
translation domain, but in libraries it is necessary to link every
i18n call to the library's own translation domain. A new code
generation option TranslationDomain= is added to enable this.
It has effect only if TranslationSystem=kde is set.

Added unit tests to check generated translation calls.

CHANGELOG: New code generation option TranslationDomain=, for use with TranslationSystem=kde; normally needed in libraries.
REVIEW: 123872

1 files changed, 8 insertions, 2 deletions

diff --git a/autotests/kconfig_compiler/kconfigcompiler_test.cpp b/autotests/kconfig_compiler/kconfigcompiler_test.cpp
index 77a31a3e..231e3c45 100644
--- a/autotests/kconfig_compiler/kconfigcompiler_test.cpp
+++ b/autotests/kconfig_compiler/kconfigcompiler_test.cpp
@@ -45,8 +45,11 @@ static CompilerTestSet testCases = {
     "test12.h", "test12.cpp",
     "test13.h", "test13.cpp",
     "test_dpointer.cpp", "test_dpointer.h",
-    "test_signal.cpp", "test_signal.h",
     "test_qdebugcategory.cpp", "test_qdebugcategory.h",
+    "test_signal.cpp", "test_signal.h",
+    "test_translation_kde.cpp", "test_translation_kde.h",
+    "test_translation_kde_domain.cpp", "test_translation_kde_domain.h",
+    "test_translation_qt.cpp", "test_translation_qt.h",
     Q_NULLPTR
 };
 
@@ -66,8 +69,11 @@ static CompilerTestSet testCasesToRun = {
     "test12",
     "test13",
     "test_dpointer",
-    "test_signal",
     "test_qdebugcategory",
+    "test_signal",
+    "test_translation_kde",
+    "test_translation_kde_domain",
+    "test_translation_qt",
     Q_NULLPTR
 };