-
Notifications
You must be signed in to change notification settings - Fork 231
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
REP: support suggesting a lowercase replacement for an all-caps input #924
Comments
You can write your dic file as:
If you type FOO then bar will be suggested on right click. |
That is good to know, but that would not work for multi-word replacements, i.e. you cannot do:
|
Replace space with underscore.
Make sure that all 5 words are part of dictionary. (help signal identificador único universal) |
That’s what I tried and did not work (there was no suggestion for UUID), although I did use ^ and $ as seen in my original report. |
I guess REP tag does not support ^ and $ |
Removing ^ and $ does not make a difference, it does not work as I would hope:
I want If I use |
Understood. It took me some time :) |
Imagine a language where “bar” is a good word, and ”FOO“ is a common misspelling:
dic:
aff
At the moment, this suggestion does not work as I would expect. “bar” is not suggested for “FOO”. Nothing is suggested for “FOO”, in fact.
The best workaround I could find was using “foo” in the REP rule, but then the suggestion you get for “FOO” is “BAR”, not “bar”.
In an actual language, this may be relatively common when an acronym needs to be replaced with a regular word (e.g. SOS → help signal). I found this when trying to suggest “identificador único universal” as a replacement for “UUID” in Galician.
The text was updated successfully, but these errors were encountered: