Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113702 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 20861 invoked from network); 22 Mar 2021 20:09:34 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Mar 2021 20:09:34 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1AEF51804DC for ; Mon, 22 Mar 2021 13:04:55 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: **** X-Spam-Status: No, score=4.7 required=5.0 tests=BAYES_20,BODY_8BITS, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 22 Mar 2021 13:04:54 -0700 (PDT) Received: by mail-lf1-f41.google.com with SMTP id b83so23229681lfd.11 for ; Mon, 22 Mar 2021 13:04:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sxhONjWZEKE5EBhGy8sakLuzyVm2FPeOr9l6mCrSV4Y=; b=ntFJmWOoyBC+PRL71knWvuYKYZcOJVLEzzuOiZQClpjpSbtTTOy8K0GO1s5/ezDzf0 +0duOxuWgSqOUBVvI1U58f7QGbokHL8Tlpg3b91ZceG5QgCQDFl8OqgBj/p4pcGZy5cO wVuafeMbOjaWIGkUmf8lAHlNJ12JZsA92dh47Biqjq20jvjp0SEJdaWLJYIseefS4VQ+ niPB3f/9szysNIJHbkH7VUygR92Ns/7TmAgge7SvHgPNeABQcJj58BfrUlbHdT9W4vvU xnJG+vZPU0NiQH5RYZd0NrDVjmwh8TxHbAA3Zv/e4nQvXeD9xkbT54eDmk2LdkU9JzTk 2kHQ== X-Gm-Message-State: AOAM533OcOEeXzGuFiWJ+kKjDuuVop+ecO2H1JOtHBk224OsX/2p7cwz 41YJF/r7JjmYjGSjBO2vUL55fZssbga+fB9K/sgtGi1r7/Fpag== X-Google-Smtp-Source: ABdhPJwzR5OPml4tqDDAWFk1rcocUvire5MWpM5AYNDr/d+1DDJJD6iRx8C5Cz5dYbTOrf5hvqmwH/QXhzd2jr4R/Kk= X-Received: by 2002:a05:6512:3d04:: with SMTP id d4mr592129lfv.102.1616443491097; Mon, 22 Mar 2021 13:04:51 -0700 (PDT) MIME-Version: 1.0 References: <693767b5-a25b-b4d9-f535-6b985bf26d67@gmail.com> <29d5329c-bea2-7944-4820-515d4a10ae86@alec.pl> In-Reply-To: <29d5329c-bea2-7944-4820-515d4a10ae86@alec.pl> Date: Mon, 22 Mar 2021 15:04:40 -0500 Message-ID: To: Aleksander Machniak Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000016328805be259451" Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode? From: pollita@php.net (Sara Golemon) --00000000000016328805be259451 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 22, 2021 at 10:04 AM Aleksander Machniak wrote: > $str =3D "=E3=82=B0=E3=83=BC=E3=82=B0=E3=83=AB=E8=B0=B7=E6=AD=8C=E4= =B8=AD=E4=BF=A1=D1=84=CE=B4=CE=BF=CE=BA=CE=B9=CE=BC=CE=AE=C3=B3=C5=BAd=C5= =BA=D1=80=C3=B6=C3=9F=F0=9F=98=81=F0=9F=98=83"; > > $this->assertSame($str, utf8_decode(utf8_encode($str))); > > Woah. Yeah. No. Don't do that. Doing that is what's wrong with utf8_en/decode(). Doing that convinces me that Rowan is right and we should deprecate then remove those functions without offering a simple replacement. Christ's sake... no. --00000000000016328805be259451--