Monday, June 4, 2007, 10:33:46 AM, Hussein Shafie wrote: [snip] > The document type (and in consequence, which configuration to use) may > be detected based on the namespace and/or the local name of the root > element. See > http://www.xmlmind.com/xmleditor/_distrib/doc/configure/detect.html > > In the example above, the detection would be based on the presence of an > attribute of the root element. This is currently not implemented but > would pose no conceptual or technical problem. If there is sufficient > interest, we could implement this feature. [snip]
I guess if you extend the detection mechanism it will be utilized by many. Like I already wanted to send a feature request in this topic. I wanted config detection based on the *value* of an attribute (or if an NMTOKEN occurs in its value), but it seems not be possible. And maybe PI-s could be usable for detection as well. You used to say that one could customize XXE to meet his needs/conventions. OK, but the problem is, if someone installs the customized DocBook config that was made for project A, which has its own particularities, then that config will be used for all DocBook documents, not only for those that belong to project A. To work this around, currently I said that project A documentation uses exactly DocBook V4.5 and then I use the DTD public ID for the detection, and hope that those who install the addon will not run into other V4.5 DocBook-s too often. In fact, I already have another custom DocBook for project B, which only to let XXE using the proper config on my XEE installation (which must handle documents from both projects) uses DocBook v4.4 instead of v4.5. Now if I could mark somehow which project the DocBook document belongs to, that would solve this. Like, I could use a <book conformance="projectA">...</book>. Or a PI maybe, like <?editor conventions="projectA" ?> (but I'm not sure how good idea that is). -- Best regards, Daniel Dekany
