Re: [Cp-tools-discuss] RFC: Gjdoc and valid HTML

[Julian Scheid]

Julian Scheid wrote:
> The problem with this is that parentheses and commas are not valid 
> characters for the NAME attribute in both XHTML and HTML4.
>
> For XHTML, the NAME attribute should actually be the ID attribute and 
> must match the XML "Name" production which only allows the following 
> ASCII7 characters: Letter, Digit, '.', '-', '_' and ':'.

I've committed a fix to CVS. The default is still to generate pages that 
don't validate but are compatible to javadoc, but now a corresponding 
warning is emitted.

You can use -validhtml to force generation of valid XHTML (and break 
compatibility to javadoc.)

When you use gjdoc (CVS version) to link to external documentation, it 
will detect whether the external docs use valid or compatible names and 
things will work fine.

However, you cannot use javadoc to link to a gjdoc documentation set 
that has been generated with -validhtml.

Also, links to member documentation are mangled when using -validhtml 
and thus not as readable (e.g. in the browser status bar) as in 
compatibility mode.

Julian