On 22-04-2012 14:24, Lucien GENTIS wrote:
> Hi all,
>
> Have you tried to enter "./build.sh validate-xml" for trunk or 2.4 branch ?
>
> I get hundreds of lines containing
> "manual/developer/modguide.xml:1647:125: Attribute "style" must be
> declared for element type ....." which hide other errors which may appear
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
> For additional commands, e-mail: docs-h...@httpd.apache.org
>
Don't forget the equally famous one:
The content of element type "p" must match
"(em|strong|code|a|br|directive|module
|program|img|cite|q|dfn|var|transnote|glossary|phonetic)"
I've seen the errors, and I know of _a_ solution, which is to loosen up
common.dtd in the build system to allow styles within a <code> tag (and
subsequently allow for <pre> inside a <p>), but the real rub here is
what Igor wrote in an email earlier this week; We don't have a
highlighting function for our documents, yet alone a way to distinguish
between configuration examples and source code, so we're forced to use
"invalid" XML segments in order to make the end result properly readable
for our readers.
So again, I implore anyone who has knowledge of, or knows someone who
knows someone who can help us in creating some form of highlighting
feature, please step forward and let us know. The alternate route would
be to just revert every example back to plain text, which would render
most of it quite unappetizing to most readers.
With regards,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
