Julian Reschke wrote: >> The precedence for this feature comes from the ITS >> (Internationalization Tag Set) in http://www.w3.org/TR/its/, which in >> section 6.2 specifies an its:translate="no" attribute and a rule for >> determining non-translatable content in an XML document. This solves >> the problem for XHTML content, but (obviously) not for HTML. >> ... > > That would work, but it may make pages with technical content very > chatty. It probably would be good to attach that property implicitly to > elements like <code>. For this purposes ITS defines translate rules which can be used to globally override translatability of specific elements/attributes. There is example definition for XHTML (which in turn have many similar elements to HTML5) so it can be taken as a starting point of exception from default translatability setting): http://www.w3.org/TR/xml-i18n-bp/#relating-its-plus-xhtml -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member ------------------------------------------------------------------Received on Thursday, 31 July 2008 21:39:23 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:40:18 GMT