From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id DAD687F2E5 for ; Wed, 9 Jan 2013 05:53:53 +0100 (CET) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of thelema314@gmail.com) identity=pra; client-ip=209.85.210.179; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="thelema314@gmail.com"; x-sender="thelema314@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of thelema314@gmail.com designates 209.85.210.179 as permitted sender) identity=mailfrom; client-ip=209.85.210.179; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="thelema314@gmail.com"; x-sender="thelema314@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ia0-f179.google.com) identity=helo; client-ip=209.85.210.179; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="thelema314@gmail.com"; x-sender="postmaster@mail-ia0-f179.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao0BAKP27FDRVdKzm2dsb2JhbABFhjmkQTOJDAGJHQgWDgEBAQEBCAkLCRQngh4BAQQBIx0BGxILAQMBCwYFBAcDCg0dAgIhAQERAQUBChIGExKHcgEDCQYMm12LZE+BcYEKhQUKGScDClmFYAEFDItcb4MrgRMDiGGLVYFWgRyKG4MxFimENA X-IronPort-AV: E=Sophos;i="4.84,435,1355094000"; d="scan'208";a="189012535" Received: from mail-ia0-f179.google.com ([209.85.210.179]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 09 Jan 2013 05:53:52 +0100 Received: by mail-ia0-f179.google.com with SMTP id o25so1088065iad.38 for ; Tue, 08 Jan 2013 20:53:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=b67P4R73RF01J7uTftiwRiZ3ZkRE9282JGSiSvXdHIM=; b=c70vs5hlze24Of3zPOOjgYG348l6jNtoO/FzXL/pcI49uwM0AJ5GjelbzgC6vjyWGn S8glE0z3WVaIOWqdw7hHyr5h1EyDaVJQF3Fd7jqGIpJi1jYuuvUQkyxLk4a0mRS1JRaO nOFK+cZBsI9rUYlwJ2ME5VRzHjIVT/UaSIRCUZ1vb9yvXbUpV+88navEYjj9MzkWl0xK k83XQuF1nC9DxEtbYyvOlPTpwmwMqGxOWTvlAp63ebmINqE1l1F8fl5RFe404R9a9YyD BrCqtFpT89LF3JAluGUqu4axV/r2Toebys9tadi4A5IAoajZP4NE4x7/JlRAR3n3FhBp SFmw== MIME-Version: 1.0 Received: by 10.50.12.166 with SMTP id z6mr275911igb.56.1357707231436; Tue, 08 Jan 2013 20:53:51 -0800 (PST) Received: by 10.50.112.42 with HTTP; Tue, 8 Jan 2013 20:53:51 -0800 (PST) In-Reply-To: <5cf1fdd4-7250-4c57-92f0-9601c90d8cfa@googlegroups.com> References: <5cf1fdd4-7250-4c57-92f0-9601c90d8cfa@googlegroups.com> Date: Tue, 8 Jan 2013 23:53:51 -0500 Message-ID: From: Edgar Friendly To: John Prevost Cc: fa.caml@googlegroups.com, caml-list Content-Type: multipart/alternative; boundary=14dae93406693d1e7f04d2d3d907 Subject: Re: [Caml-list] [ANN] Batteries 2.0.0 released --14dae93406693d1e7f04d2d3d907 Content-Type: text/plain; charset=UTF-8 There is ... light... unicode support. UTF8 strings are still supported, and can be transcoded from and to Latin-1. For anything more complex than that, you'll need to use Camomile or some other unicode library. You're right that these modules somehow got omitted from the API documentation; the online docs are being regenerated as I write this. The disappearance of UCharParser may have been a mistake; looking back at that commit, it looks like it was deleted instead of being modified to fit the removal of camomile. It will probably reappear in batteries 2.1. E. On Tue, Jan 8, 2013 at 8:52 PM, John Prevost wrote: > On Tuesday, January 8, 2013 10:29:25 AM UTC-5, Edgar Friendly wrote: > > ... the issues with Camomile's data files > {...} > > A complete list of API incompatible changes and new additions is > available at > > > > > https://github.com/ocaml-batteries-team/batteries-included/wiki/Interfacechanges12 > > > > and the new documentation is online at > > > > > http://ocaml-batteries-team.github.com/batteries-included/hdoc2/index.html > > The changes page and your comment above suggest that there's still Unicode > character support, but it doesn't seem to be listed in the API > documentation (and the UCharParser module is explicitly mentioned as being > gone, which I wouldn't expect to be the case if there were still Unicode > support.) > > Could you clarify? > > Thanks. > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs --14dae93406693d1e7f04d2d3d907 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
There is ...=C2=A0 light...=C2=A0 unicode support.=C2= =A0 UTF8 strings are still supported, and can be transcoded from and to Lat= in-1.=C2=A0 For anything more complex than that, you'll need to use Cam= omile or some other unicode library.=C2=A0 You're right that these modu= les somehow got omitted from the API documentation; the online docs are bei= ng regenerated as I write this.=C2=A0 The disappearance of UCharParser may = have been a mistake; looking back at that commit, it looks like it was dele= ted instead of being modified to fit the removal of camomile.=C2=A0 It will= probably reappear in batteries 2.1.

E.


On Tue, Jan 8, 2013 at 8:52 PM, John Prevost <= ;j.prevost@gmail.c= om> wrote:
On Tuesday, January 8, 2013 10:29:25 AM UTC-= 5, Edgar Friendly wrote:
> ... the issues with Camomile's data files
=C2=A0 {...}
> A complete list of API incompatible changes and new = additions is available at
>
> https://github.com/ocaml-batteri= es-team/batteries-included/wiki/Interfacechanges12
>
> and the new documentation is online at
>
> http://ocaml-batteries-team.github.com/b= atteries-included/hdoc2/index.html

The changes page and your comment above suggest that there's stil= l Unicode character support, but it doesn't seem to be listed in the AP= I documentation (and the UCharParser module is explicitly mentioned as bein= g gone, which I wouldn't expect to be the case if there were still Unic= ode support.)

Could you clarify?

Thanks.

--
Caml-list mailing list. =C2=A0Subscription management and archives:
ht= tps://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
<= br>
--14dae93406693d1e7f04d2d3d907--