Thomas Dumm wrote: > Do I understand you correctly: I cannot use XMLMind plus standard JEuclid in > documents conforming to a dtd beacause XMLMind is not namespace aware and > JEuclid requires the MathML-Namespace? >
Not exactly. * Yes, XMLMind XML Editor v3 is not namespace aware when the document being edited conforms to a DTD. * Yes, JEuclid requires the MathML namespace (Well, in principle. May be it is more lenient that this). * The JEuclid *add-on*, which should not be confused with JEuclid itsef, is a thin layer of code (~300 lines of Java[m] code) which integrates JEuclid into XMLmind XML Editor. This add-on *fails* to use the services of JEuclid when a MathML subtree is embedded in a document conforming to a DTD. Therefore, the culprit is the JEuclid add-on, not JEuclid itself, not XMLMind XML Editor. > PS: Is Docbook 5 not conforming to a dtd? In Docbook 5 the MathML is > properly rendered. Or does Docbook conform to a schema? I cannot recognize > this in the header of docbook5-sample.xml DocBook 5 is specified as a RELAX NG schema. (DocBook 4 is specified as a DTD.) The association between a DocBook 5 document and its schema is done by external means. There is no need to declare anything in the Document itself, which is simple, clean, elegant and efficient. > I looked around a little more. To me it looks as if the redering of the > MathML works fine with dtds if the MathML is contained in an external .mml > file and not directly in the xml file. I have attached a sample from the > Jeuclid-add-on folder. The xml file contains twice the same equation. The > first equation is referenced in an .mml file an is correctly rendered, the > second is directly embedded in the xml and is not rendered. This second case is very different from the first case: a MathML subtree embedded in a document conforming to a DTD. When a document conforming to a DTD points the a .mml external file, the JEuclid *add-on* has no problems at all using the services of JEuclid to render the MathML equations. > Does this > information help you with identification of problem/solution? As I have explained it above and in my previous email, the cause of the problem is 100% identified. The solution is to slightly modify the JEuclid *add-on*. Sorry but we will not do that because we are currently working hard on XMLMind XML Editor v4 which is always namespace aware. This new feature should solve the problem anyhow.
