Hi,
I think it's safe to drop this forward-looking statement from the utf-8(7) page now.
>From 1d43dd645ac03eeb7815d641ca041e966d7bd333 Mon Sep 17 00:00:00 2001
From: Marko Myllynen <myllynen@xxxxxxxxxx>
Date: Mon, 9 Jun 2014 16:35:09 +0300
Subject: [PATCH] utf-8.7: Drop an old comment about UTF-8 replacing ISO 8859
---
man7/utf-8.7 | 10 +---------
1 files changed, 1 insertions(+), 9 deletions(-)
diff --git a/man7/utf-8.7 b/man7/utf-8.7
index bdf5468..65cabba 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -258,15 +258,6 @@ The corresponding return sequence from
to ISO 2022 is ESC % @ ("\\x1b%@").
Other ISO 2022 sequences (such as
for switching the G0 and G1 sets) are not applicable in UTF-8 mode.
-.PP
-It can be hoped that in the foreseeable future,
-.B UTF-8
-will replace
-.B ASCII
-and
-.B ISO 8859
-at all levels as the common character encoding on POSIX systems,
-leading to a significantly richer environment for handling plain text.
.SS Security
The
.BR Unicode " and " UCS
@@ -291,6 +282,7 @@ ISO/IEC 10646-1:2000, Unicode 3.1, RFC\ 3629, Plan 9.
.\" .SH AUTHOR
.\" Markus Kuhn <mgk25@xxxxxxxxxxxx>
.SH SEE ALSO
+.BR locale (1),
.BR nl_langinfo (3),
.BR setlocale (3),
.BR charsets (7),
--
1.7.1
Thanks,
--
Marko Myllynen
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
