24337 2014-01-20 18:22:29 +0000 Authors should be able to use both "utf8" and "utf-8" labels, case-insensitively 2014-01-24 22:47:23 +0000 1 1 1 Unclassified WHATWG Encoding unspecified PC Linux RESOLVED FIXED P2 normal Unsorted 1 geoffers+w3cbugs annevk duerst mike www-international sideshowbarker+encodingspec oldest_to_newest 98783 0 geoffers+w3cbugs 2014-01-20 18:22:29 +0000 Currently the spec says: 'Authors must use the utf-8 encoding and must use the "utf-8" label to identify it.' Given the label matching is done case-insensitively, it is not entirely clear whether authors must use this label case-sensitively or not. This should be clarified, preferably to allow either case (there is no practical benefit of requiring it to be lowercased). We should also make the "utf8" label conforming. Making this non-conforming is of no practical benefit and makes a large number of documents non-conforming. 98816 1 duerst 2014-01-21 05:34:57 +0000 (In reply to Geoffrey Sneddon from comment #0) > Currently the spec says: 'Authors must use the utf-8 encoding and must use > the "utf-8" label to identify it.' > > Given the label matching is done case-insensitively, it is not entirely > clear whether authors must use this label case-sensitively or not. This > should be clarified, preferably to allow either case (there is no practical > benefit of requiring it to be lowercased). Agreed. > We should also make the "utf8" label conforming. Making this non-conforming > is of no practical benefit and makes a large number of documents > non-conforming. This looks innocuous at first. However, in some products (in particular Oracle Databases), the label "utf8" is used for a variant of UTF-8 where characters outside the BMP are encoded with two surrogates, with a total of 6 bytes. For security reasons, this is prohibited in UTF-8. 99035 2 annevk 2014-01-24 22:47:23 +0000 Yeah, only utf-8 was intentional. Clarified the case stuff. https://github.com/whatwg/encoding/commit/61af3cdf199b4ab86babd47b7d48bb328c54a702