1 views collected around this technical thread.
This tutorial demonstrates how to install the AirPower package, create a custom i18n class, add default and English language packs, register languages, and use type‑safe i18n tags in a Vue3 frontend, while also outlining the broader AirPower ecosystem and future plans.
This article introduces the auto-i18n-translation-plugins, a framework‑agnostic Vite/Webpack plugin that automatically extracts Chinese text from source code, replaces it with hash‑based $t calls, generates language packs, and seamlessly translates new or incremental strings using configurable translators such as Youdao or Google.
The article introduces auto‑i18n‑translation‑plugins, a Babel‑based automatic internationalization plugin for frontend projects that works with Vite and Webpack, detailing its features, installation, configuration options, translator setup, usage examples, and best practices for generating multilingual JSON translation files without modifying business code.
This article provides an in‑depth overview of internationalization and localization for web applications, covering concepts such as language codes, locale handling, date and time formatting, number and currency formatting, text direction, layout adjustments, and practical JavaScript Intl API examples with code snippets.
The Cloud Music overseas team built the Qianyu Platform, an automated i18n system that replaces manual copy handling with Babel‑based key generation, auto‑uploads, CDN publishing, and per‑language builds, dramatically boosting development efficiency, reducing maintenance, and delivering faster, lightweight multilingual experiences.
This tutorial explains how Spring's internationalization (i18n) works, covering core APIs, bean initialization, configuration for both classic Spring and Spring Boot, message resource files, placeholder usage, and convenient accessor utilities, with full code examples for seamless multi‑language support.
This article explains how to add multilingual capabilities to PHP applications by defining language arrays, detecting user preferences, installing and configuring the gettext extension, creating .po/.mo translation files, and providing code examples for loading translations and switching languages.
This article explains how to add robust multilingual capabilities to PHP applications by defining language arrays, detecting user preferences, configuring the gettext extension, creating translation files, and providing code examples for loading locales and switching languages.
This article explains how to create a Node‑based CLI utility that automatically scans Vue and JavaScript files in a large front‑end codebase, extracts i18n calls via AST parsing, validates translation keys, and outputs consolidated results to improve internationalization efficiency and accuracy.
The article describes Vivo’s overseas sales team’s multi‑language document system, detailing its low‑maintenance i18n design that leverages the existing configuration center, a MCMS UI, and a runtime JAR to streamline project creation, translation, testing, publishing, and real‑time front‑end text updates across web and decoupled architectures.
This article outlines a practical approach for adding i18n support to a mature React-based project by consolidating language resources, using i18next for business strings, leveraging Gulp for on‑demand locale builds, and integrating Webpack for seamless runtime loading and cache management.
This article describes a method for shortening i18n keys in Feishu's frontend architecture by encoding them into compact strings, integrating the process into Babel and webpack pipelines, and demonstrates a 7.2 MB reduction in total page code size for over 11,000 keys.
This article explains the concepts of internationalization, localization and globalization, outlines the objects and workflow of i18n, describes the evolution of the Starling platform and its tools, and provides practical guidelines for developers, product managers, and translators to implement robust multilingual support in software projects.
This article walks through preparing a Vue 3 + TypeScript project, explains the concept of setup sugar and its benefits, demonstrates the new compiler‑macro APIs such as defineProps, defineEmits and defineExpose, introduces useful hook APIs, covers Vue 3.2 additions like v‑memo and style‑variable binding, and provides tips for i18n, debugging and common pitfalls.
This article describes how to reduce the cost of adding multilingual support to existing React components by using the company's translate‑cli, an international translation platform, and the react‑intl‑universal library, together with a custom CLI built on commander and jscodeshift to automate code migration.
The article describes how Ctrip and Trip unified their disparate front‑end stacks by building a shared component library, splitting styles, adapting dark mode, implementing i18n/l10n, integrating automated testing in GitLab pipelines, and streamlining release and monitoring to improve development efficiency and reduce duplication.
This article explains how to set up internationalization and localization in a React application using react-intl, covering project scaffolding, language file organization, ID naming conventions, message merging with webpack, and currency formatting with the Intl API.
Spring Boot Admin 2.3.0, built on Spring Boot 2.3.x and Spring Cloud Hoxton.SR7, introduces i18n support, metadata configuration, request‑body caching, a new ApplicationRegistrator interface, MBean name display improvements, and enhanced alarm notifications, with full dependency details and demo screenshots provided.
This guide explains Laravel's localization features, covering folder structure for language files, configuring default and fallback locales, defining translation strings with short keys or full text, retrieving them via helper functions, handling placeholders, and managing pluralization with trans_choice.
This article outlines the evolution of mini‑program development at Ant Group, describing three engineering stages, essential tooling such as state management, Datahub mocking, monitoring, internationalization, component libraries, and SubApp architecture to bring mini‑programs closer to mainstream front‑end engineering practices.