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

Fixing the use of spanish translations #159

Merged
merged 1 commit into from
Oct 29, 2019
Merged

Fixing the use of spanish translations #159

merged 1 commit into from
Oct 29, 2019

Conversation

fdns
Copy link

@fdns fdns commented Aug 14, 2019

By default, ubcpi use the django language for spanish es-419, instead of es_419, so the spanish translations are not used.

This renames the es_419 folder to es-419, fixing the translation for the spanish language. I don't know if this is the best way, and if someone has a recommendation we can work on it.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.707% when pulling 3acf81d on fdns:eol into 998a52f on ubc:master.

@xcompass xcompass merged commit 412c114 into ubc:master Oct 29, 2019
kitsook pushed a commit that referenced this pull request Jan 13, 2020
There is a problem with the translations (see #159)

The translations catalog(ubcpi/static/js/src/translations.js) is generated using locale names and translations from transifex.

The django.utils.translation.get_language() function returns the language code (i.e. es-419), but since in the catalog we are using locale names(i.e. es_419), the strings are not being translated as expected.

With this change, now we are using the locale names and it works fine. I tested this with spanish
kitsook added a commit that referenced this pull request Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants