Comment # 12 on bug 1065569 from Stanislav Brabec

It should work with yast2-apparmor-4.0.2 and yast-translations providing a new
textdomain apparmor instead of yast2-apparmor.

Closing, as now it should be only a translators' task.

However there are still strings to be translated:
https://l10n.opensuse.org/projects/yast-apparmor/master/

> - Update yast-translations package accordingly.
Done:
https://github.com/yast/yast-translations/commit/cb7e955416ee00f1e6fa56c786fc2f96ccf26e18
Package should appear soon.

> - Migrate all existing translations to the new translation domain.
Done:
https://github.com/yast/yast-translations/commit/eede2748a591413f90c1611846b7b78686d0f753
However there is no common strings between the former yast2-apparmor before
split and new apparmor before merge, so all new strings are fuzzy matches only.

> - Update configuration of https://l10n.opensuse.org/projects/yast-apparmor/master/ to point to the new translation domain.
Done.

> - Remove special handling for textdomain starting by "yast2-" from update-tool.sh and weblate-functions.inc from yast-translations/tools.
Done:
https://github.com/yast/yast-translations/commit/8c559c1c0c8cddcc1d5da1f411fc8556b96170d7

> - And add the new contents of the yast-apparmor component to the "SUSE Linux Enterprise 15" component list. It will be processed by contracted translators.
Done.