Summary: links to pdf-files on https servers are rendered wrong
                    when creating pdf
           Product: Fop
           Version: all
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: pdf

External links to pdf-files on http-servers and https-servers seem to
lead to different output in fop pdf rendering, with the result that
links to pdf-files on https are not clickable in pdf reading programs.

My source is in docbook xml, example section:

<section> <title>test</title>
<para> <ulink url=""/> </para>
<para> <ulink url=""/> </para>
<para> <ulink url=""/> </para>
<para> <ulink url=""/> </para>
<para> <ulink url="file://index.pdf"/> </para>
<para> <ulink url="index.pdf"/> </para>

With xsltproc I get the same structure for each type of link from my source.
The pdf created from this with fop, however, creates different types of links,
with the result that the https links are not clickable.

As Andreas Delmelle confirmed, there is a bug in subroutine
The order of checks is currently so that, for an "http://"; URL, the code
generates a PDFUri
action, and for an "https://"; URL ending in ".pdf" a PDFGoToRemote action...

The file:// link issue seems already fixed in the trunk version of fop, I can
however not verify it because it fails with some java problem, nor can I build
the trunk version here due to a lack of a build system.

See also the thread on the fop users mailing list:
and Andreas Delmelle's answer:

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to