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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 737387EEBF for ; Thu, 18 Jun 2015 01:25:07 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=pra; client-ip=74.55.86.74; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of daniel.buenzli@erratique.ch) identity=mailfrom; client-ip=74.55.86.74; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="daniel.buenzli@erratique.ch"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp.webfaction.com) identity=helo; client-ip=74.55.86.74; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="daniel.buenzli@erratique.ch"; x-sender="postmaster@smtp.webfaction.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CZAQDFAIJVnEpWN0pcg2Rfgx68N4JChTkBAQEBAQESAQEBAQEGDQkJIS6ETIELAiYCSRYbAYgmBAmfIo9flkUggSGSGS+BFAWTa4RTiChBhiMPhQ+HEINbgQmDF24BAYJGAQEB X-IPAS-Result: A0CZAQDFAIJVnEpWN0pcg2Rfgx68N4JChTkBAQEBAQESAQEBAQEGDQkJIS6ETIELAiYCSRYbAYgmBAmfIo9flkUggSGSGS+BFAWTa4RTiChBhiMPhQ+HEINbgQmDF24BAYJGAQEB X-IronPort-AV: E=Sophos;i="5.13,636,1427752800"; d="scan'208";a="165896302" Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74]) by mail2-smtp-roc.national.inria.fr with ESMTP; 18 Jun 2015 01:25:06 +0200 Received: from [172.20.10.2] (188.29.165.50.threembb.co.uk [188.29.165.50]) by smtp.webfaction.com (Postfix) with ESMTP id 4B91720F50AA for ; Wed, 17 Jun 2015 23:25:04 +0000 (UTC) Date: Thu, 18 Jun 2015 00:25:03 +0100 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Caml-list Message-ID: <378B8C5CCAA040D3A515940713654B39@erratique.ch> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [Caml-list] [ANN] Uucd 3.0.0 & Uucp 1.0.0 & Uunf 1.0.0 & Uuseg 0.9.0 Hello, Unicode 8.0.0 has been released a few hours ago. It adds 7716 new characters including the sorely missing CHEESE WEDGE (U+1F9C0) character. See [1,2] for the full list of additions and more information. Accordingly the following modules had to be updated. All of this should be available in opam shortly. # Uucd 3.0.0 http://erratique.ch/software/uucd https://github.com/dbuenzli/uucd/blob/v3.0.0/CHANGES.md#v300-2015-06-17-cambridge-uk New properties and new property cases having been added, this is an incompatible release. # Uucp 1.0.0 http://erratique.ch/software/uucp https://github.com/dbuenzli/uucp/blob/v1.0.0/CHANGES.md#v100-2015-06-17-cambridge-uk New blocks and scripts having been added, this is an incompatible release (new variant cases). # Uunf 1.0.0 http://erratique.ch/software/uunf https://github.com/dbuenzli/uunf/blob/399ec05/CHANGES.md#v100-2015-06-17-cambridge-uk Uunf also gets an incompatible release to fix a very stupid API quirk, see the release notes on how to migrate code. The API is now expected to be stable. It also introduces a new Uunf_string module that allows to directly normalize OCaml UTF-X encoded strings (depends on Uutf); if that's your only need you are encouraged to directly use these functions as they could get optimized in the future. Finally it has the latest data to handle 8.0.0's characters. # Uuseg 0.9.0 http://erratique.ch/software/uuseg https://github.com/dbuenzli/uuseg/blob/65f065/CHANGES.md#v090-2015-06-17-cambridge-uk Support for 8.0.0's new line breaking and sentence boundary rules. Also adds a small incompatible change in the custom segmenter API, see the release notes. Best, Daniel [1] http://www.unicode.org/charts/PDF/Unicode-8.0/ [2] http://blog.unicode.org/2015/06/announcing-unicode-standard-version-80.html