Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103286
MIME-Version: 1.0
References: <d46e41f8-e483-8425-280e-42cc04f21242@gmx.de>
In-Reply-To: <d46e41f8-e483-8425-280e-42cc04f21242@gmx.de>
Date: Sun, 30 Sep 2018 12:42:50 +0200
Message-ID: <CAF+90c-k4Awf5qdmx1oYnKyJOj9Hyh4a-Y0gZpj_ine4hW8ATA@mail.gmail.com>
To: Christoph Becker <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005369970577145a94"
Subject: Re: [PHP-DEV] [RFC] Kill proprietary CSV escaping mechanism
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000005369970577145a94
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 27, 2018 at 12:29 PM Christoph M. Becker <cmbecker69@gmx.de>
wrote:

> Hi!
>
> I hereby put the =E2=80=9CKill proprietary CSV escaping mechanism=E2=80=
=9D under
> discussion:
>
> <https://wiki.php.net/rfc/kill-csv-escaping>
>
> Any comments are welcome!
>

Could you please add a description of how the escaping mechanism currently
works for read and write? My vague recollection is that the write and read
behavior actually have nothing to do with each other and the fputcsv
$escape parameter would be better described as the $corrupt parameter. We
may want to treat both cases in different ways.

Nikita

--0000000000005369970577145a94--