55
edits
| Line 152: | Line 152: | ||
=== Authors who want to write XHTML, but use content negotiation to serve HTML as text/html to user agents that don't support XHTML === | === Authors who want to write XHTML, but use content negotiation to serve HTML as text/html to user agents that don't support XHTML === | ||
This is the group to whom the XSL transformations are relevant. Serving ''both'' XHTML and HTML requires a transformation, usually using XSL. My suggestion would require one additional template rule. Given such authors will often be transforming not only vanilla XHTML, but XForms, SVG, etc. to HTML equivalents, such a template rule is | This is the group to whom the XSL transformations are relevant. Serving ''both'' XHTML and HTML requires a transformation, usually using XSL. My suggestion would require one additional template rule. Given such authors will often be transforming not only vanilla XHTML, but XForms, SVG, etc. to HTML equivalents, such a template rule is but a drop in an ocean of XSL complexity. (I expect such complexity to be increasingly standardized as XHTML is more widely adopted.) | ||
== Appendix: Autocomplete alternatives == | == Appendix: Autocomplete alternatives == | ||
edits