-
Notifications
You must be signed in to change notification settings - Fork 7
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
Purpose of mathml entity mapping in catalog.xml #26
Comments
Up until now, it was the simplest possible catalog that could be used. Suggestions welcome. The catalog from https://www.w3.org/2003/entities/2007xml/catalog is:
If the focheck catalog changed to use Does oXygen provide any other catalog that resolves Maybe the answer is for this catalog to use |
But do you use that mapping from anywhere in your schema or Java code? Right now your catalog is the only one mapping the "htmlmathml-f.ent" in some way. Probably all other places refer to the "htmlmathml-f.ent" as a relative location and expect it to be relative to the DTD which refers to it.
has a reference like:
which should be resolved relative to the DTD. It is now resolved to your ent file. |
It's needed because some MathML in It's not referenced by the schema because it's a RELAX NG schema. Individual FO documents would have to have a DOCTYPE declaration declaring it. focheck needs the catalog for parsing outside of oXygen, but the focheck frameworks could defer to an oXygen-wide catalog if that existed. Is it possible for the users to set the priority of their framework to 'high'? Would that solve it? We can talk about this more in Prague. |
Usually XSL-FO is automatically generated using XSLT so all entities have already been expanded by the XSLT processor. So I think cases in which XSL-FO has a DOCTYPE, declares and uses entities are quite seldom.
It would only solve it if the framework would define its own catalog system mapping, similar to what you did. If it defines no catalog mapping considering the the entity is located in the same folder with the DTD which references it, the entity will always get resolved through your mapping. I will not be at XML Prague, but about 5 members from our team will. |
Would the current |
@tgraham-antenna It's better the catalog mappings are now more precise for a certain system ID. I'm not sure when I'll be able to test the changes so you can probably close the issue. |
The focheck comes with a mapping like:
Is there a purpose for the mapping? Could it possibly be re-written to be more specific?
One of our clients used in his DTD something like:
and they expected the "bla_htmlmathml-f.ent" to be resolved to their local DTD but because Oxygen also loads the focheck catalog, the entity was mapped to the "htmlmathml-f.ent" located in the focheck framework.
The text was updated successfully, but these errors were encountered: