Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113685
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>
Message-ID: <11e9a312-ed10-412e-506d-ccf9f24457f8@alec.pl>
Date: Mon, 22 Mar 2021 17:52:00 +0100
MIME-Version: 1.0
In-Reply-To: <16ecfc31-33aa-4223-fb67-b5a4b5895f05@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode?
From: alec@alec.pl (Aleksander Machniak)

On 22.03.2021 16:41, Rowan Tommins wrote:
> That code will never do anything useful.

I already proved it is useful, regardless of it's name/intention.

This is old code, not even mine, so maybe when it's been written the PHP
documentation wasn't that clear about the function(s) intention. Or the
intention was different.

ps. to Kamil,

We use utf8_encode() to make the string safe to be put in utf-8 database
column/table. We use utf8_decode() to convert that back to what it was
before.

The tests prove that the conversion is lossless.

-- 
Aleksander Machniak
Kolab Groupware Developer        [https://kolab.org]
Roundcube Webmail Developer  [https://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com