You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2022. It is now read-only.
Between the two options, I would prefer the having untranslated contents first. Interested users might report them in the issues or, even better, submit a PR. In Beautiful Hugo's UI text for its Staticman integration, the developer who submitted the PR had copied the English UI text into i18n files for some other languages at first. Despite the missing content, the framework has been established. This gives way to my PR https://github.com/halogenica/beautifulhugo/pull/231/files.
Another option would be to create something like this at the top of the page (not real syntax here):
{{ if not .Page.Lang .Site.Lang }}
{{ i18n | "Hello user, this page has yet to be translated into your language." }}
{{ end }}
And maybe allow that to link to make PRs, like you suggest.
pacollins
changed the title
Should multilingual sites populate non-translated content?
DISCUSSION: Should multilingual sites populate non-translated content?
Aug 22, 2019
pacollins
changed the title
DISCUSSION: Should multilingual sites populate non-translated content?
ENHANCEMENT: Populate non-translated articles with default language and add "page not translated" banner.
Jan 24, 2021
pacollins
changed the title
ENHANCEMENT: Populate non-translated articles with default language and add "page not translated" banner.
FEATURE: Populate Non-Translated Articles with Default Language; Add "Page Not Translated" Banner
May 6, 2021
I am reading through the hugo functions and noticed lang.Merge which allows you to populate any non-translated articles with the default language:
Any thoughts on this? A site that loses content when you change languages is odd, but so is thinking everything is translated.
The text was updated successfully, but these errors were encountered: