Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46923 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42783 invoked from network); 1 Feb 2010 10:33:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2010 10:33:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=mozo@mozo.jp; spf=permerror; sender-id=permerror Authentication-Results: pb1.pair.com header.from=mozo@mozo.jp; sender-id=permerror Received-SPF: error (pb1.pair.com: domain mozo.jp from 209.85.216.203 cause and error) X-PHP-List-Original-Sender: mozo@mozo.jp X-Host-Fingerprint: 209.85.216.203 mail-px0-f203.google.com Received: from [209.85.216.203] ([209.85.216.203:50437] helo=mail-px0-f203.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3D/A3-17169-CEDA66B4 for ; Mon, 01 Feb 2010 05:33:18 -0500 Received: by pxi41 with SMTP id 41so4315995pxi.27 for ; Mon, 01 Feb 2010 02:33:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.141.2.4 with SMTP id e4mr3031710rvi.192.1265020393597; Mon, 01 Feb 2010 02:33:13 -0800 (PST) In-Reply-To: <0_94293100_1264988130.11390.cbgrn@enoch.corp.cybozu.co.jp> References: <0_38978400_1264671673.1668.cbgrn@enoch.corp.cybozu.co.jp> <0_94293100_1264988130.11390.cbgrn@enoch.corp.cybozu.co.jp> Date: Mon, 1 Feb 2010 19:32:53 +0900 Message-ID: To: KITAZAKI Shigeru Cc: Christopher Jones , internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] adding GB18030 support for mbstring From: mozo@mozo.jp (Moriyoshi Koizumi) 2010/2/1 KITAZAKI Shigeru : > * php_syslog.patch > =A0syslog() function cannot properly send UTF-8 strings to event log on > =A0Windows. This patch changes the internal API. We, however, must set > =A0UTF-8 on 'mbstring.internal_incoding'. > =A0In addition, this changes the severity of 'LOG_ERR' from eventlog's > =A0warning to eventlog's error. It seems this doesn't relies on any mbstring settings, but just changed syslog() to take strings encoded in UTF-8 instead of the system's default encoding. It'd look good to me if it had a new flag causing syslog() to switch to the new behaviour. Regards, Moriyoshi