Philippe Nobili wrote:
> On 04/16/2010 10:18 AM, Hussein Shafie wrote:
>> 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"?
>>
>>
>>
> That's brilliant, thanks !
>
> As always you are right... Works much better with processContents='skip'...
> Many thanks for this one.
> Best regards,
> Phil.
>
>> Also please remember that in the XHTML stock configuration, <Enter>
>> *cannot* be used to add new list items. It's Ctrl-<Enter>.
>>
> I have made a typo in my mail, I had Ctrl-<Enter> in mind. Actually, it
> works erratically; it works the first time we create the list, then it
> stops working if we try to modify it. That's the first time we see this
> behavior.
XXE probably crashes. Please run it using a console to see the Java
stack traces.
Needless to say that we cannot reproduce this problem with our stock
configurations for XHTML or W3C XML Schema (where schema elements may be
documented in XHTML).
> We have two additional short questions,
>
> 1. We need to convert some DocBook documents in XHTML; however, the
> XHTML conversion flag is dimmed and cannot be switched on; I recall that
> we have used this option years ago, do you see any reason for this
> option to be unavailable ?
>
I'm sorry but I don't understand. Is this related to the configuration
for your custom W3C XML Schema?
We don't have this problem with the stock DocBook 4 or DocBook 5
configurations.
> 2. We have two styled view, a main one, and a second one similar to the
> 'Document Structure' view for DocBook, just for highlighting the
> structure of our XML file. So we proceeded this way:
>
> <css name="JXMod Documentation" location="css/geovation.css" />
> <css name="JXMod Structure" alternate="true" location="css/structure.css" />
>
> The problem is that whatever content we place in the css/structure.css
> CSS file (even * { display: none; }), when we try to use the second
> styled view, we always end-up with the raw XML tree-view (the default
> view), except that it is on a grey background...
Never seen this.
> We look all over the place for possible reasons, but could not find
> any... as always, something obvious before our eyes that we fail to see ?
I'm sorry but I don't see what could happen here.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
