We have moved to GitHub Issues
Created by Kristian Ravnevand 08 Apr 2015, 13:22:13 Updated by Sebastiaan Janssen 15 Dec 2015, 14:29:53
Is duplicated by: U4-6634
Relates to: U4-6398
Relates to: U4-6460
Hi again, tested 7.2.4 now, it's still an issue with Norwegian language:
A follow up on this issue.
-Changed the userLanguage in the database on umbracoUser table to "nb_no" instead of "no" (no is set when choosing "Norwegian" in Umbraco backend on a given user). -Result: Labels/captions from \umbraco\Config\Lang are translated!
-Labels from the dictionary are translated correctly using "Norsk", with language id "no" not "nb_no" -Labels from \umbraco\Config\Lang are translated correctly using "nb_no" as userLanguage not "no"
Hopes this clarify :-)
I have the same issue as you Kristian. To use a wokaround where I manually need to update a database table is not an option in my scenario.
My workaround was to rename the file /Config/lang/no.xml to /Config/lang/nb.xml
Labels from the dictionary are then translated correctly using "Norwegian (Bokmål) [nb]" Labels from \umbraco\Config\Lang are automatically translated correctly
(Note: If nuget auto package restore is enabled, the no.xml file will be downloaded on publish, resulting in a duplicate key exception)
Hope there will be a fix for this soon.
Still an issue in 7.2.5
Followup. Now using "no" gives correct translation on labels in Umbraco, the only error now seems to be that the \umbraco\Config\Lang\no.xml file has wrong culture:
And everything seems fine if you are using "Norwegian" in the Language dialog (attached image).
Instead of renaming the culture like you did Kristian, I renamed the file. I think this is more correct because "no" is not a valid culture name i think.
Backwards Compatible: True
Fix Submitted: Pull request
Affected versions: 7.2.4, 7.2.5
Due in version: 7.4.0