Writing front-end code often requires developers to address the problem of internationalization at some level. Despite the current standard 1 , which introduces a bunch of new tags, simply adding support for different languages in a JavaScript plugin is still complicated. As a result, for any new project, you have to build a solution from scratch or adapt various existing APIs from other plugins that you use. In this article, I’ll describe my approach with better-dom 2 to solve the internationalization problem. Since the last article about this, “ Writing a Better JavaScript Library for the DOM 3 ,” I’ve revisited the concept to solve the issues raised through feedback. The solution was originally intended to be a set of internationalization APIs for plugins, extensions, etc. It doesn’t rely heavily on the better-dom library, so it could be adapted to any existing JavaScript library. A Typical Solution To The Problem Different APIs exist for changing languages in JavaScript
↧
