[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[groff] 01/04: groff_char(7): Clarify acceptable Unicode escapes.
From: |
G. Branden Robinson |
Subject: |
[groff] 01/04: groff_char(7): Clarify acceptable Unicode escapes. |
Date: |
Thu, 22 Oct 2020 06:22:25 -0400 (EDT) |
gbranden pushed a commit to branch master
in repository groff.
commit e3bf6b74d60d8e536dd3a17e893312a5c82efd39
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Thu Oct 22 20:52:50 2020 +1100
groff_char(7): Clarify acceptable Unicode escapes.
* man/groff_char.7.man (Description/Special character escape forms):
Clarify discussion of Unicode Normalization Form D and its
applicability to code points acceptable in Unicode numeric special
character escapes. Also document that these escapes must use
uppercase hexadecimal digits.
Attempts once again to slay the unkillable beast that is
<https://savannah.gnu.org/bugs/index.php?57618>.
---
ChangeLog | 11 +++++++++++
man/groff_char.7.man | 18 +++++++++++++++---
2 files changed, 26 insertions(+), 3 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 59ce322..754a795 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,14 @@
+2020-10-22 G. Branden Robinson <g.branden.robinson@gmail.com>
+
+ * man/groff_char.7.man (Description/Special character escape
+ forms): Clarify discussion of Unicode Normalization Form D and
+ its applicability to code points acceptable in Unicode numeric
+ special character escapes. Also document that these escapes
+ must use uppercase hexadecimal digits.
+
+ Attempts once again to slay the unkillable beast that is
+ <https://savannah.gnu.org/bugs/index.php?57618>.
+
2020-10-21 Ingo Schwarze <schwarze@openbsd.org>
On systems without NAME_MAX, use FILENAME_MAX as a last resort.
diff --git a/man/groff_char.7.man b/man/groff_char.7.man
index 9441ee5..801b8dc 100644
--- a/man/groff_char.7.man
+++ b/man/groff_char.7.man
@@ -690,7 +690,8 @@ see
is a Unicode numeric special character escape.
.
With this form,
-any Unicode point can be indicated using four to six hexadecimal digits.
+any Unicode point can be indicated using four to six hexadecimal digits,
+with hexadecimal letters accepted in uppercase form only.
.
Thus,
.B \[rs][u02DA]
@@ -706,6 +707,15 @@ requires NFD
(Normalization Form D),
where all Unicode glyphs are maximally decomposed.
.
+(Exception:
+precomposed characters in the Latin-1 supplement described above are
+also accepted.
+.
+Do not count on this exception remaining in a future
+.I @g@troff
+that accepts UTF-8 input directly.)
+.
+.
Thus,
.I @g@troff
accepts
@@ -713,10 +723,12 @@ accepts
.RB \[lq]caf \[rs][e\~aa] \[rq],
and
.RB \[lq]caf \[rs][u0065_0301] \[rq],
-but not
-.RB \[lq]caf \[rs][u00e9] \[rq],
as ways to input \[lq]caf\['e]\[rq].
.
+(Due to its ISO Latin-1 and IBM code page 1047 compatibility,
+at present it also accepts
+.RB \[lq]caf \[rs][u00E9] \[rq]).
+.
.
.TP
.BI \[rs][u base-glyph\c
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [groff] 01/04: groff_char(7): Clarify acceptable Unicode escapes.,
G. Branden Robinson <=