[docs] xmldocs - docelic modified 2 files

docs at icdevgroup.org docs at icdevgroup.org
Fri May 20 18:37:08 EDT 2005

User:      docelic
Date:      2005-05-20 22:37:07 GMT
Modified:  refs     br.tag
Added:     refs     XHTML
Documented XHTML config option

Revision  Changes    Path
1.2       +1 -0      xmldocs/refs/br.tag

rev 1.2, prev_rev 1.1
Index: br.tag
RCS file: /var/cvs/xmldocs/refs/br.tag,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- br.tag	30 Apr 2005 22:56:53 -0000	1.1
+++ br.tag	20 May 2005 22:37:07 -0000	1.2
@@ -3,6 +3,7 @@
 __NAME__ see also

1.1                  xmldocs/refs/XHTML

rev 1.1, prev_rev 1.0
Index: XHTML

__NAME__ purpose
affect Interchange to output XHTML compatible HTML output

__NAME__ see also

__NAME__ synopsis
<group choice='req'>
	<arg choice='plain'>0</arg>
	<arg choice='plain'>1</arg>

__NAME__ description
If the directive is enabled, &IC; produces more XHTML-compliant &glos-HTML;
output. This just includes the insertion of "<literal>/</literal>" 
in standalone tag endings, since argument name lowercasing and argument
option quoting (the other two "things" that make XHTML XHTML)
have been already adopted practices for all HTML output.
To illustrate with an example, tere's say, &tag-br; tag that will, by default,
output &lt;br&gt;, or &lt;br/&gt; if &conf-XHTML; is in effect.

__NAME__ notes
&IC; is gradually adopting XHTML-compliant &glos-HTML; code. Therefore,
some things might still not be XHTML-ready even after users enable
Making HTML output XHTML-compliant is extremely easy (basically, you only
need to lowercase argument names, quote argument options, and include 
<varname>$Vend::Xtrailer</varname> before the ending
"<literal>&lt;</literal>" for standalone tags. That said, XHTML-compliance
patches are gladly accepted to speed up the transition process.

__NAME__ example: Enabling XHTML

More information about the docs mailing list