summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark H Weaver <mhw@netris.org>2019-06-18 16:08:36 -0400
committerMark H Weaver <mhw@netris.org>2019-06-18 16:08:36 -0400
commit4e5b31cd7a89b92bf19943246cc0d26f4e49c103 (patch)
tree4adc4f1324e8c9342468d3b35189142168d19b57
parentc10b6a3f3455f883f29c4b03ea1e5c1fa498974b (diff)
NEWS: Fix typo.
* NEWS: Fix typo.
-rw-r--r--NEWS16
1 files changed, 8 insertions, 8 deletions
diff --git a/NEWS b/NEWS
index c48ebd99b..8b74d538a 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.