Byte order mark (English Wikipedia)

Analysis of information sources in references of the Wikipedia article "Byte order mark" in English language version.

refsWebsite
Global rank English rank
311th place
239th place
214th place
176th place
2nd place
2nd place
8,307th place
5,922nd place
8,102nd place
6,847th place
low place
low place
low place
low place
6,171st place
4,055th place
low place
low place

alfps.wordpress.com

  • Alf P. Steinbach (2011). "Unicode part 1: Windows console i/o approaches". Retrieved 24 March 2012. However, since the C++ source code was encoded as UTF-8 without BOM (as is usual in Linux), the Visual C++ compiler erroneously assumed that the source code was encoded as Windows ANSI.

bleepingcomputer.com

doi.org

fileformat.info

ietf.org

datatracker.ietf.org

tools.ietf.org

java.com

bugs.java.com

sdl.com

docs.sdl.com

unicode.org

  • "FAQ - UTF-8, UTF-16, UTF-32 & BOM". Unicode.org. Retrieved 28 January 2017.
  • "The Unicode® Standard Version 9.0" (PDF). The Unicode Consortium.
  • "The Unicode Standard 5.0, Chapter 2:General Structure" (PDF). p. 36. Retrieved 29 March 2009. Table 2-4. The Seven Unicode Encoding Schemes
  • "The Unicode Standard 5.0, Chapter 2:General Structure" (PDF). p. 36. Retrieved 30 November 2008. Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature
  • "FAQ - UTF-8, UTF-16, UTF-32 & BOM: Can a UTF-8 data stream contain the BOM character (in UTF-8 form)? If yes, then can I still assume the remaining UTF-8 bytes are in big-endian order?". Unicode.org. Retrieved 4 January 2009.
  • "Re: pre-HTML5 and the BOM from Asmus Freytag on 2012-07-13 (Unicode Mail List Archive)". Unicode.org. Retrieved 14 July 2012.
  • Honermann, Tom (2 January 2021). "Clarify guidance for use of a BOM as a UTF-8 encoding signature" (PDF). Unicode.
  • Markus Scherer. "UTS #6: Compression Scheme for Unicode". Unicode.org. Retrieved 28 January 2017.

whatwg.org

encoding.spec.whatwg.org