Hi *, Andreas Delmelle schrieb: >>> <snip /> >>> Whilst you are both technically correct, I made the change because >>> backslashes in file URLs used to work until revision 752153 when >>> Jeremias inadvertantly removed support for this. Whilst this may be >>> against the URL spec this is a feature that improves usability of the >>> product. A lot of users out there aren't aware of the details of RFC >>> 2396 and are used to being able to use backslashes in file URLs >>> (especially on Windows systems). So if we remove support for this we may >>> get a few more questions on fop-user.
For a windows user \ is a valid path separator, and should be kept working as path separator. If this function is the right place may be debatable. > Performing the substitution as part of basic URI resolution, for any > protocol or on another platform introduces a genuine bug, while not > resolving paths as URIs on one platform seems just an inconvenience. Here is another idea: Just substitute File.separator with / Pro: Would satisfy windows users Pro: The "misbehavior" only exists on windows. Con: URI Resolver would work differently on different plattforms. > Cheers > Andreas Max -- http://max.berger.name/ OpenPGP ID: C93C5700 Fpr: AB6638CE472A499B3959 ADA2F989A2E5C93C5700
signature.asc
Description: OpenPGP digital signature
