-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
default-lang logic #3872
Comments
You might be right... AFAIK, *.md does not represent the default language, it is a fallback when the default language is not available as fallback for other languages. This behaviour can be overridden by setting custom language fallbacks using The colour of the languages indicates if for a supported language and *.md a dedicated file is available. Let's assume the following supported languages [de, fr, en].
Consider the following files:
Now consider the following files:
Hope this helps... |
@pamtbaau Thank you very much! Yeah it seems that this is some kind of "technical correct" but on the enduser-side a little bit confusing. Maybe I'm going to create a merge-request for that. Thinking of something like that: |
I'm a bit confused about the language settings:
I have two languages: de,en - de should be the default language.
Everything works so far, but when I look at the context info for a page, ‘de’ is shown in red, although this is actually the default language.
This is confusing for my customer because he thinks something is missing in the translations.
Config:
There are two files per folder:
default.md
default.en.md
If I change the settings and create a default.de.md, then ‘de’ is green but the default language is red.
Not any better.
Thanks for a quick tip.
The text was updated successfully, but these errors were encountered: