If I use the word-type match, then a word like carbon. (end of sentence) or carbon, (comma punctuation) or carbon" (quotes) does not get recognized. If I use any of the other match options, then there are issues with matching phrases, such as " carbon sink " or " carbon tax ", when there are multiple words starting with the same beginning word (carbon), quite common in glossaries. A left-string match does not work here. Using the any-string match option gets you matches like hydrocarbon (where it recognizes carbon), again not ideal.
It would help to have an option to ignore punctuation: basically single and double quotes, and parentheses at the left string, and periods, commas, colons, semicolons, parentheses on the right string. We could then match phrases on word match.
I don't know if this is a support request (if there is already an answer, I couldn't find it), a bug report, or a feature request...
Comments
Comment #1
walwyn commentedI have similar problems. I've just added the latest dev release of this module (as the release version has problems with HTML in the descriptions) and this issue is still live. I even have "Left substring" set and still if the word is followed by a full-stop then it isn't linked.Time heals, the glossary links now seem to be displaying properly even with a punctuation. I guess I just hadn't waited long enough for the caches to sort themselves out.
Comment #2
nancydru