| Summary: | Hyperlinks to a directory containing a %20 space are not correctly handled | ||
|---|---|---|---|
| Product: | Fop - Now in Jira | Reporter: | Trejkaz (pen name) <trejkaz> |
| Component: | Assignee: | fop-dev | |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | trunk | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: |
Sample files
Sample files without proper URL encoding possible fix (for PDF output) |
||
Created attachment 23564 [details]
Sample files without proper URL encoding
Attaching sample files which use an un-encoded space instead of %20, demonstrating that this works correctly for some reason.
I just tried this on Foxit Reader, which exhibits the problem in the same way. Apologies for the late reply. Issue checked and confirmed with FOP Trunk. I'll attach a small patch (for Trunk) fixing the issue. It seems that PDF expects the URI to be decoded. Not entirely sure, as I don't have the PDF spec handy at the moment, but I seem to remember that the % sign is also used for PDF escapes, which may be an explanation. Created attachment 24012 [details]
possible fix (for PDF output)
This small patch fixes the issue, at least for PDF. I haven't checked whether this is also a problem for the AWT renderer...
Note: patch was a bit too quick. Encoding the URI in URIAction.toSAX() caused a testcase to fail... resetting P2 open bugs to P3 pending further review |
Created attachment 23563 [details] Sample files Attached zip file contains two FO files which are intended to link to each other's PDF after generation. The directories contain spaces, thus the url has %20 in it. However, on conversion to PDF, FOP appears to have mangled the URL somehow so that it no longer works.