On Wed, 25 Jun 2008, Julian Reschke wrote:
> >
> > Indeed. However, valid pages aren't the only pages that we want
> > interoperability for.
>
> True.
>
> But it seems to me it's much more important to come up with a
> interoperability for *valid* pages than invalid ones.
I don't know which is more important, but in any case, my intent is to
come up with interoperability for both, so it doesn't really matter.
> So documenting the current mess with respect to handling IRIs may be
> useful for browser implementors, but fixing the issue in a sane way
> would be much more useful for everybody else (yes, not in the short-term
> future).
To get to the long-term we have to go through the short-term first. We'll
never get to the long term if there's no path through the short-term that
is compatible with existing content.
(On the long term, I figure we'll just use UTF-8 exclusively, which would
pretty much solve the problem, and is compatible with a short-term
strategy like the one described in HTML5 now.)
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'