Re: [PATCH v2] utf8: handle systems that don't write BOM for UTF-16

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Feb 11, 2019, 01:16 UTC
Message-ID: <CAPig+cRTRCeGZ115gJGGNPtQ7WyFWg4Y45WOPec-8CmnG6ZRMQ@mail.gmail.com>
In-Reply-To: <20190211002307.686048-1-sandals@crustytoothpaste.net>

On Sun, Feb 10, 2019 at 7:23 PM brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 6 quoted lines

> When serializing UTF-16 (and UTF-32), there are three possible ways to
> write the stream. One can write the data with a BOM in either big-endian
> or little-endian format, or one can write the data without a BOM in
> big-endian format.
> [...]
> Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>

Premature git-send-email invocation? The commit message of v2 seems to be a bit different from v1, but the patch itself is identical.