| /external/python/google-api-python-client/docs/dyn/ |
| D | cloudsupport_v2beta.media.html | 109 { # # gdata.* are outside protos with mising documentation
110 …uot;algorithm": "A String", # # gdata.* are outside protos with mising documentation
111 …toreObjectRef": "A String", # # gdata.* are outside protos with mising documentation
112 …"blobRef": "A String", # # gdata.* are outside protos with mising documentation
113 …# gdata.* are outside protos with mising documentation # # gdata.* are outside protos with mising …
114 …lobGeneration": "A String", # # gdata.* are outside protos with mising documentation
115 … "blobId": "A String", # # gdata.* are outside protos with mising documentation
116 …oadReadHandle": "A String", # # gdata.* are outside protos with mising documentation
117 …uot;readToken": "A String", # # gdata.* are outside protos with mising documentation
118 …dataContainer": "A String", # # gdata.* are outside protos with mising documentation
[all …]
|
| /external/licenseclassifier/v2/assets/License/CERN-OHL-v1.2/ |
| D | license.txt | 20 “Documentation” means schematic diagrams, designs, circuit or circuit
23 available under the conditions of this Licence. The Documentation may
27 “Documentation Location” means a location where the Licensor has
28 placed Documentation, and which he believes will be publicly
30 the public or distribution of Documentation.
33 the Documentation or the modified Documentation.
39 Documentation and subsequently communicates to the public and/ or
40 distributes the resulting Documentation under the terms and conditions
51 communication to the public and distribution of the Documentation, and
62 the Documentation, the modified Documentation or with Products, unless
[all …]
|
| /external/cronet/third_party/libxml/fuzz/seed_corpus/ |
| D | 74fa7a7901379ffe690ba9b471bc74995bb5302c | 8 <xs:documentation>This schema defines the structure of the National
20 how to interpret this data. </xs:documentation>
24 …<xs:documentation>The root element of the NVD CVE feed. Multiple "entry" child elements describe s…
32 <xs:documentation>The schema version number supported by the feed.</xs:documentation>
37 <xs:documentation>The date the feed was generated.</xs:documentation>
45 <xs:documentation>A CVE entry.</xs:documentation>
54 <xs:documentation> Documents one CVE entry. The child elements should always
56 entry elements from the CVE XML feeds.</xs:documentation>
61 <xs:documentation>Description wrapper tag, parent to any
65 description source (i.e. CVE, NVD, ...). </xs:documentation>
[all …]
|
| /external/libxml2/test/schemas/ |
| D | nvdcve_0.xsd | 8 <xs:documentation>This schema defines the structure of the National
20 how to interpret this data. </xs:documentation>
24 …<xs:documentation>The root element of the NVD CVE feed. Multiple "entry" child elements describe s…
32 <xs:documentation>The schema version number supported by the feed.</xs:documentation>
37 <xs:documentation>The date the feed was generated.</xs:documentation>
45 <xs:documentation>A CVE entry.</xs:documentation>
54 <xs:documentation> Documents one CVE entry. The child elements should always
56 entry elements from the CVE XML feeds.</xs:documentation>
61 <xs:documentation>Description wrapper tag, parent to any
65 description source (i.e. CVE, NVD, ...). </xs:documentation>
[all …]
|
| /external/clang/include/clang/Basic/ |
| D | Attr.td | 10 // The documentation is organized by category. Attributes can have category-
11 // specific documentation that is collated within the larger document.
21 // documentation. Ideally, this category should be used for internal-only
27 // documentation. Otherwise, the documentation will specify the attribute has
32 // Specifies the documentation to be associated with the given category.
33 class Documentation {
52 def Undocumented : Documentation {
306 // Any documentation that should be associated with the attribute. Since an
308 // Documentation entry may be listed.
309 list<Documentation> Documentation;
[all …]
|
| D | DiagnosticCommentKinds.td | 11 let CategoryName = "Documentation Issue" in {
18 InGroup<Documentation>, DefaultIgnore;
22 InGroup<Documentation>, DefaultIgnore;
52 InGroup<Documentation>, DefaultIgnore;
56 InGroup<Documentation>, DefaultIgnore;
69 InGroup<Documentation>, DefaultIgnore;
78 InGroup<Documentation>, DefaultIgnore;
85 InGroup<Documentation>, DefaultIgnore;
91 InGroup<Documentation>, DefaultIgnore;
97 InGroup<Documentation>, DefaultIgnore;
[all …]
|
| /external/stardoc/docs/ |
| D | writing_stardoc.md | 4 <li><a href="#rule-documentation">Rule Documentation</a></li>
5 <li><a href="#provider-documentation">Provider Documentation</a></li>
6 <li><a href="#macro-documentation">Macro / Function Documentation</a></li>
10 When generating documentation, Stardoc parses the `.bzl` file to extract the
11 inline documentation as well as evaluates the Starlark code to determine the
12 types for rule attributes. Stardoc will, by default, generate documentation for
15 symbols for which stardoc generates documentation.
17 <a name="rule-documentation"></a>
18 ## Rule Documentation
20 When generating documentation, Stardoc parses the `.bzl` file to extract the
[all …]
|
| /external/rust/crates/vulkano/out/ |
| D | autogen.rs | 7 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
21 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
35 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
48 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
60 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
74 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
85 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
98 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
111 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
122 …- [Vulkan documentation](https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_…
[all …]
|
| /external/fonttools/Doc/ |
| D | README.md | 1 # fontTools Documentation
3 The fontTools project documentation updates continuously on Read the Docs as the project source cha…
5 The documentation is hosted at https://fonttools.readthedocs.io/.
9 - [How to Build Local Documentation](#how-to-build-local-documentation)
10 - [Contributing to the fontTools Documentation](#contributing-to-the-documentation)
11 - [Documentation License](#documentation-license)
13 ## How to Build Local Documentation
17 …and the `pip` Python package manager installed on your system to build the fontTools documentation.
19 …eate a Python virtual environment, and then install fontTools and the documentation build dependen…
26 ### Build Documentation argument
[all …]
|
| /external/mesa3d/src/freedreno/registers/ |
| D | rules-ng.xsd | 8 <documentation>
15 </documentation>
16 <documentation>Version 0.1</documentation>
44 <!-- Documentation elements -->
62 <documentation>
64 </documentation>
75 <documentation>nickType</documentation>
84 <documentation>databaseType</documentation>
94 <documentation>importType</documentation>
101 <documentation>copyrightType</documentation>
[all …]
|
| /external/pigweed/pw_docgen/ |
| D | docs.rst | 6 The docgen module provides tools to generate documentation for Pigweed-based
11 documentation. Docgen provides a convenient way to combine all of the relevant
12 documentation for a project into one place, allowing downstream consumers of
14 unified source of documentation early on.
16 The documentation generation is integrated directly into the build system. Any
17 build target can depend on documentation, which allows it to be included as part
18 of a factory release build, for example. Additionally, documentation itself can
20 Any time the code is changed, documentation will be regenerated with the updated
23 Documentation Overview
25 Each Pigweed module provides documentation describing its functionality, use
[all …]
|
| /external/python/google-api-python-client/googleapiclient/discovery_cache/documents/ |
| D | cloudsupport.v2beta.json | 650 "description": "# gdata.* are outside protos with mising documentation",
654 "description": "# gdata.* are outside protos with mising documentation",
659 "description": "# gdata.* are outside protos with mising documentation",
663 "description": "# gdata.* are outside protos with mising documentation",
668 "description": "# gdata.* are outside protos with mising documentation",
672 "description": "# gdata.* are outside protos with mising documentation",
832 "description": "# gdata.* are outside protos with mising documentation",
836 "description": "# gdata.* are outside protos with mising documentation",
842 "description": "# gdata.* are outside protos with mising documentation"
845 "description": "# gdata.* are outside protos with mising documentation",
[all …]
|
| /external/google-styleguide/docguide/ |
| D | best_practices.md | 1 # Documentation Best Practices
8 1. [Minimum viable documentation](#minimum-viable-documentation)
10 1. [Delete dead documentation](#delete-dead-documentation)
11 1. [Documentation is the story of your code](#documentation-is-the-story-of-your-code)
13 ## Minimum viable documentation
16 assembly of "documentation" in various states of disrepair.
32 **Change your documentation in the same CL as the code change**. This keeps your
39 ## Delete dead documentation
59 Your documentation should be as good as possible within a reasonable time frame.
60 The standards for a documentation review are different from the
[all …]
|
| /external/python/cpython2/Doc/library/ |
| D | pydoc.rst | 1 :mod:`pydoc` --- Documentation generator and online help system
5 :synopsis: Documentation generator and online help system.
13 single: documentation; generation
14 single: documentation; online
21 The :mod:`pydoc` module automatically generates documentation from Python
22 modules. The documentation can be presented as pages of text on the console,
25 For modules, classes, functions and methods, the displayed documentation is
33 interactive interpreter, which uses :mod:`pydoc` to generate its documentation
34 as text on the console. The same text documentation can also be viewed from
40 at a shell prompt will display documentation on the :mod:`sys` module, in a
[all …]
|
| D | docxmlrpcserver.rst | 18 :mod:`SimpleXMLRPCServer` to serve HTML documentation in response to HTTP GET
38 POST requests, documentation GET requests, and modifies logging so that the
52 HTML documentation. This allows a server to provide its own web-based
53 documentation.
58 Set the title used in the generated HTML documentation. This title will be used
64 Set the name used in the generated HTML documentation. This name will appear at
65 the top of the generated documentation inside a "h1" element.
70 Set the description used in the generated HTML documentation. This description
71 will appear as a paragraph, below the server name, in the documentation.
81 HTML documentation. This allows a server to provide its own web-based
[all …]
|
| /external/dokka/ |
| D | README.md | 7 Dokka is a documentation engine for Kotlin, performing the same function as javadoc for Java.
10 and can generate documentation in multiple formats including standard Javadoc, HTML and Markdown.
56 // List of files with module and package documentation
57 // http://kotlinlang.org/docs/reference/kotlin-doc.html#module-and-package-documentation
81 impliedPlatforms = ["JVM"] // See platforms section of documentation
97 // See platforms section of documentation
115 // No default documentation link to kotlin-stdlib
118 … // Allows linking to documentation of the project's dependencies (generated with Javadoc or Dokka)
121 // Root URL of the generated documentation to link with. The trailing slash is required!
128 // Allows to customize documentation generation options on a per-package basis
[all …]
|
| /external/python/cpython2/Lib/ |
| D | DocXMLRPCServer.py | 4 serve pydoc-style documentation in response to HTTP
5 GET requests. This documentation is dynamically generated
69 """Produce HTML documentation for a function or method object."""
110 """Produce HTML documentation for an XML-RPC server."""
135 """Generates documentation for an XML-RPC server.
142 # setup variables used for HTML documentation
143 self.server_name = 'XML-RPC Server Documentation'
147 self.server_title = 'XML-RPC Server Documentation'
150 """Set the HTML title of the generated server documentation"""
155 """Set the name of the generated HTML server documentation"""
[all …]
|
| /external/wayland/ |
| D | configure.ac | 86 AC_ARG_ENABLE([documentation], optenable
87 [AC_HELP_STRING([--disable-documentation],
88 [Disable building the documentation])],
138 …C_MSG_ERROR([Documentation build requested but doxygen not found. Install doxygen or disable the d…
145 …n 1.6+ required for documentation build. Install required doxygen version or disable the documenta…
152 …AC_MSG_ERROR([Documentation build requested but xmlto not found. Install xmlto or disable the docu…
157 …G_ERROR([Documentation build requested but graphviz's dot not found. Install graphviz or disable t…
163 … 2.26+ required for documentation build. Install required graphviz version or disable the document…
174 …Documentation build requested but docbook-xsl stylesheets are not found. Install the docbook-xsl p…
|
| /external/python/google-api-python-client/samples/ |
| D | README.md | 7 Documentation for the Ad Exchange Buyer API in
8 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/adexchangebuyer/v1.3/python/l…
22 Documentation for the AdSense Management API in
23 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/adsense/v1.3/python/latest/).
36 Documentation for the Google Analytics API in
37 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/analytics/v3/python/latest/).
51 Documentation for the Enterprise Audit API in
52 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/audit/v1/python/latest/).
65 Documentation for the Blogger API in
66 [PyDoc](https://google-api-client-libraries.appspot.com/documentation/blogger/v3/python/latest/).
[all …]
|
| /external/python/cpython3/Doc/library/ |
| D | pydoc.rst | 1 :mod:`pydoc` --- Documentation generator and online help system
5 :synopsis: Documentation generator and online help system.
13 single: documentation; generation
14 single: documentation; online
19 The :mod:`pydoc` module automatically generates documentation from Python
20 modules. The documentation can be presented as pages of text on the console,
23 For modules, classes, functions and methods, the displayed documentation is
31 interactive interpreter, which uses :mod:`pydoc` to generate its documentation
32 as text on the console. The same text documentation can also be viewed from
38 at a shell prompt will display documentation on the :mod:`sys` module, in a
[all …]
|
| /external/dng_sdk/ |
| D | LICENSE | 6 Adobe Systems Incorporated provides the Software and Documentation for use under
8 modification or distribution of the Software or Documentation, or any
13 accompanying this Agreement. "Documentation" means the documents, specifications
24 copies of the Documentation for your development purposes and to publicly
26 Documentation.
30 Documentation and you will include such notices in any copies of the Software
34 Documentation in any manner not permitted by this Agreement. No title to the
35 intellectual property in the Software or Documentation is transferred to you
37 or the Documentation except as expressly set forth in this Agreement. All rights
41 ADOBE PROVIDES THE SOFTWARE AND DOCUMENTATION ONLY ON AN "AS IS" BASIS WITHOUT
[all …]
|
| D | LICENSE.source_code | 3 Adobe Systems Incorporated provides the Software and Documentation for use under
5 modification or distribution of the Software or Documentation, or any
10 accompanying this Agreement. "Documentation" means the documents, specifications
21 copies of the Documentation for your development purposes and to publicly
23 Documentation.
27 Documentation and you will include such notices in any copies of the Software
31 Documentation in any manner not permitted by this Agreement. No title to the
32 intellectual property in the Software or Documentation is transferred to you
34 or the Documentation except as expressly set forth in this Agreement. All rights
38 ADOBE PROVIDES THE SOFTWARE AND DOCUMENTATION ONLY ON AN "AS IS" BASIS WITHOUT
[all …]
|
| D | NOTICE | 13 Adobe Systems Incorporated provides the Software and Documentation for use under
15 modification or distribution of the Software or Documentation, or any
20 accompanying this Agreement. "Documentation" means the documents, specifications
31 copies of the Documentation for your development purposes and to publicly
33 Documentation.
37 Documentation and you will include such notices in any copies of the Software
41 Documentation in any manner not permitted by this Agreement. No title to the
42 intellectual property in the Software or Documentation is transferred to you
44 or the Documentation except as expressly set forth in this Agreement. All rights
48 ADOBE PROVIDES THE SOFTWARE AND DOCUMENTATION ONLY ON AN "AS IS" BASIS WITHOUT
[all …]
|
| /external/pigweed/seed/ |
| D | 0102-module-docs.rst | 4 0102: Consistent Module Documentation
8 :fas:`seedling` SEED-0102: :ref:`Consistent Module Documentation<seed-0102>`
26 Pigweed modules ought to have documentation that is reasonably comprehensive,
29 them. This SEED proposes a documentation philosophy applicable to all Pigweed
37 primary focus of this SEED is to improve the documentation experience for users.
43 ``docs.rst`` file that contains the module's documentation. This gives the
45 documentation as they would like. However, this approach fails for Pigweed
47 documentation, and certainly fails Pigweed users who struggle to find the
49 Pigweed maintainers to write good documentation, thereby making Pigweed much
52 Pigweed's design is inherently and intentionally modular. So documentation at
[all …]
|
| /external/licenseclassifier/v2/assets/License/Sflow/ |
| D | license.txt | 4 UTILIZING THE sFlow(R) SOFTWARE ("SOFTWARE") AND/OR ANY ACCOMPANYING DOCUMENTATION
5 ("DOCUMENTATION") AND/OR THE RELATED SPECIFICATIONS ("SPECIFICATIONS"). YOUR REPRODUCTION
6 OR USE OF THE SOFTWARE AND/OR THE DOCUMENTATION AND/OR THE SPECIFICATIONS CONSTITUTES YOUR
9 THE SOFTWARE OR THE DOCUMENTATION OR THE SPECIFICATIONS.
13 "Documentation" means the user manuals, training materials, and operating materials, if any,
41 2.1 Software, Documentation and Specifications License Grant. InMon hereby grants to
45 Documentation, and the Specifications; (ii) modify the Software; (iii) implement the
48 any Products that include the Software, the Documentation, or software in which the
54 Software, the Documentation, the Specifications and any software that implements the
61 and no other mark, to identify the Software, the Documentation, the Specifications and any
[all …]
|