> But that is exactly the problem I want to address: if you type: > > SOMETHING<U+FF0E>JP > > For example, it will not be seen as a domain name in the .JP > domain, even though this was the intent (let's say also that > JP can be in full-width ASCII, which makes the U+FF0E very > plausible). Just like typing: > > SOMETHING<U+3002>JP > > won't. This is the exact same thing. So I think we need to > handle it just like U+3002 is handled. I wasn't really clear. Since it's forbidden because of the compatibility mapping, all I want is some text that identifies that as a caveat for IDN implementers, so that they don't just map U+3002 to U+002E before Nameprep and then wonder why this one doesn't work. YA
