I noticed as I was modifying some fields in a Faq-o-
matic that if I the faqomatic tag is immediately followed
by a punctuation character such as '.' or another tag, it
is parsed incorrectly. For example, if I entered
something like
<li>This is a bunch of text, blah, blah, blah...and please
See also the question <faqomatic[]:26>.</li>
After I save this, the displayed output says "(missing or
broken file)" at that cross reference, and clicking on the
link gives an error:
Warnings:
The file (26>.</li) doesn't exist.
26 is of course a valid node id -- strangely enough the
stuff inbetween [] is replaced with the correct node
name that corresponse to #26. If I change it to
<faqomatic[]:26>. </li>
(Note the space after the period) then it works, but
changing it to:
<faqomatic[]:26></li>
Causes it to fail as well in the same manner, giving the
error:
Warnings:
The file (26></li) doesn't exist
Finally, I settled on <faqomatic[]:26> </li>
(Note one space between > and <) and this fixes the
problem, the display gives the proper node name and the
link works.
Other situations that fail:
<faqomatic[]:26>)
<faqomatic[]:26>&gt;
It seems that the faqomatic meta-tag gets very upset
with non-word characters immediately following it. I'm
new to FAQ-o-Matic but this doesn't seem like it should
be tne intentional behavior, it should be roughly
equivalent to any other HTML tag, and not care about
what's outside it's angle brakets. Am I missing anything?