Daniel Noll <[email protected]> wrote: > [...] > Is this a bug, a feature, or my misunderstanding the spec?
> I thought external-destination was supposed to contain a > URL, which I would expect to be encoded as a URL. Yet when > I encode it as a URL, the link doesn't work, and when I > "forget" to encode it as a URL, it works. > [...] Well, according to the specification (cf. <URI:http://www.w3.org/TR/xsl/#external-destination>), your premise of using a plain URL is already wrong :-). It has to be given in the form | [...] external-destination="url('whatever')" [...] ^^^^^ ^^ Obviously, that is not really relevant to your problem. From a glimpse at RFC 3987 that is referenced by the specifica- tion, "pct-encoded" (%20) is *allowed* in a URL segment, while a literal space *does* *not* seem to be but "may" be converted to the former form so both forms should be treated in the same way by FOP (or a error be thrown in the later case). You might want to file a bug so that this does not get forgotten. Tim --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
