Home
last modified time | relevance | path

Searched refs:BOM (Results 1 – 25 of 45) sorted by relevance

12

/external/snakeyaml/src/test/resources/pyyaml/
Dspec-05-02-utf8.data1 # Invalid use of BOM
/external/icu/icu4c/source/samples/ugrep/
DMakefile20 CHECK_ARGS=BOM readme.txt
Dreadme.txt18 begin with a BOM, in which case they are assumed to be in the UTF encoding
19 specified by the BOM. Program output is always in the system's default
/external/llvm/test/YAMLParser/
Dspec-05-02-utf8.test3 # Invalid use of BOM
/external/clang/test/Index/
Dpreamble-reparse-with-BOM.m8 // CHECK: preamble-reparse-with-BOM.m:2:12: ObjCInterfaceDecl=I2:2:12 Extent=[2:1 - 3:5]
/external/protobuf/objectivec/Tests/
DGPBCodedInputStreamTests.m303 "\xEF\xBB\xBF String with BOM",
306 "\xEF\xBB\xBF\xe2\x99\xa1", // BOM White Heart
307 "\xEF\xBB\xBF\xEF\xBB\xBF String with Two BOM",
329 // Ensure the string is there. NSString can consume the BOM in some
/external/icu/icu4c/source/test/cintltst/
Dccapitst.c243 UChar BOM = 0x0000; in TestConvert() local
727 …ucnv_setFromUCallBack(myConverter, otherUnicodeAction(MIA1), &BOM, &oldFromUAction, &oldFromUConte… in TestConvert()
734 if (MIA1_2 != otherUnicodeAction(MIA1) || MIA1Context2 != &BOM) in TestConvert()
741 … if (U_FAILURE(err) || oldFromUAction != otherUnicodeAction(MIA1) || oldFromUContext != &BOM) in TestConvert()
755 …ucnv_setFromUCallBack(myConverter, otherUnicodeAction(MIA1), &BOM, &oldFromUAction, &oldFromUConte… in TestConvert()
757 if(MIA1_2 == otherUnicodeAction(MIA1) || MIA1Context2 == &BOM){ in TestConvert()
767 … ucnv_setToUCallBack(myConverter,otherCharAction(MIA2), &BOM, &oldToUAction, &oldToUContext, &err); in TestConvert()
774 if (MIA2_2 != otherCharAction(MIA2) || MIA2Context2 != &BOM) in TestConvert()
781 if (U_FAILURE(err) || oldToUAction != otherCharAction(MIA2) || oldToUContext != &BOM) in TestConvert()
795 if (MIA2_2 == otherCharAction(MIA2) || MIA2Context2 == &BOM){ in TestConvert()
[all …]
/external/llvm/test/Other/
DResponseFile.ll11 ; When the response file begins with UTF8 BOM sequence, we shall remove them.
/external/icu/icu4c/source/data/mappings/
Dconvrtrs.txt157 # The ICU 2.2 UTF-16/32 converters detect and write a BOM.
159 ibm-1204 { IBM* } # UTF-16 with IBM PUA and BOM sensitive
160 ibm-1205 { IBM } # UTF-16 BOM sensitive
210 ibm-1236 { IBM* } # UTF-32 with IBM PUA and BOM sensitive
211 ibm-1237 { IBM } # UTF-32 BOM sensitive
239 # "BOM" means the Unicode Byte Order Mark, which is the encoding-scheme-specific
241 # "Reverse BOM" means the BOM for the sibling encoding scheme with the
247 # From Unicode: Writes BOM.
248 # To Unicode: Detects and consumes BOM.
249 # If there is a "reverse BOM", Java throws
[all …]
/external/icu/icu4c/source/extra/uconv/resources/
Dfr.txt68 " --add-signature add a U+FEFF Unicode signature character (BOM)\n"
69 " --remove-signature remove a U+FEFF Unicode signature character (BOM)\n"
Droot.txt66 " --add-signature add a U+FEFF Unicode signature character (BOM)\n"
67 … " --remove-signature remove a U+FEFF Unicode signature character (BOM)\n"
/external/python/cpython2/Doc/library/
Dcodecs.rst306 .. data:: BOM
317 These constants define various encodings of the Unicode byte order mark (BOM)
321 native byte order, :const:`BOM` is an alias for :const:`BOM_UTF16`,
323 :const:`BOM_UTF16_BE`. The others represent the BOM in UTF-8 and UTF-32
824 there's the so called BOM ("Byte Order Mark"). This is the Unicode character
835 Unicode software still must be able to handle ``U+FEFF`` in both roles: as a BOM
862 As UTF-8 is an 8-bit encoding no BOM is required and any ``U+FEFF`` character in
873 is written to the file, a UTF-8 encoded BOM (which looks like this as a byte
883 correctly guessed from the byte sequence. So here the BOM is not used to be able
888 three bytes in the file. In UTF-8, the use of the BOM is discouraged and
[all …]
Djson.rst530 The RFC prohibits adding a byte order mark (BOM) to the start of a JSON text,
531 and this module's serializer does not add a BOM to its output.
533 BOM in their input. This module's deserializer raises a :exc:`ValueError`
534 when an initial BOM is present.
/external/icu/icu4c/source/test/testdata/
Dconversion.txt60 // Java "Unicode" requires a BOM
68 // Java "UnicodeBig" requires a BE BOM or no BOM; it consumes the BE BOM
76 // Java "UnicodeLittle" requires an LE BOM or no BOM; it consumes the LE BOM
79 …{ "x-UTF-16LE-BOM", :bin{ feff6100 }, "\\xFE\\xFFa", :intvector{ 0,0,0,0,0,0,0,0,2 }, :int{1},…
1027 // Java "UnicodeBig" writes a BOM
1031 // Java "UnicodeLittle" writes a BOM
1217 // UTF-16/32: do not output a BOM if there is no data at all
/external/python/cpython2/Doc/c-api/
Dunicode.rst543 byte order mark (BOM), the decoder switches to this byte order and the BOM is
576 byteorder == 0: native byte order (writes a BOM mark)
579 If byteorder is ``0``, the output string will always start with the Unicode BOM
580 mark (U+FEFF). In the other two modes, no BOM mark is prepended.
593 string always starts with a BOM mark. Error handling is "strict". Return
619 byte order mark (BOM), the decoder switches to this byte order and the BOM is
658 byteorder == 0: native byte order (writes a BOM mark)
661 If byteorder is ``0``, the output string will always start with the Unicode BOM
662 mark (U+FEFF). In the other two modes, no BOM mark is prepended.
678 string always starts with a BOM mark. Error handling is "strict". Return
/external/icu/icu4j/tools/misc/src/com/ibm/icu/dev/tool/translit/
DdumpICUrules.bat375 my $BOM = pack("C3", 239, 187, 191); # a UTF8 byte order mark
388 # Look for and delete BOM
390 s/^$BOM//;
/external/python/cpython2/Lib/
Dcodecs.py59 BOM = BOM_UTF16 = BOM_UTF16_LE variable
67 BOM = BOM_UTF16 = BOM_UTF16_BE variable
/external/llvm/lib/Support/Windows/
DProgram.inc523 char BOM[2];
525 memcpy(BOM, &src, 2);
526 OS.write(BOM, 2);
/external/swiftshader/third_party/llvm-subzero/lib/Support/Windows/
DProgram.inc523 char BOM[2];
525 memcpy(BOM, &src, 2);
526 OS.write(BOM, 2);
/external/walt/hardware/
DREADME.md25 * List of parts for version r0.7 - [BOM as a tsv file](WALT_bom_r07.tsv)
/external/tinyxml/
Dchanges.txt207 - Documents loaded with the UTF-8 BOM will now save with the UTF-8 BOM. Good suggestion
/external/python/cpython2/Doc/howto/
Dlogging-cookbook.rst768 Inserting a BOM into messages sent to a SysLogHandler
774 Order Mark (BOM), followed by Unicode encoded using UTF-8. (See the `relevant
778 :class:`~logging.handlers.SysLogHandler` to insert a BOM into the message, but
779 unfortunately, it was implemented incorrectly, with the BOM appearing at the
783 As this behaviour is broken, the incorrect BOM insertion code is being removed
785 want to produce RFC 5424-compliant messages which include a BOM, an optional
796 encoded as a UTF-8 BOM -- the byte-string ``'\xef\xbb\xbf'``.
Dunicode.rst569 Unicode character U+FEFF is used as a byte-order mark (BOM), and is often
571 of the file's byte ordering. Some encodings, such as UTF-16, expect a BOM to be
572 present at the start of a file; when such an encoding is used, the BOM will be
576 particular byte ordering and don't skip the BOM.
/external/markdown/docs/
DCHANGE_LOG74 Oct 30, 2007: Fixed BOM removal (thanks Malcolm Tredinnick). Fixed
/external/libxml2/os400/libxmlrpg/
Dencoding.rpgle33 * given to the parser itself. The BOM for UTF16 and the encoding

12