| /external/antlr/runtime/Cpp/include/ |
| D | antlr3input.inl | 470 // See if there is a BOM at the start of this UTF-8 sequence
480 // The UTF8 BOM is present so skip it
493 // See if there is a BOM at the start of the input. If not then
495 // machine (or it is really UCS2). If there is a BOM we determine if the encoding
502 // BOM Present, indicates Big Endian
512 // BOM present, indicates Little Endian
520 // No BOM present, assume local computer byte order
529 // See if there is a BOM at the start of the input. If not then
540 // BOM Present, indicates Big Endian
552 // BOM present, indicates Little Endian
[all …]
|
| /external/python/cpython3/Lib/test/ |
| D | tokenize_tests-latin1-coding-cookie-and-utf8-bom-sig.txt | 2 # IMPORTANT: this file has the utf-8 BOM signature '\xef\xbb\xbf'
5 # the presence of a utf-8 BOM signature -- this is intended.
|
| D | tokenize_tests-no-coding-cookie-and-utf8-bom-sig-only.txt | 1 # IMPORTANT: this file has the utf-8 BOM signature '\xef\xbb\xbf'
|
| D | tokenize_tests-utf8-coding-cookie-and-utf8-bom-sig.txt | 2 # IMPORTANT: this file has the utf-8 BOM signature '\xef\xbb\xbf'
|
| D | tokenize_tests-utf8-coding-cookie-and-no-utf8-bom-sig.txt | 3 # does NOT have the utf-8 BOM signature '\xef\xbb\xbf' at the start
|
| /external/tensorflow/tensorflow/core/api_def/base_api/ |
| D | api_def_UnicodeTranscode.pbtxt | 80 (e.g. if the encoding is UTF-16 and the BOM indicates big-endian), then that
81 BOM will be consumed and not emitted into the output. If the input encoding
82 is marked with an explicit endianness (e.g. UTF-16-BE), then the BOM is
88 with an explicit endianness, the BOM is not considered part of the string itself
|
| /external/snakeyaml/src/test/resources/pyyaml/ |
| D | spec-05-02-utf8.data | 1 # Invalid use of BOM
|
| /external/cldr/tools/java/org/unicode/cldr/icu/ |
| D | ICUWriter.java | 18 private static final String BOM = "\uFEFF"; field in ICUWriter
165 byte[] bytes = BOM.getBytes(CHARSET); in writeBOM()
|
| /external/grpc-grpc/src/csharp/ |
| D | .editorconfig | 3 charset = utf-8 ; Implies no BOM.
|
| /external/icu/icu4c/source/samples/ugrep/ |
| D | Makefile | 20 CHECK_ARGS=BOM readme.txt
|
| D | readme.txt | 18 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/swiftshader/third_party/llvm-7.0/llvm/test/YAMLParser/ |
| D | spec-05-02-utf8.test | 3 # Invalid use of BOM
|
| /external/llvm/test/YAMLParser/ |
| D | spec-05-02-utf8.test | 3 # Invalid use of BOM
|
| /external/clang/test/Index/ |
| D | preamble-reparse-with-BOM.m | 8 // CHECK: preamble-reparse-with-BOM.m:2:12: ObjCInterfaceDecl=I2:2:12 Extent=[2:1 - 3:5]
|
| /external/python/cpython3/Doc/library/ |
| D | tokenize.rst | 58 UTF-8 BOM or encoding cookie, according to :pep:`263`.
98 It detects the encoding from the presence of a UTF-8 BOM or an encoding
99 cookie as specified in :pep:`263`. If both a BOM and a cookie are present,
100 but disagree, a :exc:`SyntaxError` will be raised. Note that if the BOM is found,
|
| /external/icu/icu4c/source/test/cintltst/ |
| D | ccapitst.c | 244 UChar BOM = 0x0000; in TestConvert() local
728 …ucnv_setFromUCallBack(myConverter, otherUnicodeAction(MIA1), &BOM, &oldFromUAction, &oldFromUConte… in TestConvert()
735 if (MIA1_2 != otherUnicodeAction(MIA1) || MIA1Context2 != &BOM) in TestConvert()
742 … if (U_FAILURE(err) || oldFromUAction != otherUnicodeAction(MIA1) || oldFromUContext != &BOM) in TestConvert()
756 …ucnv_setFromUCallBack(myConverter, otherUnicodeAction(MIA1), &BOM, &oldFromUAction, &oldFromUConte… in TestConvert()
758 if(MIA1_2 == otherUnicodeAction(MIA1) || MIA1Context2 == &BOM){ in TestConvert()
768 … ucnv_setToUCallBack(myConverter,otherCharAction(MIA2), &BOM, &oldToUAction, &oldToUContext, &err); in TestConvert()
775 if (MIA2_2 != otherCharAction(MIA2) || MIA2Context2 != &BOM) in TestConvert()
782 if (U_FAILURE(err) || oldToUAction != otherCharAction(MIA2) || oldToUContext != &BOM) in TestConvert()
796 if (MIA2_2 == otherCharAction(MIA2) || MIA2Context2 == &BOM){ in TestConvert()
[all …]
|
| /external/protobuf/objectivec/Tests/ |
| D | GPBCodedInputStreamTests.m | 303 "\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/data/mappings/ |
| D | convrtrs.txt | 157 # 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/python/cpython3/PC/ |
| D | launcher.c | 1001 } BOM; typedef
1007 static BOM BOMs[] = {
1018 static BOM *
1025 BOM * result = NULL; in find_BOM()
1026 BOM *bom; in find_BOM()
1038 find_terminator(char * buffer, int len, BOM *bom) in find_terminator()
1180 BOM* bom; in maybe_handle_shebang()
|
| /external/swiftshader/third_party/llvm-7.0/llvm/test/Other/ |
| D | ResponseFile.ll | 11 ; When the response file begins with UTF8 BOM sequence, we shall remove them.
|
| /external/llvm/test/Other/ |
| D | ResponseFile.ll | 11 ; When the response file begins with UTF8 BOM sequence, we shall remove them.
|
| /external/python/cpython2/Doc/library/ |
| D | codecs.rst | 306 .. 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 …]
|
| /external/icu/icu4c/source/extra/uconv/resources/ |
| D | fr.txt | 68 " --add-signature add a U+FEFF Unicode signature character (BOM)\n"
69 " --remove-signature remove a U+FEFF Unicode signature character (BOM)\n"
|
| /external/icu/icu4c/source/test/testdata/ |
| D | conversion.txt | 60 // 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/ |
| D | unicode.rst | 543 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
|