-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
Problem with i18n when page is not translated to all target languages #2529
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@guillerodriguez did you ever figure anything out? We had pages where I18n isn't falling back to using the default translations when they are missing. |
No, unfortunately never managed to figure out what’s wrong..
El lunes, 23 de mayo de 2022, Jarrett Lusso ***@***.***>
escribió:
… @guillerodriguez <https://github.com/guillerodriguez> did you ever figure
anything out? We had pages where I18n isn't falling back to using the
default translations when they are missing.
—
Reply to this email directly, view it on GitHub
<#2529 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAS67KGZ4D3K5Q2CELMHOWLVLPBJNANCNFSM5NAKXHKQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Guillermo Rodriguez Garcia
***@***.***
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Do not close. |
@guillerodriguez is this still valid after latest merged pull requests? |
hi @guillerodriguez did you have a chance to check it out 🙏🏼? Thank you so much in advance! |
Expected behavior and actual behavior
I have a Middleman site which is translated to 4 languages: en, es, de, fr. i18n config is as follows:
For most pages there is a single source file which lives under source/localizable; i18n-specific strings are translated via the
<%= t('key') %>
helper. This works fine.For some pages, though, there are different language specific versions.
If a language-specific version is available for all languages, then this works fine as well. Let's assume I have:
If I build the site then all works as expected.
However if the language-specific version is missing for some languages, then the "default" version seems to be used for all languages. Let's assume I have:
When I build the site, I see that the default version is used for French and German (good) but also for Spanish (bad)
Not sure if this is related but in the build log I see:
The Spanish page is being processed twice -- but both times with the wrong content (the content for the default language).
Steps to reproduce the problem (from a clean middleman installation)
See above.
Additional information
The text was updated successfully, but these errors were encountered: