
	Where results make sense

Topic: Byte Order Mark

Related Topics

Universal character set

Endianness

Cygwin

Bit

Chinatown

Chemical nomenclature

Davie, Florida

In the News (Sat 26 Jul 08)

Gordon Brown

Derby County

Mike Huckabee

Lute Olson

Pearl Harbor

Sonia Gandhi

Ricky Hatton

Narendra Modi

Jesus Christ

Rudy Giuliani

	Encyclopedia: Byte Order Mark (Site not responding. Last check: 2007-10-10)
		A Byte Order Mark (BOM) is the character at code point U+FEFF ("zero-width no-break space"), when that character is used to denote the endianness of a string of UCS/Unicode characters encoded in UTF-16 or UTF-32 and/or as a marker to indicate that text is encoded in UTF-8, UTF-16 or UTF-32.
		In UTF-16, a BOM is expressed as the two-byte sequence FE FF at the beginning of the encoded string, to indicate that the encoded characters that follow it use big-endian byte order; or it is expressed as the byte sequence FF FE to indicate little-endian order.
		byte sequence FE FF at the beginning of the encoded string, to indicate that the encoded characters that follow it use big-endian byte order; or it is expressed as the byte sequence FF FE to indicate little-endian order.
	www.nationmaster.com /encyclopedia/Byte-Order-Mark (1848 words)

	Endianness - Wikipedia, the free encyclopedia
		Generally the byte (octet) is considered an atomic unit from the point of view of storage at all but the lowest levels of network protocols and storage formats.
		While variable-width text encodings using the byte as their base unit could be considered to have an inbuilt endianness this is (at least in all commonly used ones) fixed by the encoding's design.
		It permits a Byte Order Mark (BOM) of between 2 bytes at the beginning of a string to denote its endianness.
	en.wikipedia.org /wiki/Endian (2097 words)

	FAQ - UTF-8, UTF-16, UTF-32 & BOM
		The BE form uses big-endian byte serialization (most significant byte first), the LE form uses little-endian byte serialization (least significant byte first) and the unmarked form uses big-endian byte serialization by default, but may include a byte order mark at the beginning to indicate the actual byte serialization used.
		When data are exchange in the same byte order as they were in the memory of the originating system, they may appear to be in the wrong byte order on the receiving system.
		In that form, the BOM serves to indicate both that it is a Unicode file, and which of the formats it is in.
	www.unicode.org /unicode/faq/utf_bom.html (4895 words)

	Byte Order Mark
		A Byte Order Mark (BOM) is the character at code point FEFF (ZERO-WIDTH NO-BREAK SPACE), when that character is used to denote the Endianness of an encoded string of UCS/Unicode characters.
		A BOM can be used to indicate that unlabeled text is UTF-16 or UTF-8 encoded, as well as indicating the byte-order of UTF-16 text, whether labeled or not.
		In UTF-16, a BOM is expressed as the 8-bit byte sequence FE FF at the beginning of the encoded string, to indicate that the encoded characters that follow it use big-endian byte order; or it is expressed as the byte sequence FF FE to indicate little-endian order.
	www.brainyencyclopedia.com /encyclopedia/b/by/byte_order_mark.html (207 words)

	opentag.com - XML FAQ: Encoding
		The BOM is a Unicode special marker placed at the top of the file that indicate its encoding.
		It is used to indicate whether the file uses the big-endian or little-endian byte order.
		Byte order is important only for encodings using units greater than 8-bits (i.e.
	www.opentag.com /xfaq_enc.htm (998 words)

	TWiki . Javawsxml . Rome05CharsetEncoding
		Mark Pilgrim did a very good job explaining how the charset encoding should be determined, Determining the character encoding of a feed and XML on the Web Has Failed.
		Byte Order Mark encoding and XML guessed encoding detection rules are clearly explained in the XML 1.0 Third Edition Appendix F.1.
		But if XMLEnc was read it means that the encoding byte order of the stream was guessed from the first bytes in the stream, note that this is possible only if the document starts with a XML declaration.
	wiki.java.net /bin/view/Javawsxml/Rome05CharsetEncoding (1222 words)

	Unicode in XML and other Markup Languages
		Except for Line and Paragraph Separator, or the Byte Order Mark, it is acceptable for browsers and similar user agents to ignore the presence of discouraged characters in HTML or XML.
		When used as a byte order mark the character is placed at the beginning of a file.
		Mark Davis (mark.davis@us.ibm.com), and Hideki Hiura (hideki.hiura@eng.sun.com) contributed to the early drafts.
	www.w3.org /TR/unicode-xml (6853 words)

	System.Text.UTF8Encoding Class
		Constructs a new instance of the UTF8Encoding class with the specified Boolean that indicates whether the Unicode byte order mark in UTF-8 is recognized or emitted when reading from or writing to a Stream.
		A Boolean that indicates whether the Unicode byte order mark in UTF-8 is recognized or emitted when reading from or writing to a Stream.
		Returns the bytes used at the beginning of a stream to determine which encoding a file was created with.
	www.dotgnu.org /pnetlib-doc/System/Text/UTF8Encoding.html (1582 words)

	W3C I18N FAQ: Unexpected characters or blank lines
		Some applications insert a particular combination of bytes at the beginning of a file to indicate that the text contained in the file is Unicode.
		Each character in the file is represented by 2 or 4 bytes of data and the order in which these bytes are stored in the file is significant; the BOM indicates this order.
		In the UTF-8 encoding, the presence of the BOM is not essential because, unlike the UTF-16 or UTF-32 encodings, there is no alternative sequence of bytes in a character.
	www.w3.org /International/questions/qa-utf8-bom.html (767 words)

	System.Text.UnicodeEncoding Class
		This Encoding implementation can detect a byte order mark automatically and switch byte orders, based on a parameter specified in the constructor.
		Returns the bytes used at the beginning of a Stream instance to determine which Encoding implementation the stream was created with.
		System.Text.UnicodeEncoding.GetPreamble returns the Unicode byte order mark (U+FEFF) in either big-endian or little-endian order, according the ordering that the current instance was initialized with.
	www.gnu.org /software/dotgnu/pnetlib-doc/System/Text/UnicodeEncoding.html (1389 words)

	Charset (Java 2 Platform SE v1.4.2)
		charset interprets a byte-order mark to indicate the byte order of the stream but defaults to big-endian if there is no byte-order mark; when encoding, it uses big-endian byte order and writes a big-endian byte-order mark.
		In any case, when a byte-order mark is read at the beginning of a decoding operation it is omitted from the resulting sequence of characters.
		Byte order marks occuring after the first element of an input sequence are not omitted since the same code is used to represent
	java.sun.com /j2se/1.4.2/docs/api/java/nio/charset/Charset.html (2045 words)

	[No title]
		The use of a mark at the beginning of a file, which contains plain text, to identify the coding format of the characters, is commonly refere to as the Byte Order Mark or BOM for short.
		It is assumed that to be usefull, this marking need to used values that is not part of the coding of the text.
		An escape sequence consists of two or more bytes, ruled by the ISO/IEC 2022 format: Esc I F * Esc: the first is the ESCAPE character (Esc) (coded 01/11) * F: the last, known as the Final Byte, is from columns 03 to 07 of the code table, excluding the DELETE character 07/15).
	ietfreport.isoc.org /old-ids/draft-tremblay-bom-00.txt (704 words)

	Byte-order Mark
		A byte-order mark is not a control character that selects the byte order of the text; it simply informs an application receiving the file that the file is byte ordered.
		With only a single set of byte-ordering rules, users of one type of microprocessor would be forced to swap the byte order every time a plain text file is read from or written to, even if the file is never transferred to another system based on a different microprocessor.
		If a byte-order mark is found in the middle of a file, it is not interpreted as a Unicode character and has no effect on text output.
	msdn.microsoft.com /library/en-us/intl/unicode_42jv.asp?frame=true (550 words)

	FIX: UNICODE Byte Order Marks Ignored by Internet Explorer 4.0x
		If the byte sequence FF FE is found at the beginning of a file it indicates that the remaining bytes are not normalized and should be byte swapped before use.
		In other words, the Byte Order Mark is UNICODE FE FF, but since Little Endian machines automatically swap their bytes, a binary dump of the mark would be FF FE.
		If the UNICODE non-normalized, Byte Order Mark, FF FE, is encountered in a file, it indicates that the characters should be byte swapped (in a Little Endian architecture FF FE would appear as FE FF if the file were dumped).
	support.microsoft.com /support/kb/articles/q190/8/37.asp (681 words)

	Tucu's Weblog
		They are still marked as Alpha but we consider they are already stable for some serious use, we just want to do some sanity check (mostly classes, interfaces, methods and packages names) before we go with a Beta release (which we hope it will be the next one).
		The (JAXP SAX) XML parsers are not aware of the HTTP transport rules for charset encoding resolution as defined by RFC 3023.
		Mark Pilgrim did a very good analysis of the different RSS versions.
	blogs.sun.com /roller/page/tucu/20040927 (1480 words)

	Universal Feed Parser 3.2 [dive into mark]
		Section F of the XML specification provides a heuristic for determining whether an XML document is in a non-ASCII-compatible encoding, and which one.
		The heuristic is actually divided into two parts, because all XML documents are allowed to start with something called a Byte Order Mark (BOM), which is a specific Unicode character (U+FEFF) that looks different depending on the encoding and the byte order used in the document.
		(BOM FAQ) So one part of the heuristic deals with XML documents with a BOM, and the other part deals with XML without a BOM, but with an XML declaration.
	diveintomark.org /archives/2004/07/03/feed-parser-32 (534 words)

	System.IO.StreamReader (Site not responding. Last check: 2007-10-10)
		Constructs and initializes a new instance of the System.IO.StreamReader class for the specified stream, with the specified character encoding and byte order mark detection option.
		Constructs and initializes a new instance of the System.IO.StreamReader class for the specified stream, with the specified character encoding, byte order mark detection option, and buffer size.
		A bool value that indicates whether the new System.IO.StreamReader is required to look for byte order marks at the beginning of the stream.
	taubz.for.net /code/monodocs/corlib/System.IO/StreamReader.html (2635 words)

	SP - Character sets (Site not responding. Last check: 2007-10-10)
		The bytes representing the entire storage object may be preceded by a pair of bytes representing the byte order mark character (0xFEFF).
		The bytes representing each character are in the system byte order, unless the byte order mark character is present, in which case the order of its bytes determines the byte order.
		A bit combination with the 0x8000 and 0x80 bits set is encoded by the sequence of bytes with which the SJIS encoding encodes the character whose number in JIS X 0208 added to 0x8080 is equal to the bit combination.
	www.cs.indiana.edu /l/www/hyplan/asengupt/sgml/jade-1.2.1/doc/charset.htm (1176 words)

	Progress 4GL and the Unicode Byte Order Mark (BOM)
		The reason for removing the BOM is that you do not want to be splitting and concatenating strings within your application and removing and adding BOMs as you go along.
		The BOM will become a "?" (Question Mark, not the Unknown value) if the conversion is to a code page other than Unicode.
		When generating files, if the encoding is UTF-8, there is no need to generate a BOM, unless you are exporting to an application that expects a BOM as a file signature indicating the file is encoded in UTF-8 instead of another code page.
	www.xencraft.com /resources/unicodebom.html (1136 words)

	System.IO.StreamReader Class
		A Boolean value that indicates whether the new StreamReader is required to look for byte order marks at the beginning of the stream.
		Constructs and initializes a new instance of the StreamReader class for the specified stream, with the specified character encoding and byte order mark detection option.
		Constructs and initializes a new instance of the StreamReader class for the specified stream, with the specified character encoding, byte order mark detection option, and buffer size.
	www.gnu.org /software/dotgnu/pnetlib-doc/System/IO/StreamReader.html (2263 words)

	The skew.org XML Tutorial
		In computing and telecommunications, dividing the basic marks of a writing system into graphemes is helpful, but is not sufficient, on its own, to reproduce written text, since there is more to writing than just spewing a stream of graphemes.
		In order to consistently author, store, transmit and process XML documents, there must be an awareness of the encodings that are being or have been applied.
		XML documents, in order to be stored or transmitted, must manifest in an encoded form as bits and bytes, using a consistent character encoding mechanism such as UTF-16 or UTF-8.
	skew.org /xml/tutorial (8463 words)

	BOM - TheBestLinks.com - Acronym, Abbreviation, Byte Order Mark, Disambig, ...
		BOM - TheBestLinks.com - Acronym, Abbreviation, Byte Order Mark, Disambig,...
		BOM might be an acronym or abbreviation for:
		This is a disambiguation page, i.e., a navigational aid which lists other pages that might otherwise share the same title.
	www.thebestlinks.com /BOM.html (117 words)

	Byte Order Mark (Site not responding. Last check: 2007-10-10)
		For this reason, the Unicode standard specifies that a file may begin with a BOM, a sequence of reserved bytes that indicate byte order as well as the type of UTF encoding.
		Unfortunately, the UFT-8 standard allows but does not require a BOM mark in the beginning of a file.
		It does not indicate byte order; it just serves to indicate that the encoding is UTF-8 rather than something else.
	www.stanford.edu /~laurik/fsmbook/errata/BOM.html (284 words)

	Character Encoding Detection [Universal Feed Parser]
		If no encoding is given, XML supports the use of a Byte Order Mark to identify the document as some flavor of UTF-32, UTF-16, or UTF-8.
		Section F of the XML specification outlines the process for determining the character encoding based on unique properties of the Byte Order Mark in the first two to four bytes of the document.
		If no encoding is specified and no Byte Order Mark is present, XML defaults to UTF-8.
	feedparser.org /docs/character-encoding.html (448 words)

Try your search on: Qwika (all wikis)