From 974b8b5068b688258dbe1ffcc37d0ce0f3f4b4c7 Mon Sep 17 00:00:00 2001
From: Shulhan <ms@kilabit.info>
Date: Wed, 18 Feb 2026 11:12:44 +0700
Subject: all: fix parsing inline format with escaped character

If the text inside the inline format contains escaped character, the
parsing failed to find the closed character which cause the format is
not rendered as expected.
---
 testdata/inline_parser/inline_parser_test.txt | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'testdata/inline_parser/inline_parser_test.txt')

diff --git a/testdata/inline_parser/inline_parser_test.txt b/testdata/inline_parser/inline_parser_test.txt
index b40465d..8057970 100644
--- a/testdata/inline_parser/inline_parser_test.txt
+++ b/testdata/inline_parser/inline_parser_test.txt
@@ -1,3 +1,6 @@
+// SPDX-License-Identifier: GPL-3.0-or-later
+// SPDX-FileCopyrightText: 2022 M. Shulhan <ms@kilabit.info>
+
 Various tests for inlineParser.
 
 >>>
@@ -45,6 +48,7 @@ _A _B
 `A` B
 `A `B
 A `/**/` *B*
+`/\*` comment `\*/`
 
 <<< parseFormat
 _A_B
@@ -57,6 +61,7 @@ _A _B
 <code>A</code> B
 `A `B
 A <code>/<strong></strong>/</code> <strong>B</strong>
+<code>/*</code> comment <code>*/</code>
 
 >>> parseFormatUnconstrained
 __A__B
-- 
cgit v1.3