When glossary words contain certain special characters, the highlighting of the words in the project can go wrong.
For example, when having the term 'bracket(s)' in the glossary I would expect it to find exact matches in the project to turn into glossary links. It will not detect 'bracket(s)' as being a match but will see 'brackets' as a match. I can understand why this might be the case but it still doesn't quite work - the hover tooltip for 'brackets' doesn't work and appears just as a small empty box with no definition inside.
This also doesn't work correctly in the Bootstrap project, but in a different way. With the same words added to the glossary and the page as example above, this is the result on the Bootstrap page:
When glossary words contain certain special characters, the highlighting of the words in the project can go wrong.
For example, when having the term 'bracket(s)' in the glossary I would expect it to find exact matches in the project to turn into glossary links. It will not detect 'bracket(s)' as being a match but will see 'brackets' as a match. I can understand why this might be the case but it still doesn't quite work - the hover tooltip for 'brackets' doesn't work and appears just as a small empty box with no definition inside.
This also doesn't work correctly in the Bootstrap project, but in a different way. With the same words added to the glossary and the page as example above, this is the result on the Bootstrap page: