I found a potential problem: The directory Tag in the configuration
takes file paths (not URIs, since we can't detect files on arbitrary
URIs). FontInfoConfigurator doesn't try to resolve relative directories
against the base or font base URI (see #addDirectories() and
note that the file: URL scheme does not technically support relative URLs;
however, that hasn't prevented some implementations from making non-standard
extensions to provide such support
On Fri, Feb 4, 2011 at 7:08 AM, Jeremias Maerki d...@jeremias-maerki.chwrote:
I found a potential problem:
I'm talking about URIs, not URLs. There's nothing in RFC 1630 that
prohibits relative URIs for the file URI scheme. It's actually
describing relative URIs. The file URIs are eventually resolved to file
URLs which are then absolute.
On 04.02.2011 15:50:09 Glenn Adams wrote:
note that the file:
I'm not sure there is a definition of the file scheme that is not a URL
scheme. When 1630 was published, the distinction between URI and URL was not
worked out yet.
At present, the official definition of the file scheme is shown by IANA to
be 1738 (see
On 04 Feb 2011, at 17:40, Glenn Adams wrote:
snip /
so if one specifies
file:///../fop.xml
If I understand correctly, while it does not violate the URI syntax, this would
not be considered a relative URI either way.
That is, java.net.URI will consider it absolute, because it has a scheme
Done. Simon
On Tue, Jan 11, 2011 at 07:40:59PM +0100, Simon Pepping wrote:
On Tue, Jan 11, 2011 at 10:55:25AM +, Peter Hancock wrote:
Hi,
When configuring the base directory using the fop.xconf relative urls
are based on the working directory, and not the fop.xconf.
This
Hi Simon,
You beat me too it :-)
I can confirm it works for a simple case I was considering.
Thanks!
Peter
On Fri, Jan 14, 2011 at 1:04 PM, Simon Pepping spepp...@leverkruid.eu wrote:
Done. Simon
On Tue, Jan 11, 2011 at 07:40:59PM +0100, Simon Pepping wrote:
On Tue, Jan 11, 2011 at
On Tue, Jan 11, 2011 at 10:55:25AM +, Peter Hancock wrote:
Hi,
When configuring the base directory using the fop.xconf relative urls
are based on the working directory, and not the fop.xconf.
This contradicts the URI specification as pointed out in
