Well-stated, Robert. To offer a counterpoint, I think the main reason to make this change would be to maintain similarity with Moodle. Our lang system is based on theirs, but in the change from Moodle 1.9 -> 2 they changed their lang folders from "en_utf8" to just "en". So by still having the "_utf8", we look a bit outdated to potential Mahara devs coming over from Moodle.
But as you said, this offers no benefit at all to front-end users. Cheers, Aaron -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/905051 Title: The .utf8 in language packs is not meaningful and should be removed Status in Mahara ePortfolio: Triaged Bug description: We only support the UTF-8 encoding for language packages, so something like "en.utf8" should just be called "en". Here's an idea for how to make the transition: 1- add support for "en" without the .utf8 everywhere (not removing support for en.utf8) 2- switch all of our tools (e.g. the language pack scripts) to produce directories without .utf8 3- issue a warning in the admin area if there are any .utf8 directories and tell admins to rename them 4- in the pre-upgrade checks, check for .utf8 directories and abort 5- stop reading from .utf8 directories Steps 1 to 3 could be done in the same release, but 4 and 5 need to wait for at least the release after that. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/905051/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
