man*/: Fix ISO -> ISO/IEC where appropriate

Link: <https://www.iso.org>
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

5 files changed, 13 insertions, 13 deletions

diff --git a/man1/localedef.1 b/man1/localedef.1
index b41d040f7..cab34f0c6 100644
--- a/man1/localedef.1
+++ b/man1/localedef.1
@@ -8,7 +8,7 @@
 .\" This manual page was initially written by Richard Braakman
 .\" on behalf of the Debian GNU/Linux Project and anyone else
 .\" who wants it. It was amended by Alastair McKinstry to
-.\" explain new ISO 14652 elements, and amended further by
+.\" explain new ISO/IEC 14652 elements, and amended further by
 .\" Lars Wirzenius to document new functionality (as of GNU
 .\" C library 2.3.5).
 .\"
diff --git a/man3/wprintf.3 b/man3/wprintf.3
index 38feff7f1..a496e76c4 100644
--- a/man3/wprintf.3
+++ b/man3/wprintf.3
@@ -250,7 +250,7 @@ This is because the
 .I wchar_t
 representation is platform- and locale-dependent.
 (The glibc represents
-wide characters using their Unicode (ISO-10646) code point, but other
+wide characters using their Unicode (ISO/IEC 10646) code point, but other
 platforms don't do this.
 Also, the use of C99 universal character names
 of the form \eunnnn does not solve this problem.)
diff --git a/man7/charsets.7 b/man7/charsets.7
index 7db4e73c9..7ef5f0a95 100644
--- a/man7/charsets.7
+++ b/man7/charsets.7
@@ -260,7 +260,7 @@ of ASCII.
 In the same fashion as the ISO 8859 series, Thai characters are mapped into
 0xa1\[en]0xfe.
 .SS Unicode
-Unicode (ISO 10646) is a standard which aims to unambiguously represent
+Unicode (ISO/IEC 10646) is a standard which aims to unambiguously represent
 every character in every human language.
 Unicode's structure permits 20.1 bits to encode every character.
 Since most computers don't include 20.1-bit integers, Unicode is
@@ -288,7 +288,7 @@ is assembled into 00000xxx xxyyyyyy.
 A byte 1110xxxx is the start
 of a 3-byte code, and 1110xxxx 10yyyyyy 10zzzzzz is assembled
 into xxxxyyyy yyzzzzzz.
-(When UTF-8 is used to code the 31-bit ISO 10646
+(When UTF-8 is used to code the 31-bit ISO/IEC 10646
 then this progression continues up to 6-byte codes.)
 .PP
 For most texts in ISO 8859 character sets, this means that the
diff --git a/man7/unicode.7 b/man7/unicode.7
index 5a358d5bb..457ef62ee 100644
--- a/man7/unicode.7
+++ b/man7/unicode.7
@@ -11,7 +11,7 @@
 .SH NAME
 unicode \- universal character set
 .SH DESCRIPTION
-The international standard ISO 10646 defines the
+The international standard ISO/IEC 10646 defines the
 Universal Character Set (UCS).
 UCS contains all characters of all other character set standards.
 It also guarantees "round-trip compatibility";
@@ -41,7 +41,7 @@ including those provided by TeX, Postscript, APL, MS-DOS, MS-Windows,
 Macintosh, OCR fonts, as well as many word processing and publishing
 systems, and more are being added.
 .PP
-The UCS standard (ISO 10646) describes a
+The UCS standard (ISO/IEC 10646) describes a
 31-bit character set architecture
 consisting of 128 24-bit
 .IR groups ,
@@ -52,12 +52,12 @@ made up of 256 8-bit
 with 256
 .I column
 positions, one for each character.
-Part 1 of the standard (ISO 10646-1)
+Part 1 of the standard (ISO/IEC 10646-1)
 defines the first 65534 code positions (0x0000 to 0xfffd), which form
 the
 .I Basic Multilingual Plane
 (BMP), that is plane 0 in group 0.
-Part 2 of the standard (ISO 10646-2)
+Part 2 of the standard (ISO/IEC 10646-2)
 adds characters to group 0 outside the BMP in several
 .I "supplementary planes"
 in the range 0x10000 to 0x10ffff.
@@ -68,7 +68,7 @@ foreseeable future.
 The BMP contains all characters found in the
 commonly used other character sets.
 The supplemental planes added by
-ISO 10646-2 cover only more exotic characters for special scientific,
+ISO/IEC 10646-2 cover only more exotic characters for special scientific,
 dictionary printing, publishing industry, higher-level protocol and
 enthusiast needs.
 .PP
@@ -107,7 +107,7 @@ script or for mathematical typesetting and users of the International
 Phonetic Alphabet.
 .SS Implementation levels
 As not all systems are expected to support advanced mechanisms like
-combining characters, ISO 10646-1 specifies the following three
+combining characters, ISO/IEC 10646-1 specifies the following three
 .I implementation levels
 of UCS:
 .TP 0.9i
@@ -128,8 +128,8 @@ All UCS characters are supported.
 The Unicode 3.0 Standard
 published by the Unicode Consortium
 contains exactly the UCS Basic Multilingual Plane
-at implementation level 3, as described in ISO 10646-1:2000.
-Unicode 3.1 added the supplemental planes of ISO 10646-2.
+at implementation level 3, as described in ISO/IEC 10646-1:2000.
+Unicode 3.1 added the supplemental planes of ISO/IEC 10646-2.
 The Unicode standard and
 technical reports published by the Unicode Consortium provide much
 additional information on the semantics and recommended usages of
diff --git a/man7/utf-8.7 b/man7/utf-8.7
index 5ff634306..015d4b746 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -23,7 +23,7 @@ read 16-bit words as characters without major modifications.
 For these reasons,
 UCS-2 is not a suitable external encoding of Unicode
 in filenames, text files, environment variables, and so on.
-The ISO 10646 Universal Character Set (UCS),
+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.