From cb119e3af92672b8d8dc6a649e47b64ff3f318f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gy=C3=B6rgy=20Krajcsovits?= Date: Wed, 18 Mar 2026 10:49:20 +0100 Subject: [PATCH] fix(om2.0) : do we really need escaping for escaping? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In my VS Code preview and in github https://github.com/prometheus/docs/blob/main/docs/specs/om/open_metrics_spec_2_0.md#escaping the text reads just fine without it. Switch to also "View" of the changed file when reviwing this PR. Signed-off-by: György Krajcsovits --- docs/specs/om/open_metrics_spec_2_0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/specs/om/open_metrics_spec_2_0.md b/docs/specs/om/open_metrics_spec_2_0.md index c8a1a769b..d78278e8a 100644 --- a/docs/specs/om/open_metrics_spec_2_0.md +++ b/docs/specs/om/open_metrics_spec_2_0.md @@ -625,9 +625,9 @@ Complete example: #### Escaping -Where the ABNF notes escaping, the following escaping MUST be applied Line feed, `\n` (0x0A) -> literally `\\n` (Bytecode 0x5c 0x6e) Double quotes -> `\\"` (Bytecode 0x5c 0x22) Backslash -> `\\\\` (Bytecode 0x5c 0x5c) +Where the ABNF notes escaping, the following escaping MUST be applied Line feed, `\n` (0x0A) -> literally `\n` (Bytecode 0x5c 0x6e) Double quotes -> `\"` (Bytecode 0x5c 0x22) Backslash -> `\\` (Bytecode 0x5c 0x5c) -A double backslash SHOULD be used to represent a backslash character. A single backslash SHOULD NOT be used for undefined escape sequences. As an example, `\\\\a` is equivalent and preferable to `\\a`. +A double backslash SHOULD be used to represent a backslash character. A single backslash SHOULD NOT be used for undefined escape sequences. As an example, `\\a` is equivalent and preferable to `\a`. Escaping MUST also be applied to quoted UTF-8 strings.