Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95171 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11825 invoked from network); 15 Aug 2016 05:26:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Aug 2016 05:26:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.173 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.173 mail-pf0-f173.google.com Received: from [209.85.192.173] ([209.85.192.173:35847] helo=mail-pf0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 47/FA-36656-19251B75 for ; Mon, 15 Aug 2016 01:26:42 -0400 Received: by mail-pf0-f173.google.com with SMTP id h186so14228618pfg.3 for ; Sun, 14 Aug 2016 22:26:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=v+fNt197ahtzPN0qo701vPe5MsZh8hox6k0OwNtP3Hs=; b=Y6p5CrSBgxhw4rQm1cfcZ4dBUcBXlH5DzhG8kPNTlUb9yf56HedDRhb/5Id/CrgZOt qwi88P4WzP37k8N57uxaDdLJqQk9pPx3R+w9WAANNQA2M5rbkt4UKlUJuSba3OtTtyCz VNUOH4aJ0Un/ACOyC2ejm4dh8Vemz85sCRP+AWGrzhspKUucLzTDIwbJ8zt8TUwD5t/s RtQizbrGN88Cv3uNGjHEywkatoMxNIGq0B+BXBYSqGWU9YRagUD9GbSjtjpg8fXFB2Aq 64a/ARebKc+ZKM0CJdbS4znDLJZ+9+7brkW22hTxWr/LNNG1lDda3Lt820eB+9r4zwIN uITg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=v+fNt197ahtzPN0qo701vPe5MsZh8hox6k0OwNtP3Hs=; b=aMpVqwHehJhCFI2qktbqjilouVYx1wTz/TY+VgzrulL3+glj+NK4rqLAJ3FkJuuZs3 zL/igNSkc+d32/alBOxMz2kI09S+wXDwUbbWpeCjkuiE8lgorLxLUeJqUKHpSWq96ea2 4yufFLxH2romqs42vGee0ehwEkSmvRQ9CzDEydH+Jzwb2LtwvPIBYUFk5+9LVmGs38wc D5t8ell++jZzvYbH9ehUwUAT72SjI9qZzW9bMBmLhEhjkJegMto/OhGSJYnhDf1B+EFr HNx0pjg5f93y8YlrhLUw+XQ46Nilxu51Aa+ow10TPFmKLidPq3lerIgLdnQlrq4/+Cc4 iBWA== X-Gm-Message-State: AEkoouuTWiAFBCiucrBusEsE9gF0pqFrHyaubvmssMlIzWn+8UaZX6OA96heDO4Q990EvQ== X-Received: by 10.98.25.8 with SMTP id 8mr50886575pfz.94.1471238798962; Sun, 14 Aug 2016 22:26:38 -0700 (PDT) Received: from Stas-Air.local (108-233-206-104.lightspeed.sntcca.sbcglobal.net. [108.233.206.104]) by smtp.gmail.com with ESMTPSA id w76sm29217132pfd.69.2016.08.14.22.26.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 14 Aug 2016 22:26:38 -0700 (PDT) To: Yasuo Ohgaki , "internals@lists.php.net" References: Message-ID: <6163e94b-9b42-0049-1346-3e7f790801a2@gmail.com> Date: Sun, 14 Aug 2016 22:26:36 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Remove utf8_decode() and utf8_encode() From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Hi all, > > utf8_decode() and utf8_encode() are not needed and causing problems > than solving. Why you think they are not needed? Also, the manual says "utf8_encode — Encodes an ISO-8859-1 string to UTF-8". If somebody uses unknown function without even glancing at the first line of the manual, they deserve all the trouble they get. I mean, it's not a PhD-level course, it's a single line to read, and not that long one either, just 6 words. Many beer labels provide more reading material :) So, I'm not sure we need to spend time on this. Yes, it duplicates iconv and recode. So what? It hurts no one. > https://wiki.php.net/rfc/remove_utf_8_decode_encode > > Proposal > - Document deprecation them now > - Remove them from 7.2 RFC says "7.1 - Remove utf8_decode() and utf8_encode()". > I think only few users are using and they shouldn't have problem using > mbstring/iconv/intl functions. I would like to see some justification for this - was any research performed on how many users use them? -- Stas Malyshev smalyshev@gmail.com