Project

Profile

Help

Bug #3360

closed

Incorrect parsing of date/time with timezone offset -00:MM

Added by Michael Kay almost 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XPath conformance
Sprint/Milestone:
-
Start date:
2017-07-19
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.7, 9.8
Fix Committed on Branch:
9.7, 9.8
Fixed in Maintenance Release:
Platforms:

Description

When converting a string to an xs:dateTime, a timezone offset such as -00:30 is mis-parsed as +00:30. Specifically, this applies to any timezone offset that is negative and has an hours component of zero. (For a timezone of -00:00, of course, it makes no difference).

The bug has probably been in the product for ever. It applies only to xs:dateTime, not to other types (such as xs:date and xs:time) that use timezones.

Actions #1

Updated by Michael Kay almost 7 years ago

  • Applies to branch 9.7, 9.8 added
  • Fix Committed on Branch 9.7, 9.8 added

Patch committed on the 9.7 and 9.8 branches.

Actions #2

Updated by Michael Kay almost 7 years ago

Correction, the bug applies to xs:dateTime and xs:time, but not to xs:date, or xs:gXXX.

Further patch committed for xs:time in 9.7 and 9.8.

Actions #3

Updated by Michael Kay almost 7 years ago

  • Status changed from New to Resolved

Added QT3 test cases CastAs679 to -686

Actions #4

Updated by O'Neil Delpratt almost 7 years ago

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

Bug fix applied in the Saxon 9.7.0.20 maintenance release.

Actions #5

Updated by O'Neil Delpratt almost 7 years ago

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

Bug fix applied in the 9.8.0.4 maintenance release.

Please register to edit this issue

Also available in: Atom PDF