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

Correct responses sometimes invalid, punctuation possibly to blame #80

Open
ghost opened this issue Apr 20, 2016 · 1 comment
Open

Correct responses sometimes invalid, punctuation possibly to blame #80

ghost opened this issue Apr 20, 2016 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 20, 2016

I have noticed that Protobowl will not accept a variety of correct answers for the question.
Examples I have spotted in the wild so far:

  • Titles with typographic quotes sometimes reject exact matches that include the typographic quotes or that substitute in straight quotes (it usually accepts the answer if the quotes are removed altogether)
  • Answers containing the Unicode character RIGHT SINGLE QUOTATION MARK for use as an apostrophe do not accept exact match answers that also contain the apostrophe.
  • A question where the answer was "The Gilded Age: A Tale of To-day" (not in quotes) did not accept an exact match, but I think that hyphen is a regular ol' ASCII hyphen-minus
  • A question where the answer was "The Death of Wolfe" (with quotes, but straight quotes) did not accept an exact match (also with straight quotes).
  • A question where the answer was "UNESCO headquarters/building" (not in quotes) did not accept an exact match.
  • If an answer contains a parenthetical or bracketed note, sometimes an exact answer including the parenthetical note will be rejected.

Sometimes these rejections result in a prompt, sometimes they're just considered incorrect. My original conjecture was that proto was fumbling unicode somewhere (#UnicodeProblems, amirite) but I no longer know what to think.

the death of wolfe

@ghost
Copy link
Author

ghost commented Apr 20, 2017

This is still a problem.

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

No branches or pull requests

0 participants