for example -
[[@Headword:The Harbinger: Fact or Fiction?]]
The imbedded colon causes the Headword to be ignored.
If the colon after Harbinger is changed to, say, a dash, or a blank, the headword is not ignored.
experienced in environment -
Logos Bible Software 5.2b SR-8 (5.2.2.1595) Copyright 2000–2014
running windows 8.1 with all available updates applied.
I think this is probably expected behaviour. Headwords can't have colons in them because the colon has other meanings.
That doesn't stop you using a phrase with a colon in to link to a headword:
[[The Harbinger: Fact or Fiction? >> @Headword:The Harbinger]]
The "Headword" markup is intended to be used for dictionary headwords (that you could look up from some other resource); these don't typically contain colons (which is probably why that's not supported properly).
Does this text need to be a headword, or would a heading/table of contents entry be more appropriate?
Bradley, to answer your query - yes, the phrase needs to be a headword.
The solution to resolve the issue would be for the milestone handling routine for Headwords to "ignore" any legitimate colons subsequent to the first colon at the end of the milestone "@Headword:". It's simply a matter of programming the appropriate behavior. This has not been done. Forgive me for being blunt but it is just a matter of programming the desired behavior. Ignoring the headword is NOT the desired behavior.
Thanks for your kind consideration.
Dennis Audet:yes, the phrase needs to be a headword.
It doesn't prevent you from using something like:-
[[@Headword:The Harbinger Fact or Fiction?]] The Harbinger: Fact or Fiction?
The TOC is slightly wrong, but the visible heading has the colon.
Dave===
Windows 11 & Android 8