changeset 61233:5c7a0c8de2df

(Coding System Basics): Another cleanup.

--- a/lispref/nonascii.texi	Sat Apr 02 19:24:26 2005 +0000
+++ b/lispref/nonascii.texi	Sun Apr 03 04:25:05 2005 +0000
@@ -628,11 +628,11 @@
 conversion, but some of them leave the choice unspecified---to be chosen
 heuristically for each file, based on the data.
 
-In general, a coding system doesn't guarantee roundtrip identity:
-decoding text then encoding the result in the same coding system can
-produce a different byte sequence from the one you originally decoded.
-However, the following coding systems do guarantee that the result
-will be the same as what you originally decoded:
+  In general, a coding system doesn't guarantee roundtrip identity:
+decoding a byte sequence using coding system, then encoding the
+resulting text in the same coding system, can produce a different byte
+sequence.  However, the following coding systems do guarantee that the
+byte sequence will be the same as what you originally decoded:
 
 @quotation
 chinese-big5 chinese-iso-8bit cyrillic-iso-8bit emacs-mule
@@ -641,13 +641,13 @@
 japanese-iso-8bit japanese-shift-jis korean-iso-8bit raw-text
 @end quotation
 
-Encoding buffer text and then decoding the result can also fail to
-reproduce the original text.  For instance, when you encode Latin-2
+  Encoding buffer text and then decoding the result can also fail to
+reproduce the original text.  For instance, if you encode Latin-2
 characters with @code{utf-8} and decode the result using the same
 coding system, you'll get Unicode characters (of charset
-@code{mule-unicode-0100-24ff}).  When you encode Unicode characters
-with @code{iso-latin-2} and decode them back with the same coding
-system, you'll get Latin-2 characters.
+@code{mule-unicode-0100-24ff}).  If you encode Unicode characters with
+@code{iso-latin-2} and decode the result with the same coding system,
+you'll get Latin-2 characters.
 
 @cindex end of line conversion
   @dfn{End of line conversion} handles three different conventions used