I'm not talking about modifying PunyCode -- we've all agreed that that's out of scope for the charter. What I was thinking about was postprocessing the Punycode result to use the case of the letters in the Punycoded string to carry information about the case of the original string. This is just blue-skying -- nothing should distract from the main order of business, which is getting the charter done.<br>
<br>Mark<br><br><div class="gmail_quote">On Mon, Mar 31, 2008 at 1:10 PM, Vint Cerf <<a href="mailto:vint@google.com">vint@google.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I suspect we will spiral into a nonconvergent path if we start modifying punycode. it is out of bounds in any case for the proposed working group chartedm<br>
<div class="Ih2E3d"><br>
----- Original Message -----<br>
From: <a href="mailto:idna-update-bounces@alvestrand.no">idna-update-bounces@alvestrand.no</a> <<a href="mailto:idna-update-bounces@alvestrand.no">idna-update-bounces@alvestrand.no</a>><br>
To: Mark Davis <<a href="mailto:mark.davis@icu-project.org">mark.davis@icu-project.org</a>><br>
Cc: Sotiris Panaretou <<a href="mailto:panaretou.sotiris@ucy.ac.cy">panaretou.sotiris@ucy.ac.cy</a>>; Patrik Fältström <<a href="mailto:patrik@frobbit.se">patrik@frobbit.se</a>>; John C Klensin <<a href="mailto:klensin@jck.com">klensin@jck.com</a>>; Vaggelis Segredakis <<a href="mailto:segred@ics.forth.gr">segred@ics.forth.gr</a>>; <a href="mailto:idna-update@alvestrand.no">idna-update@alvestrand.no</a> <<a href="mailto:idna-update@alvestrand.no">idna-update@alvestrand.no</a>><br>
Sent: Mon Mar 31 02:09:01 2008<br>
Subject: Re: Greek Casefolding sigma<br>
<br>
</div><div class="Ih2E3d">On Sat, Mar 29, 2008 at 7:49 PM, Mark Davis <<a href="mailto:mark.davis@icu-project.org">mark.davis@icu-project.org</a>> wrote:<br>
> The simplest mechanism would be to then take that set of bits and walk<br>
> through the Punycode, and for each bit in the vector changing each cased<br>
> letter to uppercase to represent a 1 bit, and leaving it lowercase represent<br>
> a 0 bit.<br>
<br>
I recommend against inventing a new mechanism here. Punycode already<br>
provides an "originally-uppercase" bit per source character. Within<br>
IDNA, the uppercase information could be extracted before or during<br>
folding, and then passed into the Punycode-encoding function.<br>
<br>
Unfortunately, there is only one bit per character, which as you point<br>
out is insufficient in some cases for precise representation of the<br>
original character. I am not sure if there is room to reliably extend<br>
the mechanism to 2 bits per character while maintaining compabibility<br>
and not confusing existing implementations that use the predefined<br>
mechanism.<br>
<br>
markus<br>
--<br>
Google Internationalization<br>
</div><div><div></div><div class="Wj3C7c">_______________________________________________<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><br>_______________________________________________<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>
<br></blockquote></div><br><br clear="all"><br>-- <br>Mark