On Tuesday, 31 October 2017 9:48 Jan Engelhardt wrote:
On Tuesday 2017-10-31 08:42, Michal Kubecek wrote:
ISO-8859-* does not __have__ a byte __order__ to begin with -- it is a single-byte encoding.
Neither does UTF-8
As a multibyte encoding, it *does* have an order, even if just a single defined one. Swapping two octets does not necessarily produce the same character value (U+xxxx). In ISO-8859, you can do this switch and you will get the same character values.
If you wish to call it byte order, you certainly can. But unlike for e.g. UTF-16, there is no actual need for "BOM" in UTF-8 text. It's just a way some editors do to say "this is UTF-8" - but it doesn't actually work in general and confuses various parsers. The very idea of putting the information about encoding into the text itself is IMHO completely wrong as it can only work for a very limited set of encodings and only for limited number of applications processing the text documents. Such information must be specified outside the document itself, explicitly or implicitly. Michal Kubecek -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org