ryan at ryancannon.com
Fri Jan 5 10:24:15 PST 2007
>> I also think the standard should require parsers to match the
>> tag and the visible text (failure meaning the tag is rejected).
> Careful with this: already having accents is not a piece of cake,
> but you
> will have to match
> <a rel="tag" href=".../%E3t%E3">été</a>
> and other niceties (and consider the charset)
> You'll also have the case where the link is on an image...
<a rel="tag" href=".../ee"><abbr title="ee">éé</abbr></a>
<a rel="tag" href=".../ee"><img alt="ee" src="foo.png"></a>
address both of those problems, respectively.
Ciaran McNulty wrote:
> There are also issues with multilingual sites that might want a
> unified tagging scheme.
> e.g. <a href="http://example.com/tags/fish" rel="tag">poisson</a>
This is an interesting problem that I have yet to see discussed in
We do, however, have a few tools to deal with it:
It seems like, at the minimum, you should already be doing
<a href="http://example.com/tags/fish" hreflang="en"
I have yet, however, to encounter a site that uses the hreflang
demarcate links to pages in different languages. In fact, based on
Web Authoring Statistics, hreflang is used less often than <a ;="">
MSI Student, School of Information
University of Michigan
More information about the microformats-discuss