You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the problem is that date strings in different countries have different meaning. I'm refering e.g. to the following issues #3, #20 and #21 but there are a lot more cases of course.
Now the problem is that the timeZone cannot and should not be used as locale initializer. Because 1. there are different countries in the same time zone but more important: 2. there are German speaking people in the US or english ones in Germany etc. So a new locale attribute for the Parser class needs to be introduced where often a completely different parsing schema is necessary.
The text was updated successfully, but these errors were encountered:
Hey,
the problem is that date strings in different countries have different meaning. I'm refering e.g. to the following issues #3, #20 and #21 but there are a lot more cases of course.
Now the problem is that the timeZone cannot and should not be used as locale initializer. Because 1. there are different countries in the same time zone but more important: 2. there are German speaking people in the US or english ones in Germany etc. So a new locale attribute for the Parser class needs to be introduced where often a completely different parsing schema is necessary.
The text was updated successfully, but these errors were encountered: