-
Notifications
You must be signed in to change notification settings - Fork 19
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
Accent mark handling #6
Comments
It goes even further...
|
@clvLabs so sorry I missed this notification from last year 😱! What would you like to see as the handling for this case? Should draw warn that the spelling has been corrected? Thank you for filing this issue :)) |
Ah, or simply replace the "word" field with the corrected one returned by RAE 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When searching for words with accent marks, there's an odd behaviour:
ficción
), everything works as expectedficcion
) the accent mark has been omitted and the search engine manages to find it anyway 👍 . But the returned object includes the wrong spelling in theword
fieldfíccion
) a wrong accent mark has been added and the same thing happensPeekin'round the code found that the word used to generate the returned object is the same received by parameter - define.go:127
Haven't gone thru the scraping details, but I guess the correct word spelling will be in the returned document.
It would be a very nice feature to have (I use drae very frequently) since sometimes I don't feel confident about having the spelling right even if I check the dictionary (so I have to go to the official site)
BTW, thanks a lot for drae!!!!
The text was updated successfully, but these errors were encountered: