I added a new language and it is enabled. When I select it from the drop-down, it is not chosen for the application, it goes back to Default language. If I choose a language that comes standard (such as German), it works fine. Is this because I need to do all the translations for the new language before it will work? Or are there other steps involved?
7 Answer(s)
-
0
I also would like to know if a new language will be migrated to Production when using migrator.exe :).
-
0
hi,
-> First of all, tell what you are using (MVC+Jquery, Core Angular + .NET Framework version) Are you using XML localization files?
If you see the new language in combobox then it means you've successfully added it. To see what caused the problem, check the Web.MVC or Web.Host error logs. You might have added duplicate keys..
New language is being added to Configuration.Localization.Languages in PreInitialize of the module. There's no need for DB migration. (localizations are stored in XMLs) but when you edit localizations via Web page it saves it to DB.
You can see the localization doc here <a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Localization">https://aspnetboilerplate.com/Pages/Doc ... calization</a>
-
0
I'm using ASP.NET Core & jQuery. The new language I added is available in the drop-down. I see that it is also saved in the AbpLanguages table. I added a target value for the first few texts, and also see that these are saved in the AbpLanguageTexts table.
When I select the new language from the drop-down, it doesn't get selected.
Is there a step I am missing? Do I need to add all the target vales first? Do I need to edit some xml files?
-
0
I can also add that I downloaded the latest version of aspnetzero last night, and I installed it on another PC. I am not working on the same instance as when I posted this back in April. If you don't understand my problem, it is simple to recreate by just adding a new language, then select it, and see what happens :).
-
0
Hi,
<ins>LanguageName property:</ins> The name of the language must be a culture code from this list. This matches to the ApplicationLanguage's Name property but is not a forced foreign key to make it independent from the language entry. IApplicationLanguageTextManager handles it properly
See the doc: <a class="postlink" href="https://aspnetboilerplate.com/Pages/Documents/Zero/Language-Management">https://aspnetboilerplate.com/Pages/Doc ... Management</a>
-
0
I did add a language from the list. For me, this worked after cleaning up browser history.
-
0
cool!
