W3C home > Mailing lists > Public > uri@w3.org > August 2013

Re: Standardizing on IDNA 2003 in the URL Standard

From: John C Klensin <klensin@jck.com>
Date: Wed, 21 Aug 2013 21:50:47 -0400
To: John Cowan <cowan@mercury.ccil.org>
cc: Shawn Steele <Shawn.Steele@microsoft.com>, Gervase Markham <gerv@mozilla.org>, "Jungshik SHIN (신정식)" <jshin1987@gmail.com>, Simon Montagu <smontagu@smontagu.org>, public-iri@w3.org, uri@w3.org, idna-update@alvestrand.no, Peter Saint-Andre <stpeter@stpeter.im>, Anne van Kesteren <annevk@annevk.nl>, "www-tag.w3.org" <www-tag@w3.org>
Message-ID: <AE211FCA6E8066534BA62333@JcK-HP8200.jck.com>


--On Wednesday, August 21, 2013 17:30 -0400 John Cowan
<cowan@mercury.ccil.org> wrote:

> John C Klensin scripsit:
> 
>> That would have meant no separate code point for a final
>> sigma in Greek;
> 
> See my earlier post for why that's not possible.
> 
>> no separate code points for final Kaf, Mem, Nun, Pe, or Tsadi
>> in Hebrew;
> 
> This is even less possible.  In Hebrew, a pe at the end of a
> word is always /f/.  But in Yiddish, there is a contrast
> between /p/ and /f/ in final position that Hebrew does not
> have, and in that case a non-final pe in final position is
> used for /p/, sometimes but not always with a dagesh (embedded
> dot).
> 
> In short, Greek and Hebrew positional variants require AI-hard
> algorithms.

John,

As I said, I know a rather long list of reasons why the model I
tried to describe was not reasonable or desirable and suggested
that people more expert would have an even longer list.  

Your note only reinforced that impression.

The point was merely to suggest that there are no simplistic and
still fully general solutions to the relevant set of problems.
Your note reinforce that suggestion too.

thanks,

   john
Received on Thursday, 22 August 2013 01:51:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:16 UTC