-
Notifications
You must be signed in to change notification settings - Fork 95
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
Skosmos UI loads in Arabic #1453
Comments
General
Response Headers
Request Headers
|
What languages have been configured in |
@osma we have the default value:
|
This is the code that selects the language. The choice is informed by
It looks like 4. happens, even though at least 3. should work in this case, as the request included an Accept-Language header which should have matched But I think these response headers are suspicious:
These are not typical Skosmos/PHP/Apache response headers. Why is |
Yes there's a proxy in front. We also have this in the config: skosmos:language "en";
skosmos:defaultLanguage "en"; Assuming Skosmos/controller/WebController.php Line 106 in a6f1795
If the |
These are vocabulary specific settings. They are not relevant in this case, since the request was for the front page, outside of any vocabulary.
That's a good point. I think you should use |
Right. But the lang codes are passed to the I'm guessing some sort of mapping has to happen between the two lang code conventions. |
I don't think there exists a PHP convention for language tags. Mostly the So the |
PHP locale names is what I meant :)
In this case the |
You are probably right. I was looking at config.ttl.dist which is the default config for non-docker users. It does not have these language settings. Can you verify that the problem is resolved if you change the underscores to hyphens in your config? |
Will try :) |
Some users are reporting that the Skosmos UI loads in Arabic by default, without having chosen that language.
Will try to investigate and gather more information.
The text was updated successfully, but these errors were encountered: