[fpc-pascal] fpcdoc gives a lot of warnings
Michael Van Canneyt
michael.vancanneyt at wisa.be
Wed Dec 13 14:35:49 CET 2006
On Wed, 13 Dec 2006, Vincent Snijders wrote:
> Hi,
>
> If I use thhe fpc 2.1.1 version of fpdoc on the rtl documentation files, I get
> a lot of warnings like:
>
> Writing 7520 pages...
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [<no context>] Invalid description (illegal XML element: "#text")
> [#rtl.strutils.AnsiMatchText] Invalid description (illegal XML element:
> "#text")
> [#rtl.strutils.AnsiMatchText] Invalid description (illegal XML element:
> "#text")
> [#rtl.strutils.AnsiMatchText] Invalid description (illegal XML element:
> "#text")
> [#rtl.strutils.AnsiMatchStr] Invalid description (illegal XML element:
> "#text")
> [#rtl.strutils.AnsiMatchStr] Invalid description (illegal XML element:
> "#text")
> [#rtl.strutils.AnsiMatchStr] Invalid description (illegal XML element:
> "#text")
>
> Do you have an idea, what causes this? Is the new parser adding #text nodes,
> that the old parser didn't? Is fpdoc's checking too strict?
Hm. I don't know. looking at strutils.xml, I think it is a whitespace issue:
I assume it thinks there is too much whitespace between <descr> and the
starting <p> tag. I'll have to check this.
Michael.
More information about the fpc-pascal
mailing list