Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I18n support - different languages/countries #48

Open
karussell opened this issue Nov 26, 2012 · 0 comments
Open

I18n support - different languages/countries #48

karussell opened this issue Nov 26, 2012 · 0 comments

Comments

@karussell
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant