From: Richard M. Stallman Date: Sun, 3 Apr 2005 04:25:20 +0000 (+0000) Subject: (Coding System Basics): Another cleanup. X-Git-Tag: ttn-vms-21-2-B4~1276 X-Git-Url: https://code.delx.au/gnu-emacs/commitdiff_plain/aa945b597de91f6d780064b4a2a2df6c26ca1926?ds=sidebyside (Coding System Basics): Another cleanup. --- diff --git a/lispref/ChangeLog b/lispref/ChangeLog index 8a34499507..3c3cc48a70 100644 --- a/lispref/ChangeLog +++ b/lispref/ChangeLog @@ -1,3 +1,7 @@ +2005-04-02 Richard M. Stallman + + * nonascii.texi (Coding System Basics): Another wording cleanup. + 2005-04-01 Richard M. Stallman * nonascii.texi (Coding System Basics): Clarify previous change. diff --git a/lispref/nonascii.texi b/lispref/nonascii.texi index 4e38c300a6..aaa23e90a4 100644 --- a/lispref/nonascii.texi +++ b/lispref/nonascii.texi @@ -628,11 +628,11 @@ characters; for example, there are three coding systems for the Cyrillic 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 @@ iso-latin-4 iso-latin-5 iso-latin-8 iso-latin-9 iso-safe 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