Kenneth Whistler wrote: > Technically, the two approaches are identical, since the repertoire is > defined against Unicode 3.0 and not yet assigned characters are > forbidden. While the two approach is the same, common implementation will take the current I-D as "allow unless specify otherwise". I am not sure what will happened when we have no script in later version. Hence, I am more in favour with "disallow unless specify otherwise". (This is the third time i am hammering this at Paul :-) -James Seng
- [idn] nameprep forbidden characters Adam M. Costello
- Re: [idn] nameprep forbidden characters Mark Davis
- Re: [idn] nameprep forbidden characters Edmon
- Re: [idn] nameprep forbidden characters Kent Crispin
- RE: [idn] nameprep forbidden characters Wael Nasr
- Re: [idn] nameprep forbidden characters Kenneth Whistler
- Re: [idn] nameprep forbidden characters Rick H Wesson
- Re: [idn] nameprep forbidden characters James Seng
- Re: [idn] nameprep forbidden characters James Seng
- Re: [idn] nameprep forbidden characters Rick H Wesson
- Re: [idn] nameprep forbidden characters Randy Bush
- Re: [idn] nameprep forbidden characters Kenneth Whistler
- RE: [idn] nameprep forbidden characters Jonathan Rosenne
- Re: [idn] nameprep forbidden characters James Seng
- Re: [idn] nameprep forbidden characters Dave Crocker
- Re: [idn] nameprep forbidden characters Patrik F�ltstr�m
- Re: [idn] nameprep forbidden characters Paul Hoffman / IMC
- Re: [idn] nameprep forbidden characters James Seng
