While generating examples for the Guidelines, saxon reports the following error:
"no template in teicertainty.xsl for your use of certainty"
The only file that triggers these errors is trans-numnoncongruent.xml
Some code forensics will be needed to figure out which element/attribute/value combination(s) are causing the problem. Modifications either to the examples or to the tei-certainty templates in the example guidelines may be required.
This is due to a line of code in the stylesheet
teicertainty.xsl
that (uniquely in the EpiDoc xsl to my knowledge) throws<xsl:message>
(not exactly an error) when to match is found in the various<xsl:when>
s of a<xsl:choose>
. Anywhere else the test just fails elegantly (i.e. does nothing, or apply-templates, vel sim.), which I think is preferable.The question is, do we want to cater for all possible uses of
<certainty/>
(or at least all those in the Guidelines examples) in the Reference Stylesheets, or do we just want to make them available for custoization by people who really want to use them?Perhaps a better question is, how would we expect the examples in trans-numnoncongruent to look? I think they are right as they are, although perhaps an apparatus note should be generated (but the GLs aren't able to illustrate that at the moment).
My proposal is to remove the
<xsl:message>
construct from the Stylesheets, so this error no longer arises. Will implement.Commented out
<xsl:otherwise>
that contained the<xsl:message>
construct in teicertainty.xsl. Committed at github-3ec22ba.