Louis,<br>there is no more need to oppose any IDNA2008 proposition. They decided to under-support French (and other Latin) languages. As discussed during the March 31 meeting in ENSAM, we now have a growing acceptance of JFC's generalization proposition. It replaces conflicts by complementarity, and defuses the growing political opposition to Unicode, Google and the American bias.<br>
<br>The engaged work just makes IDNA an ADNs application example with two simultaneous architectures (unilateral and multilateral). So, you might want to keep _watching and reporting_ on this list for us, since you are less interested by our ADN analysis. But, please, do not create any contention with this group: whatever their solution and whatever their publication date we will integrate it.<br>
Coridalement.<br><br>Et merci pout toute l'aide que tu nous a apportée. Cordialement.<br>Rémy Renardin. <br><br><div class="gmail_quote">2009/4/2 LB <span dir="ltr"><<a href="mailto:lbleriot@gmail.com">lbleriot@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2009/4/1 Erik van der Poel <<a href="mailto:erikv@google.com">erikv@google.com</a>>:<br>
<div class="im">> Another goal is to avoid forcing the user to type<br>
> lower-case, when ASCII users have never been forced to type<br>
> lower-case. So, software must do the mapping, and therefore the<br>
> protocol must require it.<br>
<br>
</div>It is obvious that this is in contradiction semantics for languages<br>
such as French. This goal forces the francophonie to a separate<br>
system. This was perfectly understood these last days, since the WG<br>
does not concern itself with the support of the writing of French, and<br>
does not allow the management of the total naming space by area<br>
managers. These two points are the first two requirements of cultural<br>
empowerment, as generally understood by French Thought.<br>
<br>
This imposed separate system should take account of remarks by John<br>
Klensin and decisions of managers of areas, without seeking for<br>
reasons of technical details of the Internet strata to reduce the<br>
capacity of the Intersem strata (semiotics, linguistics,<br>
multilinguistics, orthography).<br>
<br>
In return, the naming system compatible with the French language (and<br>
probably many others) that the WG, and the positions taken during and<br>
after San Francisco, now require (we hoped to avoid), should have a<br>
flexibility that leaves each area manager (or group of area managers)<br>
the flexibility to adapt to the constraints of IDNA2008 when<br>
interfacing is required at the application level (since the server is<br>
not concerned).<br>
<br>
----<br>
<font color="#888888">LB<br>
france@large<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</div></div></blockquote></div><br>