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.

Sign up for GitHub

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

Jump to bottom

Use utf8 throughout... #16

Open
lyda opened this issue Nov 14, 2012 · 0 comments
Open

Use utf8 throughout... #16

lyda opened this issue Nov 14, 2012 · 0 comments

Comments

@lyda
Copy link
Owner

lyda commented Nov 14, 2012

One of the words from the misspellings list that is not included is gardai -> gardaí due to the fact that utf8 is not supported.

  1. Change the code such that it is.
  2. Add a test case including "gardaí".
  3. Revisit commit 475fe97 and _WORD_REGEX. Change it to do a findall and have it list the chars it allows in words rather than the chars that are not in words. Actually it could even dynamically generate that list from the wordlist it is using.
@lyda lyda mentioned this issue Nov 14, 2012
Closed
myint added a commit to myint/misspellings that referenced this issue Mar 30, 2013
@myint
Add Unicode support
4412b7b 
This addresses items 1 and 2 of issue lyda#16.
@myint myint mentioned this issue Mar 30, 2013
Merged
myint added a commit to myint/misspellings that referenced this issue Mar 31, 2013
@myint
Split on all non-words
d2bc0b2 
Previously, there were some special cases (like "<"). This change takes
care of all non-words instead of just special cases. This resolves item
3 of issue lyda#16 in an alternate way.
myint added a commit to myint/misspellings that referenced this issue Jun 9, 2013
@myint
Add Unicode support
a5894e1 
This addresses items 1 and 2 of issue lyda#16.
myint added a commit to myint/misspellings that referenced this issue Jun 9, 2013
@myint
Split on all non-words
a32d0fc 
Previously, there were some special cases (like "<"). This change takes
care of all non-words instead of just special cases. This resolves item
3 of issue lyda#16 in an alternate way.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lyda