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

add support for tentative letters #96

Open
martindemello opened this issue Dec 11, 2023 · 3 comments
Open

add support for tentative letters #96

martindemello opened this issue Dec 11, 2023 · 3 comments

Comments

@martindemello
Copy link

As a solver, I sometimes want to guess at an answer and enter it into the grid, while making it clear that I haven't fully solved the clue and this is therefore not a "firm" entry. It would be useful for exolve to support this, perhaps with some sort of cell background (using lowercase letters is common but that only works for alphabets that have lowercase).

@viresh-ratnakar
Copy link
Owner

I have updated the code to deal with this better.

Please note that Exolve somehow would need to know how to segment a sequence of characters in the placeholder slot into letters. I have taken the same approach for this as in the grid specification: you can separate letters by spaces.

See this documentation that I've now added to the README file:

You may also want to provide placeholder blanks for languages such as Hindi that have compound letters. Exolve recognizes multi-character letters separated by spaces within placeholders. So, if you have a 3-letter clue, and the placeholder text contains "उ स्ता द" then copying this into a 3-letter entry will place "उ" in the first cell, "स्ता" in the second cell, and "द" in the third cell.

@viresh-ratnakar
Copy link
Owner

BTW: there are many times when it would be nice to get weigh-ins from more users, and I find that rarely happening on GitHub Issue/Discussion area. So I've now created a Google Group. Do consider joining: https://groups.google.com/g/exolve-exet-etc

@viresh-ratnakar
Copy link
Owner

Uh. I just realized, that my previous comment should have gone to a different issue altogether :-)

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

2 participants