From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p1SF9B1G005939 for ; Mon, 28 Feb 2011 16:09:11 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmsFAOxIa01ii1vSeGdsb2JhbACYAI5bAQwJCgcSBCKsSYIdhDiJCQEEBAGFXASFEIpLiFM X-IronPort-AV: E=Sophos;i="4.62,240,1297033200"; d="scan'208";a="88838750" Received: from nm16-vm0.bullet.mail.sp2.yahoo.com ([98.139.91.210]) by mail4-smtp-sop.national.inria.fr with SMTP; 28 Feb 2011 16:09:04 +0100 Received: from [98.139.91.63] by nm16.bullet.mail.sp2.yahoo.com with NNFMP; 28 Feb 2011 15:09:02 -0000 Received: from [98.139.91.29] by tm3.bullet.mail.sp2.yahoo.com with NNFMP; 28 Feb 2011 15:09:02 -0000 Received: from [127.0.0.1] by omp1029.mail.sp2.yahoo.com with NNFMP; 28 Feb 2011 15:09:02 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 892732.62457.bm@omp1029.mail.sp2.yahoo.com Received: (qmail 97836 invoked by uid 60001); 28 Feb 2011 15:09:02 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1298905742; bh=8D5m6sWpZF6BP8twjjpvH42IBtCHVI6LvVCyj4qEifk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=e9hoOS5f/jgpzx/8pdlF3CPIxfu01zpWG1EEdD648TFwJQvxZHypIgMYE1QptBUmXuaKTupABeJrTHYhVB7AmC5jGv9+JyjQClyGJH4Jsr/edKR1dH8y887B4BKt0KI+eCXZN/UEHijd8devWCgL2RuZNh8nLtDTOOrMeMBrLY0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=kwap65dXzGGYsaIJdUdRyCPJntnjXnBdbCKD3VXfRqOlETWRfSRpm7yLZJyHz9S3+gAckTgtXiH7LOCeRgvCfIjfaRS61o09+1eCQIaYW1N4XNkrSXLFnzg55yZ07VR1mKOzu+pwIaSANt2gHyCynKPnl6zye3LlKwjgh86I+8M=; Message-ID: <564395.96781.qm@web111507.mail.gq1.yahoo.com> X-YMail-OSG: iEAbXQIVM1lc1D4gzoT2ID5IEnqLWFr4dvMW16cy0PmD0W8 J10sgEEN59K9glKS2g1_oiu7VVaGlOL3av1k9qI3bm93y_oZT4T8cFSLrd5L Coi3tat69gRiSghdiB0ZeluWU3GcJOBwnMlHzM_1Mtx3i9CgN3Xqu_TxOuOu t9uaE7pr7MWEC003eqOWBmS.zloCZXVsCp2svPRQ6UeEb6D9NqApBKl0YI5m XpLfJiskEBkHZU5i8uylwb1fjpldYBkTY9KVGpwKSzJE26BO78DbFJq8bTmE zuZZTRN5LBFFnRXDwy2_NvSD3IiWzFwAJhJBbBU9PoK.RPHcRvjeXVc1DwqO LmuirZGMOhwG86uBr9GZU1bIAeEvuK4GbGrPSwLUOjt1.AWD.j7g2oa.JPCN V1p..lVHcy103 Received: from [213.205.70.203] by web111507.mail.gq1.yahoo.com via HTTP; Mon, 28 Feb 2011 07:09:02 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.109.292656 Date: Mon, 28 Feb 2011 07:09:02 -0800 (PST) From: Dario Teixeira To: Christophe TROESTLER , Gerd Stolpmann Cc: OCaml Mailing List In-Reply-To: <1298902420.27243.42.camel@thinkpad> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id p1SF9B1G005939 Subject: Re: [Caml-list] GSoC: better UTF-8 support Hi, > Probably you would choose uni_char=int as representation for characters, > but for strings there are several possibilities: > > - 16 bits/char: This path is taken by other languages, but only a >   subset of Unicode chars can be represented directly I think this particular representation should be discarded upfront. It gives the illusion of proper Unicode support, when in fact it is fundamentally broken. Cheers, Dario Teixeira