EnglishArabic I live أسكُن
During a webinar on Dynamic Language Teaching through Pressbooks, Arabic teachers pointed out some issues with the alignment of RTL content. Wonder if it's a broad PB issue, if it's a specific module used (say, Tablepress?), or if it's a textbook design issue. H5P activities from another book were deemed better.
You may want to customize validation messages (or give support to i18n).
Organization of Locale Files
Ultimately though, I'd say the file structure that makes the most sense for your i18n workflow is the best one.
There's a few other questions on StackOverflow regarding how to structure YAML files for i18n, and I don't think there is a 'right' answer to your question. If it works for you, then great! I would say that any answer you get will be completely subjective, and more about i18n and translation management rather than anything specifically to do with the Rails way.
count, where available, can be used for pluralization if present:
WordPress 5.0 introduced the wp-i18n JavaScript package that provides the functions needed to add translatable strings as you would in PHP.
The custom id is persistent. The extractor tool does not change it when the translatable text changes. Therefore, you do not need to update the translation. This approach makes maintenance easier
key point! it allows English speaking site without worrying about translations at all, and keeping translation unit keys constant over time even if the English text is changing
The Angular extraction tool preserves both the meaning and the description in the translation source file to facilitate contextually-specific translations, but only the combination of meaning and text message are used to generate the specific id of a translation. If you have two similar text messages with different meanings, they are extracted separately. If you have two similar text messages with different descriptions (not different meanings), then they are extracted only once
important - this is how the 'keys' for the translation person are extracted - what determines the singularity of the translation item.
You need to build and deploy a separate version of the app for each supported language
key point!
The CLI imports the locale data for you when you use the parameter --configuration with ng serve and ng build
See sample i18n app (link in the beginning of this document). Basically, in package.json: "scripts": { "start": "ng serve", "start:fr": "ng serve --configuration=fr", "build": "ng build --prod", "build:fr": "ng build --configuration=production-fr",
localised to different regional contexts and curricula
Local appropriation could lead to something interesting. Typically, though, localisation is a top-down process: take a culture-specific item, strip it down to its bare essentials, make it available in other cultural contexts, add a bit of local flavour.
まぶた）
Testing a highlight on Ruby text.
Highlight is meant to wrap this image:
Highlight is also meant to include the super-script hiragana characters: まぶた
Actual highlight includes the hiragana characters "まぶた" as well as "）"