Describe the reason for these changes and the problem that they solve
This changeset introduces support for markup highlighting of ingredient names that contain non-ASCII characters. This has surfaced as an issue in openculinary/frontend#162.
Briefly summarize the changes
Upgrade to a version of hashedixsearch that supports highlighting of non-ASCII terms
Perform transliteration during stemming of ingredient terms so that an ASCII version of each ingredient name and query is used to term matching purposes (i.e. allow jalapeno to match against jalapeño)
How have the changes been tested?
The underlying hashedixsearch library's unit test coverage demonstates that this is possible
Unit test coverage is provided
Local development testing has been performed
List any issues that this change relates to
Relates to openculinary/hashedixsearch#23
Resolves openculinary/frontend#162
Describe the reason for these changes and the problem that they solve
This changeset introduces support for markup highlighting of ingredient names that contain non-ASCII characters. This has surfaced as an issue in openculinary/frontend#162.
Briefly summarize the changes
hashedixsearch
that supports highlighting of non-ASCII termsjalapeno
to match againstjalapeño
)How have the changes been tested?
hashedixsearch
library's unit test coverage demonstates that this is possibleList any issues that this change relates to Relates to openculinary/hashedixsearch#23 Resolves openculinary/frontend#162