Hello Rui,
Sunday, June 29, 2008, 3:36:58 PM, you wrote:
Removing multibyte encoding support from PHP 5.3 will cause
the severe incompatibility problem with the older PHP 5.x.
As Stefan noted, Shift_JIS character encoding which is widely used in
Japan is not flex safe encoding because it
Hello Marcus,
The script encoding is specified by a couple of different ways.
(1) mbstinrg.script_encoding in php.ini
(2) declare(encopding=Shift_JIS) on each PHP script
- multibyte_encoding_001.phpt
(3) BOM in Unicode script
- multibyte_encoding_00[23].phpt
Removing multibyte encoding support from PHP 5.3 will cause
the severe incompatibility problem with the older PHP 5.x.
As Stefan noted, Shift_JIS character encoding which is widely used in
Japan is not flex safe encoding because it includes 0x5c (backslash) as
second byte of a multibyte
Rui, thanks for your efforts on this. And yes, it would be really good
if you could encourage some people to write more tests for this feature.
We were completely lost in trying to maintain compatibility with this
because of the lack of tests and documentation.
Now we have something to go
On Mon, 16 Jun 2008, Andi Gutmans wrote:
From: Lukas Kahwe Smith [mailto:[EMAIL PROTECTED]
I was under impression parser multibyte support wasn't yet fixed.
Was it?
Maybe we should decide if this a show stopper or not. From my
understanding we still do not have any example of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is used when reading scripts that are in encodings like Shift-JIS
which is very common in Japan. In any case, I have tried to get
involvement from some people I know over there without much success.
I've asked around a bit as well with
On 24.06.2008, at 16:10, Derick Rethans wrote:
On Mon, 16 Jun 2008, Andi Gutmans wrote:
From: Lukas Kahwe Smith [mailto:[EMAIL PROTECTED]
I was under impression parser multibyte support wasn't yet fixed.
Was it?
Maybe we should decide if this a show stopper or not. From my
understanding
On 24.06.2008, at 16:21, Stefan Esser wrote:
If PHP 5.3 drops this feature it might close some multibyte security
problems. However this also means that all those
Japanese/Chinese/Korean/Taiwanese/... multibyte scripts will not run
anymore. This forces systems to stay on PHP 5.2 which will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Lukas,
As such the conclusion can only be that investing any time in readding
this feature would be a bad idea. If anyone actually uses this feature
they will have to come out of the woodwork now or when 5.3 is out. At
this point we might
W liście Stefan Esser z dnia wtorek 24 czerwca 2008:
The problem here is that newer Asian systems will use UTF-8 (except
those nations using characters not possible in utf-8) and therefore the
customers of the PHP developers (on this list) will not need that
support.
UTF-8 can express all
Paweł Stradomski wrote:
W liście Stefan Esser z dnia wtorek 24 czerwca 2008:
The problem here is that newer Asian systems will use UTF-8 (except
those nations using characters not possible in utf-8) and therefore the
customers of the PHP developers (on this list) will not need that
support.
Asbjørn Sloth Tønnesen wrote:
Some some minor inconsistencies, between Shift-JIS and Unicode.
http://en.wikipedia.org/wiki/Unicode#Mapping_to_legacy_character_sets
And I say good riddance! The yen/backslash conflation has given me
plenty a PITA in the past.
--
Edward Z. Yang
Hi!
Maybe we should decide if this a show stopper or not. From my
We had this functionality in 5.x. People used it. There's no reason to
drop it except for patch authors not implementing it.
I think it's just wrong to submit patch dropping significant chunk of
PHP engine functionality,
On 16.06.2008, at 22:04, Stanislav Malyshev wrote:
Hi!
Maybe we should decide if this a show stopper or not. From my
We had this functionality in 5.x. People used it. There's no reason
to drop it except for patch authors not implementing it.
I think it's just wrong to submit patch
-Original Message-
From: Lukas Kahwe Smith [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 14, 2008 3:10 PM
To: Stas Malyshev
Cc: Steph Fox; internals
Subject: Re: [PHP-DEV] New flame
I was under impression parser multibyte support wasn't yet fixed.
Was it?
Maybe we should
PHP 5.3 appears (to me at least) ready for release, give or take a
Will PHP 5.3 be released with fileinfo or will be still me made to use
hacks to detirmine mime types?
Kevin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Kevin Waterson wrote:
PHP 5.3 appears (to me at least) ready for release, give or take a
Will PHP 5.3 be released with fileinfo or will be still me made to use
hacks to detirmine mime types?
Just stumbled on this one myself
The Linux guys have put in a 'nice improvement to attachment
On 01.06.2008, at 07:11, Stanislav Malyshev wrote:
Hi!
PHP 5.3 appears (to me at least) ready for release, give or take a
bit of
ironing.
I was under impression parser multibyte support wasn't yet fixed.
Was it?
Maybe we should decide if this a show stopper or not. From my
PHP 5.3 appears (to me at least) ready for release, give or take a bit of
ironing.
Win32 mail() doesn't.
That's 'a bit of ironing'. The point of the post was:
So can we focus on 6 for a bit please? Like, make it Unicode-only and
iron
out the BC issues arising from that as far as is
Hi!
PHP 5.3 appears (to me at least) ready for release, give or take a bit of
ironing.
I was under impression parser multibyte support wasn't yet fixed. Was it?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
Hi all,
I'd like to set the world on fire before disappearing off for the rest of
the day, so bear with me :)
PHP 5.3 appears (to me at least) ready for release, give or take a bit of
ironing. The only problem is the one of other-version compatibility, which
really is a PHP 6 issue. We
2008/5/30 Steph Fox [EMAIL PROTECTED]:
Hi all,
I'd like to set the world on fire before disappearing off for the rest of
the day, so bear with me :)
At this stage, I was going to say Congratulations, go off and enjoy
yourself. You deserve it!.
Then I read the rest of the message. Now I
22 matches
Mail list logo
