Hi, Edward
Edward Doolittle writes: > 2) Development of Moodle glossaries. Glossaries can be uploaded to a > Moodle site using an appropriate XML file. Glossaries could be > developed in Org mode, including JSXgraph diagrams and graphs, PNG > images, and so on, and then Org mode converted to XML and the XML > transformed to Moodle Glossary XML using XSLT. (I don't really know > those tools at all, so I don't know if that would be a good way to go > about the process; exporting directly to Moodle Glossary was my first > thought, but it is not a general export that is necessary or > appropriate, rather an export of a specifically designed Org file. > XSLT seems old fashioned but there are tools around, and there is a > project for exporting Org mode to XML.) I'm a Moodle noob and rusty on the tools, but this is interesting to think about. You may not need any additional library for the XML export bit. The builtin Org HTML exporter does XHTML export by default, and XHTML is an XML, so one could just apply XSLT to that. There may be advantages to using a library like om-to-xml (cleaner, more semantic XML; access to more properties than what gets exported). But it looks like Moodle only uses XML to wrap the glossary entries and their properties; any markup inside the glossary definitions appears to be in HTML (with the html tags entity-escaped), not defined by the Moodle glossary XML format. So if you're going to have some markup in the definitions, you may be better off leaving the (X)HTML part to Org instead of reimplementing it in XSLT. Another option might be to dispense with XSLT entirely and just write elisp code to map the entries of an Org glossary and generate Moodle XML from that. How would you format the glossary on the Org side? Would you use Org entries (** term) or Org description lists (- term :: definition)? On the Moodle side, do you want keywords and attachments? Yours, Christian
