Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix translations for EULA spoke related strings #109

Merged

Conversation

M4rtinK
Copy link
Contributor

@M4rtinK M4rtinK commented Sep 23, 2020

There were two strings that were not translated due to
wrong translation context - the Licensing category name
and the EULA spoke status message. In both cases the strings
were just marked for translation with N_() only to be translated
with _() from Anaconda with the "anaconda" context instead of
the correct context of "initial-setup" or translated with _()
imported from Anaconda.

For the category name, just switch to Initial Setup localization module
and translate the category name directly.

For the EULA spoke title, use workaround similar to one used
by the OSCAP addon - see bug 1673071 for more details.

Resolves: rhbz#1814952

@pep8speaks
Copy link

pep8speaks commented Sep 23, 2020

Hello @M4rtinK! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2020-09-23 13:49:11 UTC

There were two strings that were not translated due to
wrong translation context - the Licensing category name
and the EULA spoke status message. In both cases the strings
were just marked for translation with N_() only to be translated
with _() from Anaconda with the "anaconda" context instead of
the correct context of "initial-setup" or translated with _()
imported from Anaconda.

For the category name, just switch to Initial Setup localization module
and translate the category name directly.

For the EULA spoke title, use workaround similar to one used
by the OSCAP addon - see bug 1673071 for more details.

Resolves: rhbz#1814952
@M4rtinK
Copy link
Contributor Author

M4rtinK commented Sep 23, 2020

So this is how it looked before (licensing related strings are not translated):
initial_setup_broken_translation_hub

This is how the fixed screen looks like:
initial_setup_fixed_translation_hub

Copy link
Contributor

@VladimirSlavik VladimirSlavik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thank you!

Copy link
Member

@jkonecny12 jkonecny12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@M4rtinK M4rtinK merged commit d91e35d into rhinstaller:rhel8-branch Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants