Re: [PATCH 0/2] Improve documentation on UTF-16

[PATCH 0/2] Improve documentation on UTF-16 · brian m. carlson <hidden> · 2018-12-27
[PATCH 1/2] Documentation: document UTF-16-related behavior · brian m. carlson <hidden> · 2018-12-27
[PATCH 2/2] utf8: add comment explaining why BOMs are rejected · brian m. carlson <hidden> · 2018-12-27
Re: [PATCH 0/2] Improve documentation on UTF-16 · Johannes Sixt <hidden> · 2018-12-27
Re: [PATCH 0/2] Improve documentation on UTF-16 · brian m. carlson <hidden> · 2018-12-27
Re: [PATCH 0/2] Improve documentation on UTF-16 · Johannes Sixt <hidden> · 2018-12-27
Re: [PATCH 0/2] Improve documentation on UTF-16 · brian m. carlson <hidden> · 2018-12-27
Re: [PATCH 0/2] Improve documentation on UTF-16 · Johannes Sixt <hidden> · 2018-12-28
Re: [PATCH 0/2] Improve documentation on UTF-16 · Philip Oakley <hidden> · 2018-12-28
Re: [PATCH 0/2] Improve documentation on UTF-16 · Ævar Arnfjörð Bjarmason <hidden> · 2018-12-28
Re: [PATCH 0/2] Improve documentation on UTF-16 · Philip Oakley <hidden> · 2018-12-28
Re: [PATCH 0/2] Improve documentation on UTF-16 · brian m. carlson <hidden> · 2018-12-29

From: Ævar Arnfjörð Bjarmason <hidden>
Date: 2018-12-28 08:46:25

On Thu, Dec 27 2018, brian m. carlson wrote:

We've recently fielded several reports from unhappy Windows users about
our handling of UTF-16, UTF-16LE, and UTF-16BE, none of which seem to be
suitable for certain Windows programs.

Just for context, is "we" here $DAYJOB or a reference to some previous
ML thread(s) on this list, or something else?

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help