Known bugs

Ressource files

Each ressource files used in content.xml is copied into the scar archive, links works in the outputFile. But once you're in Opale you will see (in the explorer) that each ressource files' icon is crossed (the outputFile's isn't though). Technically speaking this is not a bug, but I had to notice it.

Hdoc's "container.xml" namespace.

All hdoc samples given in the "Download" section have been tested and should work well. If you want to use your own hdoc files, make sure that container.xml's root contains version="1.0" and xmlns="urn:utc.fr:ics:hdoc:container" attributes. Otherwise ant building will fail.

Hdoc's "content.xml" path

It is not specified in hdoc's standard but I assume that hdoc's content file (usually named "content.xml") fullpath is a relative path that begins at the root of the hdoc archive. That means that the full-path attribute of <rootfile> (in container.xml) begins with a character, and not a special sequence such as ".", ".." or "/". It is already the case for my samples, but if you want to use your own samples make sure this full-path attribute is ok.

Website

The website is still in alpha testing, I have still problems with files and folders rights and properties. Right now you can use my uploaded samples, convert them and download .opale converted files but there are still some troubles with uploading and uploaded files deleting.

Hdoc's head's meta with name attribute

My conversion handles rights (http://moodle.utc.fr/mod/forum/discuss.php?d=8656), author and (partially) keywords. Yet Opale doesn't recognize them if hdoc's content.xml metas are not correctly sorted in that order :

  • <meta name="keywords">

  • <meta name="rights">

  • <meta name="author">

Html node

The freemind format allows to add html in a node. As the html is written by the user, there is no garantee about the content. Moreover, the node name is always contained in the html, but not with a specific tag. So it can be stored in a p, a, span tag.