Internationalization, like security, is often a left-for-later discussion. XMLC, however, benefits as an open source project by the fact that the members are from across the world, where highly localized applications, many of which come from the United States, are a must.
As usual, there are a number of ways to approach internationalizing your XMLC presentations:
Create a separate HTML template for each locale supported.
Create one HTML template and substitute all text in the template during runtime with the localized equivalent.
Both of the above, depending on the situation.
As you read the preceding list, you probably saw some issues right away. First, if you are building an application that must satisfy the language requirements ...