Transformations are parameterised so that they may be used by different projects with only a change in local parameters, the scripts themselves being identical for all users. Change the parameters either by (a) changing the global-parameters.xml in your local copy (please do not commit these changes to SVN), or (b) setting local variables in your Saxon command-line, Oxygen scenario, etc.
See also Good practice for editing Example Stylesheets.
The parameters currently defined include:
Parameter | Description |
---|---|
$apparatus-style | DEPRECATED values are 'default' (generate apparatus from tei:div[@type='apparatus'] ) and 'ddbdp' (generate apparatus from tei:app, tei:subst, tei:choice, tei:hi etc. elements in the text. |
$css-loc | value is '../xsl/global.css'. Path of CSS file referenced in the resulting HTML file. |
$docroot | value is '../output/data' |
$edition-type | values are 'interpretive' (default) and 'diplomatic' (prints edition in uppercase, no restored, corrected, expanded characters, etc.) |
$edn-structure | "Edition Structure": working values are 'default' (no metadata), 'inslib' and 'iospe'. In progress templates include: 'dol' (Dodona Online), 'spes' (Servi Publici: Everybody's Slaves), 'edak' (Epigraphische Datenbank zum antiken Kleinasien). |
$hgv-gloss | value is '../../../xml/idp.data/trunk/HGV_trans_EpiDoc/glossary.xml'. Location of HGV glossary file relative to the current file. |
$leiden-style | values include 'panciera' (default), 'ddbdp', 'dohnicht', 'edh-web' (and 'edh-itx', 'edh-names'), 'ila', 'london', 'petrae', 'rib', 'seg', and 'sammelbuch'. These change minor variations in local Leiden usage; brackets for corrected text, display of previously read text, illegible characters, etc. |
$line-inc | default value = 5, may be locally defined to any integer value |
$topNav | values are 'default' and 'ddbdp' |
$verse-lines | values are 'off' (default), and 'on' (when a text of section of text is tagged using <lg> and <l> elements [ instead of <ab>] then edition is formatted and numbered in verse lines rather than epigraphic lines; gaps with scansion tagged will also be displayed as metrical symbols) |
Basically, we have a parameter called $leiden-style (among others), which is defined in a file called global-parameters.xml, but could also be passed to the XSLT as a parameter via Oxygen, Saxon, or whatever. So if you declared that for the purposes of your project $leiden-style='gandhara', and send that information with your transformation, then any template in the EpiDoc XSLT that behaves differently in your conventions than in Leiden will be activated in the Gandhara way rather than the Panciera way.
So for example (much simplified, and actions in pseudocode):
<xsl:template match="tei:unclear"> <xsl:choose> <xsl:when test="$parm-leiden-style="edh"> <!-- just print text, no underdots --> </xsl:when> <xsl:when test="$parm-leiden-style="gandhara"> <!-- surround text in square brackets --> </xsl:when> <xsl:otherwise> <!-- put underdots under each letter --> </xsl:otherwise> </xsl:choose> </xsl:template>
This way the template allows you to display square brackets for unclear text without breaking the way all the Leiden-based projects display their EpiDoc.
That's all you need to do. You don't even really need to include your parameter value in the global parameters (although it would be helpful to do so for those people who use that as their entry into the XSLT).
Home: ReleaseProc
Home: Stylesheets
Home: TechDocs
Home: XsltGoodPractice