Add new method parseDate2(..) with fixed behaviour for Dst offset

[andriy-samson]

To revial the problem of Daylight Saving Time(DST), you can uncomment the test case: DateParserTest.test_showsDstProblem() Also, I think that the problem is visible only when it runs on machine with time zone where DST is active during the test. For example on machine with regional settings of time zone where the it has DST activated (summer period)

To avoid backward compatibility problem I didn't change the internal implementation of DateBuilder.toDate() method wher the original time zone offset computation is done. Instead I try to add a new method with expected (fixed) fixed behaviour.

Let me know if you need more information, Regards, Andriy

[sisyphsu]

You modified too many codes, I cannot accept it, sry.

And I think there should have a better way to support DST offset, pls give me some time.

[andriy-samson]

Thanks for your feedback. I didn't expect this pull request to be accepted it as it is. In this pull request I would like just to show the problem (in test cases) and possible solution just using external API. For sure there is a better fix. The real fix has to be done in DateBuilder.toDate() or deeper.

The idea is simple:

• If a time zone is detected in parsed datetime, then any DST computation should be ignored, because parsed time zone does not have information about exact geographical region. Because a single time zone can have multiple geographical region with different DST rules.
• If time zone is not present in parsed datetime, then a local time zone is used for computation and its DST will be automatically applied.

I will try to revert all and find a better solution for this problem.

Regards, Andriy.