XML related stuff including, but not limited to, the XML authoring framework

Nigel Stanger authored on 12 Apr 2019
configuration Added examples of XML resolver configuration files and instructions on what to do with them. 8 years ago
modules Switched div to span for text colours 3 years ago
.gitignore Added generated files to .gitignore. 8 years ago
Makefile Removed now obsolete CVS substitutions. 8 years ago
README.md Minor reformatting 3 years ago
extract_svg_layers.xsl • Rewrote Oracle documentation and Blackboard elements to use the hyperlink template rather than hyperlink-internal. 6 years ago
format-master.xml • Added support for menukeys (closes #12). 4 years ago
generate_calendar_dates.php Automated calculation of current year and first Monday. 3 years ago
html_calendar.xsl - Deprecated the old teaching calendar stylesheets. They'll stick around, 9 years ago
latex_calendar.xsl - Deprecated the old teaching calendar stylesheets. They'll stick around, 9 years ago
oracle-docs.perl • Removed another obsolete comment (no longer relevant to do item). 5 years ago
quick-reference.markdown Added support for basic text colouring 3 years ago
xml2xslt.xsl Reduced spacing after answer environment 3 years ago

Master XSLT stylesheets for the INFO database authoring framework

You will need SAXON-B installed in order to process these successfully. The final released version of SAXON-B is Earlier versions may not support the required features, and later versions change the architecture in ways that will probably break this framework!

To install:

    git clone https://github.com/Otago-InfoSci-Database/XML.git
    cd XML

You’ll need to have the XML Entity Resolver set up with a catalog that includes the generated .xsl files in this directory. The usual approach is to create somewhere (e.g., ~/Library/Catalogs under Mac OS X) a catalog.xml file that includes URI mappings for all the local .xsl files, then create somewhere (e.g., ~/Library/Java) a CatalogManager.properties file that tells the resolver where to find catalog files (both user and system). Ensure that CatalogManager.properties or more likely its containing directory is in your Java class path. See the configuration directory for examples of both these files that you can use as a template.

To update:

    git pull

Documents that use the framework depend on the master stylesheets, and so will automatically rebuild from scratch the next time they are built.

Most of the actual stylesheet code is in the modules directory.