[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] URL encoding in html page
> "David Leung (Neteka Inc.)" <firstname.lastname@example.org> wrote:
> > If we use ACE as the URL links then all web designers in the world
> > needs to be retrained for ACE conversion.
> Either the web designer uses an HTML editor, in which case the editor
> should know the HTML syntax rules and convert to/from the local charset
> as needed, or the web designer uses a text editor, in which case the web
> designer is taking responsibility for knowing and obeying the HTML/URI
> syntax rules, one of which is that href and src attributes contain only
> ASCII characters.
So now IDN is a larger scope than we expected, not just browser software
needs to upgrade, even html editor like Dreamweaver, etc needs to upgrade...
interesting idea... I am wondering how many companys will be affected by
this if even HTML editors or text editors need to upgrade, and what about if
they are using an editor and really wants to but something like "bq--xxxx"
on the page, should the editor shows the local encoding on the interface and
keep the ACE in the backend or people are not able to put anything that
looks like an ACE domain on homepage anymore...
> Maybe future HTML/URI specs will allow non-ASCII characters in href and
> src attributes, but it's not obvious how to do that without breaking
> deployed browsers, and that discussion is for another forum.
I guess this is simiilar to say that if some one put a IPv6 link on the page
and will break some browsers that follows old specs, upgrading an RFC
document so that URI can contains non-ASCII is not that hard of a thing...
Hmm... also I am still wondering what kind of variable definition will treat
7bits and 8bits differently and will cause a overflow... : )