Project

Profile

Help

Bug #5940

closed

Should we resolve implicit (or explicit) file: URIs for the -o option?

Added by Norm Tovey-Walsh about 1 year ago. Updated 7 months ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2023-03-24
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
11, 12, trunk
Fix Committed on Branch:
11, 12, trunk
Fixed in Maintenance Release:
Platforms:

Description

The documentation is clear that -o is a filename, but...

  1. If a user specifies -u, it's very tempting to specify a file: URI for -o
  2. Even if a user doesn't specify -u, we detect file: URIs on inputs implicitly, shouldn't we do the same for the output?
Actions #1

Updated by Norm Tovey-Walsh about 1 year ago

  • Status changed from New to Resolved
  • Applies to branch 11, 12, trunk added
  • Fix Committed on Branch 11, 12, trunk added

Added code to check for file: URIs in output files. They're unwrapped to just paths, being careful on Windows to remove the leading slash before a drive letter.

Actions #2

Updated by O'Neil Delpratt 11 months ago

  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 12.2 added

Bug fix applied in the Saxon 12.2 maintenance release.

Actions #3

Updated by Debbie Lockett 7 months ago

  • Status changed from Resolved to Closed
  • Fixed in Maintenance Release 11.6 added

Bug fix applied in the Saxon 11.6 maintenance release.

Please register to edit this issue

Also available in: Atom PDF