emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/lispref/nonascii.texi


From: Richard M . Stallman
Subject: [Emacs-diffs] Changes to emacs/lispref/nonascii.texi
Date: Fri, 01 Apr 2005 17:08:40 -0500

Index: emacs/lispref/nonascii.texi
diff -c emacs/lispref/nonascii.texi:1.47 emacs/lispref/nonascii.texi:1.48
*** emacs/lispref/nonascii.texi:1.47    Fri Apr  1 00:29:51 2005
--- emacs/lispref/nonascii.texi Fri Apr  1 22:08:39 2005
***************
*** 628,638 ****
  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 a roundtrip identity,
! i.e. decoding followed by encoding in the same coding system can
! result in the different byte sequence.  But there are several coding
! systems that go guarantee that the result will be the same as what you
! originally decoded.  They are:
  
  @quotation
  chinese-big5 chinese-iso-8bit cyrillic-iso-8bit emacs-mule
--- 628,638 ----
  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:
  
  @quotation
  chinese-big5 chinese-iso-8bit cyrillic-iso-8bit emacs-mule
***************
*** 641,654 ****
  japanese-iso-8bit japanese-shift-jis korean-iso-8bit raw-text
  @end quotation
  
! Likewise, a coding systme doesn't guarantee the other way of roundtrip
! identity, i.e. encoding buffer text into a coding system followed by
! decoding again with the same coding system will produce the different
! buffer text.  For instance, when you encode Latin-2 characters by
! @code{utf-8} and decode it back by the same coding system, you'll get
! Unicode charactes (of charset @code{mule-unicode-0100-24ff}), and when
! you encode Unicode characters by @code{iso-latin-2} and decode it back
! by 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
--- 641,653 ----
  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
! 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.
  
  @cindex end of line conversion
    @dfn{End of line conversion} handles three different conventions used




reply via email to

[Prev in Thread] Current Thread [Next in Thread]