diff options
author | Charles A. Roelli <charles@aurox.ch> | 2019-04-26 21:49:46 +0200 |
---|---|---|
committer | Charles A. Roelli <charles@aurox.ch> | 2019-04-26 21:49:46 +0200 |
commit | 0e8d452c1c166ff65a0325de23bc04b57aea68d8 (patch) | |
tree | fc795f6e920f8180a0e445649d5c47b7a6363ff6 /doc/lispref/nonascii.texi | |
parent | 25a2ff72d09dfedc3803984cd1744c982de1c709 (diff) | |
download | emacs-0e8d452c1c166ff65a0325de23bc04b57aea68d8.tar.gz emacs-0e8d452c1c166ff65a0325de23bc04b57aea68d8.tar.bz2 emacs-0e8d452c1c166ff65a0325de23bc04b57aea68d8.zip |
; * doc/lispref/nonascii.texi (Coding System Basics): Fix grammar.
Diffstat (limited to 'doc/lispref/nonascii.texi')
-rw-r--r-- | doc/lispref/nonascii.texi | 2 |
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 possible. In general, a coding system doesn't guarantee roundtrip identity: -decoding a byte sequence using coding system, then encoding the +decoding a byte sequence using a coding system, then encoding the resulting text in the same coding system, can produce a different byte sequence. But some coding systems do guarantee that the byte sequence will be the same as what you originally decoded. Here are a few |