I agree with you too, the apparent RX/AH method of creating a
destination for all "id"s seems very inefficient, possibly creating even
security issues (theoretically, if one uses an id like an SSN next to
the text giving data on a person but *without* the intention of the ID
getting into the output PDF document, then mydoc.pdf#someSSN will open
the document to the person's name.) Also, AFAIK the XSL 1.1 Rec does
not mandate us doing this for "id" anyway. So having a fox:destination
*property* in 0.9x instead of a fox:destination FO seems like a better idea.
Glen
Jeremias Maerki wrote:
Agreed, an extension property would be better than fox:destination, but
creating a destination for all "id" attributes doesn't sound ideal to me.
On 25.08.2006 16:11:34 Glen Mazza wrote:
I would prefer avoiding the use of fox:destination, as the XSL WG did
not see a need for a separate FO for this when they placed bookmarks
into 1.1. Instead, I think it would be better to implement it the way
the commercial processors handle them, which is I believe is relying
either on the id on the element to be anchored or another property
[1][2][3]. Relying on a property instead of a new FO would probably be
easier/cleaner than introducing fox:destination back to the source code
anyway, as there would be no XSL document validation issues to be
checking for.
Glen
[1] http://sourceware.org/ml/docbook-apps/2005-q2/msg00214.html
[2] http://www.oasis-open.org/archives/docbook-apps/200602/msg00174.html
[3] http://sourceware.org/ml/docbook-apps/2005-q2/msg00216.html
Jeremias Maerki wrote:
Indeed, we had fox:destination in FOP 0.20.5 but this has not been
reimplemented, yet. Contributions are welcome as always. If you need
pointers, we're always eager to provide those to get you started.
On 24.08.2006 09:59:52 andyrob_24_7 wrote:
Is there a way to achieve destinations in a pdf (so you can link to a certain
page), in FOP?
It seems this is not yet in 0.92?
Jeremias Maerki
---------------------------------------------------------------------
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]
