search

TEIC / Stylesheets

TEI XSL Stylesheets
231 stars 124 forks source link

teidata.xmlName does not get teidata.name special processing? #569

Open sydb opened 1 year ago

sydb commented 1 year ago

If an element’s content is defined in P5 itself as teidata.name it is correctly converted to (#PCDATA) in DTDs generated through customization. But if it is defined as teidata.xmlName it is incorrectly converted to %teidata.xmlName;, which is defined as CDATA; thus the resulting declaration is <!ELEMENT whatever CDATA > which produces a fatal error.

Note that this problem does not seem to occur if the element whose content is defined as teidata.xmlName is (re-)defined in the customization file, whether it uses a @mode of "add" or "change". I have not checked what happens when a datatype is itself defined with a <dataRef key="teidata.xmlName">. I am not sure it is worth bothering; I am hoping when we fix the problem for the elements it fixes any other such problems, too.

sydb commented 1 year ago

Reminder

When this ticket is addressed we need to search the Guidelines for occurrences of <dataRef name="NCName"> that really should be <dataRef key="teidata.xmlName"> and fix them. At the moment <altIdent> is the only case I know of off the top of my head, although perhaps teidata.nullOrName need be corrected, too.