| /frameworks/compile/libbcc/ |
| README.html | 2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
| /frameworks/compile/slang/ |
| README.html | 2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
| WspTypeDecoder.java | 103 WELL_KNOWN_MIME_TYPES.put(0x3B, "application/xhtml+xml");
113 WELL_KNOWN_MIME_TYPES.put(0x45, "application/vnd.wap.xhtml+xml");
|
| /libcore/luni/src/main/java/libcore/net/ |
| MimeUtils.java | 213 add("application/xhtml+xml", "xhtml");
|
| /prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/share/doc/mpfr/ |
| FAQ.html | 2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
26 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
| /prebuilts/gdb/darwin-x86/lib/python2.7/ |
| HTMLParser.py | 1 """A parser for HTML and XHTML."""
321 # XHTML-style empty tag: <span attr="value" />
|
| /prebuilts/gdb/linux-x86/lib/python2.7/ |
| HTMLParser.py | 1 """A parser for HTML and XHTML."""
321 # XHTML-style empty tag: <span attr="value" />
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/ |
| HTMLParser.py | 1 """A parser for HTML and XHTML."""
321 # XHTML-style empty tag: <span attr="value" />
|
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/ |
| HTMLParser.py | 1 """A parser for HTML and XHTML."""
321 # XHTML-style empty tag: <span attr="value" />
|
| /prebuilts/tools/linux-x86/swt/ |
| about.html | 1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3 <html xmlns="http://www.w3.org/1999/xhtml">
|
| /prebuilts/tools/linux-x86_64/swt/ |
| about.html | 1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3 <html xmlns="http://www.w3.org/1999/xhtml">
|
| /external/python/cpython3/Lib/test/ |
| mime.types | 637 application/vnd.oipf.dae.xhtml+xml
785 application/vnd.pwg-xhtml-print+xml
[all...] |
| test_xml_etree.py | 861 elem = ET.XML("<html:html xmlns:html='http://www.w3.org/1999/xhtml' />")
863 '<html:html xmlns:html="http://www.w3.org/1999/xhtml" />') # 2.2
[all...] |
| /external/scapy/scapy/contrib/ |
| bgp.py | [all...] |
| /prebuilts/go/darwin-x86/misc/nacl/testdata/ |
| mime.types | 679 # application/vnd.oipf.dae.xhtml+xml
829 # application/vnd.pwg-xhtml-print+xml
[all...] |
| /prebuilts/go/linux-x86/misc/nacl/testdata/ |
| mime.types | 679 # application/vnd.oipf.dae.xhtml+xml
829 # application/vnd.pwg-xhtml-print+xml
[all...] |
| /external/autotest/client/profilers/oprofile/ |
| oprofile-0.9.4.tar.bz2 | |
| /external/google-styleguide/ |
| xmlstyle.html | 351 Google XML Document Format Style Guide</h1><div style="text-align: center;">Version 1.0<br>Copyright Google 2008<br><br></div><h2>Introduction</h2>This document provides a set of guidelines for general use when designing new XML document formats (and to some extent XML documents as well; see Section 11). Document formats usually include both formal parts (DTDs, schemas) and parts expressed in normative English prose.<br><br>These guidelines apply to new designs, and are not intended to force retroactive changes in existing designs. When participating in the creation of public or private document format designs, the guidelines may be helpful but should not control the group consensus.<br><br>This guide is meant for the design of XML that is to be generated and consumed by machines rather than human beings. Its rules are <i>not applicable</i> to formats such as XHTML (which should be formatted as much like HTML as possible) or ODF which are meant to express rich text. A document that includes embedded content in XHTML or some other rich-text format, but also contains purely machine-interpretable portions, SHOULD follow this style guide for the machine-interpretable portions. It also does not affect XML document formats that are created by translations from proto buffers or through some other type of format.<br><br>Brief rationales have been added to most of the guidelines. They are maintained in the same document in hopes that they won't get out of date, but they are not considered normative.<br><br>The terms MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are used in this document in the sense of <a title="RFC 2119" href="https://www.ietf.org/rfc/rfc2119.txt" id="iecm">RFC 2119.</a><br> <br><h2>1. To design or not to design, that is the question<br></h2><ol><li>Attempt to reuse existing XML formats whenever possible, especially those which allow extensions. Creating an entirely new format should be done only with care and consideration; read <a title="Tim Bray's warnings" href="https://www.tbray.org/ongoing/When/200x/2006/01/08/No-New-XML-Languages" id="d3cy">Tim Bray's warnings</a> first. Try to get wide review of your format, from outside your organization as well, if possible. [<i>Rationale:</i> New document formats have a cost: they must be reviewed, documented, and learned by users.]<br><br></li><li>If you are reusing or extending an existing format, make <i>sensible</i>
423 </p><p> </p><h2>11. Representation of XML document instances<br></h2><p><b>Note:</b> These points are only guidelines, as the format of program-created instances will often be outside the programmer's control (for example, when an XML serialization library is being used). <i>In no case</i> should XML parsers rely on these guidelines being followed. Use standard XML parsers, not hand-rolled hacks.<br></p><p><br></p><ol><li>The character encoding used SHOULD be UTF-8. Exceptions should require extremely compelling circumstances. [<i>Rationale:</i> UTF-8 is universal and in common use.]<br><br></li><li>Namespaces SHOULD be declared in the root element of a document wherever possible. [<i>Rationale: </i>Clarity and consistency.]<br><br></li><li>The mapping of namespace URIs to prefixes SHOULD remain constant throughout the document, and SHOULD also be used in documentation of the design. [<i>Rationale: </i>Clarity and consistency.]<br><br></li><li>Well-known prefixes such as html: (for XHTML), dc: (for Dublin Core metadata), and xs: (for XML Schema) should be used for standard namespaces. [<i>Rationale:</i> Human readability.]<br><br></li><li>Redundant whitespace in a tag SHOULD NOT be
[all...] |
| /external/python/cpython2/Doc/library/ |
| xml.etree.elementtree.rst | 880 >>> tree.parse("index.xhtml")
891 >>> tree.write("output.xhtml")
[all...] |
| /libcore/luni/src/main/native/ |
| org_apache_harmony_xml_ExpatParser.cpp | 499 * Returns the namespace URI, like "http://www.w3.org/1999/xhtml".
568 * "uri|localName|prefix" (example: "http://www.w3.org/1999/xhtml|h1|html")
569 * "uri|localName" (example: "http://www.w3.org/1999/xhtml|h1")
[all...] |
| /build/make/core/ |
| build-system.html | 1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
4 <html xmlns="http://www.w3.org/1999/xhtml">
9 - keep the document xhtml-compliant, as many people use validating editors
28 <!-- commenting out so the xhtml validator doesn't whine about < and &&;
[all...] |
| /dalvik/docs/ |
| java-constraints.html | 1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/ |
| htmllib.py | 26 It supports all entity names required by the XHTML 1.0 Recommendation.
|
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Lib/test/ |
| test_sgmllib.py | 186 """Handling of XHTML-style empty start tags"""
|
| /external/bart/docs/api_reference/ |
| conf.py | 212 # This is the file name suffix for HTML files (e.g. ".xhtml").
|
