Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25806 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4053 invoked by uid 1010); 23 Sep 2006 22:46:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 4038 invoked from network); 23 Sep 2006 22:46:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2006 22:46:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=rui_hirokawa@ybb.ne.jp; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rui_hirokawa@ybb.ne.jp; sender-id=unknown; domainkeys=good Received-SPF: error (pb1.pair.com: domain ybb.ne.jp from 203.216.228.252 cause and error) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rui_hirokawa@ybb.ne.jp X-Host-Fingerprint: 203.216.228.252 ybbsmtp20.mail.tnz.yahoo.co.jp FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [203.216.228.252] ([203.216.228.252:21294] helo=ybbsmtp20.mail.tnz.yahoo.co.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 37/72-14982-739B5154 for ; Sat, 23 Sep 2006 18:46:17 -0400 Received: (qmail 7070 invoked by alias); 23 Sep 2006 22:46:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ybb20050223; d=ybb.ne.jp; b=G0eIs4j7hPjvN+4jRfpXJqBustlVlqnMXjyMeYRNYi3za+R66YVuu27FLAaB6edsemkwbzmJJHLyyxjuFXHOHEBUPTsduo5Wz5kIEPzXgmKyYkonCZJ3gVN9IDR6BB18 ; Received: from unknown (HELO ?192.168.1.142?) (rui?hirokawa@219.204.92.5 with plain) by ybbsmtp20.mail.tnz.yahoo.co.jp with SMTP; 23 Sep 2006 22:46:11 -0000 X-Apparently-From: X-yjpVirusScan: Scanned Message-ID: <4515B932.3080901@ybb.ne.jp> Date: Sat, 23 Sep 2006 13:46:10 -0900 User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: derick@php.net CC: internals@lists.php.net Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: RFC: about mb_list_encoding() /mb_list_encodings_alias_names( ), mb_list_mime_names( ) From: rui_hirokawa@ybb.ne.jp (Rui Hirokawa) Hi Derick, Currently, we are discussing about the specification of mb_list_encoding () and some other related functions such as mb_list_encodings_alias_names(), mb_list_mime_names() on mailing list for Japanese PHP developers. In mbstring, the encoding is defined in the three ways (1.character encoding,2.its alias, 3.MIME encoding). mb_list_encoding() returns the list of supported character encodings in mbstring, but, it doesn't return the alias and MIME encoding. The list of alias and MIME encoding are also useful for us. mb_list_encodings_alias_names(), mb_list_mime_names() are recently added as new functions in PHP_5_2 branch. mb_list_encodings_alias_names() returns the supported list of alias encoding. mb_list_mime_names() returns the supported list of MIME encoding. The other solution to support list of alias and MIME encoding is adding an option to mb_list_encoding() such as mb_list_encodings([int type]) type : MB_ENCODING_LISTS_ALL (returns encodings, alias, MIME) MB_ENCODING_LISTS_ALIAS (returns alias) MB_ENCODING_LISTS_MIME (returns mime) MB_ENCODING_LISTS_ENTITY (returns encodings, default for backward compatibility) I know you wrote the function mb_list_encoding() in 2004. -- Revision 1.211 Mon Mar 8 22:18:03 2004 UTC by derick Branch: MAIN - Added mb_list_encoding() to return an array with all mbstring supported encodings. -- What do you think about the specification ? Which way do you prefer to support alias/MIME encoding? 1. adding new functions (mb_list_encodings_alias_names(), mb_list_mime_names()) 2. adding an option to mb_list_encoding(). Regards, Rui Hirokawa