Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113696
To: internals@lists.php.net
References: <f313c9c4-f8a2-0b39-7499-30620d80cecd@gmail.com>
 <CAESVnVoa2U1ZCsthWCt8Cu8Es-P8WWO=vky4TG5CmtaoumEmUA@mail.gmail.com>
 <e120bf6b-12cd-5b3e-b27c-b746d1a1661b@gmail.com>
 <CAESVnVqJh3oOM-5CkatiUctRupOdS7mce7QYzv3uxUb3QcpHWw@mail.gmail.com>
 <693767b5-a25b-b4d9-f535-6b985bf26d67@gmail.com>
 <29d5329c-bea2-7944-4820-515d4a10ae86@alec.pl>
 <16ecfc31-33aa-4223-fb67-b5a4b5895f05@gmail.com>
 <11e9a312-ed10-412e-506d-ccf9f24457f8@alec.pl>
 <CAAwdEzBYXgDj_Do_LPeZXaMnjeLZcjPQmo+u2wTNFLfttoyzQw@mail.gmail.com>
 <CAAwdEzAMCqGOL94rPtojZkg5H42z4gGJtCBbDkWpJZ=g0=kLJw@mail.gmail.com>
Message-ID: <aa1e9d05-427f-492b-2187-072ee0be2f3c@gmail.com>
Date: Mon, 22 Mar 2021 17:54:32 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <CAAwdEzAMCqGOL94rPtojZkg5H42z4gGJtCBbDkWpJZ=g0=kLJw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode?
From: rowan.collins@gmail.com (Rowan Tommins)

On 22/03/2021 17:38, Alexandru Pătrănescu wrote:
> As Rowan mentioned, base64_encode would have worked. But that means one
> quarter of the available max column space would be lost as a downside.


Depending on the data, abusing Latin1-to-UTF8 translation can easily 
result in a longer string than base64.


$str = '🤡🤡';

echo strlen(base64_encode($str));
// 12

echo strlen(utf8_encode($str));
// 16


Regards,

-- 
Rowan Tommins
[IMSoP]