<br><br><div class="gmail_quote">2009/3/2 Erik van der Poel <span dir="ltr"><<a href="mailto:erikv@google.com">erikv@google.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">>> The current DNS does not allow <a href="http://ecole.fr" target="_blank">ecole.fr</a> and Ecole.fr to resolve to<br></div><div class="Ih2E3d">
>> different IP addresses. So you will have to encode these somehow. This<br>
>> means that you need a prefix. You cannot use xn-- because that is for<br>
>> Punycode. You cannot use Punycode because it does not encode ASCII. It<br>
>> just copies the ASCII characters directly into the output. For<br>
>> example, français is encoded as franais-xxa. Note the directly copied<br>
>> ASCII characters "franais". Appendix A of Punycode (RFC 3492) allows<br>
>> you to encode upper/lower case. So you might have xn--Franais-xxa.fr,<br>
>> but this would resolve to the same IP address as <a href="http://xn--franais-xxa.fr" target="_blank">xn--franais-xxa.fr</a>.<br>
>> So you need something other than Punycode that does not copy ASCII<br>
>> characters directly to the output.<br>
><br>
</div><div class="Ih2E3d">> No. If I include bigtitles as TEMPORARY (cf. my other suggestion),<br>
> "Français" would become "<a href="http://xx--ranais-bfcdq.fr" target="_blank">xx--ranais-bfcdq.fr</a>" but "français" would be<br>
> "<a href="http://xx-franais-xxa.fr" target="_blank">xx-franais-xxa.fr</a>".<br>
<br>
</div>I see. Does this use an assigned Unicode code point for the big F?</blockquote><div><br></div><div>yes. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Good luck with your proposal. Do other French-speakers agree with this proposal?</blockquote><div><br></div><div>This is not a proposal. This is a problem we (French speakers) have to address; and it is a solution. </div>
<div><br></div><div>The problem will be addressed anyway, within IDNA or not. The target we (france@large) have is that it keeps a maximum compatibility/interoperability with IDNA. </div><div><br></div><div>jfc</div></div>