From 434843ecccd1bb163432b404a27e86188675c584 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Thu, 9 Jul 2009 03:05:18 +0000 Subject: [PATCH] Use consistent case for "Unicode Standard". Minor rearrangements to improve TeX line-filling. --- doc/lispref/nonascii.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi index ab1d00434d5..870c028a311 100644 --- a/doc/lispref/nonascii.texi +++ b/doc/lispref/nonascii.texi @@ -349,7 +349,7 @@ specifies how the character behaves and how it should be handled during text processing and display. Thus, character properties are an important part of specifying the character's semantics. - Emacs generally follows the Unicode Standard in its implementation + On the whole, Emacs follows the Unicode Standard in its implementation of character properties. In particular, Emacs supports the @uref{http://www.unicode.org/reports/tr23/, Unicode Character Property Model}, and the Emacs character property database is derived from the @@ -535,7 +535,7 @@ is printable, and if it results in @code{nil}, it is not. @cindex coded character set An Emacs @dfn{character set}, or @dfn{charset}, is a set of characters in which each character is assigned a numeric code point. (The -Unicode standard calls this a @dfn{coded character set}.) Each Emacs +Unicode Standard calls this a @dfn{coded character set}.) Each Emacs charset has a name which is a symbol. A single character can belong to any number of different character sets, but it will generally have a different code point in each charset. Examples of character sets -- 2.39.2