Philippe Nobili wrote:
> 
> Basically, we have in our XML-schema two different ways to put some
> documentation:
> 
> 1. a simple element <help>
> 2. an extended help element <xhelp> which serves as a container for any
> XHTML element from XHTML namespace. So far so good.
> 
> We proceeded as you explained in your mail, (excerpt):
> 
> We added  XHTML support + validation support:
> <cfg:include location="xxe-config:xhtml/xhtml_support.incl" />
> <cfg:validate........
> 
> We added a template for <xhelp> elements:
> 
> <cfg:elementTemplate name="xhelp" selectable="override">
>     <xhelp xmlns="http://www.cggveritas.com/geovation/module/1.0";>
>       <body  xmlns="http://www.w3.org/1999/xhtml";><p
> xmlns="http://www.w3.org/1999/xhtml";></p></body>
>     </xhelp>
>   </cfg:elementTemplate>
> 
> Now,
> 
> We can edit the XHTML documentation online in the styled view, we get
> the appropriate list of XHTML elements, they are rendered correctly, etc etc
> 
> But there are residual problems we fail to tackle; we would really
> appreciate if you could help us with these...
> 
> + There is no way to make XMLMind validates our documents, it complains
> about any XHTML element we insert (error: cannot find a declaration for
> child element xhtml:body).
> 
>     We added the <validate> instruction in our .xxe file, so we fail to
> see what is wrong, especially because XMLMind lets us add the XHTML 
> elements in the right places....


Please proceed as follows:

[1] Comment out <cfg:validate.../> in your .xxe file.

[2] Open a document containing one or more <cggv:xhelp>/<xhtml:body>
elements.

[3] Validate your document.

If my guesses are right, you should see: "error: cannot find a
declaration for child element xhtml:body".

If my guesses are right, your validation problem is not related to
<cfg:validate.../> at all. It is related to the way you have defined
<cggv:xhelp> in your custom W3C XML Schema. That is, does <cggv:xhelp>
allow some ``wildcard contents'' with processContents="lax" or
processContents="skip"?



> + Some of the keyboard shortcuts used when authoring XHTML in the styled
> view do not work (e.g. <Enter> to add new list items). We have to go
> through the list of elements to add items.
> 

Please fix the validation problem first.

Also please remember that in the XHTML stock configuration, <Enter>
*cannot* be used to add new list items. It's Ctrl-<Enter>. See
http://www.xmlmind.com/xmleditor/_distrib/doc/quickrefcard/quickrefcard-A4.pdf



> + The last one is minor; our structure is very simple:
> 
>    <desc>
>      <help> | <xhelp>
> 
>    What we wish to do with the insertDocumentation is to make it available:
>      when a <desc> element is selected, in which case it would take the
> content of the <help> and replace the <help> element -- if any -- by
> <xhelp><p> with the same content in the paragraph.
> 
>      At least we would like to be able to simply replace <help> by
> <xhelp> with our template.
> 
>     So far, the command is available when it is supposed to, but does
> nothing, so I guess we have it wrong...
> 

There is no way to do this directly using XXE's native commands (e.g.
convert, wrap, insert, add). You need to write a *macro* which does
what's described above.



--> I think that we have reached here the limits of normal, informal,
support:

* If you suspect you have found bugs (e.g. the validation errors and/or
the missing bindings), do not hesitate to send us your configuration so
we can reproduce these bugs.

* If you want us to turn your configuration into a production-quality
add-on, for example by writing the above macro, please consider
purchasing a number of xe-su units. See
http://www.xmlmind.com/xmleditor/customization_service.html





 
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to