mention MirOS OPTU-8 (and OPTU-16) encoding some more

This commit is contained in:
tg 2008-08-02 00:57:28 +00:00
parent 024f0e161d
commit 027e9efa85

8
mksh.1
View File

@ -1,4 +1,4 @@
.\" $MirOS: src/bin/mksh/mksh.1,v 1.131 2008/07/09 21:32:43 tg Exp $
.\" $MirOS: src/bin/mksh/mksh.1,v 1.132 2008/08/02 00:57:28 tg Exp $
.\" $OpenBSD: ksh.1,v 1.122 2008/05/17 23:31:52 sobrado Exp $
.\"-
.\" Try to make GNU groff and AT&T nroff more compatible
@ -30,7 +30,7 @@
.el .xD \\$1 \\$2 \\$3 \\$4 \\$5 \\$6 \\$7 \\$8
..
.\"-
.Dd $Mdocdate: July 9 2008 $
.Dd $Mdocdate: August 2 2008 $
.Dt MKSH 1
.Os MirBSD
.Sh NAME
@ -2156,8 +2156,8 @@ transparent) ASCII or Unicode codepoints, depending on the shell's
.Ic utf8\-hack
flag (current setting).
Note that NUL bytes (integral value of zero) cannot be used.
In Unicode mode, raw octets are mapped into the range EF80..EFFF,
which is in the PUA and has been assigned by CSUR for this use.
In Unicode mode, raw octets are mapped into the range EF80..EFFF as in
OPTU-8, which is in the PUA and has been assigned by CSUR for this use.
If more than one octet in ASCII mode, or a sequence of more than one
octet not forming a valid and minimal CESU-8 sequence is passed, the
behaviour is undefined (usually, the shell aborts with a parse error,