[tei-council] Interesting Oxygen behaviour
Martin Holmes
mholmes at uvic.ca
Tue Jun 19 16:44:42 EDT 2012
I have some an ex-TCP document that was failing to validate under the
previous release of TEI because it had a <closer> in a <postscript>.
With the new release out, I tried validating this document against the
new tei_all:
http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng
It failed, complaining about the <closer>. I did Reset Cache and
Validate, many times. I went to the documentation and to the schema
itself to confirm that <closer> is now allowed in <postscript>. I did
Validate With and put in the URL of the tei_all, and also had it in the
document as an <?xml-model?> PI. No joy.
It wasn't till I actually downloaded the oxygen-tei packages and
overwrote my TEI framework folder in Oxygen that I got the correct
result. It appears that if you try to validate a file against a TEI
schema on the TEI website, Oxygen is determined to use its own local
copy, without checking whether they're the same or not. That wasted a
bunch of my time.
Cheers,
Martin
--
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)
More information about the tei-council
mailing list