http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c1 --- Comment #1 from Arvin Schnell --- The translation process is explained at https://github.com/yast/yast-translations/. Unfortunately it is not enough to debug it. One thing I noticed is that "rake pot" generates "yast2-apparmor.pot" where is likely should generate "apparmor.pot". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://trello.com/c/p7dRjh | |NT/1851-ostumbleweed-p3-106 | |5569-yast2-apparmor-with-in | |complete-german-translation Assignee|yast2-maintainers@suse.de |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c2 Goldwyn Rodrigues changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com, | |ke@suse.com, | |sbrabec@suse.com Flags| |needinfo?(sbrabec@suse.com) --- Comment #2 from Goldwyn Rodrigues --- Stanislav, There were some changes which went into yast-apparmor, but the translations were not done. Could you co-ordinate this? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c4 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #4 from Stanislav Brabec --- Well, this is a bit strange: y2makepot now creates two pot files inside apparmor module: yast2-apparmor.pot: 49558 bytes apparmor.pot: 1496 bytes It looks more like a bug than a feature. If it is intended, I'll split it in the Weblate as well. If not, please revert. If it was intended as rename to apparmor, then it is a nice cosmetic change, but it is unfinished. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|sbrabec@suse.com |rgoldwyn@suse.com Flags|needinfo?(sbrabec@suse.com) | |, needinfo? | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c8 --- Comment #8 from Goldwyn Rodrigues --- (In reply to Stanislav Brabec from comment #7)

Here you can see that your package uses two textdomains:

~/yast-checkout/apparmor> grep -r textdomain src src/include/apparmor/apparmor_ycp_utils.rb: textdomain "yast2-apparmor" src/include/apparmor/config_complain.rb: textdomain "yast2-apparmor" src/include/apparmor/helps.rb: textdomain "yast2-apparmor" src/include/apparmor/aa-config.rb: textdomain "yast2-apparmor" src/include/apparmor/apparmor_profile_check.rb: textdomain "yast2-apparmor" src/include/apparmor/profile_dialogs.rb: textdomain "yast2-apparmor" src/include/apparmor/capabilities.rb: textdomain "yast2-apparmor" src/modules/AppArmorDialogs.rb: textdomain "yast2-apparmor" src/lib/apparmor/genprof.rb: textdomain 'apparmor' src/lib/apparmor/settings.rb: textdomain 'apparmor' src/clients/apparmor.rb: textdomain "yast2-apparmor"

This is not good without knowing what you are doing.

Sorry, I did not know what the keyword is for. Now that I understood it, I will change all of them to consistent "apparmor" to be uniform with the the rest of the yast clients. I assume changing textdomain "yast2-apparmor" to textdomain "apparmor" should be enough. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c10 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #10 from Stanislav Brabec --- yast-apparmor textdomain fix: https://github.com/yast/yast-apparmor/pull/21 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c12 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Assignee|rgoldwyn@suse.com |sbrabec@suse.com --- Comment #12 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/cb7e955416ee00f1e6fa56c786f... Package should appear soon.

- Migrate all existing translations to the new translation domain. Done: https://github.com/yast/yast-translations/commit/eede2748a591413f90c1611846b... 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/8c559c1c0c8cddcc1d5da1f411f...

- 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.

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c14 Frank Kruger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #14 from Frank Kruger --- Should be reopened, since the issue still exists. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c17 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@suse.com --- Comment #17 from Stanislav Brabec --- For now, it was updated manually https://build.opensuse.org/request/show/557087 I guess that it was disabled intentionally, as it would generate many requests daily, 20MB changes data each. I have been told that the robot submits on each spec file version update. yast2-trans Git does not contain spec file, so this restriction does not apply. It is possible to add a spec file to the GitHub. But as 99% of yast-translations commits are done by robot, it is not clean, how to generate "version update" submits. I guess that automatic submit once or twice a week, or on request could work better. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c21 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lslezak@suse.com) | --- Comment #21 from Ladislav Slezák --- (In reply to Christopher Hofmann from comment #19)

What I do not know is, how the translations package build in OBS is triggered. Do you know, Ladislav?

As Stanislav commented, for the translation packages we need a bit different approach to avoid flooding OBS with submit requests... For now the packages must be submitted manually. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1065569 http://bugzilla.suse.com/show_bug.cgi?id=1065569#c23 Frank Kruger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #23 from Frank Kruger --- (In reply to Frank Kruger from comment #22)

(In reply to Frank Kruger from comment #18)

...

Created attachment 753343 [details] Still mixed languages

Using yast2-trans-de-84.87.20171214.b62b0550c-294.1.noarch from https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Tumbleweed/ almost solves the issue. There is one page still not translated (see attachment).

The issue is solved for Leap 15.0 with yast2-trans-84.87.20180301.762401304, but not for TW which still has version 20180208. Anyway, please feel free to close this bug.

With the update to TW20180407 and yast2-trans-de-84.87.20180406.01ef53789 the issue is solved. Closing as fixed. -- You are receiving this mail because: You are on the CC list for the bug.