The SE Warningbrowser generates mixed errormessages : ------------------------------------------------------------------------- If sie denken, dass es wine-preloader standardmässig erlaubt sein sollte, mmap_zero Zugriff auf memprotect zu erhalten. Then sie sollten dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Do zugriff jetzt erlauben, indem Sie die nachfolgenden Befehle ausführen: # grep wine-preloader /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp ------------------------------------------------------------------------- better translation: ------------------------------------------------------------------------- Wenn Sie denken, dass es dem <i>wine-preloader</i> standardmässig erlaubt sein sollte, mmap_zero Zugriff auf memprotect zu erhalten, dann sollten Sie dies als Fehler melden. Um diesen Zugriff zu erlauben, können Sie ein lokales Richtlinien-Modul erstellen. Sie erlauben den Zugriff, indem Sie die nachfolgenden Befehle ausführen: # grep wine-preloader /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp ------------------------------------------------------------------------- It's not easy to generate such things automatically in a perfect translation. Maybe more parts have to be changed to accomplish it.
Is this a bug in the German translation itself, or the way the translations are handled by setroubleshoot?
i think both, it's not so well formulated and mixed with english.
All strings are translated on the Zanata platform. The English strings "If" and "Then" are correctly translated. It seems that they are just not applied by setroubleshoot. You can see here, that the "If" and "Then" strings are translated in the setroubleshoot repo: https://pagure.io/setroubleshoot/blob/master/f/framework/po/de.po#_214 https://pagure.io/setroubleshoot/blob/master/f/framework/po/de.po#_609 But I don't know why these strings aren't applied.
Any news on this?
It was fixed in the latest setroubleshoot and setroubleshoot-plugins - https://pagure.io/setroubleshoot/c/98c2ad7c16be9b79f880964b3ccfbfbc5bb4ed58?branch=master Updated string were uploaded to fedora.zanata.org And there are few other improvement in the latest release which makes more strings in sealert browser translatable. I'd like to push these changes to Fedora 27 but we are after String Freeze so it should stay only in Rawhide/Fedora 28
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This issue is being fixed in Fedora 28.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.