A new way of internationalization (a propsal from Japanese team)

Hi, this is Nick from Tokyo, Japan.

I would like to propose the way of internationalization.
(I also posted this to JIRA as a new proposal)

Here is a proposal from Japanese MODx team,

Why don’t we define a "setlocale (LC_ALL, ’xxxxx’)" or "(LC_TIME, ’xxxxx’)" on config.inc.php file ?

It can be effective for all of MODx snippets --- such as Ditto or Jot or everything ---- so we don’t have to change the snippet’s locale settings.

In Japan, we tried to add a "setlocale (LC_ALL, ’ja_JP.UTF-8’);" script at the first line of config.inc.php, and it had effects for Ditto and Jot, so we don’t have to change Ditto’s and Jot’s inside locale settings.

So our proposals are;

1:
Config.inc.php file should have a locale setting, such as "setlocale (LC_ALL, ’ja_JP.UTF-8’);" or "setlocale (LC_TIME, ’xxxxx’)".
With "xxxx", en_US is better at a default status, and all of world’s MODx team only change this setting to their country’s locale setting.

2:
The core team would make a guideline of internationalization.

3:
Every snippets that has locale setting scripts should entrust their language settings to config.inc.php file, and all of MODx translator and developper would follow the core team’s guideline of interenationalizing way.

4:
Translation teams of all around the world would submit a new language files of snippets and needed files that is following the new guideline.

It can be useful for every users and every developpers who engage in MODx project, cause they have to change only one line of config file, and all snippets follow the settings.

Please give a consideration to this proposal.

Nick_smallworld from Tokyo, Japan

Very interesting idea, but how would this affect multilingual sites?

Could a plugin be used for multilingual sites, to override the locale setting based on.. a TV, or the URL, or Context.. ?

Nick, has there been any more thought on how this affects multi-language sites from the Japanese community?