[Guile-commits] 01/01: NEWS: Fix typo.

[Mark H. Weaver]

mhw pushed a commit to branch stable-2.2
in repository guile.

commit 4e5b31cd7a89b92bf19943246cc0d26f4e49c103
Author: Mark H Weaver <address@hidden>
Date:   Tue Jun 18 16:08:36 2019 -0400

    NEWS: Fix typo.
    
    * NEWS: Fix typo.
---
 NEWS | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/NEWS b/NEWS
index c48ebd9..8b74d53 100644
--- a/NEWS
+++ b/NEWS
@@ -57,14 +57,14 @@ when using parallel builds.
 ** put-u8 now always writes a single byte, regardless of the port encoding.
 
 Previously, (put-u8 PORT OCTET) worked as expected only when writing to
-binary ports, i.e. those with port encoding "ISO-8851-1".  Strictly
-speaking, this meets the requirements of the R6RS 'put-u8', which need
-only support binary ports.  However, Guile in fact allows binary I/O to
-be performed on any port, and yet 'put-u8' behaved in a surprising way
-with other port encodings: it would perform a _textual_ I/O operation,
-writing the character with Unicode scalar value OCTET.  Now, 'put-u8'
-always writes a single byte with value OCTET, regardless of the port
-encoding.
+binary ports, i.e. those with port encoding "ISO-8859-1" a.k.a. Latin-1.
+Strictly speaking, this meets the requirements of the R6RS 'put-u8',
+which need only support binary ports.  However, Guile in fact allows
+binary I/O to be performed on any port, and yet 'put-u8' behaved in a
+surprising way with other port encodings: it would perform a _textual_
+I/O operation, writing the character with Unicode scalar value OCTET.
+Now, 'put-u8' always writes a single byte with value OCTET, regardless
+of the port encoding.
 
 ** Optimize fixnum exact integer square roots.