-
Notifications
You must be signed in to change notification settings - Fork 120
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
Make glossary entries case insensitive #703
Comments
IME, this is not true. Terms are case-insensitive. Perhaps provide an example of a failure, because there could be another factor (e.g. not being detected as a whole word correctly, due to parentheses) |
Hi @webaware, |
I can confirm the glossary matching is case sensitive, it's an easy technical fix. |
Thanks @toolstack |
Ah yes, indeed I have GlotDict. My bad for not reading the trac ticket. |
All good @webaware, was my bad for not posting here originally |
Hello,
With Glotpress Glossary the words within the glossary are underlined on the original string making it easier to see what should be translated. That's especially helpful with the flavoured english translations (Canadian, a=Australian, etc). But currently they're all case sensitive so if you have color>colour in the glossary but it's a single word string for Color then it won't be underlined.
Would be nice if glossary terms are case-insensitive. Please let me know if this won't be picked up anytime soon as I'll manually add capitalized versions to the Glossary.
Thank you
Original meta.trac ticket - https://meta.trac.wordpress.org/ticket/2778
The text was updated successfully, but these errors were encountered: