On Friday 2017-10-27 18:23, Brüns, Stefan wrote:
The only real fix is to use an in-file marker such that the file becomes self-describing, and there are sufficient examples in history how to pull that off:
- Byte Order Mark to determine UTF-8, UTF-{16,32}{BE,LE}
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. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org