summaryrefslogtreecommitdiffstats
path: root/Doc/howto/unicode.rst
diff options
context:
space:
mode:
authorSerhiy Storchaka <storchaka@gmail.com>2013-02-16 15:29:56 (GMT)
committerSerhiy Storchaka <storchaka@gmail.com>2013-02-16 15:29:56 (GMT)
commitf8def28ff03f3167bd0becabab4dc5d70ee22033 (patch)
tree5424070e12f33782e463043030531641866bbf2c /Doc/howto/unicode.rst
parenta0eb80999538febe046164bae541d3f07b899dfb (diff)
downloadcpython-f8def28ff03f3167bd0becabab4dc5d70ee22033.zip
cpython-f8def28ff03f3167bd0becabab4dc5d70ee22033.tar.gz
cpython-f8def28ff03f3167bd0becabab4dc5d70ee22033.tar.bz2
Issue #17193: Use binary prefixes (KiB, MiB, GiB) for memory units.
Diffstat (limited to 'Doc/howto/unicode.rst')
-rw-r--r--Doc/howto/unicode.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/howto/unicode.rst b/Doc/howto/unicode.rst
index 7500dce..3dafc8c 100644
--- a/Doc/howto/unicode.rst
+++ b/Doc/howto/unicode.rst
@@ -456,11 +456,11 @@ with ``bytes.decode(encoding)``. However, the manual approach is not recommende
One problem is the multi-byte nature of encodings; one Unicode character can be
represented by several bytes. If you want to read the file in arbitrary-sized
-chunks (say, 1k or 4k), you need to write error-handling code to catch the case
+chunks (say, 1024 or 4096 bytes), you need to write error-handling code to catch the case
where only part of the bytes encoding a single Unicode character are read at the
end of a chunk. One solution would be to read the entire file into memory and
then perform the decoding, but that prevents you from working with files that
-are extremely large; if you need to read a 2GB file, you need 2GB of RAM.
+are extremely large; if you need to read a 2 GiB file, you need 2 GiB of RAM.
(More, really, since for at least a moment you'd need to have both the encoded
string and its Unicode version in memory.)