Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79265
Return-Path: <rowan.collins@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 12246 invoked from network); 28 Nov 2014 08:58:20 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 28 Nov 2014 08:58:20 -0000
Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender)
X-PHP-List-Original-Sender: rowan.collins@gmail.com
X-Host-Fingerprint: 74.125.82.42 mail-wg0-f42.google.com  
Received: from [74.125.82.42] ([74.125.82.42:64448] helo=mail-wg0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 3F/E7-59154-A2938745 for <internals@lists.php.net>; Fri, 28 Nov 2014 03:58:20 -0500
Received: by mail-wg0-f42.google.com with SMTP id z12so8297890wgg.1
        for <internals@lists.php.net>; Fri, 28 Nov 2014 00:58:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=user-agent:in-reply-to:references:mime-version
         :content-transfer-encoding:content-type:subject:from:date:to
         :message-id;
        bh=N5olM7LYGP/JhcW1vjCPOZ05XPGMh5+XeGrkkMLOC20=;
        b=RYjN5Lqcq96ZsEdx04CbQ54LiCfE7qE3e+t6Rh6trtEZcLYnaScspwcNbbGZIjVSl/
         o4Y/te7URrtoyNmsVfc4IdaEkjqygZmClpfuiU/grz7BAGR/k8/pFivmdkD7EXw3POtV
         7OjAQrrE9gSdcEXNqwydsnfkL330UWOysTLm8MnDQ5QcJ9O/kdUmSHYecskwApUHJli9
         kbPsLoi+8JDgN6xJNrILd39jOfn687kgHSS9riS2liKxgOASaA7m8KiJweGoBYN/np6e
         G78D0U14AsPvmCDWSyO/wKCNTbx+KIVTpSqQDUbd20V6Z9fHmFi7X49KUgjzHRHOf5mD
         xIVA==
X-Received: by 10.194.60.45 with SMTP id e13mr23164766wjr.109.1417165095579;
        Fri, 28 Nov 2014 00:58:15 -0800 (PST)
Received: from [192.168.0.3] (cpc68956-brig15-2-0-cust215.3-3.cable.virginm.net. [82.6.24.216])
        by mx.google.com with ESMTPSA id h13sm28682711wiw.4.2014.11.28.00.58.14
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Fri, 28 Nov 2014 00:58:14 -0800 (PST)
User-Agent: K-9 Mail for Android
In-Reply-To: <54781B8C.3030408@gmail.com>
References: <CAESVnVpkEmCxL-hApFX=iidA+J3Aejw7ryDs1FjomUSkymQpNA@mail.gmail.com> <54767CAC.9060608@gmail.com> <5476DF5C.6040807@gmail.com> <A10502BB-26EE-4A62-9E2F-9BDB40A99D5E@ajf.me> <54774075.2090904@gmail.com> <54781B8C.3030408@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Fri, 28 Nov 2014 08:57:09 +0000
To: Stanislav Malyshev <smalyshev@gmail.com>,internals@lists.php.net
Message-ID: <F322339A-5DDE-4D1E-952F-48F7C3D13303@gmail.com>
Subject: Re: [PHP-DEV] [RFC] IntlChar class and intl_char_*() functions
From: rowan.collins@gmail.com (Rowan Collins)

On 28 November 2014 06:51:56 GMT, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>Hi!
>
>> We already have the single-byte versions: chr() and ord(). It's been
>on
>
>Not really. chr(0xA1) is a byte with value 0xA1. The function I propose
>would instead produce "\xC2\xA1".

Ah, yes, so it would. According to MDN, the JS functions actually return UTF-16, so it's not really the same as those either - it needs to specifically return a UTF-8 byte sequence.