aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCharles A. Roelli2019-04-26 21:49:46 +0200
committerCharles A. Roelli2019-04-26 21:49:46 +0200
commit0e8d452c1c166ff65a0325de23bc04b57aea68d8 (patch)
treefc795f6e920f8180a0e445649d5c47b7a6363ff6
parent25a2ff72d09dfedc3803984cd1744c982de1c709 (diff)
downloademacs-0e8d452c1c166ff65a0325de23bc04b57aea68d8.tar.gz
emacs-0e8d452c1c166ff65a0325de23bc04b57aea68d8.zip
; * doc/lispref/nonascii.texi (Coding System Basics): Fix grammar.
-rw-r--r--doc/lispref/nonascii.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi
index d58041b279b..df4f2932c6e 100644
--- a/doc/lispref/nonascii.texi
+++ b/doc/lispref/nonascii.texi
@@ -1049,7 +1049,7 @@ is like @code{undecided}, but it prefers to choose @code{utf-8} when
1049possible. 1049possible.
1050 1050
1051 In general, a coding system doesn't guarantee roundtrip identity: 1051 In general, a coding system doesn't guarantee roundtrip identity:
1052decoding a byte sequence using coding system, then encoding the 1052decoding a byte sequence using a coding system, then encoding the
1053resulting text in the same coding system, can produce a different byte 1053resulting text in the same coding system, can produce a different byte
1054sequence. But some coding systems do guarantee that the byte sequence 1054sequence. But some coding systems do guarantee that the byte sequence
1055will be the same as what you originally decoded. Here are a few 1055will be the same as what you originally decoded. Here are a few