Skip to content
This repository has been archived by the owner on Aug 26, 2024. It is now read-only.

Uniform treatment of strings in Unicode. #20

Merged
merged 13 commits into from
May 3, 2013
Merged

Uniform treatment of strings in Unicode. #20

merged 13 commits into from
May 3, 2013

Conversation

tlaunay
Copy link

@tlaunay tlaunay commented Mar 15, 2013

Uniform treatment of strings in Unicode. Non-ASCII chars are now considered in strings, which allows for matches in Cyrillic, Chinese, Greek, etc.

Also removed some unused imports and updated the tests.

@josegonzalez
Copy link
Contributor

Are all these commits supposed to be here? If so, I'll pester people at sg so that this gets merged where possible.

(I'm one of the people you contacted on the 5th, sorry for the late reply!)

@tlaunay
Copy link
Author

tlaunay commented Apr 2, 2013

Yes, they are, we are working together! No problem with the late reply. :)

@josegonzalez
Copy link
Contributor

@acslater00 given our internal usage of fuzzywuzzy, does it make more sense to have functions like u_partial_token_set_ratio() which work on unicode strings, or perhaps have a unicode=False argument that can be toggled to get the new code?

If so, I can work with @tlaunay to make the required changes.

acslater00 pushed a commit that referenced this pull request May 3, 2013
Pull Request #20 Augmented With force_ascii parameter
@acslater00 acslater00 merged commit 6e07a3a into seatgeek:master May 3, 2013
@josegonzalez
Copy link
Contributor

This was merged, thanks @tlaunay and @lerignoux for the pull request!

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

Successfully merging this pull request may close these issues.

5 participants