| /aosp_15_r20/external/cldr/docs/ldml/ |
| H A D | tr35-messageFormat.md | 6 |-------|------------------------|
13 …odel, syntax, processing, and conformance requirements for the next generation of dynamic messages.
19 <!-- _This is a draft document which may be updated, replaced, or superseded by other documents at …
21 …a stable document; it is inappropriate to cite this document as other than a work in progress._ -->
35 * Part 2: [General](tr35-general.md#Contents) (display names & transforms, etc.)
36 * Part 3: [Numbers](tr35-numbers.md#Contents) (number & currency formatting)
37 * Part 4: [Dates](tr35-dates.md#Contents) (date, time, time zone formatting)
38 * Part 5: [Collation](tr35-collation.md#Contents) (sorting, searching, grouping)
39 * Part 6: [Supplemental](tr35-info.md#Contents) (supplemental data)
40 * Part 7: [Keyboards](tr35-keyboards.md#Contents) (keyboard mappings)
[all …]
|
| /aosp_15_r20/external/python/cpython3/Doc/howto/ |
| D | logging-cookbook.rst | 1 .. _logging-cookbook:
7 :Author: Vinay Sajip <vinay_sajip at red-dove dot com>
11 :ref:`cookbook-ref-links`.
16 ---------------------------------
32 # create file handler which logs even debug messages
37 ch.setLevel(logging.ERROR)
39 formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
78 .. code-block:: none
80 2005-03-23 23:47:11,663 - spam_application - INFO -
82 2005-03-23 23:47:11,665 - spam_application.auxiliary.Auxiliary - INFO -
[all …]
|
| D | logging.rst | 5 :Author: Vinay Sajip <vinay_sajip at red-dove dot com>
7 .. _logging-basic-tutorial:
12 ----------------------
26 are :func:`debug`, :func:`info`, :func:`warning`, :func:`error` and
30 +-------------------------------------+--------------------------------------+
36 +-------------------------------------+--------------------------------------+
41 +-------------------------------------+--------------------------------------+
51 +-------------------------------------+--------------------------------------+
52 | Report an error regarding a | Raise an exception |
54 +-------------------------------------+--------------------------------------+
[all …]
|
| /aosp_15_r20/external/pigweed/pw_tokenizer/ |
| H A D | detokenization.rst | 3 .. _module-pw_tokenizer-detokenization:
8 .. pigweed-module-subpage::
15 --------------------------------
17 --------------------------------
18 A project might tokenize its log messages with the
19 :ref:`module-pw_tokenizer-base64-format`. Consider the following log file, which
22 .. code-block:: text
32 .. code-block::
41 .. code-block:: text
51 This example uses the :ref:`module-pw_tokenizer-base64-format`, which
[all …]
|
| /aosp_15_r20/external/python/cpython3/Doc/library/ |
| D | logging.rst | 1 :mod:`logging` --- Logging facility for Python
7 .. moduleauthor:: Vinay Sajip <vinay_sajip@red-dove.com>
8 .. sectionauthor:: Vinay Sajip <vinay_sajip@red-dove.com>
19 * :ref:`Basic Tutorial <logging-basic-tutorial>`
20 * :ref:`Advanced Tutorial <logging-advanced-tutorial>`
21 * :ref:`Logging Cookbook <logging-cookbook>`
23 --------------
30 can include your own messages integrated with messages from third-party
35 .. code-block:: none
59 --------------
[all …]
|
| /aosp_15_r20/external/python/cpython2/Doc/library/ |
| D | logging.rst | 1 :mod:`logging` --- Logging facility for Python
8 .. moduleauthor:: Vinay Sajip <vinay_sajip@red-dove.com>
9 .. sectionauthor:: Vinay Sajip <vinay_sajip@red-dove.com>
19 * :ref:`Basic Tutorial <logging-basic-tutorial>`
20 * :ref:`Advanced Tutorial <logging-advanced-tutorial>`
21 * :ref:`Logging Cookbook <logging-cookbook>`
25 --------------
34 can include your own messages integrated with messages from third-party
55 --------------
58 instantiated directly, but always through the module-level function
[all …]
|
| /aosp_15_r20/external/python/cpython2/Doc/howto/ |
| D | logging.rst | 5 :Author: Vinay Sajip <vinay_sajip at red-dove dot com>
7 .. _logging-basic-tutorial:
12 ----------------------
26 are :func:`debug`, :func:`info`, :func:`warning`, :func:`error` and
30 +-------------------------------------+--------------------------------------+
36 +-------------------------------------+--------------------------------------+
41 +-------------------------------------+--------------------------------------+
51 +-------------------------------------+--------------------------------------+
52 | Report an error regarding a | Raise an exception |
54 +-------------------------------------+--------------------------------------+
[all …]
|
| /aosp_15_r20/external/rust/android-crates-io/crates/tokio-test/src/ |
| D | macros.rs | 8 /// # Custom Messages
11 /// arguments for formatting.
47 /// # Custom Messages
50 /// arguments for formatting.
75 /// Asserts a `Poll<Result<...>>` is ready and `Err`, returning the error.
80 /// # Custom Messages
83 /// arguments for formatting.
113 /// # Custom Messages
116 /// arguments for formatting.
152 /// # Custom Messages
[all …]
|
| /aosp_15_r20/external/pigweed/pw_presubmit/py/pw_presubmit/format/ |
| H A D | core.py | 7 # https://www.apache.org/licenses/LICENSE-2.0
14 """Formatting library core."""
29 def _ensure_newline(orig: str) -> str:
37 def simple_diff(path: Path, original: str, formatted: str) -> str:
69 This type is returned by in-memory formatting check operations.
72 ok: A boolean indicating whether or not formatting was successful.
76 the formatting process.
89 ok: A boolean indicating whether or not formatting was successful.
90 diff: The resulting diff of applying code formatting, as a
91 human-readable string.
[all …]
|
| /aosp_15_r20/external/icu/libicu/cts_headers/unicode/ |
| H A D | plurfmt.h | 5 * Copyright (C) 2007-2014, International Business Machines Corporation and
40 * messages with plural inflection. It is based on <i>plural
41 * selection</i>, i.e. the caller specifies messages for each
46 * <h4>The Problem of Plural Forms in Internationalized Messages</h4>
49 * plurals. Creating internationalized messages that include plural
70 * use the predefined keywords. The whole plural formatting of messages can
73 …* https://unicode-org.github.io/cldr-staging/charts/latest/supplemental/language_plural_rules.…
77 * <p>Note: Typically, plural formatting is done via <code>MessageFormat</code>
79 * rather than using a stand-alone <code>PluralFormat</code>.
103 * between the {curly braces} and their sub-message,
[all …]
|
| H A D | msgfmt.h | 4 * Copyright (C) 2007-2013, International Business Machines Corporation and
28 * \brief C++ API: Formats messages in a language-neutral way.
65 * itself doesn't implement locale-specific behavior. Any locale-specific
69 * <p>Arguments can be named (using identifiers) or numbered (using small ASCII-digit integers).
80 * <p>An argument might have a "complex" type with nested MessageFormat sub-patterns.
81 * During formatting, one of these sub-messages is selected according to the argument value
85 * a top-level argument, overriding the default formatting and parsing behavior
87 * However, custom formatting can be achieved more simply by writing
91 * <p>When formatting, MessageFormat takes a collection of argument values
102 * as an ASCII-decimal-digit string (without leading zero).
[all …]
|
| /aosp_15_r20/external/cronet/third_party/icu/source/i18n/unicode/ |
| H A D | plurfmt.h | 5 * Copyright (C) 2007-2014, International Business Machines Corporation and
40 * messages with plural inflection. It is based on <i>plural
41 * selection</i>, i.e. the caller specifies messages for each
46 * <h4>The Problem of Plural Forms in Internationalized Messages</h4>
49 * plurals. Creating internationalized messages that include plural
70 * use the predefined keywords. The whole plural formatting of messages can
73 …* https://unicode-org.github.io/cldr-staging/charts/latest/supplemental/language_plural_rules.…
77 * <p>Note: Typically, plural formatting is done via <code>MessageFormat</code>
79 * rather than using a stand-alone <code>PluralFormat</code>.
103 * between the {curly braces} and their sub-message,
[all …]
|
| H A D | msgfmt.h | 4 * Copyright (C) 2007-2013, International Business Machines Corporation and
28 * \brief C++ API: Formats messages in a language-neutral way.
65 * itself doesn't implement locale-specific behavior. Any locale-specific
69 * <p>Arguments can be named (using identifiers) or numbered (using small ASCII-digit integers).
80 * <p>An argument might have a "complex" type with nested MessageFormat sub-patterns.
81 * During formatting, one of these sub-messages is selected according to the argument value
85 * a top-level argument, overriding the default formatting and parsing behavior
87 * However, custom formatting can be achieved more simply by writing
91 * <p>When formatting, MessageFormat takes a collection of argument values
102 * as an ASCII-decimal-digit string (without leading zero).
[all …]
|
| /aosp_15_r20/external/icu/icu4c/source/i18n/unicode/ |
| H A D | plurfmt.h | 5 * Copyright (C) 2007-2014, International Business Machines Corporation and
40 * messages with plural inflection. It is based on <i>plural
41 * selection</i>, i.e. the caller specifies messages for each
46 * <h4>The Problem of Plural Forms in Internationalized Messages</h4>
49 * plurals. Creating internationalized messages that include plural
70 * use the predefined keywords. The whole plural formatting of messages can
73 …* https://unicode-org.github.io/cldr-staging/charts/latest/supplemental/language_plural_rules.…
77 * <p>Note: Typically, plural formatting is done via <code>MessageFormat</code>
79 * rather than using a stand-alone <code>PluralFormat</code>.
103 * between the {curly braces} and their sub-message,
[all …]
|
| H A D | msgfmt.h | 4 * Copyright (C) 2007-2013, International Business Machines Corporation and
28 * \brief C++ API: Formats messages in a language-neutral way.
65 * itself doesn't implement locale-specific behavior. Any locale-specific
69 * <p>Arguments can be named (using identifiers) or numbered (using small ASCII-digit integers).
80 * <p>An argument might have a "complex" type with nested MessageFormat sub-patterns.
81 * During formatting, one of these sub-messages is selected according to the argument value
85 * a top-level argument, overriding the default formatting and parsing behavior
87 * However, custom formatting can be achieved more simply by writing
91 * <p>When formatting, MessageFormat takes a collection of argument values
102 * as an ASCII-decimal-digit string (without leading zero).
[all …]
|
| /aosp_15_r20/prebuilts/runtime/mainline/i18n/test-exports/common_os/include/external/icu/icu4c/source/i18n/unicode/ |
| H A D | plurfmt.h | 5 * Copyright (C) 2007-2014, International Business Machines Corporation and
40 * messages with plural inflection. It is based on <i>plural
41 * selection</i>, i.e. the caller specifies messages for each
46 * <h4>The Problem of Plural Forms in Internationalized Messages</h4>
49 * plurals. Creating internationalized messages that include plural
70 * use the predefined keywords. The whole plural formatting of messages can
73 * http://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/language_plural_rules.html
77 * <p>Note: Typically, plural formatting is done via <code>MessageFormat</code>
79 * rather than using a stand-alone <code>PluralFormat</code>.
103 * between the {curly braces} and their sub-message,
[all …]
|
| H A D | msgfmt.h | 4 * Copyright (C) 2007-2013, International Business Machines Corporation and
28 * \brief C++ API: Formats messages in a language-neutral way.
65 * itself doesn't implement locale-specific behavior. Any locale-specific
69 * <p>Arguments can be named (using identifiers) or numbered (using small ASCII-digit integers).
80 * <p>An argument might have a "complex" type with nested MessageFormat sub-patterns.
81 * During formatting, one of these sub-messages is selected according to the argument value
85 * a top-level argument, overriding the default formatting and parsing behavior
87 * However, custom formatting can be achieved more simply by writing
91 * <p>When formatting, MessageFormat takes a collection of argument values
102 * as an ASCII-decimal-digit string (without leading zero).
[all …]
|
| /aosp_15_r20/prebuilts/rust/linux-x86/1.80.1/lib/rustlib/src/rust/library/std/src/ |
| H A D | macros.rs | 6 // ignore-tidy-dbg
18 /* compiler built-in */
27 /// Note that stdout is frequently line-buffered by default so it may be
42 /// [`eprint!`] instead to print error and progress messages.
44 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
56 /// Writing to non-blocking stdout can cause an error, which will lead
107 /// [`eprintln!`] instead to print error and progress messages.
109 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
120 /// Writing to non-blocking stdout can cause an error, which will lead
147 /// Prints to the standard error.
[all …]
|
| /aosp_15_r20/prebuilts/rust/linux-musl-x86/1.80.1/lib/rustlib/src/rust/library/std/src/ |
| H A D | macros.rs | 6 // ignore-tidy-dbg
18 /* compiler built-in */
27 /// Note that stdout is frequently line-buffered by default so it may be
42 /// [`eprint!`] instead to print error and progress messages.
44 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
56 /// Writing to non-blocking stdout can cause an error, which will lead
107 /// [`eprintln!`] instead to print error and progress messages.
109 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
120 /// Writing to non-blocking stdout can cause an error, which will lead
147 /// Prints to the standard error.
[all …]
|
| /aosp_15_r20/external/vulkan-validation-layers/ |
| H A D | CONTRIBUTING.md | 5 The source code for The Vulkan-ValidationLayer components is sponsored by Khronos and LunarG.
6 * [Khronos Vulkan-ValidationLayers](https://github.com/KhronosGroup/Vulkan-ValidationLayers)
17 * Examine the [issues list](https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues)
19 * Alternatively, run the `vk_validation_stats.py` script (in the scripts directory) with the `-todo`
20 command line argument to see a list of as-yet unimplemented validation checks.
28 Please see the [section about Validation Layers](#special-considerations-for-validation-layers)
47 This will involve [forking the repository](https://help.github.com/articles/fork-a-repo/),
48 …mmits, and then [submitting a pull request](https://help.github.com/articles/using-pull-requests/).
49 * Please read and adhere to the style and process [guidelines ](#coding-conventions-and-formatting)…
56 #### **Coding Conventions and Formatting**
[all …]
|
| /aosp_15_r20/prebuilts/rust/linux-musl-x86/1.81.0/lib/rustlib/src/rust/library/std/src/ |
| H A D | macros.rs | 6 // ignore-tidy-dbg
18 /* compiler built-in */
27 /// Note that stdout is frequently line-buffered by default so it may be
42 /// [`eprint!`] instead to print error and progress messages.
44 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
56 /// Writing to non-blocking stdout can cause an error, which will lead
107 /// [`eprintln!`] instead to print error and progress messages.
109 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
120 /// Writing to non-blocking stdout can cause an error, which will lead
147 /// Prints to the standard error.
[all …]
|
| /aosp_15_r20/prebuilts/rust/linux-x86/1.81.0/lib/rustlib/src/rust/library/std/src/ |
| H A D | macros.rs | 6 // ignore-tidy-dbg
18 /* compiler built-in */
27 /// Note that stdout is frequently line-buffered by default so it may be
42 /// [`eprint!`] instead to print error and progress messages.
44 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
56 /// Writing to non-blocking stdout can cause an error, which will lead
107 /// [`eprintln!`] instead to print error and progress messages.
109 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
120 /// Writing to non-blocking stdout can cause an error, which will lead
147 /// Prints to the standard error.
[all …]
|
| /aosp_15_r20/prebuilts/rust/linux-x86/1.81.0.u1/lib/rustlib/src/rust/library/std/src/ |
| H A D | macros.rs | 6 // ignore-tidy-dbg
18 /* compiler built-in */
27 /// Note that stdout is frequently line-buffered by default so it may be
42 /// [`eprint!`] instead to print error and progress messages.
44 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
56 /// Writing to non-blocking stdout can cause an error, which will lead
107 /// [`eprintln!`] instead to print error and progress messages.
109 /// See [the formatting documentation in `std::fmt`](../std/fmt/index.html)
120 /// Writing to non-blocking stdout can cause an error, which will lead
147 /// Prints to the standard error.
[all …]
|
| /aosp_15_r20/external/googleapis/google/apps/card/v1/ |
| H A D | card.proto | 7 // http://www.apache.org/licenses/LICENSE-2.0
30 // Add-on.
42 // dialog](https://developers.google.com/workspace/chat/design-components-card-dialog).
43 // * For Google Workspace Add-ons, see [Card-based
44 // interfaces](https://developers.google.com/apps-script/add-ons/concepts/cards).
57 // "cardId": "unique-card-id",
63 // "https://developers.google.com/workspace/chat/images/quickstart-app-avatar.png",
94 // "text": "+1 (555) 555-1234"
135 …// header](https://developers.google.com/workspace/chat/design-components-card-dialog#add_a_header…
137 // [Google Workspace Add-ons and Chat
[all …]
|
| /aosp_15_r20/external/googleapis/google/chat/v1/ |
| H A D | message.proto | 7 // http://www.apache.org/licenses/LICENSE-2.0
47 pattern: "spaces/{space}/messages/{message}"
52 // Format: `spaces/{space}/messages/{message}`
56 // `{message}` is a system-assigned ID for the message. For example,
57 // `spaces/AAAAAAAAAAA/messages/BBBBBBBBBBB.BBBBBBBBBBB`.
62 // `spaces/AAAAAAAAAAA/messages/client-custom-name`. For details, see [Name
64 // message](https://developers.google.com/workspace/chat/create-messages#name_a_created_message).
69 // user](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user),
97 // Plain-text body of the message. The first link to an image, video, or web
99 // [preview chip](https://developers.google.com/workspace/chat/preview-links).
[all …]
|