php-i18n Digest 22 Oct 2001 06:50:18 -0000 Issue 91
Topics (messages 206 through 210):
Re: UNICODE in PHP
206 by: Carl W. Brown
207 by: Rui Hirokawa
208 by: Per
209 by: Andi Gutmans
Why WAIT??? Refinance NOW!!!
210 by: bradnelson.yahoo.com
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Per,
I have develop an open source Unicode support package that would be easy to
integrate into PHP. It provides UTF-8, UTF-16, UTF-32 and many of the
popular MBCS codepages including GB18030 support.
>From what I can remember of the Japanese support package the only thing not
covered with to Unicode support is automatic code page recognition. This is
not hard if all you are doing is determining which Japanese code page it is.
Trying to discriminate between a wide variety of code pages is very
difficult.
There seems to be interest in having Unicode support but not in doing it.
Carl
> -----Original Message-----
> From: Per [mailto:[EMAIL PROTECTED]]
> Sent: Friday, October 19, 2001 11:02 AM
> To: [EMAIL PROTECTED]
> Subject: [PHP-I18N] UNICODE in PHP
>
>
> Hi,
>
> I would be most interested in knowing the current status of multi-byte
> character handling in PHP, and also some kind of forecast of when it is
> expected to work in a stable manner. Currently, there is an experimental
> module for this at http://www.php.net/manual/en/ref.mbstring.php.
> How stable
> is it? Does it support all the "normal" string functions?
>
> Best regards,
> Per Aronsson
>
>
>
> --
> PHP Internationalization Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
Hi,
On Fri, 19 Oct 2001 20:01:38 +0200
"Per" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I would be most interested in knowing the current status of multi-byte
> character handling in PHP, and also some kind of forecast of when it is
> expected to work in a stable manner. Currently, there is an experimental
> module for this at http://www.php.net/manual/en/ref.mbstring.php. How stable
> is it? Does it support all the "normal" string functions?
I think mbstring is fairly stable now.
I already removed ext/mbstring/EXPERIMENTAL from CVS tree.
It doesn't support all string functions, but,
it is very useful to build multi-byte enabled Web applications.
mbstring has some multi-byte string handling functions
shown in below,
- character encoding conversion between Unicode and
japanese encoding (EUC-JP,Shift_JIS,ISO-2022-JP), ISO-8859-1..9
- some string functions with multi-byte string compatibility
strlen, substr, strpos, etc.
- POST/GET/Cookie input character encoding detection and conversion to
internal encoding.
- output character encoding convertion.
mbstring uses gerenal implementaion for multi-language support,
but, currently it supports only japanese multi-byte encoding
and Unicode, and some single byte encoding.
PHP 4.0.6 is the first version of PHP 4 which has multi-byte support.
In japan, almost PHP users are using PHP 4.0.6 with mbstring
or japanese localized version of PHP 3 (called PHP-3.0.18-i18n).
Limitations of mbstring are,
- mbstring doesn't support multi-byte regex.
(You can use mbregex extension.)
- mbstring doesn't support all string functions.
Native unicode support for PHP 4 is neccesary to make
php-i18n.
I hope Zend Engine 2/ PHP 5 (?) will support
this functionality.
--
-----------------------------------------------------
Rui Hirokawa <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
I would like to thank both Carl W Brown and Rui Hirokawa for their
instructive and clarifying replies.
I just now got this link sent to me from Avi Lewin:
http://www.zend.com/zend/week/week58.php where it says:
PHP Weekly Summary: A change of plans for PHP 4.0.7/4.1.0 releases, new
Unicode support, Alternative syntax, Pctnl documentation, fix to ZIP
extension and PayFlowPro for Win32. [15.OCT.2001]
Sounds very promising!
Thank you all!
/Per Aronsson
-----------
"Rui Hirokawa" <[EMAIL PROTECTED]> skrev i meddelandet
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
> Hi,
>
> On Fri, 19 Oct 2001 20:01:38 +0200
> "Per" <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I would be most interested in knowing the current status of multi-byte
> > character handling in PHP, and also some kind of forecast of when it is
> > expected to work in a stable manner. Currently, there is an experimental
> > module for this at http://www.php.net/manual/en/ref.mbstring.php. How
stable
> > is it? Does it support all the "normal" string functions?
>
> I think mbstring is fairly stable now.
> I already removed ext/mbstring/EXPERIMENTAL from CVS tree.
>
> It doesn't support all string functions, but,
> it is very useful to build multi-byte enabled Web applications.
>
> mbstring has some multi-byte string handling functions
> shown in below,
>
> - character encoding conversion between Unicode and
> japanese encoding (EUC-JP,Shift_JIS,ISO-2022-JP), ISO-8859-1..9
> - some string functions with multi-byte string compatibility
> strlen, substr, strpos, etc.
> - POST/GET/Cookie input character encoding detection and conversion to
> internal encoding.
> - output character encoding convertion.
>
> mbstring uses gerenal implementaion for multi-language support,
> but, currently it supports only japanese multi-byte encoding
> and Unicode, and some single byte encoding.
>
> PHP 4.0.6 is the first version of PHP 4 which has multi-byte support.
> In japan, almost PHP users are using PHP 4.0.6 with mbstring
> or japanese localized version of PHP 3 (called PHP-3.0.18-i18n).
>
> Limitations of mbstring are,
>
> - mbstring doesn't support multi-byte regex.
> (You can use mbregex extension.)
> - mbstring doesn't support all string functions.
>
> Native unicode support for PHP 4 is neccesary to make
> php-i18n.
> I hope Zend Engine 2/ PHP 5 (?) will support
> this functionality.
>
> --
> -----------------------------------------------------
> Rui Hirokawa <[EMAIL PROTECTED]>
> <[EMAIL PROTECTED]>
>
No one seems to be working seriously on full Unicode support except for the
mainly Japanese work Rui has done. I thought that the Email from Carl Brown
was quite promising but adding good i18n support to PHP will require much
more interest and volunteers. It seemed that not many people were very
interested.
Andi
At 05:04 PM 10/21/2001 +0200, Per wrote:
>I would like to thank both Carl W Brown and Rui Hirokawa for their
>instructive and clarifying replies.
>
>I just now got this link sent to me from Avi Lewin:
>http://www.zend.com/zend/week/week58.php where it says:
>PHP Weekly Summary: A change of plans for PHP 4.0.7/4.1.0 releases, new
>Unicode support, Alternative syntax, Pctnl documentation, fix to ZIP
>extension and PayFlowPro for Win32. [15.OCT.2001]
>
>Sounds very promising!
>
>
>Thank you all!
>
>/Per Aronsson
>-----------
>
>"Rui Hirokawa" <[EMAIL PROTECTED]> skrev i meddelandet
>[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> >
> > Hi,
> >
> > On Fri, 19 Oct 2001 20:01:38 +0200
> > "Per" <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > I would be most interested in knowing the current status of multi-byte
> > > character handling in PHP, and also some kind of forecast of when it is
> > > expected to work in a stable manner. Currently, there is an experimental
> > > module for this at http://www.php.net/manual/en/ref.mbstring.php. How
>stable
> > > is it? Does it support all the "normal" string functions?
> >
> > I think mbstring is fairly stable now.
> > I already removed ext/mbstring/EXPERIMENTAL from CVS tree.
> >
> > It doesn't support all string functions, but,
> > it is very useful to build multi-byte enabled Web applications.
> >
> > mbstring has some multi-byte string handling functions
> > shown in below,
> >
> > - character encoding conversion between Unicode and
> > japanese encoding (EUC-JP,Shift_JIS,ISO-2022-JP), ISO-8859-1..9
> > - some string functions with multi-byte string compatibility
> > strlen, substr, strpos, etc.
> > - POST/GET/Cookie input character encoding detection and conversion to
> > internal encoding.
> > - output character encoding convertion.
> >
> > mbstring uses gerenal implementaion for multi-language support,
> > but, currently it supports only japanese multi-byte encoding
> > and Unicode, and some single byte encoding.
> >
> > PHP 4.0.6 is the first version of PHP 4 which has multi-byte support.
> > In japan, almost PHP users are using PHP 4.0.6 with mbstring
> > or japanese localized version of PHP 3 (called PHP-3.0.18-i18n).
> >
> > Limitations of mbstring are,
> >
> > - mbstring doesn't support multi-byte regex.
> > (You can use mbregex extension.)
> > - mbstring doesn't support all string functions.
> >
> > Native unicode support for PHP 4 is neccesary to make
> > php-i18n.
> > I hope Zend Engine 2/ PHP 5 (?) will support
> > this functionality.
> >
> > --
> > -----------------------------------------------------
> > Rui Hirokawa <[EMAIL PROTECTED]>
> > <[EMAIL PROTECTED]>
> >
>
>
>
>--
>PHP Internationalization Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]
We can help!
Mortgage Rates have been slashed again!
*Lower your monthly payment!
*Shorten the term of your loan!
*Reduce your interest rate!
SAVE MONEY!!!
NOW is the time to refinance... rates have
NEVER been lower!
We CAN assist everyone, even if you've
been turned down before!
Take just a minute to complete this form
and a Loan Consultant will contact you at
your convenience.
http://www.firstmortgagedebt.com
Your information is secure, confidential and
you are under NO OBLIGATION for this
free analysis.
****************************************************************
Since you have received this message you have either responded
to one of our offers in the past or your address has been
registered with us. If you wish to be removed please reply to:
mailto:[EMAIL PROTECTED]?subject=remove
**********************************************************
