Category: i18n

Developers can easily localize country names using CLDR (Common Locale Data Repository), saving valuable translation resources. However, there are a few important considerations that developers should be aware of. When developers encounter a situation where they realize the product’s UI displays a lengthy list of country names in English that needs to be localized into…

In i18n world, long text and flexible UI that can handle it is a major task that almost every companies and products are facing and need to resolve. For the web, there are already so many good solutions, and most them provide high quality. Here I have done some CSS and JS works that resolves…

In the i18n world, Pseudo Loc Test is one of the early stage methods that gives some benefits.  With the ECMAScript 6, we already have a good number of npm packages that we can simply install and initiate on our applications. Most of them support the Latin 1 & 2 character set, but not many…

Method  1 – starting with develop branch This is an actual structure that most dev teams currently have, but mostly managed manually. Commiting/creating PRs/merging the English contents are still manual developer activities, but committing(delivering) translation files, notifying related stakeholders will be automated at the end, and these are all the tasks that the automation actually…

Consolidating English content You can automate the process of collecting and centralizing content updates being worked on in individual branches into a single location in various ways. The complexity of automation depends on how the developer proceeds with front/backend work for a specific feature, and how they go through the process of QA and production…