W3C home > Mailing lists > Public > www-international@w3.org > January to March 2007

RE: IDNs, do they work? (some scripts are less equal than others).

From: Richard Ishida <ishida@w3.org>
Date: Thu, 22 Mar 2007 16:08:54 -0000
To: "'Najib Tounsi'" <ntounsi@emi.ac.ma>
Cc: "'WWW International'" <www-international@w3.org>, "'W3C Offices'" <w3c-office-pr@w3.org>
Message-ID: <006c01c76c9c$66c80130$6401a8c0@rishida>

Najib, 

Your sample files seem to be corrupted. Can you put them on a server somewhere?

Thanks,
RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)
 
http://www.w3.org/People/Ishida/
http://www.w3.org/International/
http://people.w3.org/rishida/blog/
http://www.flickr.com/photos/ishida/
 
 

> -----Original Message-----
> From: Najib Tounsi [mailto:ntounsi@emi.ac.ma] 
> Sent: 07 March 2007 20:28
> To: Richard Ishida
> Cc: 'WWW International'; W3C Offices
> Subject: Re: IDNs, do they work? (some scripts are less equal 
> than others).
> 
> Hi all,
> 
> Here are some additional tests about IDNs and browsers (how 
> do browsers 
> display non US-ASCII scripts in domain names: original or punycode?) 
> (see [1][2]).
> 
> 1) Browsers policy: Firefox claims that for some trusted 
> TLDs, the IDN 
> is displayed in native script. This is true for the scripts 
> tested but 
> not for Arabic or Hebrew.
> See attached file Issue1.html
> So, we should add a new line in the table with an Arabic IDN.
> 
> 2) What do browsers answer in case of syntactically invalid IDN?
> Most browsers display an error message like  "Address not found", 
> without explaining why.
> Only Opera shows "Invalid URL" and explain why.
> See attached file Issue2.html
> 
> 3) Href attribute: Native vs Punicode vs Escape sequence
> - In punycode --> Well, but not very user friendly.
> - In native script --> Well, but security risks (Phishing).
> - In escaped sequences: --> Bad. The IDN doesn't work.
> 
> I think, users should be warned about this last point.
> For example, as an authoring tool, NVU silently modify links  (href 
> attribute value) containing non US-ASCII characters by replacing them 
> with an equivalent escape sequence (e.g.  with %E9). However, 
> this may 
> work for the filePath part of an IRI but not for the domaine 
> name part. 
> A solution is to (re)edit your html in a text editor and 
> repair the href 
> attibutes.
> See attached file Issue3.html
> 
> Best regards,
> 
> Najib
> 
> 
> PS: At the preceding telecon, I've  put a strange note about 
> Safari. I 
> don't remember the exact scenario leading to what I noticed 
> before and 
> tried to find it but nothing wrong happened. So let's forget about it.
> 
> [1]http://lists.w3.org/Archives/Public/public-i18n-geo/2007Feb
/0000.html
> [2]http://lists.w3.org/Archives/Public/public-i18n-geo/2007Feb
/0009.html
> 
> 
> -- 
> Najib TOUNSI (mailto:tounsi @ w3.org)
> Bureau W3C au Maroc (http://www.w3c.org.ma/)
> Ecole Mohammadia d'Ingenieurs, BP 765 Agdal-RABAT Maroc (Morocco)
> Phone : +212 (0) 37 68 71 50 (P1711)  Fax : +212 (0) 37 77 88 53
> Mobile: +212 (0) 61 22 00 30
> 
> --------------------------------------------------------------
> ----------
> 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.16/729 - Release Date: 21/03/2007 07:52
 
Received on Thursday, 22 March 2007 16:08:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:17:09 GMT