character set for Nepali IDN

[Sarmad Hussain]

Dear John and all,

Agreed that some of the restrictions (PVALID --> DISALLOWED) can go to
language tables, at the registry level.  

However, it is important that that none of the PVALID characters in a
language (as determined by its community) are labelled as DISALLOWED by the
IDNAbis revision process, because it would not be possible to override
DISALLOWED status through the language tables.  That is the case because
applications will not allow users to type in DISALLOWED characters in the
IDNs (as is the current practice). 

Regards,
Sarmad 


 
> -----Original Message-----
> From: John C Klensin [mailto:klensin at jck.com]
> Sent: Tuesday, February 19, 2008 8:16 PM
> To: Basanta shrestha; idna-update at alvestrand.no
> Cc: sarmad.hussain at nu.edu.pk; Bal Krishna Bal; Amar Gurung
> Subject: Re: character set for Nepali IDN
> 
> 
> 
> --On Tuesday, 19 February, 2008 16:32 +0545 Basanta shrestha
> <basanta.shrestha at gmail.com> wrote:
> 
> > Dear Sir/Madam,
> > Listed below are the unicode codepoints and their status to be
> > used for internationalized domain names.
> > Language = Nepali ( ne_NP)
> > Script  = Devanagari
> > Requires ZWNJ & ZWJ ( 200D & 200C)
> >
> >
> > 0901	          PVALID
> > 0902	          PVALID
> > 0903	          PVALID
> > 0904	          DISALLOWED
> >...
> 
> Dear Basanta Shrestha,
> 
> I am trying to study this extremely helpful list but, while I am
> doing so, want to be sure that you are aware of one critical
> issue: neither the DNS, nor any present or proposed version of
> IDNA, are able to make distinctions among languages that share a
> script.  Nepali-specific information may be very useful as a
> recommendation for registries accepting strings to be registered
> as labels in that language but, from an overall IDNA
> perspective, a single list of characters and rules are needed
> for Devanagari, independent of any of the specific languages
> that use that script.
> 
> regards,
>   John Klensin