It was just a blanket search. As for bug 29518, I think it is worth
fixing at some point in time.
You could conceivable build a multilingual site where your "language
pack" files were an ini file of key=translated text, and you loaded them
at run time. A lot of projects use a PHP file with a php
Yeah good idea. I'll try and see what I can do.
Andi
At 08:14 AM 8/31/2004 +0200, Derick Rethans wrote:
On Mon, 30 Aug 2004, Andi Gutmans wrote:
> Adam,
>
> That link is in the History section of the Zend Engine II section. We left
> it and our original RFC there so that people can take a look but
On Tue, 31 Aug 2004, Masaki Fujimoto wrote:
> http://bugs.php.net/bug.php?id=29518
>
> how do you think about this? it's worth fixing? or you think this
> is just a bogus one?
It's not very easy to fix I think, and where is it documented that the
ini files that this function parses can be in any
Hello,
I walked through the bugs you mentioned, however I cannot find any
bugs really related to the option (apparently all of the bugs have
nothing to do with the option).
so, actually I'm still not sure why you think the option causes
bugs. or, just because you searched the bugs with the
'
The bugs I saw were just the result of a quick search for multibyte, or
more --enable-zend-multibyte:
http://bugs.php.net/search.php?search_for=--enable-zend-
multibyte&boolean=0&limit=10&order_by=&direction=ASC&cmd=display&status=Open&php_os=&phpver=&assign=&author_email=&bug_age=0
A few relevan
On Mon, 30 Aug 2004, Andi Gutmans wrote:
> Adam,
>
> That link is in the History section of the Zend Engine II section. We left
> it and our original RFC there so that people can take a look but PHP 5 has
> changed very much since then.
Perhaps it's a good idea to add a BIG disclaimer on that sam
Hello,
the option is, to handle following issues (though I've been away
for months... :(
* parsing scripts written in flex-unfriendly encodings
(e.g. Shift_JIS, BIG-5, etc)
* parsing scripts containing BOM (Byte Order Mark)
* converting encoding of each script to one "internal" encoding
* pars
What is the "--enable-zend-multibyte" configuration option used for
then?
I've noticed a few bug reports where this option was the culprit.
Al
On Mon, 2004-08-30 at 11:50 -0700, Andi Gutmans wrote:
> Adam,
>
> That link is in the History section of the Zend Engine II section. We left
> it and
On Sat, 28 Aug 2004, Al Baker wrote:
> So, all the mb_* functions will have the experimental removed? I see a
> few that still have it, or is that just the mirrors not up to date yet?
I'd go for the iconv() functions as you need to external extension for
this in PHP 5 (it's enabled by default).
The warning will be gone after the next build of the manual.
Mehdi
Al Baker wrote:
So, all the mb_* functions will have the experimental removed? I see a
few that still have it, or is that just the mirrors not up to date yet?
Al
On Sat, 2004-08-28 at 23:35 +1000, Dave Barr wrote:
Derick Rethans wr
So, all the mb_* functions will have the experimental removed? I see a
few that still have it, or is that just the mirrors not up to date yet?
Al
On Sat, 2004-08-28 at 23:35 +1000, Dave Barr wrote:
> Derick Rethans wrote:
> > On Fri, 27 Aug 2004, Al Baker wrote:
> >
> >
> >>Thanks for the conf
On Sat, 28 Aug 2004, Moriyoshi Koizumi wrote:
> Maybe sorts of character classes don't work as you expect, because
> they lack comprehensive collation support that fully conforms to the
> Unicode
> specification. It's stable I think, but actually not complete yet.
ICU has gotten a lot more modular
Derick Rethans wrote:
On Fri, 27 Aug 2004, Al Baker wrote:
Thanks for the confirmation. The experimental warning appears on any of
the individual help files for mbstring (e.g. mb_ereg).
Can you file a "Documentation" problem for that on bugs.php.net please?
Don't bother, I have fixed this in the
On Fri, 27 Aug 2004, Al Baker wrote:
> Thanks for the confirmation. The experimental warning appears on any of
> the individual help files for mbstring (e.g. mb_ereg).
Can you file a "Documentation" problem for that on bugs.php.net please?
regards,
Derick
--
Derick Rethans
http://derickrethan
On 2004/08/28, at 8:17, Sean Coates wrote:
Are these functions in fact non-experimental? If so, I will remove the
warning from the mb_* functions in the manual.
Yep, definitely. Thanks in advance :)
Moriyoshi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www
Hi,
On 2004/08/28, at 8:38, Al Baker wrote:
Thanks for the confirmation. The experimental warning appears on any
of
the individual help files for mbstring (e.g. mb_ereg).
Hmm, warnings seem to persist in manual pages of the multibyte regular
expression functions. I'll remove them later :)
Do you
Are these functions in fact non-experimental? If so, I will remove the
warning from the mb_* functions in the manual.
S
Al Baker wrote:
Thanks for the confirmation. The experimental warning appears on any of
the individual help files for mbstring (e.g. mb_ereg).
Which manual says that mbstring
Thanks for the confirmation. The experimental warning appears on any of
the individual help files for mbstring (e.g. mb_ereg).
Do you know if the regular expression support lets you match alpha and
numeric content like you would normally?
Al
On Sat, 2004-08-28 at 05:52 +0900, Moriyoshi Koizumi
Hi,
On 2004/08/28, at 5:15, Al Baker wrote:
I'm trying to find status on the multibyte support in PHP. The manual
shows the functions in mbstring to be experimental and it's hard to
find
evidence of how stable it really is.
Which manual says that mbstring is still experimental? :) it was marked
"
19 matches
Mail list logo
