On Tue, May 31, 2011 at 10:42 AM, Stas Malyshev wrote:
> Hi!
>
>
> I was under the impression it was a drop-in-replacement, so a pecl ext
>>
> doesn't make much sense.
>
> I'd say if it's a drop-in PECL ext may still make sense - you don't compile
> in the old one but use the PECL one instead. Wo
Hi!
I was under the impression it was a drop-in-replacement, so a pecl ext
doesn't make much sense.
I'd say if it's a drop-in PECL ext may still make sense - you don't
compile in the old one but use the PECL one instead. Wouldn't it work?
--
Stanislav Malyshev, Software Architect
SugarCRM:
On Tue, May 31, 2011 at 09:44, Stas Malyshev wrote:
> Hi!
>
>>> I set up a RFC page for this in wiki.php.net. Here it goes:
>>> http://wiki.php.net/rfc/altmbstring
>>
>> So.. Shouldn't we try to get this into PHP5.4?
>
> Is it ready? Maybe have it as a PECL extension?
I was under the impression
Hi!
I set up a RFC page for this in wiki.php.net. Here it goes:
http://wiki.php.net/rfc/altmbstring
So.. Shouldn't we try to get this into PHP5.4?
Is it ready? Maybe have it as a PECL extension?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext.
On Tue, Jul 28, 2009 at 10:41, Moriyoshi Koizumi wrote:
> I set up a RFC page for this in wiki.php.net. Here it goes:
> http://wiki.php.net/rfc/altmbstring
So.. Shouldn't we try to get this into PHP5.4?
-Hannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
On Tue, Aug 4, 2009 at 2:47 AM, Stanislav Malyshev wrote:
>> And yes, it's worth providing separate conversion system. You might
>> not be aware of it, but there are several sets of different character
>> sets, each of which is often represented with a specific encoding
>> scheme. Shift_JIS is o
Hi!
It can be done through conversion error handlers. You can append an
encoded form of a codepoint for such unassigned characters to the
buffer within the handler.
OK, if so we may want to add implementation of this behavior to our ICU
support.
And yes, it's worth providing separate conve
On Sat, Aug 1, 2009 at 9:02 AM, Stanislav Malyshev wrote:
> Hi!
>
>> They calculate the total width of a string based on "east asian width"
>> property, which is still valid to give a rough measurement of the
>> rendered string.
>
> OK, I guess if it's some kind of special calculation that doesn't
Hi!
They calculate the total width of a string based on "east asian width"
property, which is still valid to give a rough measurement of the
rendered string.
OK, I guess if it's some kind of special calculation that doesn't follow
from others it should be preserved, there are tons of such spe
Hi,
On Sat, Aug 1, 2009 at 1:37 AM, Stanislav Malyshev wrote:
> Hi!
>
>>> mb_str* - shouldn't you in 6 just convert them to unicode and do all
>>> string
>>> operations with Unicode strings? Also, in 5 isn't there some intersection
>>> with grapheme_* functions?
>>
>> mb_strwidth() and mb_strimwid
Hi!
mb_str* - shouldn't you in 6 just convert them to unicode and do all string
operations with Unicode strings? Also, in 5 isn't there some intersection
with grapheme_* functions?
mb_strwidth() and mb_strimwidth() are not covered.
True. I wonder what this function is useful for?
mb_output
Hi!
support for Unicode string manipulation, but it would actually be
better a bit if they supported arbitrary encoding as arguments.
There's no such thing as "encoding" in PHP 6 - all strings are Unicode.
If you've got binary data in some encoding, I think the recommended way
for PHP 6 woul
On Fri, Jul 31, 2009 at 5:24 PM, Moriyoshi Koizumi wrote:
>> mb_str* - shouldn't you in 6 just convert them to unicode and do all string
>> operations with Unicode strings? Also, in 5 isn't there some intersection
>> with grapheme_* functions?
>
> mb_strwidth() and mb_strimwidth() are not covered.
On Fri, Jul 31, 2009 at 2:37 AM, Stanislav Malyshev wrote:
> Hi!
>
>> Aren't there any interests on this? If you think PHP 6 is gonna cover
>> all of the functionality that allegedly-cruft mbstring currently
>> provides, that is almost wrong :-p
>
> Could you please explain why PHP6 doesn't provide
Hi!
Aren't there any interests on this? If you think PHP 6 is gonna cover
all of the functionality that allegedly-cruft mbstring currently
provides, that is almost wrong :-p
Could you please explain why PHP6 doesn't provide what mbstring is
doing? I.e, let's go over the functions:
mb_parse_
I'm just waiting for you to just commit it.. :)
--Jani
On 07/29/2009 12:08 PM, Moriyoshi Koizumi wrote:
Aren't there any interests on this? If you think PHP 6 is gonna cover
all of the functionality that allegedly-cruft mbstring currently
provides, that is almost wrong :-p
Moriyoshi
On Tue, J
16 matches
Mail list logo
