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

Allow choice of case sensitivity and or not to use regular expressions in user dictionary entries #39

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 2 comments

Comments

@nvaccessAuto
Copy link

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Reported by mdcurran on 2008-03-09 07:34
Currently user dictionaries force users to create and edit entries as regular expressions. Many users just want to add a simple string replacement, and probably also make it case-sensitive.
The Dictionary Entry dialog (used for adding and editing) should contain two checkboxes (case sensitive, and regular expression). And the userDicthandler code must be changed to support these new features. This change would make NVDA user dictionaries much easier to use, and much like other screen readers' dictionary support. Eventually it may be an idea to rename user dictionaries to speech dictionaries, as I assume this system probably wouldn't be used for braille. Plus, a few users have asked just exactly what user dictionaries are (the name is a little confusing to some).

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Attachment userDictsWithCaseSensitiveAndRegexpOptions.patch added by mdcurran on 2008-03-09 09:56
Description:
Patch that implements the features.

@nvaccessAuto
Copy link
Author

@nvaccessAuto nvaccessAuto commented Jan 1, 2010

Comment 1 by mdcurran on 2008-03-22 07:52
implemented in svn r1847. However user dictionaries have not been named to speech dictionaries yet.
Changes:
State: closed

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

Successfully merging a pull request may close this issue.

None yet
2 participants