AW: keep is not auto but context is
Hi Andreas, Nope, doesn't bother me that much, since it makes no difference. Regards, Georg Datterl -- Kontakt -- Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH:www.irs-nbg.de Willmy PrintMedia GmbH:www.willmy.de Willmy Consult Content GmbH: www.willmycc.de -Ursprüngliche Nachricht- Von: Andreas Delmelle [mailto:andreas.delme...@telenet.be] Gesendet: Montag, 24. August 2009 17:59 An: fop-users@xmlgraphics.apache.org Betreff: Re: keep is not auto but context is On 24 Aug 2009, at 15:00, Georg Datterl wrote: Hi Georg What does this message mean? It's a warning message, indicating that the current keep-context is set to auto, but the keep-property specified on the FO for which layout/breaking is performed, has a different value. I guess the message could probably be set to a lower level (DEBUG) if it bothers you... Regards Andreas Regards, Andreas Delmelle mailto:andreas.delmelle.AT.telenet.be jabber: mandr...@jabber.org skype: adlm0608 --- - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
AW: Display of fractions
Hi Andreas, You are right. Both pdfs are created from the same fo file, but the one which doesn't work as expected is reformatted by Xmlspy first. And there's no way as far as I can see, to keep the inlines in one line. Well, doesn't matter. I was hoping it would be a clue to improve the blank-block algorithm, but no luck. Thanks for your help, now I can concentrate on the next problem. Regards, Georg Datterl -- Kontakt -- Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH:www.irs-nbg.de Willmy PrintMedia GmbH:www.willmy.de Willmy Consult Content GmbH: www.willmycc.de -Ursprüngliche Nachricht- Von: Andreas Delmelle [mailto:andreas.delme...@telenet.be] Gesendet: Montag, 24. August 2009 18:13 An: fop-users@xmlgraphics.apache.org Betreff: Re: Display of fractions On 24 Aug 2009, at 13:33, Georg Datterl wrote: Hi Georg In my fo file I have a text like fo:inline font-family=arial bold font-size=4pt line- height=8pt baseline-shift=2pt3/fo:inline fo:inline font-family=arial bold font-size=6pt line- height=8pt∕/fo:inline fo:inline font-family=arial bold font-size=4pt line- height=8pt4/fo:inline The second character is Unicode 2215. When I generate the PDF through the batch file from subversion, this sequence looks like 3 / 4, whereas when I generate the PDF through my application, it is pulled together to a bit more than one character width and looks like a true fraction. See attached screenshot. Can anybody tell me, which part of fop is responsible for this difference and why the batch file does not trigger this part? My best guess would be a difference in white-space in the source FO. If you serialize it to disk first, depending on the value of the 'indent' attribute on xsl:output, the XSLT processor may add white- space in between the fo:inlines. When you feed XML+XSLT to FOP in your application, the fo:inlines are most likely not separated by white- space (a compliant XSLT processor should ignore the 'indent' attribute in that case), hence why you get the intended result there. Note that there is, AFAIK, no combination of related properties in XSL- FO that would completely suppress the linefeeds between the fo:inlines. There will always at least remain a space, which could be a ZWSP if linefeed-treatment is set to treat-as-zero-width-space. The only fail-safe approach is always to make sure that there is no white-space in the FO source that you do not intend to see in the eventual output. HTH! Andreas Andreas Delmelle mailto:andreas.delmelle.AT.telenet.be jabber: mandr...@jabber.org skype: adlm0608 --- - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: keep is not auto but context is
Hi, Andreas Delmelle wrote: On 24 Aug 2009, at 17:58, Andreas Delmelle wrote: On 24 Aug 2009, at 15:00, Georg Datterl wrote: What does this message mean? It's a warning message, indicating that the current keep-context is set to auto, but the keep-property specified on the FO for which layout/breaking is performed, has a different value. Note: AFAICT, this message mainly originates from keeps on table-elements for which they are not completely implemented yet. fo:table-cells are an example where support for keeps is lacking, but since it does work for fo:table-row, and fo:table-cell inherits the value from its ancestors... Keeps do /not/ apply to fo:table-cell: http://www.w3.org/TR/xsl11/#fo_table-cell Keeps are fully implemented on all supported table elements to which they apply, that is fo:table and fo:table-row (the fo:table-and-caption and fo:table-caption elements are not supported at all). Keep-together is an inherited property, so the descendant elements of fo:table-cell to which that property applies will behave accordingly. But the code related to table-cell has nothing special to do. So whatever that warning means, it is not related to tables. At any rate, it has no noticeable effect on the output. The warning appears for some testcases as well, but would disappear if keeps on table-cells would be properly implemented. Vincent - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: AW: AW: AW: AW: AW: Area Tree Handling
Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
AW: AW: AW: AW: AW: AW: Area Tree Handling
Hi Tom, bpd is the HEIGHT of the area. prod-id is the reference attribute id. Those are the ones I use extensively. Mit freundlichen Grüßen Georg Datterl -- Kontakt -- Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH:www.irs-nbg.de Willmy PrintMedia GmbH:www.willmy.de Willmy Consult Content GmbH: www.willmycc.de -Ursprüngliche Nachricht- Von: TomWilcox [mailto:wil...@hp.com] Gesendet: Dienstag, 25. August 2009 16:26 An: fop-users@xmlgraphics.apache.org Betreff: Re: AW: AW: AW: AW: AW: Area Tree Handling Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: AW: AW: AW: AW: AW: Area Tree Handling
There's no formal documentation of the area tree XML format to date. It is something very very few people need to use and the whole thing grew organically over time, so documentation wasn't a top priority. A contribution in this direction would be highly welcome. I'm happy to fill in any blanks if such a documentation is started. I don't have time to write the whole thing myself in the short term. bpd = block-progression-dimension of the content rectangle of the area (= height for lr-tb script) bpda = allocated bpd = content bpd + spaces + borders + padding ipd = inline-progression-dimension of the content rectangle of the area (= width for lr-tb script) ipda = allocated ipd = content ipd + spaces + borders + padding Units are millipoints (1000ths of a point) as used in most of FOP (most notably the layout engine). Please note that our area tree is relatively close to the conceptual area tree (with its traits) described in the XSL specification. If you know a bit of the specification, the area tree XML is much easier to read. If you look into our layout engine test suite (test/layoutengine/standard-testcases), you'll find a lot of examples of what is expected in the area tree for various situations. HTH On 25.08.2009 16:26:29 TomWilcox wrote: Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: AW: AW: AW: AW: AW: Area Tree Handling
Hi Jeremias and Georg, Thanks very much. That's really helpful and at least good to know that no proper documentation exists. I have taken the liberty of starting a wiki to share this information whilst I attempt to accumulate more info about the IF tree. If anyone would like to contribute please do. It would be great to produce something of use to anyone else with similar needs. I have added the information that you have both provided me to the wiki page (and cited you both as contributors) please let me know if this is not OK and feel free to edit. Thanks, Tom Jeremias Maerki-2 wrote: There's no formal documentation of the area tree XML format to date. It is something very very few people need to use and the whole thing grew organically over time, so documentation wasn't a top priority. A contribution in this direction would be highly welcome. I'm happy to fill in any blanks if such a documentation is started. I don't have time to write the whole thing myself in the short term. bpd = block-progression-dimension of the content rectangle of the area (= height for lr-tb script) bpda = allocated bpd = content bpd + spaces + borders + padding ipd = inline-progression-dimension of the content rectangle of the area (= width for lr-tb script) ipda = allocated ipd = content ipd + spaces + borders + padding Units are millipoints (1000ths of a point) as used in most of FOP (most notably the layout engine). Please note that our area tree is relatively close to the conceptual area tree (with its traits) described in the XSL specification. If you know a bit of the specification, the area tree XML is much easier to read. If you look into our layout engine test suite (test/layoutengine/standard-testcases), you'll find a lot of examples of what is expected in the area tree for various situations. HTH On 25.08.2009 16:26:29 TomWilcox wrote: Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25136874.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: AW: AW: AW: AW: AW: Area Tree Handling
Hi Jeremias and Georg, Thanks very much. That's really helpful and at least good to know that no proper documentation exists. I have taken the liberty of starting a wiki to share this information whilst I attempt to accumulate more info about the IF tree. If anyone would like to contribute please do. It would be great to produce something of use to anyone else with similar needs. I have added the information that you have both provided me to the wiki page (and cited you both as contributors) please let me know if this is not OK and feel free to edit. http://fop-if-tree.wikispaces.com/ Thanks, Tom Jeremias Maerki-2 wrote: There's no formal documentation of the area tree XML format to date. It is something very very few people need to use and the whole thing grew organically over time, so documentation wasn't a top priority. A contribution in this direction would be highly welcome. I'm happy to fill in any blanks if such a documentation is started. I don't have time to write the whole thing myself in the short term. bpd = block-progression-dimension of the content rectangle of the area (= height for lr-tb script) bpda = allocated bpd = content bpd + spaces + borders + padding ipd = inline-progression-dimension of the content rectangle of the area (= width for lr-tb script) ipda = allocated ipd = content ipd + spaces + borders + padding Units are millipoints (1000ths of a point) as used in most of FOP (most notably the layout engine). Please note that our area tree is relatively close to the conceptual area tree (with its traits) described in the XSL specification. If you know a bit of the specification, the area tree XML is much easier to read. If you look into our layout engine test suite (test/layoutengine/standard-testcases), you'll find a lot of examples of what is expected in the area tree for various situations. HTH On 25.08.2009 16:26:29 TomWilcox wrote: Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25136891.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: AW: AW: AW: AW: AW: Area Tree Handling
Tom, that's great, but why don't you just use our main Wiki? http://wiki.apache.org/xmlgraphics-fop/ Another request: Please call this area tree XML rather than intermediate format. Yes, we called it that in the past but we have two intermediate formats now, so it's necessary to keep the two apart. On 25.08.2009 17:43:16 TomWilcox wrote: Hi Jeremias and Georg, Thanks very much. That's really helpful and at least good to know that no proper documentation exists. I have taken the liberty of starting a wiki to share this information whilst I attempt to accumulate more info about the IF tree. If anyone would like to contribute please do. It would be great to produce something of use to anyone else with similar needs. I have added the information that you have both provided me to the wiki page (and cited you both as contributors) please let me know if this is not OK and feel free to edit. http://fop-if-tree.wikispaces.com/ Thanks, Tom Jeremias Maerki-2 wrote: There's no formal documentation of the area tree XML format to date. It is something very very few people need to use and the whole thing grew organically over time, so documentation wasn't a top priority. A contribution in this direction would be highly welcome. I'm happy to fill in any blanks if such a documentation is started. I don't have time to write the whole thing myself in the short term. bpd = block-progression-dimension of the content rectangle of the area (= height for lr-tb script) bpda = allocated bpd = content bpd + spaces + borders + padding ipd = inline-progression-dimension of the content rectangle of the area (= width for lr-tb script) ipda = allocated ipd = content ipd + spaces + borders + padding Units are millipoints (1000ths of a point) as used in most of FOP (most notably the layout engine). Please note that our area tree is relatively close to the conceptual area tree (with its traits) described in the XSL specification. If you know a bit of the specification, the area tree XML is much easier to read. If you look into our layout engine test suite (test/layoutengine/standard-testcases), you'll find a lot of examples of what is expected in the area tree for various situations. HTH On 25.08.2009 16:26:29 TomWilcox wrote: Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25136891.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: AW: AW: AW: AW: AW: Area Tree Handling
OK Can do.. Jeremias Maerki-2 wrote: Tom, that's great, but why don't you just use our main Wiki? http://wiki.apache.org/xmlgraphics-fop/ Another request: Please call this area tree XML rather than intermediate format. Yes, we called it that in the past but we have two intermediate formats now, so it's necessary to keep the two apart. On 25.08.2009 17:43:16 TomWilcox wrote: Hi Jeremias and Georg, Thanks very much. That's really helpful and at least good to know that no proper documentation exists. I have taken the liberty of starting a wiki to share this information whilst I attempt to accumulate more info about the IF tree. If anyone would like to contribute please do. It would be great to produce something of use to anyone else with similar needs. I have added the information that you have both provided me to the wiki page (and cited you both as contributors) please let me know if this is not OK and feel free to edit. http://fop-if-tree.wikispaces.com/ Thanks, Tom Jeremias Maerki-2 wrote: There's no formal documentation of the area tree XML format to date. It is something very very few people need to use and the whole thing grew organically over time, so documentation wasn't a top priority. A contribution in this direction would be highly welcome. I'm happy to fill in any blanks if such a documentation is started. I don't have time to write the whole thing myself in the short term. bpd = block-progression-dimension of the content rectangle of the area (= height for lr-tb script) bpda = allocated bpd = content bpd + spaces + borders + padding ipd = inline-progression-dimension of the content rectangle of the area (= width for lr-tb script) ipda = allocated ipd = content ipd + spaces + borders + padding Units are millipoints (1000ths of a point) as used in most of FOP (most notably the layout engine). Please note that our area tree is relatively close to the conceptual area tree (with its traits) described in the XSL specification. If you know a bit of the specification, the area tree XML is much easier to read. If you look into our layout engine test suite (test/layoutengine/standard-testcases), you'll find a lot of examples of what is expected in the area tree for various situations. HTH On 25.08.2009 16:26:29 TomWilcox wrote: Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25136891.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25137081.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: AW: AW: AW: AW: AW: Area Tree Handling
Alright Jeremias I have created a page for the AT XML Documentation on the FOP wiki: http://wiki.apache.org/xmlgraphics-fop/AreaTreeXMLDocumentation I have taken the liberty of adding a link to it on the main page to encourage awareness.. Thanks for your help. Tom Jeremias Maerki-2 wrote: Tom, that's great, but why don't you just use our main Wiki? http://wiki.apache.org/xmlgraphics-fop/ Another request: Please call this area tree XML rather than intermediate format. Yes, we called it that in the past but we have two intermediate formats now, so it's necessary to keep the two apart. On 25.08.2009 17:43:16 TomWilcox wrote: Hi Jeremias and Georg, Thanks very much. That's really helpful and at least good to know that no proper documentation exists. I have taken the liberty of starting a wiki to share this information whilst I attempt to accumulate more info about the IF tree. If anyone would like to contribute please do. It would be great to produce something of use to anyone else with similar needs. I have added the information that you have both provided me to the wiki page (and cited you both as contributors) please let me know if this is not OK and feel free to edit. http://fop-if-tree.wikispaces.com/ Thanks, Tom Jeremias Maerki-2 wrote: There's no formal documentation of the area tree XML format to date. It is something very very few people need to use and the whole thing grew organically over time, so documentation wasn't a top priority. A contribution in this direction would be highly welcome. I'm happy to fill in any blanks if such a documentation is started. I don't have time to write the whole thing myself in the short term. bpd = block-progression-dimension of the content rectangle of the area (= height for lr-tb script) bpda = allocated bpd = content bpd + spaces + borders + padding ipd = inline-progression-dimension of the content rectangle of the area (= width for lr-tb script) ipda = allocated ipd = content ipd + spaces + borders + padding Units are millipoints (1000ths of a point) as used in most of FOP (most notably the layout engine). Please note that our area tree is relatively close to the conceptual area tree (with its traits) described in the XSL specification. If you know a bit of the specification, the area tree XML is much easier to read. If you look into our layout engine test suite (test/layoutengine/standard-testcases), you'll find a lot of examples of what is expected in the area tree for various situations. HTH On 25.08.2009 16:26:29 TomWilcox wrote: Hi Guys, Sorry to return your attention to this aging thread! I am knee deep in IF and I have a been attempting to divine what each of the different node attributes represent such as bpd (block progression dimension?), etc. It would be really good to have a definitive description of the meaning and function of each of the attribute (and nodes) in an IF document. I have been searching diligently however I have failed to find any document that completely satisfies this requirement. Would be possible for you provide me with a link to a thorough documentation of the IF format or, if not, perhaps you might be able to provide an explanation of the attributes important for reading the dimension of a given block from an IF document (I think position is bpd, ipd, .. but ipda? and bpda?) and what are the units (millipoints?). I am very grateful for any assistance. Thanks in advance, Tom -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25135373.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25136891.html Sent from the FOP - Users mailing list archive at Nabble.com. Jeremias Maerki - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://www.nabble.com/Area-Tree-Handling-tp24431098p25137549.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: keep is not auto but context is
On 25 Aug 2009, at 12:22, Vincent Hennebert wrote: Keeps do /not/ apply to fo:table-cell: http://www.w3.org/TR/xsl11/#fo_table-cell snip / So whatever that warning means, it is not related to tables. OK, so I guess it's just a coincidence that the warning appears only in table-related tests... Will look into it --sometime ;-) Later Andreas Andreas Delmelle mailto:andreas.delmelle.AT.telenet.be jabber: mandr...@jabber.org skype: adlm0608 --- - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Fwd: Love Apache? Give Back with a MyApache Shoutout!
-- Forwarded message -- From: Sally Khudairi s...@apache.org Subject: Love Apache? Give Back with a MyApache Shoutout! The Apache Software Foundation has become a worldwide force in the software industry because of the diverse programs, applications,and tools built on its projects such as the HTTP Server, Tomcat, Hadoop, Lucene and many others. This year, we’re celebrating 10 years of the ASF! While the Foundation and committers have kept the innovation coming, it's the millions of users who have helped make Apache one of the most pervasive Open Source communities in the world. So, in celebrating the success of Apache, we’re celebrating you. To recognize the breadth of the Apache footprint, we're inviting all Apache users to submit a video telling everyone why you love Apache. Maybe you've created a cool program, Website or device. Maybe you use Apache at work and it makes your life a bit easier. Or perhaps you just love hacking on Apache software. We want to hear all about it! WHO SHOULD SUBMIT? MyApache community video submissions are open for any individual or group who has used or is using Apache code from any Apache project an in interesting way. There is no limit to the number of videos an individual or group can submit, but each video must cover a different Apache use or implementation. WHAT WE'RE LOOKING FOR IN YOUR VIDEO SALUTE Each MyApache video submission should be no longer than 1 minute in length. While we encourage you to get creative and play up the humor, any videos containing inappropriate, distasteful or illegal content will be disqualified and prohibited from being posted. MyApache video content should tell the story of who you are as an Apache user and how you have used Apache. Video content should describe: 1. Things you have created or accomplished with Apache 2. Why you love Apache 3. Your thoughts and happy anniversary wishes to the Apache Software Foundation (singing “Happy Birthday” is encouraged!) Your video content can answer a combination of these questions: Q. Why do I like Apache? Q. Why did I start using Apache? Q. How long have I used Apache? Q. How often do I use Apache? Q. How do I use Apache? Q. Do I use Apache at work, for hobby or other times? Q. What Apache project(s) do I currently work with or have worked with in the past? Q. What was particularly good about those projects or their communities? Q. What and where are some of the improvements I’ve seen in Apache since I began using it? Q. How does Apache differ from other Open Source communities? Q. What is my happy anniversary wish to Apache? Q. Why would I like to thank Apache? HOW TO SUBMIT YOUR MYAPACHE VIDEO To submit your video, go to www.YouSendIt.com and use the Try Sending Now feature to submit your video (you can also sign up for a free YouSendIt Lite account). Videos should be sent to apache...@pageonepr.com with MyApache Video Submission, [Your Name] in the subject line. In the email message, please include the following information. We will tag your video with your first name and last name initial only. Full Name: Age: Email address (for notification): Employer: Title: Open Source affiliations: If submitting a video as a group, please choose one contact person. CREATE A KNOCK-OUT MYAPACHE VIDEO, GET FEATURED AT APACHECON All videos submitted for MyApache will be previewed and posted on TheApacheWay YouTube channel (www.youtube.com/user/TheApacheWay). Videos may also appear on the Websites of The Apache Software Foundation and/or ApacheCon. Outstanding videos will be showcased this November at ApacheCon US during key conference events, and two lucky submittors will be chosen to attend the ASF's Big Feather Birthday Bash during the conference! The deadline to submit your video to have it considered for the ApacheCon showcase is Friday, 2 October, 2009 at midnight Pacific Time. Now that you have the info, you’re ready to start rolling. Lights, camera, action, Apache! # # #
Issue with table border in afp when reference orientation is mentioned for a fo:block-container
Hello Everybody, Can any one guide me how to fix this issue. when i use table border for a table in fo. It displays fine when using it normally but in afp when you try to rotate the table say 90 degrees the border-color is applying for the whole cell and i could'nt see anything. Did anyone faced this kind of problem? Please let me know if you have any solution how to fix this. Thanks, Bharat. -- View this message in context: http://www.nabble.com/Issue-with-table-border-in-afp-when-reference-orientation-is-mentioned-for-a-fo%3Ablock-container-tp25145823p25145823.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
