Django, i18n, problems with translation after changing LANGUAGE_CODE - python-3.x

I have created a multilingual website using Django i18n. But later I needed to change the default language (before LANGUAGE_CODE='ru') to one of those that were in the LANGUAGES configuration setting (now LANGUAGE_CODE='uk').
After that, when the user opens this site and selects the language 'ru', the translation does not work correctly. The models translate correctly, but the templates remain in 'uk'.
At the same time, when the user opens this website and selects the language 'uk' or 'en', the translation works without problems.
Tell me please, what is the reason and how can I solve this problem, or at least where it would be reasonable to search?

The problem was that the translation from Russian into Russian was not completed, so the translation from Russian into Ukrainian was taken.
While the default was Russian, no translation was made at all, since there is no translation to this node in the default language. And when it became Ukrainian, in the absence of a translation, translation into Ukrainian began to be used.

Related

Android Studio use one specific language for all other than default

How do I set Android Studio project to use English translation for all locales other than the default language? If I have values/ and values-en/ directories, I want all locales other than the default to use the English translation.
I think you should a bit change your mind and think that all locales should use English translation but in one case (let's say for Spanish) should be no-English. Set values as your English directory and values-xxx for this as you said default case.
If a guy would have a phone with this default locale, he would have no-English translation, otherwise it would be translated to English.
Hope it will help

Is Android device's locale based solely on Language setting?

If the device chooses French as the language, will the locale automatically set to French as well? Or does it depend on user's current location?
For iOS, language and region are separate settings while in Android, seems like we only get to choose Language but not the region.
Comparison:
Android - Chooses French language, locale becomes fr-FR
iOS - Chooses English language, French region, locale becomes en-FR
For Android is there any other way to retrieve device's region?
I have been Googling around but couldn't find a good source of information on this topic yet.
In Android you can select Portuguese (Portugal) or Portuguese (Brasil) which translates to pt-PT and pt-BR. In this case there are two different languages, which I personally find it redundant, because the better way of handling this would be to separate languages and regions.
However you can programmatically change the language and region, by setting:
new Locale("pt", "PT");
You can read more about programmatically changing the language here:
http://gunhansancar.com/change-language-programmatically-in-android/
http://www.sureshjoshi.com/mobile/changing-android-locale-programmatically/
or anywhere on Stackoverflow :) there are lots of articles written about it

Why translation in liferay doesn't work - asset publisher

I start to use Asset Publisher in liferay. I added an article with some text in english. Then I want to add translation but there was no my language. So I added into portal-ext.properties next lines to enable more languages.
locales.enabled=ca_ES,zh_CN,en_US,fi_FI,fr_FR,de_DE,iw_IL,hu_HU,ja_JP,pt_BR,es_ES,cs_CZ,sk_SK
My language then appear, but the problem is the translation doesn't work. Not to my language, it doesn't work to any other languages. All it did is it just changed the font of the text. That's all. Can you help me and tell me what should I do? Thanks a lot.
Seems to be solved on the Liferay forums: You'll need to provide the translation yourself. Liferay offers the functionality to enter translated articles, but it doesn't translate the articles itself.
If I may add a personal remark: "...luckily". Automatic translation is not that good.

How to translate XPage application "on the fly"?

On IBM's website, I found a nice tutorial about localization of XPage applications. If you look in the comments, you'll see I added a couple before figuring out how to make it work.
For the fun of it, change the language option to French, and take a look at my comments below. My comments were translated! Not super well, but I was able to correct the French text, without changing the original English text. Based on the French, I don't believe the original wiki page was translated, either.
With localization, you can change the properties files, reimport them, etc... but what about the comments or text entered by users? Does anyone know how IBM did this?
Any insight would be greatly appreciated.
Translations on the IBM wikis are machine translations that use n.Fluent from IBM Research for real-time translation. See the wiki help for details and the IBM developerWorks group for n.Fluent for more info.
Thanks, Doc! In my work group, we have offically certified translators who work with English, French, Spanish, Russian, Chinese and Arabic. They'll be able to translate all the programmatic terms, and we'll look into the Google API if we need to modify a lot of user entered text in the applications I'm building.

using different themes for different languages with i18n in drupal 6

I am developing a website which has both English and Arabic versions. I have installed Arabic language and the i18n module, which is working fine and I am able to add Arabic translation for the English contents.The URL prefix 'site.com/ar' is also working fine.
Since Arabic is a right-to-left language I want to show different theme for the Arabic content,which contains images with Arabic text etc.(a flipped or mirror version of the English theme with Arabic text).
Is there any good solution for this scenario where site.com/ar should show the Arabic theme and site.com/en should show the English theme?
Thanks,
You may be able to use the Sections module to switch the themes, based on the path.
I'm not sure if this would help with right-to-left languages, but you may also consider adding body classes based on the language and using those to modify the theme.
You may also find Notes on Setting up a Drupal Site for Internationalization and/or Internationalization & RTL Drupal Theming helpful.

Resources