| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/distutils/command/ |
| install.py | 562 # convert to local form in case Unix notation used (as it
|
| /prebuilts/tools/common/m2/repository/com/sun/xml/dtd-parser/dtd-parser/1.1/ |
| dtd-parser-1.1.jar | |
| /prebuilts/tools/common/m2/repository/xml-apis/xml-apis/1.4.01/ |
| xml-apis-1.4.01-sources.jar | |
| /system/connectivity/shill/doc/ |
| device-api.txt | 180 hexidecimal notation, e.g., "aa:bb:cc:dd:ee:ff",
|
| /toolchain/binutils/binutils-2.25/gprof/ |
| README | 115 you must use the colon notation explained
|
| /external/chromium-trace/catapult/third_party/polymer/components/web-animations-js/node_modules/chai/ |
| chai.js | [all...] |
| /external/ImageMagick/ImageMagick/script/ |
| color.html | 89 <p>The format of an sRGB value in hexadecimal notation is a '#' immediately followed by either three, six, or twelve hexadecimal characters. The three-digit sRGB notation (#rgb) is converted into six-digit form (#rrggbb) by replicating digits, not by adding zeros. For example, #fb0 expands to #ffbb00. This ensures that white (#ffffff) can be specified with the short notation (#fff) and removes any dependencies on the color depth of the image. Use the hexadecimal notation whenever performance is an issue. ImageMagick does not need to load the expansive color table to interpret a hexadecimal color, e.g., <code>#000000</code>, but it does if <code>black</code> is used instead.</p>
91 <p>The format of an sRGB value in the functional notation is 'rgb(<var>r</var>,<var>g</var>,<var>b</var>)', where <var>r</var>, <var>g</var>, and <var>b</var> are either three integer or float values in the range 0?255 or three integer or float percentage values in the range 0?100%. The value 255 corresponds to 100%, and to #F or #FF in the hexadecimal notation: rgb(255, 255, 255) = rgb(100%, 100%, 100%) = #FFF = #FFFFFF. </p>
104 <p>The format of an RGBA value in the functional notation is 'rgba(<var>r</var>,<var>g</var>,<var>b</var>,<var>a</var>)', where <var>r</var>, <var>g</var>, and <var>b</var> are as described above for the RGB functional notation, and where the alpha value <var>a</var> ranges from 0.0 (fully transparent) to 1.0 (fully opaque).</p>
153 <p>Just as the 'rgb()' functional notation has the 'rgba()' alpha counterpart, the 'hsl()' and 'hsb()' functional notations have their 'hsla()' 'hsba()' alpha counterparts. These examples specify the same color:</p>
[all...] |
| /external/ImageMagick/www/ |
| color.html | 93 <p>The format of an sRGB value in hexadecimal notation is a '#' immediately followed by either three, six, or twelve hexadecimal characters. The three-digit sRGB notation (#rgb) is converted into six-digit form (#rrggbb) by replicating digits, not by adding zeros. For example, #fb0 expands to #ffbb00. This ensures that white (#ffffff) can be specified with the short notation (#fff) and removes any dependencies on the color depth of the image. Use the hexadecimal notation whenever performance is an issue. ImageMagick does not need to load the expansive color table to interpret a hexadecimal color, e.g., <code>#000000</code>, but it does if <code>black</code> is used instead.</p>
95 <p>The format of an sRGB value in the functional notation is 'rgb(<var>r</var>,<var>g</var>,<var>b</var>)', where <var>r</var>, <var>g</var>, and <var>b</var> are either three integer or float values in the range 0?255 or three integer or float percentage values in the range 0?100%. The value 255 corresponds to 100%, and to #F or #FF in the hexadecimal notation: rgb(255, 255, 255) = rgb(100%, 100%, 100%) = #FFF = #FFFFFF. </p>
108 <p>The format of an RGBA value in the functional notation is 'rgba(<var>r</var>,<var>g</var>,<var>b</var>,<var>a</var>)', where <var>r</var>, <var>g</var>, and <var>b</var> are as described above for the RGB functional notation, and where the alpha value <var>a</var> ranges from 0.0 (fully transparent) to 1.0 (fully opaque).</p>
157 <p>Just as the 'rgb()' functional notation has the 'rgba()' alpha counterpart, the 'hsl()' and 'hsb()' functional notations have their 'hsla()' 'hsba()' alpha counterparts. These examples specify the same color:</p>
[all...] |
| /prebuilts/gdb/darwin-x86/lib/python2.7/pydoc_data/ |
| topics.py | 12 'bltin-ellipsis-object': '\nThe Ellipsis Object\n*******************\n\nThis object is used by extended slice notation (see *Slicings*). It\nsupports no special operations. There is exactly one ellipsis object,\nnamed ``Ellipsis`` (a built-in name).\n\nIt is written as ``Ellipsis``. When in a subscript, it can also be\nwritten as ``...``, for example ``seq[...]``.\n',
[all...] |
| /prebuilts/gdb/linux-x86/lib/python2.7/pydoc_data/ |
| topics.py | 12 'bltin-ellipsis-object': '\nThe Ellipsis Object\n*******************\n\nThis object is used by extended slice notation (see *Slicings*). It\nsupports no special operations. There is exactly one ellipsis object,\nnamed ``Ellipsis`` (a built-in name).\n\nIt is written as ``Ellipsis``. When in a subscript, it can also be\nwritten as ``...``, for example ``seq[...]``.\n',
[all...] |
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/pydoc_data/ |
| topics.py | 12 'bltin-ellipsis-object': '\nThe Ellipsis Object\n*******************\n\nThis object is used by extended slice notation (see *Slicings*). It\nsupports no special operations. There is exactly one ellipsis object,\nnamed ``Ellipsis`` (a built-in name).\n\nIt is written as ``Ellipsis``. When in a subscript, it can also be\nwritten as ``...``, for example ``seq[...]``.\n',
[all...] |
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/pydoc_data/ |
| topics.py | 12 'bltin-ellipsis-object': '\nThe Ellipsis Object\n*******************\n\nThis object is used by extended slice notation (see *Slicings*). It\nsupports no special operations. There is exactly one ellipsis object,\nnamed ``Ellipsis`` (a built-in name).\n\nIt is written as ``Ellipsis``. When in a subscript, it can also be\nwritten as ``...``, for example ``seq[...]``.\n',
[all...] |
| /external/bison/lib/ |
| vasnprintf.c | [all...] |
| /external/dbus/doc/ |
| dbus-specification.xml | [all...] |
| /external/apache-xml/src/main/java/org/apache/xml/dtm/ref/ |
| DTMNodeProxy.java | [all...] |
| /external/chromium-trace/catapult/third_party/gsutil/third_party/boto/boto/vpc/ |
| __init__.py | 641 :param cidr_block: The CIDR range to allow or deny, in CIDR notation (for example,
709 :param cidr_block: The CIDR range to allow or deny, in CIDR notation (for example,
[all...] |
| /external/curl/src/ |
| tool_getparam.c | 485 /* addr in dot notation */
489 /* addr in dot notation */
[all...] |
| /external/icu/icu4c/source/test/intltest/ |
| numberformat2test.cpp | [all...] |
| /external/icu/icu4j/ |
| readme.html | 114 Enhancements</b></a> – Scientific Notation, Spelled-out, etc.<br>
626 Format Enhancements</a> – Scientific Notation, Spelled out.</li>
[all...] |
| /external/libexif/libexif/ |
| exif-tag.c | 122 "in ASCII notation. The format is not specified. If the GPS "
[all...] |
| /external/libxml2/result/valid/ |
| xlink.xml | 230 <head>Notation</head>
231 <p>The formal grammar for <termref def="dt-locator">locators</termref> is given using a simple Extended Backus-Naur Form (EBNF) location, as described in <xspecref href="http://www.w3.org/TR/REC-xml#sec-notation">the XML specification</xspecref>.</p>
[all...] |
| /external/libxml2/test/valid/ |
| xlink.xml | 231 <head>Notation</head>
232 <p>The formal grammar for <termref def="dt-locator">locators</termref> is given using a simple Extended Backus-Naur Form (EBNF) location, as described in <xspecref href="http://www.w3.org/TR/REC-xml#sec-notation">the XML specification</xspecref>.</p>
[all...] |
| /external/messageformat/ |
| readme.html | 98 Enhancements</b></a> – Scientific Notation, Spelled-out, etc.<br>
578 Format Enhancements</a> – Scientific Notation, Spelled out.</li>
[all...] |
| /external/opencv3/modules/core/include/opencv2/core/ |
| matx.hpp | 76 M(i,j) notation. Most of the common matrix operations (see also @ref MatrixExpressions ) are
283 In addition to the universal notation like Vec<float, 3>, you can use shorter aliases
[all...] |
| /external/snakeyaml/src/changes/ |
| changes.xml | 180 Fix issue 144: improve type inference for Compact Object Notation (2012-03-16)
267 Fix scientific notation inconsistency in the YAML 1.1 specification:
[all...] |
