Nucleus CMS 3.64 has a capability to utilize many languages in its core but still not because
1. still use default MySQL collation, latin1_swedish_ci, which deals with latin1 (ISO-8859-1).
2. still based on ISO-8859 series as its default character encoding scheme
3. cannot deal with multibyte characters
As a result, Nucleus CMS cannot deal with non-latin languages such as Japanese.
Additionally this causes the lack of ability utilizing UTF-8 because this character encoding scheme encodes all of the characters except for ASII as multi-byte.
Then I open five tickets below,
1. set utf8-related collation for its database (3485392)
https://sourceforge.net/tracker/?func=detail&aid=3485392&group_id=66479&atid=514646
2. implementing multi-byte processing into its whole core (3485393)
https://sourceforge.net/tracker/?func=detail&aid=3485393&group_id=66479&atid=514646
3. allow to import skins encoded by the other character encoding schemes than ISO-8859-1/US-ASCII/UTF-8 (3485395)
https://sourceforge.net/tracker/?func=detail&aid=3485395&group_id=66479&atid=514646
4. make a rule for dealing with locales and arranging translation files following to it (3485396)
https://sourceforge.net/tracker/?func=detail&aid=3485396&group_id=66479&atid=514646
5. separate the decision process of character encoding scheme and locale (3485397)
https://sourceforge.net/tracker/?func=detail&aid=3485397&group_id=66479&atid=514646
Now these 5 issue is implemented and the tickets are closed. But here I added new one.
6. locale-selectable install script
https://sourceforge.net/tracker/?func=detail&aid=3485783&group_id=66479&atid=514646
added new one
7. capable to apply translation message in whole context
https://sourceforge.net/tracker/?func=detail&aid=3523725&group_id=66479&atid=514646
added new one
8. force locale and charset from plugins
https://sourceforge.net/tracker/?func=detail&aid=3523726&group_id=66479&atid=514646