To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=107437
User mst changed the following:
What |Old value |New value
================================================================================
Status|REOPENED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Tue Jan 19 17:28:16 +0000
2010 -------
hi tobys,
yes, i understand that this is not optimal.
unfortunately fixing these problems with util.DateTime would require a lot of
work:
- we cannot change util.DateTime because it is published (any fix would make it
incompatible)
- therefore it is necessary to introduce a new struct, say, NewDateTime
- now comes the hard part: identify all the places in the entire OOo codebase
where DateTime is used, and change these to additionally handle NewDateTime
because currently i don't have the time to do all this work, i've created issue
108348 to track it.
if you want to track the progress, you can subscribe to it by adding yourself to
the CC list.
now, _this_ issue here is about the bug that our XML import code erroneously
rejected valid XMLSchema-Part2 dateTime strings containing timezones, or a minus
sign.
this is now fixed.
please do not reopen this issue here (unless you find a valid dateTime that is
completely rejected by the fixed OOo).
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
