-
Notifications
You must be signed in to change notification settings - Fork 33
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
i18n workflow: force compile fuzzy #103
Comments
Can we check the status of this issue?
|
|
I think earliest end of September I can investigate that. |
wrt. point 3:
wrt. point 2:
wrt. point 1: I will try go through all packages and check for the |
based on this: have fuzzy:
no fuzzy but likely no problem:
no fuzzy and more likely a problem:
no fuzzy and maybe a problem:
not checked
|
wrt 'no fuzzy but likely no problem:' within each repo searched for result:
|
Additionally found: https://github.com/inveniosoftware/cookiecutter-invenio-module/blob/6decff43538c9e317175bfed33878fe7b0843a53/%7B%7B%20cookiecutter.project_shortname%20%7D%7D/setup.cfg#L80 Conclusion:
|
All PRs are merged. For the moment we should be good. Let's close it. @zzacharo |
In order to compile fuzzy marked strings, we need to force it.
todoso we have to add this line
use-fuzzy = True
to the[compile_catalog]
section ofsetup.cfg
file.This should be added to the following modules:
Close related issue #inveniosoftware/invenio-app-rdm/issues/230
The text was updated successfully, but these errors were encountered: