-
Notifications
You must be signed in to change notification settings - Fork 467
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
Word "do" is parsed as "tomorrow" #567
Comments
"Do" is short for "Domingo" - Spanish for Sunday. Include argument
Restrict languages to remove these noises. Unfortunately, "next month" is not detected:
|
Oh that's good to know! I didn't know about the But is that the intended behavior? I mean... I get that it detected a word that might mean a date in spanish, but the sentence is not written in spanish at all and clearly the word "Do" does not mean "Sunday" at this sentence in particular |
dateparser cannot detect the language of the whole text and act accordingly. @ArthurSens Do you want this ticket to remain open as a request to add language detection to dateparser? Otherwise, since you can use |
Hmm… dateparser does have some kind of language detection functionality, so maybe this is not too far-fetched. |
I don't have any needs, since I use this module only with some things that I do as a hobby and I don't have the necessary knowledge to help you guys with a PR But if you think it's not troublesome, I guess it would be appreciated by the community (I'd be happy for sure 😄 ) (it's your call to close this or not) |
Command
Current result
Expected result
To be honest, it would be nice if
next month
could be parsed by getting the current month and adding 1...buuuuut the main reason of the issue is that the word "Do" is being interpreted for some reasonThe text was updated successfully, but these errors were encountered: