When trying to use the multilingual external module to translate embedded fields, the embedded fields don't show up correctly. Does the module not support field embedding or is there a special way to make this work?
Related
I have an application built in AngularJS. I need to change the language from English to Arabic.
Is there any plugin to do this automatically that can change all my views from English to Arabic.
Plugins are not available to translate from one language to another. Angular's internationalization (i18n) tools help make your app available in multiple languages.
https://angular-translate.github.io/
According to docs, the app.json only allows to define one locale.
locale: "fr"
What happens if I have a multiple language application and I want users to select dynamically their language?
How can I include more than one locale ?
And then, how can I dynamically load the locale with just changing an Ext variable ? Something like:
Ext.setLocale("es");
ExtJs is not able to do this natively.
In my application I have solved this by defining a language class that works similar to gettext.
This allows me to have the code base in the default language with every string wrapped in the function Lang._('My text'). The translation is then done independently of ExtJs (In my case the translation interface is written in ExtJs, but the translation itself is independent).
I still cannot change the language dynamically. For this, I need to rerender the application in the browser. In my case, the translations are compiled into app.js, and therefore there is no need to reload app.js from the server.
I have only two languages, so this approach is OK. If you need to support many language, the best way is to load the translation string before rendering the application. To switch the language, you need then to load the translation and rerender the UI.
There is a good article about this on Saki's ExtJs site.
I have been given a project made in chinese language that uses nodejs, angularjs, and nodejs also provides restAPIs to mobile apps. I am required to give multiple language support in this project. I have planned to make json files for each language and load the file when required. But i am confused if it is the right way to do the project.
See the modules on npm:
https://www.npmjs.com/browse/keyword/multilingual
https://www.npmjs.com/browse/keyword/i18n
There are a lot of them - both specific ones for the framework that you're using and general one to be used in projects independent on the framework.
I am new to automation.My project is a multilingual website.Wanted to know how best can I automate it using selenium webdriver & Testng.
You can automate a multilingual website using Selenium Webdriver, there are few basic things you need to keep in mind:
If you are using locators which is using any textual content like
text(), starts-with() e.t.c - You need to handle them separately
for each language.
If you are using any text based validations, you need to take care of them as well.
I would suggest you to create a localization file for each language and load them according to the language you are using. In that localization file you can handle things like locators and assertions which uses text()
I am working on a multi-lingual website in Drupal 7. I installed the i18n module to translate the content on the website. However, I also have other site interface elements on the front-end part of the website like button texts, navigation links, etc that I would like to translate.
Is it really necessary to develop different themes per language? Or is there a more elegant solution to do this?
Thanks!
"Is it really necessary to develop different themes per language?"
No, it isn't. Every visual text can be translated, via the Translate interface-entry in the admin menu. If you write your own modules, templates and stuff, use the t-function to make the terms available in Translate interface or write your own po-files.
There is one issue of course: if the length of the terms in language A is too different to language B you can get in trouble with your layout. So test everything in depth and load different css styles if necessary.