4 ms·
looks good, I like the option to select different template engines. On the other hand, your i18n approach is not correct, since you are using only the language
by ubersoldat2k7 14y ago
looks good, I like the option to select different template engines.
On the other hand, your i18n approach is not correct, since you are using only the language and not the country code: en_GB is different than en_US in lots of aspects, i.e. currencies.
Internationalization is the first thing I tend to look at a framework and many fail on it.
- florinpatrascu 14y agoLack of examples, sorry. Country and Language are both supported. You can create the following properties file: messages_en_GB.properties, and you have a language and country based translation! I will clarify this aspect in the docs, many thanks for catching that!
- florinpatrascu 14y agoupdated the docs with a better message: http://micro-docs.simplegames.ca/internationalization.md http://micro-docs.simplegames.ca/internationalization.md, please note the Country role in naming the translation files. Thank you!