representation inside database should be utf8_general_ci with sql set_chareset to utf8, in our case the database size is doubled since each char is 16bit but still much safer for multi languages, what do you think?
-- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/680269 Title: language is by english language name and should be ISO-639-1 Status in Aiki Framework: Confirmed Bug description: Aiki is preferring an english spelling of languages and it should represent, and it should be enforced that aiki supports language codes for language switching and not long ass english names that only english speaking people can read. ISO-639-1 is the standard, and ISO-639-2 is the secondary part for regional differences. This is what everyone in the entire world supports. We should too: http://www.gnu.org/software/gettext/manual/gettext.html.gz#Usual- Language-Codes Thus, US English is en_US. English is en or en_EN. Arabic would be ar, or ar_AR, or saudi arabic would be ar_SA The underscore and hyphen should be read the same, just like google and every other project in the world uses: so en_US is the same as en- US, and its not case sensitive. The simplest solution is to use the key 'en' for basic english and 'ar' for basic arabic. Then in the language can have a word like english and arabic, then in another language like arabic, could have arabic translations for word english and arabic. Make sense? This should be fixed here and on all aiki installations. _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
