Lines Matching refs:markup

15 markup format defined here to identify pieces of information that should be
16 converted to human-readable form after the fact. As with other markup formats,
18 markup elements will be replaced with expanded text, or converted into active UI
24 information, such as C++ symbol demangling. Instead, logging must include markup
28 This format identifies markup elements with a syntax that is both simple and
31 or end of a markup element should rarely if ever appear incidentally in logging
48 symbolizing filter. Most markup elements must appear entirely on a single line
49 (often with other text before and/or after the markup element). There are some
50 markup elements that are specified to span lines, with line breaks in the middle
52 breaks in arbitrary places inside a markup element, but only inside certain
67 The symbolizer markup scheme relies on contextual information about runtime
68 memory address layout to make it possible to convert markup elements into useful
87 The markup format supports a restricted subset of ANSI X3.64 SGR (Select Graphic
88 Rendition) control sequences. These are unlike other markup elements:
95   substantial changes to generate semantic markup instead.
106 An SGR control sequence is not interpreted inside any other markup element.
107 However, other markup elements may appear between SGR control sequences and the
109 markup element in the filter's output.
129 Common markup element syntax
132 All the markup elements share a common syntactic structure to facilitate simple
143 No markup elements or ANSI SGR control sequences are interpreted inside the
179   recommended that this markup element be used to identify a symbol name so that
320   identifier are outside the scope of the markup format per se. In general it
324   the markup. It indicates that a dump file of some sort has been published.
354 markup may no longer be readily accessible for whatever reason.
433 .. [#not_yet_implemented] This markup element is not yet implemented in