Revision as of 09:32, 25 October 2022 edit 2406:840:80:6::248 (talk) →Not being seriously pursued: fix typo ← Previous edit		Revision as of 14:03, 20 January 2023 edit undo Hexware (talk \| contribs) Extended confirmed users 755 edits Fix wrong wording; Cited spec does not require UTF-8 output, just that decoders be able to "... read entities in both the UTF-8 and UTF-16 encodings." The convention of outputting in UTF-8 exclusively is a convention due to its prevalence. Tag: 2017 wikitext editor Next edit →
Line 12: Therefore, even on most UTF-16 systems such as [[Windows]] and [[Java (software platform)\|Java]], UTF-16 text files are not common; older 8-bit encodings such as ASCII or [[ISO-8859-1]] are still used, forgoing Unicode support; or UTF-8 is used for Unicode. One rare counter-example is the "strings" file used by [[macOS]] ([[Mac OS X Panther\|Mac OS X 10.3 Panther]] and later) applications for lookup of internationalized versions of messages which defaults to UTF-16, with "files encoded using UTF-8 ... not guaranteed to work."<ref>[https://developer.apple.com/documentation/MacOSX/Conceptual/BPInternational/Articles/StringsFiles.html Apple Developer Connection: Internationalization Programming Topics: Strings Files]</ref> [[XML]] is, [[de facto\|by ~~default~~convention]], encoded as UTF-8, and all XML processors must at least support UTF-8 (including US-ASCII by definition) and UTF-16.<ref>{{cite web \|url=http://www.w3.org/TR/xml/#charencoding \|title=Character Encoding in Entities

Comparison of Unicode encodings: Difference between revisions