Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113695 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 3398 invoked from network); 22 Mar 2021 17:43:28 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Mar 2021 17:43:28 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 805671804F4 for ; Mon, 22 Mar 2021 10:38:47 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) (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 10:38:46 -0700 (PDT) Received: by mail-ej1-f54.google.com with SMTP id k10so22687471ejg.0 for ; Mon, 22 Mar 2021 10:38:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yqtzoO2bgdKIktAMjHCNCfkEqwUPJxxH0DJpdiF2exw=; b=bX598xkOQAgPmW7OYk+g2NB3O0PX6VX45ttm5Gp6ArrXUwSRWFKpML9PBxr9XhgMTJ 2ppPxGPJaPKw0Bw8okqQsD2/ls4NkmpheROKeTeJ0Bvdq7wWxt8oUx2MDEYrIVTtkMBk vcfm3GwK4g34pUGkR2qfjc2iruii0cEGclrwrfYitnDhlvKra5otN9B8vuHLukuL1ggd ISdByClT9m8cRmwAQvbl21VWxwCibsG6fG9DTxvlu4KBZ5BNJU7cRjhKDNGBOpNQHgo+ 34V7UON8thSujMjbitbbAH4KJc6GWLo9WR43FgoL2Mt6U/OdrUVKtKFzGdlEGfdPm5Rk +MBA== 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=yqtzoO2bgdKIktAMjHCNCfkEqwUPJxxH0DJpdiF2exw=; b=ECjpkXx5wAlvY2X2C5inUK/MZu4O53xrmRiHQ1kUJrgC+Cl9sF3xo+JWtt2BI9KuPW b9FD8LzR5btztS2J6Vv0XJ1goFKZlbe0C37yQkkmEoba3XBJ1bFQG0Wwrucl9thBwM9P VhU4R3o/DPWh6wbpBMY+p5JpE2JGgayP/VZpaPXJiRcAWF1EOIli685L7pTDjzTf1l0/ idlkCI/LHFR70gc8l2MXqAFHUd0JOkC7o804kJKmk5qyQOxc7RwYKtJiF8v4tc7wqTqg b9cQIs1ODq3LOTu4M7MkaDtFLlMFMG94gvLHg+jSZh+YuwZV+uLg7Yfp0ZtWqGTDbkqQ 63Fw== X-Gm-Message-State: AOAM533fPQ6q/cL1MXcihaOPou6iPOgkuI/MzqDc7p4MpMOF7C8lbl/J njG8gsxVDKLtheZeb79Cnx+m5YWjeTPJSvwqpW8= X-Google-Smtp-Source: ABdhPJyefEMhb01jGn5VE6dmfxiBcnhMh57IrpGnb6v4959o+nC/DJvEiAA36ioXM7cvWtP+DUSUuPmkTYagTWjsGk8= X-Received: by 2002:a17:906:1ecc:: with SMTP id m12mr957437ejj.4.1616434725132; Mon, 22 Mar 2021 10:38:45 -0700 (PDT) MIME-Version: 1.0 References: <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> In-Reply-To: Date: Mon, 22 Mar 2021 19:38:28 +0200 Message-ID: To: Aleksander Machniak Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000981c0605be23899b" Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode? From: drealecs@gmail.com (=?UTF-8?Q?Alexandru_P=C4=83tr=C4=83nescu?=) --000000000000981c0605be23899b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 22, 2021 at 7:24 PM Alexandru P=C4=83tr=C4=83nescu wrote: > > There could have been better ways to fix it. > json_encode / json_decode would have worked just the same. > > Nope, strings in a json object must be UTF-8. 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. > > Regards, > Alex > --000000000000981c0605be23899b--