Re: 4.0.6

From: Date: Mon, 30 Apr 2001 20:56:11 +0000
Subject: Re: 4.0.6
References: 1 2 3 4  Groups: php.dev 
Request: Send a blank email to php-dev+get-53126@lists.php.net to get a copy of this message
On Mon, 30 Apr 2001 18:27:26 +0300 Andi Gutmans wrote: > At 12:23 AM 5/1/2001 +0900, Rui Hirokawa wrote: > > >On Mon, 30 Apr 2001 17:26:58 +0300 > >Andi Gutmans <andi@zend.com> wrote: > > > > > At 10:01 PM 4/29/2001 -0400, Sterling Hughes wrote: > > > >ext/wchar (wide character support?) > > > >ext/mstring (multibyte string functions) > > > >ext/jpstring (japanese string functions) > > > > > > I'd make mstring -> mbstring. > > > The question is if it's worth splitting this up into more than one > > > extension. Probably not. > > > So we should probably be picking out of wchar, mbstring, jpstring. > > > Rui, what do you think? > > > >I prefer unified approach is better for php-i18n than splitting > >some modules. > >I think mbstring is better, although this module also > >supports single-byte encoding like ISO-8859-X. > >Some people might say 'wchar' is better choise, > >because this module converts string to wide character internally. > > > >If someone want to add some other encoding support, > >he should add mbfilter_xx.c mbfilter_xx.h where xx means some > >specific language like ja (japanese). > > > >Anyway, because I am not original author of this module, > >I must discuss to Mr. Tsukada ,the original author of jstring > >about renaming the module. > > OK. I think wchar or mbstring are both good. jstring will just confuse people. > I think mbstring is nice. Takuya Tsukada

« previous php.dev (#53126) next »