You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it's possible for just about any unicode character to be used in Crossword. A crossword puzzle can be created in Russian, for example - the characters can be provided to the creator and a puzzle will be generated properly, and (it looks like) scoring will work properly as well.
Currently the Crossword player has an explicit list of characters that are considered 'allowed input'. These include the 0-9 digits, all English letters, and a number of accented characters common to western European languages. Any character included in a puzzle that is not in that list will be pre-filled and non-editable.
Consider keeping the current set of 'allowed characters' as a 'standard' set but also scraping additional characters from the qset to generate a 'all possible characters for this puzzle' list. Or potentially allowing widget creators to configure a list of allowed/disallowed characters.
The text was updated successfully, but these errors were encountered:
This request comes specifically from a UCF instructor (Kyung Mee Joo) looking for Korean language support, we should focus there if general Foreign language support is too broad.
We currently have limited support for accented characters in the form of a 'special characters' tray that can be shown/hidden at will. Might make sense to try replacing that with a virtual keyboard that supports multiple languages. May need to check out https://github.com/Mottie/Keyboard or https://github.com/klonikar/js-keyboard.
Currently it's possible for just about any unicode character to be used in Crossword. A crossword puzzle can be created in Russian, for example - the characters can be provided to the creator and a puzzle will be generated properly, and (it looks like) scoring will work properly as well.
Currently the Crossword player has an explicit list of characters that are considered 'allowed input'. These include the 0-9 digits, all English letters, and a number of accented characters common to western European languages. Any character included in a puzzle that is not in that list will be pre-filled and non-editable.
Consider keeping the current set of 'allowed characters' as a 'standard' set but also scraping additional characters from the qset to generate a 'all possible characters for this puzzle' list. Or potentially allowing widget creators to configure a list of allowed/disallowed characters.
The text was updated successfully, but these errors were encountered: