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.

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

Single Quote as an apostrophe in Search Text vs Smart Quote - search fails for words across the two types. #157

Open
nrshapiro opened this issue Apr 14, 2022 · 1 comment
Assignees
Labels
Search Issue Indexing or Search entry issue

Comments

@nrshapiro
Copy link
Contributor

nrshapiro commented Apr 14, 2022

Currently, typing a single quote ' in a search field doesn't find articles where a smart quote ՚ exists, for example

For example, try Day՚s in the title vs Day's

The issue is smart quote/apostrophe is really:

HTML Entity: ’ or ’ or ’

The single quote you type on your keyboard is different. The authoring apps are changing these to smart (curly) quotes.

Smart quotes also exist throughout the database surrounding single quoted phrases, thus involving a &lsquo.

This would also affect double quotes, but these are not allowed in searches anyway.

I am thinking about possible solutions to improving searches where single quotes are part of the search criteria.

@nrshapiro nrshapiro added the Search Issue Indexing or Search entry issue label Apr 14, 2022
@nrshapiro nrshapiro self-assigned this Apr 14, 2022
@nrshapiro
Copy link
Contributor Author

After doing some research, I believe the curly apostrophe is the preferred and correct apostrophe to use in English and in French, at least.

I am thinking about/proposing the following for apostrophes:

  1. Have the data processor stage replace act like a modern word processor and replace all ' with ՚ in the context of an apostrophe or single char quote. Likewise for left curly single quote. This only impacts EXP_ARCH1 (generated) files, not KBD3 files.
  2. Have the server likewise automatically convert single quotes (left and right) in search strings to curly quotes.

Problem solved--Still would need to think of potential negatives. But since no permanent data would be changed, it would be easily reversible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Search Issue Indexing or Search entry issue
Projects
None yet
Development

No branches or pull requests

1 participant