On Tue, 2 Dec 2008, Felix Sasaki wrote: > > > > As has been noted, for more in-depth control, the ITS vocabulary is > > probably the better solution; indeed an ITS tranlation rule set [2] > > could be used to define the processing of a microformat formally. > > Just a clarification question: Do you think that rule set should only be > used to define the processing of the microformat, e.g. > <its:translateRule selector="//*[@class='notranslate']" translate="no"/> > or also for describing defaults like what you proposed e.g. for code, > e.g. <its:translateRule selector="//code" translate="no"/> Either, and also for defining page-specific processing. I'm just pointing out that the problem has already been addressed in more detail. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'Received on Tuesday, 2 December 2008 20:54:32 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:40:56 UTC