In general, the internationalization (i18n) process starts from backend API libraries or resource bundles and ends on the user interface (UI) page — web UI is only responsible for the i18n stuffs’ representation. In traditional processes, both localization and i18n formatting are decoupled from contextual UI environment after multilayer compilation. Translators or linguists can’t get context information for the source strings which leads to problems such as increased complexity and difficulty ensuring the translation quality and finding UI strings in resource files. In most cases, it is impossible for translators or linguists to access products’ portals for localization, screenshots can be referred to but are still difficult to reflect real UI pages in the product environment in real time. The contextual translation online editor presented with algorithms intends to provide a new solution to solve these legacy problems.
Takeaways: Attendees will hear a solution about how to provide context information to translator and reviewer.