Re: [PATCH v8 3/7] utf8: add function to detect prohibited UTF-16/32 BOM

> On 27 Feb 2018, at 06:17, Eric Sunshine wrote: > > On Sun, Feb 25, 2018 at 6:35 AM, Lars Schneider > wrote: >>> On 25 Feb 2018, at 04:41, Eric Sunshine wrote: >>> Is this interpretation correct? When I read [1], I

Re: [PATCH v8 3/7] utf8: add function to detect prohibited UTF-16/32 BOM

On Sun, Feb 25, 2018 at 6:35 AM, Lars Schneider wrote: >> On 25 Feb 2018, at 04:41, Eric Sunshine wrote: >> Is this interpretation correct? When I read [1], I interpret it as >> saying that no BOM _of any sort_ should be present when the

Re: [PATCH v8 3/7] utf8: add function to detect prohibited UTF-16/32 BOM

> On 25 Feb 2018, at 04:41, Eric Sunshine wrote: > > On Sat, Feb 24, 2018 at 11:27 AM, wrote: >> Whenever a data stream is declared to be UTF-16BE, UTF-16LE, UTF-32BE >> or UTF-32LE a BOM must not be used [1]. The function returns true if

Re: [PATCH v8 3/7] utf8: add function to detect prohibited UTF-16/32 BOM

On Sat, Feb 24, 2018 at 11:27 AM, wrote: > Whenever a data stream is declared to be UTF-16BE, UTF-16LE, UTF-32BE > or UTF-32LE a BOM must not be used [1]. The function returns true if > this is the case. > > [1] http://unicode.org/faq/utf_bom.html#bom10 > >

[PATCH v8 3/7] utf8: add function to detect prohibited UTF-16/32 BOM

From: Lars Schneider Whenever a data stream is declared to be UTF-16BE, UTF-16LE, UTF-32BE or UTF-32LE a BOM must not be used [1]. The function returns true if this is the case. This function is used in a subsequent commit. [1]