Searched
full:entities (Results
401 -
425 of
1749) sorted by null
<<11121314151617181920>>
/prebuilts/tools/common/m2/repository/org/apache/httpcomponents/httpcomponents-client/4.2.1/ |
httpcomponents-client-4.2.1.pom | 303 <entities> 308 </entities>
|
/prebuilts/tools/common/m2/repository/org/apache/httpcomponents/httpcomponents-client/4.3.2/ |
httpcomponents-client-4.3.2.pom | 263 <entities>
268 </entities>
|
/external/libxml2/doc/devhelp/ |
libxml2-parserInternals.html | [all...] |
/external/libxml2/doc/html/ |
libxml-parserInternals.html | [all...] |
/build/tools/ |
generate-notice-files.py | 81 """Produce entities within text."""
|
/external/apache-xml/src/main/java/org/apache/xml/dtm/ |
DTMFilter.java | 76 * entities are not part of the document tree, they do not appear when
|
/external/clang/tools/libclang/ |
CursorVisitor.h | 180 /// \brief Visit declarations and preprocessed entities for the file region
|
/external/droiddriver/src/io/appium/droiddriver/helpers/ |
package-info.java | 26 * The organization of the entities (pages, components) does not need to strictly follow the AUT
|
/external/guava/guava/src/com/google/common/escape/ |
ArrayBasedUnicodeEscaper.java | 35 * replacement array contains information about the named HTML entities
|
/external/libpcap/Win32/Include/net/ |
if.h | 50 * which may be of interest to management entities.
|
/external/libxml2/python/tests/ |
reader2.py | 161 # entities, making sure the entity ref node doesn't show up in that case
|
/external/libxml2/test/valid/dtds/ |
xhtml1-strict.dtd | 22 <!--================ Character mnemonic entities =========================--> 25 "-//W3C//ENTITIES Latin 1 for XHTML//EN" 30 "-//W3C//ENTITIES Symbols for XHTML//EN" 35 "-//W3C//ENTITIES Special for XHTML//EN"
|
/external/libxml2/win32/VC10/ |
libxml2-focus.vcxproj | 137 <ClCompile Include="..\..\entities.c" />
|
/external/llvm/lib/CodeGen/AsmPrinter/ |
DwarfCompileUnit.h | 42 /// GlobalNames - A map of globally visible named entities for this unit.
|
/external/markdown/MarkdownTest/Tests_2004/ |
Markdown Documentation - Syntax.text | 126 used to denote HTML entities. If you want to use them as literal 127 characters, you must escape them as entities, e.g. `<`, and 500 are automatically converted into HTML entities. This makes it very 769 entities automatically, which makes it easy to include example HTML
|
/external/markdown/MarkdownTest/Tests_2007/ |
Markdown Documentation - Syntax.text | 126 used to denote HTML entities. If you want to use them as literal 127 characters, you must escape them as entities, e.g. `<`, and 500 are automatically converted into HTML entities. This makes it very 769 entities automatically, which makes it easy to include example HTML
|
/external/markdown/docs/ |
CHANGE_LOG | 166 Aug. 11, 2005: Added support for inline html and entities, inline
|
/external/markdown/tests/extensions-x-def_list/ |
markdown-syntax.txt | 126 used to denote HTML entities. If you want to use them as literal 127 characters, you must escape them as entities, e.g. `<`, and 500 are automatically converted into HTML entities. This makes it very 769 entities automatically, which makes it easy to include example HTML
|
/external/markdown/tests/extensions-x-toc/ |
syntax-toc.txt | 89 used to denote HTML entities. If you want to use them as literal 90 characters, you must escape them as entities, e.g. `<`, and 463 are automatically converted into HTML entities. This makes it very 732 entities automatically, which makes it easy to include example HTML
|
/external/markdown/tests/markdown-test/ |
markdown-syntax.txt | 126 used to denote HTML entities. If you want to use them as literal 127 characters, you must escape them as entities, e.g. `<`, and 500 are automatically converted into HTML entities. This makes it very 769 entities automatically, which makes it easy to include example HTML
|
/external/mesa3d/src/gallium/docs/source/ |
conf.py | 133 # typographically correct entities.
|
/external/protobuf/src/google/protobuf/compiler/javanano/ |
javanano_helpers.h | 84 // given parent message (or NULL for file-scope entities). Whether the file's
|
/external/tinyxml/docs/ |
index.html | 21 TinyXml attempts to be a flexible parser, but with truly correct and compliant XML output. TinyXml should compile on any reasonably C++ compliant system. It does not rely on exceptions or RTTI. It can be compiled with or without STL support. TinyXml fully supports the UTF-8 encoding, and the first 64k character entities.<p> 76 <h3>Entities </h3> 78 TinyXml recognizes the pre-defined "character entities", meaning special characters. Namely:<p> 88 will have the Value() of "Far & Away" when queried from the <a class="el" href="classTiXmlText.html">TiXmlText</a> object, and will be written back to the XML stream/file as an ampersand. Older versions of TinyXml "preserved" character entities, but the newer versions will translate them into characters.<p>
|
/external/valgrind/VEX/priv/ |
host_generic_simd64.h | 38 These are purely back-end entities and cannot be seen/referenced
|
/external/valgrind/docs/xml/ |
xml_help.txt | 32 use 'html entities' in your markup, eg. '<' If you *do* use
|
Completed in 346 milliseconds
<<11121314151617181920>>