On Tuesday, 31 October 2017 8:11 Jan Engelhardt wrote:
On Friday 2017-10-27 18:23, Brüns, Stefan wrote:
Byte order mark is ambiguous - it is three bytes, which are valid codepoints in e.g. ISO-8859-1. Granted, it is unlikely, but ...
The byte order mark is not ambiguous for what it was meant to do, since there is a bijective mapping between the domain of (defined) bit patterns and the codomain of (defined) encodings. ISO-8859-* is just not within the set. Understandably so, since ISO-8859-* does not __have__ a byte __order__ to begin with ? it is a single-byte encoding.
Neither does UTF-8, that's why I always considered putting a "BOM" into a UTF-8 text a sign that someone doesn't know what they are doing and why. But I believe Stefan wanted to point out that UTF-8 "BOM" consists of three bytes which are valid ISO-8859-1 characters so that a document in ISO-8859-1 could, in theory, start with them (however unlikely that is). Michal Kubeček -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org