Hi,
I thought I would try using the LazDoc editor which is built into the
IDE (not standalone lazde). Off the bat it seems to work really well,
but then I built my documentation to html.
All my "see also" links, the <link> tag and the <printshort> tags
used inside the descriptions get escaped and appear exactly as I typed
them in the html generated documentation, instead of creating links.
Seems we have a chicken and egg situation here. The built-in LazDoc
editor escapes everything to generate valid html and the standalone
'lazde' doesn't escape enough. :-) How do we let the different
editors know when to escape text and when not to. Example the & sign
must be escaped, the < and > signs as well, except when they get used
as link tags.
I gather the parser needs to be improved to handle this correctly?
These special rules could get quite complex, quickly. Is there not
maybe a different way we can handle this. Using different tags that
don't conflict with XML tags. Maybe something like the PasDoc or
Javadoc syntax using the @ sign infront of keywords.
example:
@link(text goes here) vs <link>text goes here</link>
I'm using Lazarus 0.9.21 (r10611) and FPC 2.1.1 under Linux.
--
Graeme Geldenhuys
There's no place like S34° 03.168' E018° 49.342'
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
