mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Hi Cecilia

I believe doing the option 1 is the preferred choice as because
restricting the filenames in an instance of Mahara is not needed if no
one exports anything. Also it is not needed if users export and display
on same OS ifrastructure.

It only becomes a problem when exporting from system that can handle
more things and then importing to system that can't handle some of those
things (see comment #12)

So we should only deal with this problem where it makes most sense, and
that is during export. We should make our exported zipped up content
compatible with more systems.

So please continue with working on a fix for option 1

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

Title:
  UTF8 character encoding problem in HTML export

Status in Mahara:
  In Progress

Bug description:
  - Tested in demo.mahara.org
  - Client Os : Windows
  - Chrome 64.0.3282.186, Firefox 58.0.2, Microsoft Edge 41.16299.248.0

  Steps to reproduce

  - Create a Portfolio page with UTF8 accents in Title.
  - Export to HTML with "All my data"
  - Url to the page in index.html contains accents
  - Look in the archive /views/ and the folder's page name contains undefined characters (Windows)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1756904/+subscriptions