Hide Forgot
Description of problem: It seems that Publican automatically munges the URLs for internal cross-references in such a way that these cross-references work correctly in generated PDF format. But there is an edge case where this URL munging ought not to occur. If I make a reference to a resource under the files/ directory (for example, <link xl:href="files/Messages.zip"/> in DocBook 5 syntax), I would prefer if this mapped to the location of the resource on the Customer Portal. For example, in this case that would be: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2.1/html/Tooling_Tutorials/files/Messages.zip That would make it possible to download the resource file even when clicking on the link from a PDF. At the moment, the URL just gets munged in a way that does not make sense and the resource is inaccessible from PDF.
Just to clarify, the DocBook example I gave in the description above is not quite right (although it is also an edge case that should be handled appropriately. In our DocBook source, the link is defined as follows: <link xl:href="https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2.1/html/Tooling_Tutorials/files/Messages.zip">Messages.zip</link> That is, the full URL is specified in the source. Publican tries to munge this URL when it generates the PDF format.