Comment 5 for bug 739528

A problem with this is instead of the html export using the 'raw' theme's information under /theme/raw/ it actually uses the 'raw' theme information under /export/html/theme/raw/.

So the first step for this would be to refactor how it currently works so that the html export uses resources under /theme/ directory instead. This will cut out some duplication and confusion.

Also it will allow us to check for the resources under a particular theme and then fallback to the 'raw' if the resources are not found. And also allow the export html to incorporte css / image changes easier.

I suspect the template/css/image files under /export/html/theme/raw/ will differ slightly to their main counterparts at the moment. So there will be some merging/renaming of things needed.