mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

I agree that, yes we only run in utf8, and that the .utf8 in folder
names is not needed - but to change it will mean work for little or no
gain but big headaches to obtain - as all the 3rd party stuff will have
.utf8 style directories.

-- 
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