aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2005-04-03 04:25:20 +0000
committerRichard M. Stallman2005-04-03 04:25:20 +0000
commitaa945b597de91f6d780064b4a2a2df6c26ca1926 (patch)
tree514cd5872fe09d9d63331e71a80307987f9cc9a8
parentab77efd0e55c661ea8fd45df28f2a39d0c46fbd8 (diff)
downloademacs-aa945b597de91f6d780064b4a2a2df6c26ca1926.tar.gz
emacs-aa945b597de91f6d780064b4a2a2df6c26ca1926.zip
(Coding System Basics): Another cleanup.
-rw-r--r--lispref/ChangeLog4
-rw-r--r--lispref/nonascii.texi20
2 files changed, 14 insertions, 10 deletions
diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index 8a34499507f..3c3cc48a70d 100644
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,7 @@
12005-04-02 Richard M. Stallman <rms@gnu.org>
2
3 * nonascii.texi (Coding System Basics): Another wording cleanup.
4
12005-04-01 Richard M. Stallman <rms@gnu.org> 52005-04-01 Richard M. Stallman <rms@gnu.org>
2 6
3 * nonascii.texi (Coding System Basics): Clarify previous change. 7 * nonascii.texi (Coding System Basics): Clarify previous change.
diff --git a/lispref/nonascii.texi b/lispref/nonascii.texi
index 4e38c300a61..aaa23e90a48 100644
--- a/lispref/nonascii.texi
+++ b/lispref/nonascii.texi
@@ -628,11 +628,11 @@ characters; for example, there are three coding systems for the Cyrillic
628conversion, but some of them leave the choice unspecified---to be chosen 628conversion, but some of them leave the choice unspecified---to be chosen
629heuristically for each file, based on the data. 629heuristically for each file, based on the data.
630 630
631In general, a coding system doesn't guarantee roundtrip identity: 631 In general, a coding system doesn't guarantee roundtrip identity:
632decoding text then encoding the result in the same coding system can 632decoding a byte sequence using coding system, then encoding the
633produce a different byte sequence from the one you originally decoded. 633resulting text in the same coding system, can produce a different byte
634However, the following coding systems do guarantee that the result 634sequence. However, the following coding systems do guarantee that the
635will be the same as what you originally decoded: 635byte sequence will be the same as what you originally decoded:
636 636
637@quotation 637@quotation
638chinese-big5 chinese-iso-8bit cyrillic-iso-8bit emacs-mule 638chinese-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
641japanese-iso-8bit japanese-shift-jis korean-iso-8bit raw-text 641japanese-iso-8bit japanese-shift-jis korean-iso-8bit raw-text
642@end quotation 642@end quotation
643 643
644Encoding buffer text and then decoding the result can also fail to 644 Encoding buffer text and then decoding the result can also fail to
645reproduce the original text. For instance, when you encode Latin-2 645reproduce the original text. For instance, if you encode Latin-2
646characters with @code{utf-8} and decode the result using the same 646characters with @code{utf-8} and decode the result using the same
647coding system, you'll get Unicode characters (of charset 647coding system, you'll get Unicode characters (of charset
648@code{mule-unicode-0100-24ff}). When you encode Unicode characters 648@code{mule-unicode-0100-24ff}). If you encode Unicode characters with
649with @code{iso-latin-2} and decode them back with the same coding 649@code{iso-latin-2} and decode the result with the same coding system,
650system, you'll get Latin-2 characters. 650you'll get Latin-2 characters.
651 651
652@cindex end of line conversion 652@cindex end of line conversion
653 @dfn{End of line conversion} handles three different conventions used 653 @dfn{End of line conversion} handles three different conventions used