From 5a6e790247ca8f0964ee8acd6dc6c564daaf6077 Mon Sep 17 00:00:00 2001
From: Alan Mackenzie <acm@muc.de>
Date: Tue, 9 Jun 2020 16:58:52 +0000
Subject: [PATCH] Orthographical amendments to commit
 145aab0672ae259736ee9230f8e0ff4effa5f4fd

* etc/NEWS: Correct the spelling of CC Mode.

* lisp/progmodes/cc-fonts.el (doxygen-font-lock-doc-comments): Replace curly
  quotes in comments by ASCII ones.
---
 etc/NEWS                   |  2 +-
 lisp/progmodes/cc-fonts.el | 18 +++++++++---------
 2 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/etc/NEWS b/etc/NEWS
index 6e94d4a91ba..b0c523672e8 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -333,7 +333,7 @@ prefix on the Subject line in various languages.
 These new navigation commands are bound to 'n' and 'p' in
 'apropos-mode'.
 
-** CC mode
+** CC Mode
 
 *** Added support for Doxygen documentation style.
 'doxygen' is now a valid 'c-doc-comment-style' which recognises all
diff --git a/lisp/progmodes/cc-fonts.el b/lisp/progmodes/cc-fonts.el
index 9ea08a46244..386cc2f16fe 100644
--- a/lisp/progmodes/cc-fonts.el
+++ b/lisp/progmodes/cc-fonts.el
@@ -3024,18 +3024,18 @@ need for `pike-font-lock-extra-types'.")
   ;; needed to do that efficiently.
   `((,(concat
        ;; Make sure that the special character has not been escaped.  E.g. in
-       ;; ‘\@foo’ only ‘\@’ is a command (similarly for other characters like
-       ;; ‘\\foo’, ‘\<foo’ and ‘\&foo’).  The downside now is that we don’t
+       ;; `\@foo' only `\@' is a command (similarly for other characters like
+       ;; `\\foo', `\<foo' and `\&foo').  The downside now is that we don't
        ;; match command started just after an escaped character, e.g. in
-       ;; ‘\@\foo’ we should match ‘\@’ as well as ‘\foo’ but only the former
+       ;; `\@\foo' we should match `\@' as well as `\foo' but only the former
        ;; is matched.
        "\\(?:^\\|[^\\@]\\)\\("
          ;; Doxygen commands start with backslash or an at sign.  Note that for
-         ;; brevity in the comments only ‘\’ will be mentioned.
+         ;; brevity in the comments only `\' will be mentioned.
          "[\\@]\\(?:"
-           ;; Doxygen commands except those starting with ‘f’
+           ;; Doxygen commands except those starting with `f'
            "[a-eg-z][a-z]*"
-           ;; Doxygen command starting with ‘f’:
+           ;; Doxygen command starting with `f':
            "\\|f\\(?:"
              "[][$}]"                         ; \f$ \f} \f[ \f]
              "\\|{\\(?:[a-zA-Z]+\\*?}{?\\)?"  ; \f{ \f{env} \f{env}{
@@ -3062,8 +3062,8 @@ need for `pike-font-lock-extra-types'.")
     ;; Autolinking. Doxygen auto-links anything that is a class name but we have
     ;; no hope of matching those.  We are, however, able to match functions and
     ;; members using explicit scoped syntax.  For functions, we can also find
-    ;; them by noticing argument-list.  Note that Doxygen accepts ‘::’ as well
-    ;; as ‘#’ as scope operators.
+    ;; them by noticing argument-list.  Note that Doxygen accepts `::' as well
+    ;; as `#' as scope operators.
     (,(let* ((ref "[\\@]ref\\s-+")
              (ref-opt (concat "\\(?:" ref "\\)?"))
              (id "[a-zA-Z_][a-zA-Z_0-9]*")
@@ -3079,7 +3079,7 @@ need for `pike-font-lock-extra-types'.")
          "\\)"))
      1 font-lock-function-name-face prepend nil)
     ;; Match URLs and emails.  This has two purposes.  First of all, Doxygen
-    ;; autolinks URLs.  Second of all, ‘@bar’ in ‘foo@bar.baz’ has been matched
+    ;; autolinks URLs.  Second of all, `@bar' in `foo@bar.baz' has been matched
     ;; above as a command; try and overwrite it.
     (,(let* ((host "[A-Za-z0-9]\\(?:[A-Za-z0-9-]\\{0,61\\}[A-Za-z0-9]\\)")
              (fqdn (concat "\\(?:" host "\\.\\)+" host))
-- 
2.39.5