I'm beginning to feel I've stirred a hornet's nest. Not sure if that's
a bad thing though. ;)
On 06/13/2011 03:54 PM, Andreas L. Delmelle wrote:
On 13 Jun 2011, at 12:05, Vincent Hennebert wrote:
On 10/06/11 18:32, Andreas L. Delmelle wrote:
The area tree XML stores the specified "id" as a "prod-id" attribute. There can
definitely be multiple areas with the same prod-id, as a block can be broken over multiple columns
or pages.
Since prod-id is FOP proprietary anyway, I don't immediately see anything
against a convention of allowing this to be a separated list of producer-ids.
Section 6.1.1 of the XSL-FO 1.1 Recommendation [1] mentions the
‘generated-by’ and ‘returned-by’ traits that XSL-FO processors are
supposed to create, and that would probably prove handy in such
situations.
[1] http://www.w3.org/TR/xsl11/#define-returned-by
Interesting catch! Yep, generated-by almost seems synonymous to the current
prod-id, if we substitute the 'formatting object' with its 'id'. Granted, we do
not auto-generate ids just yet...
For the returned-by trait, in order to be able to serialize/externalize it,
there is obviously the question of the format for the separator. Have to make
sure to point out to users that they should preferably not use those (sequences
of) characters in values for the 'id' property, if they use the AT or IF
formats. Or at least, make the implementation robust enough to account for the
(remote) possibility of brackets and commas appearing in an ID.
Regards
Andreas
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
