How do I make a same-document link when already using an xml-base="..." attribute?
Here's my HTML input, http://www.sfu.ca/~jdbates/tmp/css/201001030/manual.html
- and here's the PDF I generated with Prince 7.0, http://www.sfu.ca/~jdbates/tmp/css/201001030/manual.pdf
An example from the input is,
I want this to be a same-document link to the section with id "d1e90", but in the generated PDF, clicking this link instead opens http://ica-atom.org/docs/index.php?title=UM-1#d1e90 in a browser : (
I think it's because of this attribute, xml:base="http://ica-atom.org/docs/index.php?title=UM-1"
If I drop this attribute ^ - then in the generated PDF, clicking the link jumps to the section with id "d1e90" (which is what I want) and doesn't open a browser
- unfortunately, without the xml:base="..." attribute, clicking other links doesn't open the correct URLs and images are missing : (
How do I make a same-document link without dropping the xml:base="..." attribute?
According to RFC 3986 section 4.4, http://tools.ietf.org/html/rfc3986#section-4.4
When a URI reference refers to a URI that is, aside from its fragment
component (if any), identical to the base URI (Section 5.1), that
reference is called a "same-document" reference. The most frequent
examples of same-document references are relative references that are
empty or include only the number sign ("#") separator followed by a
fragment identifier.
In this case my understanding is that the xml:base="http://ica-atom.org/docs/index.php?title=UM-1" attribute defines the "base URI". The relative "URI reference" "#d1e90" resolves to http://ica-atom.org/docs/index.php?title=UM-1#d1e90. Except for the fragment component, this is identical to the base URI, so is a same-document reference?
When a same-document reference is dereferenced for a retrieval
action, the target of that reference is defined to be within the same
entity (representation, document, or message) as the reference;
therefore, a dereference should not result in a new retrieval action.
So clicking this link should jump to the section with id "d1e90", not open a browser?
Is this a problem with Prince, or with my PDF reader? (or my interpretation of the RFC...)
Here's my HTML input, http://www.sfu.ca/~jdbates/tmp/css/201001030/manual.html
- and here's the PDF I generated with Prince 7.0, http://www.sfu.ca/~jdbates/tmp/css/201001030/manual.pdf
An example from the input is,
<a href="#d1e90" title="UM-1.1" shape="rect">UM-1.1 What is ICA-AtoM?</a>
I want this to be a same-document link to the section with id "d1e90", but in the generated PDF, clicking this link instead opens http://ica-atom.org/docs/index.php?title=UM-1#d1e90 in a browser : (
I think it's because of this attribute, xml:base="http://ica-atom.org/docs/index.php?title=UM-1"
If I drop this attribute ^ - then in the generated PDF, clicking the link jumps to the section with id "d1e90" (which is what I want) and doesn't open a browser
- unfortunately, without the xml:base="..." attribute, clicking other links doesn't open the correct URLs and images are missing : (
How do I make a same-document link without dropping the xml:base="..." attribute?
According to RFC 3986 section 4.4, http://tools.ietf.org/html/rfc3986#section-4.4
When a URI reference refers to a URI that is, aside from its fragment
component (if any), identical to the base URI (Section 5.1), that
reference is called a "same-document" reference. The most frequent
examples of same-document references are relative references that are
empty or include only the number sign ("#") separator followed by a
fragment identifier.
In this case my understanding is that the xml:base="http://ica-atom.org/docs/index.php?title=UM-1" attribute defines the "base URI". The relative "URI reference" "#d1e90" resolves to http://ica-atom.org/docs/index.php?title=UM-1#d1e90. Except for the fragment component, this is identical to the base URI, so is a same-document reference?
When a same-document reference is dereferenced for a retrieval
action, the target of that reference is defined to be within the same
entity (representation, document, or message) as the reference;
therefore, a dereference should not result in a new retrieval action.
So clicking this link should jump to the section with id "d1e90", not open a browser?
Is this a problem with Prince, or with my PDF reader? (or my interpretation of the RFC...)