aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/emacs/ChangeLog5
-rw-r--r--doc/emacs/rmail.texi18
-rw-r--r--etc/NEWS5
3 files changed, 12 insertions, 16 deletions
diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index e70ad7d7b8c..be30efa88c3 100644
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,8 @@
12009-02-07 Eli Zaretskii <eliz@gnu.org>
2
3 * rmail.texi (Rmail Coding) <rmail-redecode-body>: Remove stale
4 documentation of possible problems with redecoding.
5
12009-02-03 Glenn Morris <rgm@gnu.org> 62009-02-03 Glenn Morris <rgm@gnu.org>
2 7
3 * rmail.texi (Out of Rmail): Mention b2m.pl. 8 * rmail.texi (Out of Rmail): Mention b2m.pl.
diff --git a/doc/emacs/rmail.texi b/doc/emacs/rmail.texi
index 844fa34cb4e..1d07f1cc2c1 100644
--- a/doc/emacs/rmail.texi
+++ b/doc/emacs/rmail.texi
@@ -1098,24 +1098,10 @@ its characters displayed as empty boxes, this may have happened.
1098 You can correct the problem by decoding the message again using the 1098 You can correct the problem by decoding the message again using the
1099right coding system, if you can figure out or guess which one is 1099right coding system, if you can figure out or guess which one is
1100right. To do this, invoke the @kbd{M-x rmail-redecode-body} command. 1100right. To do this, invoke the @kbd{M-x rmail-redecode-body} command.
1101It reads the name of a coding system, encodes the message body using 1101It reads the name of a coding system, and then redecodes the message
1102whichever coding system was used to decode it before, then redecodes 1102using the coding system you specified. If you specified the right
1103it using the coding system you specified. If you specified the right
1104coding system, the result should be readable. 1103coding system, the result should be readable.
1105 1104
1106 Decoding and encoding using the wrong coding system is lossless for
1107most encodings, in particular with 8-bit encodings such as iso-8859 or
1108koi8. So, if the initial attempt to redecode the message didn't
1109result in a legible text, you can try other coding systems until you
1110succeed.
1111
1112 With some coding systems, notably those from the iso-2022 family,
1113information can be lost in decoding, so that encoding the message
1114again won't bring back the original incoming text. In such a case,
1115@code{rmail-redecode-body} cannot work. However, the problems that
1116call for use of @code{rmail-redecode-body} rarely occur with those
1117coding systems. So in practice the command works when you need it.
1118
1119@node Rmail Editing 1105@node Rmail Editing
1120@section Editing Within a Message 1106@section Editing Within a Message
1121 1107
diff --git a/etc/NEWS b/etc/NEWS
index 7aca85dc665..d0c80bd4d2c 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -937,6 +937,11 @@ Rmail usage unaltered.
937 937
938FIXME: Add more mbox merge details 938FIXME: Add more mbox merge details
939 939
940*** The command `rmail-redecode-body' no longer accepts the optional arg RAW.
941Since Rmail now holds messages in their original undecoded form in a
942separate buffer, `rmail-redecode-body' no longer encodes the original
943message, and therefore there should be no need to avoid encoding it.
944
940** TeX modes 945** TeX modes
941--- 946---
942*** New option latex-indent-within-escaped-parens 947*** New option latex-indent-within-escaped-parens