Re: FOP compliance in XML?
Benoit, 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]
Re: FOP compliance in XML?
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: Benoit, 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 http://synclude.com Synclude Ltd. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP compliance in XML?
Hi, Below is the result of my cross-checking. For each element and attribute, the first value (yes/no) comes from the schema and the second one comes from the file compliance.xml. The values tell if the element/attribute is supported. Then there is my comment. Notes: 1. Individual compound properties (.minimum, etc.) are not listed separately in compliance.xml and thus are not compared 2. Only differences are listed, so the list does not tell when both sources are wrong ;-) HTH, Benoit Maisonny element declarations: yes/no element color-profile: yes/no element title: yes/no element block-container: yes/partial # this diff is OK element leader: yes/partial element page-number-citation: yes/partial # this diff is OK element table-caption: yes/no #I'd say no: table-and-caption is not element multi-case: yes/no element multi-property-set: yes/no attribute active-state: yes/no attribute alignment-adjust: yes/no attribute alignment-baseline: yes/no attribute background-image: no/yes attribute baseline-shift: yes/no attribute border: yes/no attribute border-after-precedence: yes/no attribute border-before-precedence: yes/no attribute border-collapse: yes/no attribute border-end-precedence: yes/no attribute border-separation: yes/no attribute border-start-precedence: yes/no attribute case-name: yes/no attribute case-title: yes/no attribute clear: yes/no attribute color-profile-name: yes/no attribute column-number: yes/no attribute content-height: yes/no attribute content-type: yes/no attribute content-width: yes/no attribute destination-placement-offset: yes/no attribute display-align: yes/no attribute dominant-baseline: yes/no attribute ends-row: yes/no attribute float: yes/no # I think it's no attribute force-page-count: yes/no attribute format: yes/no attribute grouping-separator: yes/no attribute grouping-size: yes/no attribute indicate-destination: yes/no attribute keep-together: yes/partial # this diff is OK attribute keep-with-next: yes/partial # this diff is OK attribute keep-with-previous: no/partial attribute letter-value: yes/no attribute margin: no/partial attribute margin-bottom: yes/partial # this diff is OK attribute margin-left: yes/partial # this diff is OK attribute margin-right: yes/partial # this diff is OK attribute margin-top: yes/partial # this diff is OK attribute marker-class-name: yes/no # I think it's yes attribute media-usage: yes/no attribute number-columns-repeated: yes/no attribute orphans: yes/no attribute overflow: yes/no attribute padding: yes/partial # this diff is OK attribute position: yes/partial # this diff is OK attribute precedence: yes/no attribute relative-align: yes/no attribute rendering-intent: yes/no attribute retrieve-boundary: yes/no #I'd say partial: page only attribute retrieve-class-name: yes/no # I think it's yes attribute retrieve-position: yes/no attribute scaling: yes/no attribute scaling-method: yes/no attribute show-destination: yes/no attribute size: yes/no attribute space-after: no/partial # I think it's partial attribute space-before: no/partial # I think it's partial attribute starting-state: yes/no attribute starts-row: yes/no attribute suppress-at-line-break: yes/no attribute table-layout: yes/no # I'd say partial: fixed only attribute target-presentation-context: yes/no attribute target-processing-context: yes/no attribute target-stylesheet: yes/no attribute text-shadow: yes/no attribute treat-as-word-space: yes/no attribute unicode-bidi: yes/no attribute vertical-align: yes/no # I think it's no attribute widows: yes/no attribute z-index: yes/no Benoit Maisonny wrote: Thanks, Victor. I'll cross-check with what I have (Chuck Paussa's schema) and with my experience with FOP. Is there a keyword or something else we can use to query bugzilla about these limitations? Or maybe they are not all listed? Benoit Maisonny Victor Mote wrote: A couple of caveats: 1) The html version on our website is misleading because the color-coding is scrubbed out in our forrest conversion (I am trying to get that fixed). 2) The content applies to 0.20.5, not the main branch. 3) The content might not be entirely accurate. It came from some other documents, which I think were a bit out of date. It is really intended as a good starting place. In particular, I think there are places where we say that FOP is in compliance, but where there are some limitations that need to be cross-referenced. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP compliance in XML?
Thanks, Victor. I'll cross-check with what I have (Chuck Paussa's schema) and with my experience with FOP. Is there a keyword or something else we can use to query bugzilla about these limitations? Or maybe they are not all listed? Benoit Maisonny Victor Mote wrote: A couple of caveats: 1) The html version on our website is misleading because the color-coding is scrubbed out in our forrest conversion (I am trying to get that fixed). 2) The content applies to 0.20.5, not the main branch. 3) The content might not be entirely accurate. It came from some other documents, which I think were a bit out of date. It is really intended as a good starting place. In particular, I think there are places where we say that FOP is in compliance, but where there are some limitations that need to be cross-referenced. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP compliance in XML?
Benoit Maisonny wrote: Is there a keyword or something else we can use to query bugzilla about these limitations? Or maybe they are not all listed? I've never made a comprehensive review of what is in Bugzilla. I don't know of any way to derive the list you seek. My goal has been to review the mailing lists each day distill this information from the questions problems that go by there, but I have not yet been able to implement that. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FOP compliance in XML?
Hi, Is there an XML version of the tables in http://xml.apache.org/fop/compliance.html? Alternatively, I'd be interested to have the compliance information (comments) merged into Chuck Paussa's FO/FOP schema. Either way, if nobody is doing it already, then I volunteer. Benoit Maisonny -- .. Benoit Maisonny[EMAIL PROTECTED] Director Consultant http://synclude.com Synclude Ltd. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP compliance in XML?
Yes, see here: http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/xdocs/compliance.xml?rev=1.5content-type=text/vnd.viewcvs-markup Volunteers are always welcome. :-) What exactly would you like to do with it? On 13.01.2003 12:52:29 Benoit Maisonny wrote: Hi, Is there an XML version of the tables in http://xml.apache.org/fop/compliance.html? Alternatively, I'd be interested to have the compliance information (comments) merged into Chuck Paussa's FO/FOP schema. Either way, if nobody is doing it already, then I volunteer. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP compliance in XML?
Benoit Maisonny wrote: This looks perfect for my needs! I am working on an FO quick reference that includes compliance information for fop and xep. A couple of caveats: 1) The html version on our website is misleading because the color-coding is scrubbed out in our forrest conversion (I am trying to get that fixed). 2) The content applies to 0.20.5, not the main branch. 3) The content might not be entirely accurate. It came from some other documents, which I think were a bit out of date. It is really intended as a good starting place. In particular, I think there are places where we say that FOP is in compliance, but where there are some limitations that need to be cross-referenced. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
