(maven-ear-plugin) branch master updated: Drop backslash escapes that Markdown does not need

[sl...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-ear-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new 5793a1d  Drop backslash escapes that Markdown does not need
5793a1d is described below

commit 5793a1d8bb58bd7b4444883d8de526a479bc5272
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Fri Aug 7 11:57:18 2026 +0200

    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 <escapeString> 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 4b2fc69..6228d6b 100644
--- a/src/site/markdown/examples/filtering-advanced.md.vm
+++ b/src/site/markdown/examples/filtering-advanced.md.vm
@@ -61,7 +61,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