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
Back to app not translated #1622
Comments
Nice catch! I clearly didn't think about that at the time. Would you be able to open a PR for this? |
Is there a better way than Google translate to come up with the required translations? |
Unfortunately, this is basically what I'd been doing. The other option is to add them in English to all of the translation files, but that's not great either. In general, I've found people will open PRs to fix translations if they're not very good and so I've been relying on that. |
Adding in English would prevent tools that spot missing translations from working so I would avoid it as an option. |
How about this plan:
I'm not sure how a missing translation would affect people though. I just tried running the example app in Spanish and got an error Thoughts? |
I think working with errors is an acceptable trade off, to encourage translation contributions. |
Should probably have a README entry saying not to expect locale files to be perfect. |
So @pablobm, I also had the same issue in portuguese, it is due to Kaminari We have 2 options:
|
@betelgeuse - I agree with adding that note to the README. @edimossilva - From what I see on the Kaminari repo, they don't appear to provide translations for any language. It looks to me as though they expect each application to provide their own. In this case, we'll have to provide it ourselves. |
@pablobm, so should I create another issue related to kaminari translations? |
@edimossilva - Yes, I think that opening a separate issue would be the right approach. |
Use administrate with locale different from English
Not being able to translate "Back to app"
master of administrate
The code added in #1376 is missing i18n keys.
The text was updated successfully, but these errors were encountered: