Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108900
Message-ID: <58566.4e385490.1583689214.nsm@avilys.eik.lt>
In-Reply-To: 
     <CA+kxMuSBsC1ZfPrOWdWhc92Q0Dx_1vF22f5Dv888jr0vo9usqg@mail.gmail.com>
References: <09dd1b84-ed33-a059-82f9-5efd179e69d6@gmx.de>
    <CA+kxMuSBsC1ZfPrOWdWhc92Q0Dx_1vF22f5Dv888jr0vo9usqg@mail.gmail.com>
Date: Sun, 8 Mar 2020 19:40:14 +0200 (EET)
To: internals@lists.php.net
User-Agent: NaSMail/1.7.1
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] iconv vs. mbstring
From: tokul@users.sourceforge.net ("Tomas Kuliavas")

2020.03.08 16:08 Dan Ackroyd rašė:
> On Tue, 3 Mar 2020 at 22:17, Christoph M. Becker <cmbecker69@gmx.de>
> wrote:
>>
>> for more
>> general string functionality, it would be ext/mbstring.
>>
>> Thoughts?
>>
>
> Related to this discussion, please could someone remind me why the
> mbstring extension is an extension and not part of core PHP?
>
> I realise at the time it was introduced, UTF-8 was far less widely
> used: https://en.wikipedia.org/wiki/UTF-8#/media/File:Utf8webgrowth.svg
>
> But now UTF-8 is pretty much the default for the vast majority of
> projects, so does that decision to keep it as an optional extension
> still hold up?

Majority is not 100%. Your German folders in webmails are not in UTF-8.
Even if application operates in utf-8, it still must be able to work not
with utf-8 and PHP functions that changed default from ascii/iso-8859-1 to
utf-8 were not designed to operate in real world.

Reason why mbstring are not base string functions is why PHP6 does not exist.

-- 
Tomas