Name | Type |
---|---|
Hotwords in wiki page description break wiki links to page | tracker item |
hotwords with period at the end do not parse | tracker item |
Hotwords with space between two words | tracker item |
Glossary by way of Hotwords
I was recently looking for a way to easily make a Glossary when I came across the Hotwords feature. I immediately took to the feature and began using it. But I got to thinking, it would be nice if I could enter a description, check mark a box(to include the word in a glossary page) and check mark a box(to use the word as a Hotword). Then just have a wiki page with a {glossary} tag or have a predefined wiki Glossary page. |
tracker item |
Hotwords and WikiWords are parsed to links in Table of Contents (maketoc) entries, breaking HTML
When including a maketoc into a page, the titles in the page are still parsed for WikiWords and Hotwords. This breaks HTML, links, and may decrease the readability of page TOC-s. |
tracker item |
natokpe | tracker item |
Hotwords parsed/expanded with built-in macro {toc}, breaking HTML and links
Hotword processing needs to be turned off for the text expansion of the built-in macro __toc__: {CODE()}{toc}{CODE} If a page name in a structure has spaces, and a defined __hotword__ appears as a name in the page, then the __toc__ expansion is corrupted by the __hotword__ processing. For example, if the page name in a structure is __xxx yyy zzz ddd__ and __zzz__ is a defined __hotword__, then the resulting link out of the __toc__ expansion is the equivalent of: {CODE()}((xxx yyy zzz ddd|xxx yyy)) ((zzz)) ddd{CODE} Note how the trailing portion of the page name is not linked at all now. This may apply to expanding the built-in macro __maketoc__, especially when aliases are shown, as well. Verified on the opensourcecms.org installation as requested. |
tracker item |
"example." <<< does not parse
"example" parses