groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 01/01: groff_char.man: Add some words for `\[uXXXX]'.


From: Werner LEMBERG
Subject: [groff] 01/01: groff_char.man: Add some words for `\[uXXXX]'.
Date: Sat, 18 Oct 2014 07:24:50 +0000

wl pushed a commit to branch master
in repository groff.

commit 4834f90f52d90209a4136505ee35c211babd8230
Author: Werner Lemberg <address@hidden>
Date:   Sat Oct 18 09:24:10 2014 +0200

    groff_char.man: Add some words for `\[uXXXX]'.
---
 man/groff_char.man |   12 +++++++++++-
 1 files changed, 11 insertions(+), 1 deletions(-)

diff --git a/man/groff_char.man b/man/groff_char.man
index 7ad00cd..b35049b 100644
--- a/man/groff_char.man
+++ b/man/groff_char.man
@@ -525,9 +525,19 @@ glyph names).
 .
 They are normally mapped onto glyphs using the \f(CW.trin\fP request.
 .
+.
+.P
 Another special convention is the handling of glyphs with names directly
-derived from a Unicode code point; this is discussed below.
+derived from a Unicode code point; this is shown in the 
+\[oq]Unicode\[cq] column of the table below.
+.
+In general, all glyphs not having a name as listed in this manual page can
+be accessed with the \[oq]\f(CW\e[u\fP\,\fIXXXX\/\fP\f(CW]\fP\[cq]
+construct; please go to section \[oq]Using Symbols\[cq] in the groff info
+manual for more details.
 .
+.
+.P
 Moreover, new glyph names can be created by the \f(CW.char\fP request; see
 .BR groff (@MAN7EXT@).
 .



reply via email to

[Prev in Thread] Current Thread [Next in Thread]