Nicola Ken Barozzi wrote:
IMHO we should eventually support every xhtml2 module, but it's not
strictly needed. Ok to leave it out for now, and see later to include it
via an input module, as it's just a (legacy induced) substitute for
span href=/span.
Today i added the complete XHTML2 RELAX
David Crossley wrote:
CAUTION: I have only skim read the recommendations, I do not consider
myself clued in yet.
Internationalisation:
-
Do we also need the i18n?
14. XHTML I18N Attribute Module
In our current sitemap, the i18n text is
being handled towards the end of
Nicola Ken Barozzi wrote:
10. XHTML Hypertext Module
http://www.w3.org/TR/xhtml2/mod-hypertext.html
* 10.1. The a element
We don't need this, it's use is deprecated in XHTML2 by allowing an href
attribute on any element:
Linking: In HTML 3, only a elements could be the source and
Ross Gardler wrote:
Nicola Ken Barozzi wrote:
10. XHTML Hypertext Module
http://www.w3.org/TR/xhtml2/mod-hypertext.html
* 10.1. The a element
We don't need this, it's use is deprecated in XHTML2 by allowing an href
attribute on any element:
IMHO we should eventually support
Internationalisation:
-
Do we also need the i18n?
14. XHTML I18N Attribute Module
In our current sitemap, the i18n text is
being handled towards the end of the process,
so we need to carry the i18n attributes all the
way through.
Entity references:
--
Entity
Nicola Ken Barozzi wrote:
First of all, we need a sample XHTML2 document that we will use to
render. It will contain all the module elements and attributes that we
will use and should be regularly updated to keep the new ones as we
progress. The content should be a description of the tags
