aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2001-02-17 22:16:01 +0000
committerRichard M. Stallman2001-02-17 22:16:01 +0000
commit358f71fdf6c1189dd8290af01d78990e0a434fc5 (patch)
treef0aaa86eae12e80bf7bf9522b0f8903e8f3e3ab5
parentb9fe3dc8d5b225f0740649fb38690b122d7d61c3 (diff)
downloademacs-358f71fdf6c1189dd8290af01d78990e0a434fc5.tar.gz
emacs-358f71fdf6c1189dd8290af01d78990e0a434fc5.zip
New node Rmail Coding for the discussion of coding systems.
Clarify goto-address and fix errors. Minor cleanups.
-rw-r--r--man/rmail.texi88
1 files changed, 49 insertions, 39 deletions
diff --git a/man/rmail.texi b/man/rmail.texi
index 1945545b724..06dc569ffd5 100644
--- a/man/rmail.texi
+++ b/man/rmail.texi
@@ -32,6 +32,7 @@ visiting a proper Rmail file.
32* Summary: Rmail Summary. Summaries show brief info on many messages. 32* Summary: Rmail Summary. Summaries show brief info on many messages.
33* Sort: Rmail Sorting. Sorting messages in Rmail. 33* Sort: Rmail Sorting. Sorting messages in Rmail.
34* Display: Rmail Display. How Rmail displays a message; customization. 34* Display: Rmail Display. How Rmail displays a message; customization.
35* Coding: Rmail Coding. How Rmail handles decoding character sets.
35* Editing: Rmail Editing. Editing message text and headers in Rmail. 36* Editing: Rmail Editing. Editing message text and headers in Rmail.
36* Digest: Rmail Digest. Extracting the messages from a digest message. 37* Digest: Rmail Digest. Extracting the messages from a digest message.
37* Out of Rmail:: Converting an Rmail file to mailbox format. 38* Out of Rmail:: Converting an Rmail file to mailbox format.
@@ -976,12 +977,12 @@ means to show the reformatted header, and a zero or negative argument
976means to show the full header. 977means to show the full header.
977 978
978@vindex rmail-highlighted-headers 979@vindex rmail-highlighted-headers
979 When used with a terminal that supports multiple fonts or colors, Rmail 980 When the terminal supports multiple fonts or colors, Rmail
980highlights certain header fields that are especially interesting---by 981highlights certain header fields that are especially interesting---by
981default, the @samp{From} and @samp{Subject} fields. The variable 982default, the @samp{From} and @samp{Subject} fields. The variable
982@code{rmail-highlighted-headers} holds a regular expression that 983@code{rmail-highlighted-headers} holds a regular expression that
983specifies the header fields to highlight; if it matches the beginning of 984specifies the header fields to highlight; if it matches the beginning
984a header field, that whole field is highlighted. 985of a header field, that whole field is highlighted.
985 986
986 If you specify unusual colors for your text foreground and background, 987 If you specify unusual colors for your text foreground and background,
987the colors used for highlighting may not go well with them. If so, 988the colors used for highlighting may not go well with them. If so,
@@ -992,48 +993,57 @@ highlighting as well. @xref{Faces}, for how to do this.
992 To turn off highlighting entirely in Rmail, set 993 To turn off highlighting entirely in Rmail, set
993@code{rmail-highlighted-headers} to @code{nil}. 994@code{rmail-highlighted-headers} to @code{nil}.
994 995
995@findex goto-addr 996 You can highlight and activate URLs in incoming messages by adding
996 URLs in messages may be highlighted and activated for following with the 997the function @code{goto-address} to the hook
997mouse or keyboard by customizing the hook @code{rmail-show-message-hook} 998@code{rmail-show-message-hook}. Then you can browse these URLs by
998to add @code{goto-addr}. 999clicking on them with @kbd{Mouse-2} or by moving to one and typing
1000@kbd{C-c @key{RET}}. @xref{Goto-address}.
1001
1002@node Rmail Coding
1003@section Rmail and Coding Systems
999 1004
1000@cindex decoding mail messages (Rmail) 1005@cindex decoding mail messages (Rmail)
1001 Rmail automatically decodes messages which contain non-@sc{ascii} 1006 Rmail automatically decodes messages which contain non-@sc{ascii}
1002characters, like it does with visited files and output from 1007characters, just as it does with files you visit and with and
1003subprocesses. Rmail uses the standard ``charset=@var{encoding}'' 1008subprocess output. Rmail uses the standard
1004header in the message to find out how was the message encoded by the 1009@samp{charset=@var{charset}} header in the message to determine how
1005sender. It then maps @var{encoding} into the corresponding coding 1010the was message encoded by the sender. It maps @var{charset} into the
1006system (@pxref{Coding Systems}), and uses that coding system to decode 1011corresponding Emacs coding system (@pxref{Coding Systems}), and uses
1007message text. If the message header doesn't have the charset 1012that coding system to decode message text. If the message header
1008specification, or if the @var{encoding} it specifies is not recognized 1013doesn't have the charset specification, or if the @var{charset} it
1009by Emacs, Rmail attempts to detect the encoding by applying the usual 1014specifies is not recognized, Rmail chooses the coding system with the
1010heuristics and defaults (@pxref{Recognize Coding}). 1015usual Emacs heuristics and defaults (@pxref{Recognize Coding}).
1011 1016
1012@findex rmail-redecode-body
1013@cindex fixing incorrectly decoded mail messages 1017@cindex fixing incorrectly decoded mail messages
1014 Occasionally, a message might be decoded incorrectly, either because 1018 Occasionally, a message is decoded incorrectly, either because Emacs
1015Emacs failed to guess the encoding in the absence of the ``charset'' 1019guessed the wrong coding system in the absence of the @samp{charset}
1016specification, or because the ``charset'' specification was wrong. 1020specification, or because the specification was inaccurate. For
1017For example, a misconfigured mailer could send a message with a 1021example, a misconfigured mailer could send a message with a
1018``charset=iso-8859-1'' header whereas the mssage is encoded in koi8-r. 1022@samp{charset=iso-8859-1} header when the message is actually encoded
1019Whenever you see a message text garbled or some of its characters 1023in @code{koi8-r}. When you see the message text garbled, or some of
1020displayed as empty boxes, you can try to fix that by decoding the 1024its characters displayed as empty boxes, this may have happened.
1021message again using a specific coding system. (This requires that you
1022guess the correct encoding, or talk to the sender and ask them.) To
1023that end, invoke the @code{rmail-redecode-body} command. It prompts
1024for a name of a coding system and then redecodes the message body
1025using that coding system.
1026
1027 Redecoding the message body is a lossless operation with most
1028encodings, in particular with 8-bit encodings such as iso-8859 or
1029koi8. So, if the initial attempt to redecode the message didn't
1030result in a legible text, you could try other possible encodings,
1031until you succeed.
1032 1025
1033 With some encodings, notably those from the iso-2022 family, 1026@findex rmail-redecode-body
1034@code{rmail-redecode-body} might fail to recover the original form of 1027 You can correct the problem by decoding the message again using the
1035the message. However, such encodings rarely cause the kind of trouble 1028right coding system, if you can figure out or guess which one is
1036for which @code{rmail-redecode-body} is intended to be used. 1029right. To do this, invoke the @kbd{M-x rmail-redecode-body} command.
1030It reads the name of a coding system, encodes the message body using
1031whichever coding system was used to decode it before, then redecodes
1032it using the coding system you specified. If you specified the right
1033coding system, the result should be readable.
1034
1035 Decoding and encoding using the wrong coding system is lossless for
1036most encodings, in particular with 8-bit encodings such as iso-8859 or
1037koi8. So, if the initial attempt to redecode the message didn't
1038result in a legible text, you can try other coding systems until you
1039succeed.
1040
1041 With some coding systems, notably those from the iso-2022 family,
1042information can be lost in decoding, so that encoding the message
1043again won't bring back the original incoming text. In such a case,
1044@code{rmail-redecode-body} cannot work. However, the problems that
1045call for use of @code{rmail-redecode-body} rarely occur with those
1046coding systems. So in practice the command works when you need it.
1037 1047
1038@node Rmail Editing 1048@node Rmail Editing
1039@section Editing Within a Message 1049@section Editing Within a Message