Note: A version of this post appears in the proceedings of XML Prague 2024 My current project is to simplify the work involved in creating assessment content for learners. These assessments consist of short activities where the student must look at an image, listen to an audio file, or read a text, and then choose… Continue reading Automating import and layout of content in InDesign
Author: Mark
Migrating a very old Joomla site
Many (many) years ago I set up a web site for the local community centre, using Joomla 2.5.11. Some years after that a section on local history was added, which became popular. Now the community centre have decided to update their site, not before time, and I have been asked to find a new home… Continue reading Migrating a very old Joomla site
Locating the result document after fn:transform()
Something unexpected happened when I ran an XSLT transformation using fn:transform() within another XSLT script, instead of just running it directly. <xsl:variable name=”xslt-options” as=”map(*)”> <xsl:map> <xsl:map-entry key=”‘stylesheet-location'” select=”$url”/> <xsl:map-entry key=”‘source-node'” select=”$input”/> <xsl:map-entry key=”‘stylesheet-params'” select=”$stylesheet-params”/> </xsl:map> </xsl:variable> <xsl:variable name=”output” as=”map(*)” select=”fn:transform($xslt-options)”/> <xsl:sequence select=”map:get($output,’output’)”/> My stylesheet located at $url uses <xsl:result-document> to produce some secondary output, but… Continue reading Locating the result document after fn:transform()