From 4051ca4c1c6b3fe1989bc59d0c584464e8f8d84b Mon Sep 17 00:00:00 2001 From: Ingo Schwarze Date: Sun, 5 Jun 2022 13:54:09 +0000 Subject: With the improved escape sequence parser, it becomes easy to also improve diagnostics. Distinguish "incomplete escape sequence", "invalid special character", and "unknown special character" from the generic "invalid escape sequence", also promoting them from WARNING to ERROR because incomplete escape sequences are severe syntax violations and because encountering an invalid or unknown special character makes it likely that part of the document content intended by the authors gets lost. --- regress/char/accent/nocombine.out_lint | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'regress/char/accent') diff --git a/regress/char/accent/nocombine.out_lint b/regress/char/accent/nocombine.out_lint index c9de4162..0f7be4d0 100644 --- a/regress/char/accent/nocombine.out_lint +++ b/regress/char/accent/nocombine.out_lint @@ -1,2 +1,2 @@ -mandoc: nocombine.in:8:27: WARNING: invalid escape sequence: \['] -mandoc: nocombine.in:14:27: WARNING: invalid escape sequence: \[`] +mandoc: nocombine.in:8:27: ERROR: invalid special character: \['] +mandoc: nocombine.in:14:27: ERROR: invalid special character: \[`] -- cgit