Adding upstream version 6.7.upstream/6.7

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 30 insertions, 36 deletions

diff --git a/man7/utf-8.7 b/man7/utf-8.7
index 8a5f7ab..077fa42 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -7,7 +7,7 @@
 .\" 2001-05-11  Markus Kuhn <mgk25@cl.cam.ac.uk>
 .\"      Update
 .\"
-.TH UTF-8 7 2023-03-12 "Linux man-pages 6.05.01"
+.TH UTF-8 7 2024-03-14 "Linux man-pages 6.7"
 .SH NAME
 UTF-8 \- an ASCII compatible multibyte Unicode encoding
 .SH DESCRIPTION
@@ -27,14 +27,13 @@ The ISO/IEC 10646 Universal Character Set (UCS),
 a superset of Unicode, occupies an even larger code
 space\[em]31\ bits\[em]and the obvious
 UCS-4 encoding for it (a sequence of 32-bit words) has the same problems.
-.PP
+.P
 The UTF-8 encoding of Unicode and UCS
 does not have these problems and is the common way in which
 Unicode is used on UNIX-style operating systems.
 .SS Properties
 The UTF-8 encoding has the following nice properties:
-.TP 0.2i
-*
+.IP \[bu] 3
 UCS
 characters 0x00000000 to 0x0000007f (the classic US-ASCII
 characters) are encoded simply as bytes 0x00 to 0x7f (ASCII
@@ -43,24 +42,19 @@ This means that files and strings which contain only
 7-bit ASCII characters have the same encoding under both
 ASCII
 and
-UTF-8 .
-.TP
-*
+UTF-8.
+.IP \[bu]
 All UCS characters greater than 0x7f are encoded as a multibyte sequence
 consisting only of bytes in the range 0x80 to 0xfd, so no ASCII
 byte can appear as part of another character and there are no
 problems with, for example,  \[aq]\e0\[aq] or \[aq]/\[aq].
-.TP
-*
+.IP \[bu]
 The lexicographic sorting order of UCS-4 strings is preserved.
-.TP
-*
+.IP \[bu]
 All possible 2\[ha]31 UCS codes can be encoded using UTF-8.
-.TP
-*
+.IP \[bu]
 The bytes 0xc0, 0xc1, 0xfe, and 0xff are never used in the UTF-8 encoding.
-.TP
-*
+.IP \[bu]
 The first byte of a multibyte sequence which represents a single non-ASCII
 UCS character is always in the range 0xc2 to 0xfd and indicates how long
 this multibyte sequence is.
@@ -68,8 +62,7 @@ All further bytes in a multibyte sequence
 are in the range 0x80 to 0xbf.
 This allows easy resynchronization and
 makes the encoding stateless and robust against missing bytes.
-.TP
-*
+.IP \[bu]
 UTF-8 encoded UCS characters may be up to six bytes long, however the
 Unicode standard specifies no characters above 0x10ffff, so Unicode characters
 can be only up to four bytes long in
@@ -77,7 +70,7 @@ UTF-8.
 .SS Encoding
 The following byte sequences are used to represent a character.
 The sequence to be used depends on the UCS code number of the character:
-.TP 0.4i
+.TP
 0x00000000 \- 0x0000007F:
 .RI 0 xxxxxxx
 .TP
@@ -110,14 +103,14 @@ The sequence to be used depends on the UCS code number of the character:
 .RI 10 xxxxxx
 .RI 10 xxxxxx
 .RI 10 xxxxxx
-.PP
+.P
 The
 .I xxx
 bit positions are filled with the bits of the character code number in
 binary representation, most significant bit first (big-endian).
 Only the shortest possible multibyte sequence
 which can represent the code number of the character can be used.
-.PP
+.P
 The UCS code values 0xd800\[en]0xdfff (UTF-16 surrogates) as well as 0xfffe and
 0xffff (UCS noncharacters) should not appear in conforming UTF-8 streams.
 According to RFC 3629 no point above U+10FFFF should be used,
@@ -125,45 +118,46 @@ which limits characters to four bytes.
 .SS Example
 The Unicode character 0xa9 = 1010 1001 (the copyright sign) is encoded
 in UTF-8 as
-.PP
+.P
 .RS
 11000010 10101001 = 0xc2 0xa9
 .RE
-.PP
+.P
 and character 0x2260 = 0010 0010 0110 0000 (the "not equal" symbol) is
 encoded as:
-.PP
+.P
 .RS
 11100010 10001001 10100000 = 0xe2 0x89 0xa0
 .RE
 .SS Application notes
 Users have to select a UTF-8 locale, for example with
-.PP
+.P
 .RS
 export LANG=en_GB.UTF-8
 .RE
-.PP
+.P
 in order to activate the UTF-8 support in applications.
-.PP
+.P
 Application software that has to be aware of the used character
 encoding should always set the locale with for example
-.PP
+.P
 .RS
 setlocale(LC_CTYPE, "")
 .RE
-.PP
+.P
 and programmers can then test the expression
-.PP
+.P
 .RS
 strcmp(nl_langinfo(CODESET), "UTF-8") == 0
 .RE
-.PP
+.P
 to determine whether a UTF-8 locale has been selected and whether
 therefore all plaintext standard input and output, terminal
 communication, plaintext file content, filenames, and environment
 variables are encoded in UTF-8.
-.PP
-Programmers accustomed to single-byte encodings such as US-ASCII or ISO 8859
+.P
+Programmers accustomed to single-byte encodings
+such as US-ASCII or ISO/IEC\~8859
 have to be aware that two assumptions made so far are no longer valid
 in UTF-8 locales.
 Firstly, a single byte does not necessarily correspond any
@@ -178,14 +172,14 @@ Library functions such as
 and
 .BR wcswidth (3)
 should be used today to count characters and cursor positions.
-.PP
-The official ESC sequence to switch from an ISO 2022
+.P
+The official ESC sequence to switch from an ISO/IEC\~2022
 encoding scheme (as used for instance by VT100 terminals) to
 UTF-8 is ESC % G
 ("\ex1b%G").
 The corresponding return sequence from
-UTF-8 to ISO 2022 is ESC % @ ("\ex1b%@").
-Other ISO 2022 sequences (such as
+UTF-8 to ISO/IEC\~2022 is ESC % @ ("\ex1b%@").
+Other ISO/IEC\~2022 sequences (such as
 for switching the G0 and G1 sets) are not applicable in UTF-8 mode.
 .SS Security
 The Unicode and UCS standards require that producers of UTF-8