Could you add some chars to the boundary check in "_glossary_is_boundary" function ?
(or a str_replace when setting $searchtext in "_glossary_insertlink")

1. ’
2. “
3. ”
4. ´
5. °
6. ®

Maybe this concerns utf8 characters and perhaps there are also other ones...

Thank you for your work!
Devis Lucato

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Title: _glossary_is_boundary , new chars » Additional word boundary characters
Status: Active » Postponed (maintainer needs more info)

I have no problem looking at this to see if I can do it. The big problem I see at the moment is that these characters can be typed in several different ways, not the least of which is as HTML entities.

Devis’s picture

Devis commented

In my case these characters are present without html encoding, as is.

HTML encoding should be already supported because html codes start and finish with "&" and ";".

1) &34;keyword&34;

2) “keyword”

Case 1 should be already supported, but not case 2.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Postponed (maintainer needs more info) » Fixed

I'll raise you by ©¼½¾.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.