Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roma (Roma2, at least) fails to generate Schematron properly #1863

Closed
sydb opened this issue Mar 23, 2019 · 5 comments
Closed

Roma (Roma2, at least) fails to generate Schematron properly #1863

sydb opened this issue Mar 23, 2019 · 5 comments
Assignees

Comments

@sydb
Copy link
Member

sydb commented Mar 23, 2019

  1. Roma still gives users the opportunity to download “Schematron” as opposed to “ISO Schematron”. But we have not supported Schematron 1.x for years; the Schematron 1.5 extracted from the Guidelines by Roma is an empty file. (Well, it has an <sch:title>, but no rules.)

  2. Roma2, our “temporary” replacement for the standard Roma install, is not correctly generating ISO Schematron from a customization file, whether that customization is uploaded or one of the pre-loads. The output looks like a Java error, and is not even well-formed XML. (Due to 2 XML declarations; the 2nd one gets interpreted as a PI that is not allowed to start with “xml”.) I have no idea whether this problem is part of the ADHO server failure issue set (see TEI Website's not working #1855), or would occur with any installation of Roma or not. The error file is attached as tei_drama_schematron_error.txt. This error brought to my attention by Melanie Demmer.

  3. Roma does not list tei_simplePrint or tei_customization as possible starting points.

tei_drama_schematron_error.txt

@peterstadler
Copy link
Member

peterstadler commented Mar 23, 2019

Hi @sydb, that's several issues not necessarily connected, right?

Second, 1) and 3) are Roma issues and should be moved there -- but, since they are more or less cosmetic I think I'd label them as "wont fix" as RomaJS is about to take over.

issue 2) is probably a Stylesheets issue or an OxGarage issue, since Roma delegates the processing of all output formats to OxGarage.

@peterstadler
Copy link
Member

NB, there are also schematron related issues at TEIC/Stylesheets#368 and TEIC/TEIGarage#28

@sydb
Copy link
Member Author

sydb commented Apr 1, 2019

Note: leaving this ticket unassigned, because @peterstadler is correct, it should at least be moved elswhere (and assigned there), if not split up, too.

@raffazizzi
Copy link
Contributor

@sydb would you be able to recreate the issues as @peterstadler described in the respective repositories? Then we can close this issue

@sydb
Copy link
Member Author

sydb commented Jan 18, 2021

(1) and (3) re-created in Roma repo; (2) is no longer a problem.

@sydb sydb closed this as completed Jan 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants