Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47286 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 43238 invoked from network); 15 Mar 2010 06:20:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Mar 2010 06:20:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=indeyets@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=indeyets@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.78.26 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: indeyets@gmail.com X-Host-Fingerprint: 74.125.78.26 ey-out-2122.google.com Received: from [74.125.78.26] ([74.125.78.26:60586] helo=ey-out-2122.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CE/0E-07348-5A1DD9B4 for ; Mon, 15 Mar 2010 01:20:22 -0500 Received: by ey-out-2122.google.com with SMTP id 4so223068eyf.39 for ; Sun, 14 Mar 2010 23:20:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=hEjvYdKoAEevrUUvC4gxPRVIWxvjkcldCO0MA7nBO6A=; b=tBd1NXJdwACGTxZvUBfYqVlYrj+goQ9Hvi7R7GSTFw3ncJrPh8wi3d3DG0qxWJX1an 4my7pdb1Pzs+pzMOuPx/Xs3Di6lfhNdG8PD8slu1f3rNLTCmw8BTILT4EVAfOdwwWBwT kKsgx6w7p5YMm9PIqQJUHhQwuCixMmaMOY9z0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=i4KN3BN8/mSnaEqQJsv2OEUzu1e40GEmC6Nfrw6GheWg08V0Bi2s4GgpIUbxr+mL2w TKiye8j8+K3sB8IlDB+/8IxO6+kTvjDVcsppFWk/XLv9T+0KJz9e5JlpK73RlxZJldv9 bvlvjgQ8yDQz/mZpSEpA1s1KE4bZpsSfNO/Uk= Received: by 10.213.100.165 with SMTP id y37mr1933367ebn.71.1268634019124; Sun, 14 Mar 2010 23:20:19 -0700 (PDT) Received: from nirvana.lan ([93.185.190.227]) by mx.google.com with ESMTPS id 13sm2332719ewy.9.2010.03.14.23.20.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 14 Mar 2010 23:20:18 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=windows-1252 In-Reply-To: <99cf22521003140743t29ce3ecxeaa0b5d4609ba7a2@mail.gmail.com> Date: Mon, 15 Mar 2010 09:20:15 +0300 Cc: PHP Development Content-Transfer-Encoding: quoted-printable Message-ID: <5F23DE62-C8EC-4499-8001-504A5BBFEFBE@gmail.com> References: <4B9C9007.1080802@lsces.co.uk> <4B9C91D7.2050402@rowe-clan.net> <13008E62F851429F84B9FE2F3F230286@pc> <4bcbf4711003140723s712c2653xa61e8f6053983553@mail.gmail.com> <99cf22521003140743t29ce3ecxeaa0b5d4609ba7a2@mail.gmail.com> To: dreamcat four X-Mailer: Apple Mail (2.1077) Subject: Re: [PHP-DEV] Where are we ACTUALLY on Unicode? From: indeyets@gmail.com (Alexey Zakhlestin) On 14.03.2010, at 17:43, dreamcat four wrote: > You should implement UTF-8, with a view to still allow adding UTF-16 > support later on. That is to say, the encoding should be wrapped, and > switchable underneath. Of course all that is easier said than done > with PHP. But thats the right way to do it. I think you misunderstand and probably there are others too=85 The discussion is not about which encodings should be supported and = which should not. PHP6 in its current form supports pretty much all = encodings there are. The discussion is about which encoding should be = taken as "internal representation". Currently, PHP6 uses UTF-16 for this = purpose.=