Fix round tripping of read->print for symbols with strange quotes

Since 2017-07-22 "Signal error for symbol names with strange
quotes (Bug#2967)", symbol names beginning with certain quote
characters require an escaping backslash.  However, the corresponding
change for printing missed, so that (eq (read (prin1-to-string SYM))
SYM) does not give `t' for such symbols.
* src/character.c (confusable_symbol_character_p): New function,
extracted from test `read1'.
* src/lread.c (read1): Use it.
* src/print.c (print_object): Use it to print a backslash for symbols
starting with characters that `read1' requires to be escaped.
* test/src/print-tests.el (print-read-roundtrip): New test.
* etc/NEWS.26:
* etc/NEWS: Clarify the announcement for the earlier reader
change (Bug#30217).

2 files changed, 9 insertions, 5 deletions

diff --git a/etc/NEWS b/etc/NEWS
index 2888acd4dcb..80ddf10488c 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -229,6 +229,15 @@ as new-style, bind the new variable 'force-new-style-backquotes' to t.
 ** 'print-quoted' now defaults to t, so if you want to see
 (quote x) instead of 'x you will have to bind it to nil where applicable.
 
+** To avoid confusion caused by "smart quotes", the reader signals an
+error when reading Lisp symbols which begin with one of the following
+quotation characters: ‘’‛“”‟〞＂＇.  A symbol beginning with such a
+character can be written by escaping the quotation character with a
+backslash.  For example:
+
+    (read "‘smart") => (invalid-read-syntax "strange quote" "‘")
+    (read "\\‘smart") == (intern "‘smart")
+
 ** Internal parsing commands now use syntax-ppss and disregard
 open-paren-in-column-0-is-defun-start.  This affects mostly things like
 forward-comment, scan-sexps, and forward-sexp when parsing backward.
diff --git a/etc/NEWS.26 b/etc/NEWS.26
index 46762d65e18..76e6316ca2e 100644
--- a/etc/NEWS.26
+++ b/etc/NEWS.26
@@ -1377,11 +1377,6 @@ second argument instead of its first.
 renamed to 'lread--old-style-backquotes'.  No user code should use
 this variable.
 
----
-** To avoid confusion caused by "smart quotes", the reader no longer
-accepts Lisp symbols which begin with the following quotation
-characters: ‘’‛“”‟〞＂＇, unless they are escaped with backslash.
-
 +++
 ** 'default-file-name-coding-system' now defaults to a coding system
 that does not process CRLF.  For example, it defaults to 'utf-8-unix'