Yes, I read your comments, and the comparison I posted earlier take this into consideration. (Unless something went wrong in my XSLT, that is)
What my XSLT does is to look for each element or attribute whether it is referred to in a group or attributeGroup named ???_Not. If it is the case, then it wrote "no", otherwise "yes".

Of course I don't consider the annotations to generate yes/no value, but it's ok: it's equivalent to "partial" support. The clear yes/no differences are more interesting to look at for possible corrections of either your schema or the compliance.xml file.

Now, if FOP itself is lying about what it supports, that's another story ;-)

I take this opportunity to thank you once again, Chuck, for your very valuable work on this schema.

Benoit Maisonny

Chuck Paussa wrote:

In the FOP schema I developed, there's a set of switches that you have to edit in order to differentiate between what is and is not supported in FOP. The schema, as I provided it, validates for the full FO spec. You need to go in and comment out the templates with a name of ???_NOT in order to exclude those elements that are not supported. There are also individual comments on some elements and values as to whether specific values are supported.
For instance, check in the schema for "Inherit" In most cases, the spec says that it is a valid value and yet FOP rejects it as invalid and then inherits anyway.

Chuck Paussa

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Benoit Maisonny                [EMAIL PROTECTED]
Director & Consultant
Synclude Ltd.

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to