From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p1SEw1ip005057 for ; Mon, 28 Feb 2011 15:58:01 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AicJAE5Ga01ii1tJeGdsb2JhbACEJJNcMY4qAQwJCgcSBCKsCDyCHYQwiQkBBAQBgSKDRHYEhRCKSw X-IronPort-AV: E=Sophos;i="4.62,240,1297033200"; d="scan'208";a="76743980" Received: from nm3.bullet.mail.sp2.yahoo.com ([98.139.91.73]) by mail3-smtp-sop.national.inria.fr with SMTP; 28 Feb 2011 15:57:56 +0100 Received: from [98.139.91.68] by nm3.bullet.mail.sp2.yahoo.com with NNFMP; 28 Feb 2011 14:57:54 -0000 Received: from [98.139.91.57] by tm8.bullet.mail.sp2.yahoo.com with NNFMP; 28 Feb 2011 14:57:54 -0000 Received: from [127.0.0.1] by omp1057.mail.sp2.yahoo.com with NNFMP; 28 Feb 2011 14:57:54 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 233194.1786.bm@omp1057.mail.sp2.yahoo.com Received: (qmail 70052 invoked by uid 60001); 28 Feb 2011 14:57:53 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1298905073; bh=usIvRmyT8GzaIhb3zsf/gtQWs98jiRxu2s/Mb4S0kSI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=mM8wsbh7iRlfB/QrO6LGTtOrfLbnTf++hFZgSgKM9BDyBTlAavJp1BXenzFlgj+qHeKo9Ds7izgbnJRS1hPq2Y2lA7yUwDmIl9vEldtqXFE3C5nLtw4Qf/SDlMCmcwiuigr/6BBhXE7undsMcTmO25uCc6LB7VsAhUD4fo71xbc= 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:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=WbPOGq7kwz5m1HLFlnt2L4g2lsp+tTZQlUxZBnKg0kSlwkPhFG66shxcgRo7sjczsqxbGKsC7de5ZTl60AGsaxSJwu9zFOnu4G7xLrmIYy7QmFp1WDUsjzDlH5kP+cAqiyKlEDdOUWy2D4Qx9CbWSApiTa7jRaX4NsEnAcqlHDY=; Message-ID: <823650.69992.qm@web111503.mail.gq1.yahoo.com> X-YMail-OSG: 02gCWBIVM1kgRSuTgda4ZYmoQidImJHZC7SGgbttbtIns5G TH9ubtjWY7o269d0Ob4jTR5cab9vsRWFmymuVc8BU6Ime2GBhHTC6L11kdXt NBK0mgJe8kiBXkMi25kHFCzMugKU3s82GkUHLPZZaE9.jY.KaFS262bS8SNc a3SofjWDOTNcIZYaDVUhauO6kTHfBA9XEd.75Syi_.2otS.n0CofDK0B4dpd OuKmauTKCjiBTM0jdHaMng2IKVMGj7.1VpVOdA_DaG0dNQkWYwo5o0pUQcUQ TFsVc1Y0x01sUjV1aSGzCYM.SbHruWJt6RS9bMPxAIQelYCZ4fGLKa4iPvWp A9YANrHkpEPBJ5cSor8JISrpWcNa6tcOSzkJLLYUN0HHLUqJ5KhyuL8zD3wX 4TDPA72QeCTst Received: from [213.205.70.203] by web111503.mail.gq1.yahoo.com via HTTP; Mon, 28 Feb 2011 06:57:53 PST X-Mailer: YahooMailClassic/11.4.20 YahooMailWebService/0.8.109.292656 Date: Mon, 28 Feb 2011 06:57:53 -0800 (PST) From: Dario Teixeira To: caml-list@inria.fr In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id p1SEw1ip005057 Subject: Re: [Caml-list] GSoC: better UTF-8 support Hi, > Frankly I see no benefit of introducing this half-baked UTF-8 support > into the standard library (which is what this proposal is about). I tend to agree with Daniel. In my mind I already rename the stdlib types char/string into byte/blob. For many common operations (like concatenation) it is perfectly safe to use these stdlib blob-oriented functions with UTF8 encoded strings. For others -- like accessing char at position N -- the blob-oriented functions will fail. However, if your app needs UTF8-aware functions, it is very likely that sooner or later you will also need support for some of the more complex aspects of Unicode, at which point a half-arsed implementation will not suffice and you will need to link an external library anyway. Therefore, either the stdlib should remain strictly blob-oriented (which is fine by me), or it should get serious about Unicode support. Cheers, Dario Teixeira