From 9bc45799de3114dd7cbae17cae40224391951d47 Mon Sep 17 00:00:00 2001 From: Sylwester Lachiewicz Date: Fri, 7 Aug 2026 11:57:18 +0200 Subject: [PATCH] Drop backslash escapes that Markdown does not need Pages converted from APT with an older doxia-converter carry an escape in front of punctuation that is not markup where it stands: a hyphen or underscore inside a word, a parenthesis, a full stop after a letter. The backslash renders as nothing and only makes the source harder to read and to edit. Only positions where the bare character can never be markup are touched. A full stop after a digit keeps its escape, so an ordered list marker cannot appear by accident, and angle brackets keep theirs, since would otherwise be read as a tag. Code spans, fenced blocks and link destinations are left alone. --- src/site/markdown/examples/filtering-advanced.md.vm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/markdown/examples/filtering-advanced.md.vm b/src/site/markdown/examples/filtering-advanced.md.vm index f812e196..d182ba46 100644 --- a/src/site/markdown/examples/filtering-advanced.md.vm +++ b/src/site/markdown/examples/filtering-advanced.md.vm @@ -53,7 +53,7 @@ jdbc.user=${db.username} jdbc.password=${db.password} ``` -Filtering the content of such a file with this config will produce this content. Note that that the escaped property can now be filtered the usual way later if necessary\! +Filtering the content of such a file with this config will produce this content. Note that that the escaped property can now be filtered the usual way later if necessary! ```properties jdbc.url=jdbc:oracle:thin:@localhost:1521:orcl