On 06/10/2011 12:50 PM, Hussein Shafie wrote:
I was able to reproduce the problem you describe using attached makefile
(please look at it to see which convertdoc commands I've used).

Now if I uncomment:

###OLINK_PARAMS=-p insert.olink.pdf.frag 1

and run:

make clean all

that is, if I pass parameter insert.olink.pdf.frag=1 to the DocBook XSL
stylesheets, this solves the problem.

I was not able to reproduce the problem at first because I used our own
working environment for that. And in our working environment, we have
always passed parameter insert.olink.pdf.frag=1 to the DocBook XSL
stylesheets.

Reference:

http://docbook.sourceforge.net/release/xsl/current/doc/fo/insert.olink.pdf.frag.html


Many thanks, we forgot about this parameter. According to DocBook XSL documentation, this should work just fine without this parameter in our case though... Excerpt:

"If /|insert.olink.pdf.frag|/ <http://docbook.sourceforge.net/release/xsl/1.75.2/doc/html/insert.olink.pdf.frag.html> is set to zero (the default value), then the |href| attribute from the olink database is not appended to PDF olinks, so the fragment identifier is left off. A PDF olink is any olink for which the |baseuri| attribute from the matching |document| element in the olink database ends with '.pdf'.

If I understand this sentence correctly, it should work in our case (we do not use link fragments in PDF) with *insert.olink.fragment=0*. It this statement correct ? If yes, do you think it's worth reporting the problem to DocBook bug tracker ?

Many thanks again for your very efficient support; we will turn *insert.olink.fragment *to 1 in our DocBook customization to fix the problem for our internal clients.

Best regards.
Philippe.



 
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to