Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: People with From: <mail@domain.com>
Date: 26 Apr 2000 13:29:49 -0400	[thread overview]
Message-ID: <2nu2gon52q.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Florian Weimer's message of "26 Apr 2000 19:14:43 +0200"

>>>>> "Florian" == Florian Weimer <fw@deneb.cygnus.argh.org> writes:

Florian> BTW: I've browsed some source code and discovered a code/comment
Florian> discrepancy in "mm-encode-body", non-MULE case:

Florian>   (if (not (featurep 'mule))
Florian>       ;; In the non-Mule case, we search for non-ASCII chars and
Florian>       ;; return the value of `mm-default-charset' if any are found.
Florian>       (save-excursion
Florian> 	(goto-char (point-min))
Florian> 	(if (re-search-forward "[^\x0-\x7f]" nil t)
Florian> 	    (or mail-parse-charset
Florian> 		(mm-read-charset "Charset used in the article: "))
Florian> 	  ;; The logic in `mml-generate-mime-1' confirms that it's OK
Florian> 	  ;; to return nil here.
Florian> 	  nil))

Florian> The comment says "mm-default-charset", but actually it's
Florian> "mail-parse-charset".  The value that's actually used by Gnus
Florian> is "message-default-charset", as it seems (in fact, this is a
Florian> FAQ ;).  I'll change the comment accordingly.

No, you should not. mail-parse-charset is dynamically bound. It is
only used in lower level functions. User should not use it at all.

-- 
Shenghuo



  reply	other threads:[~2000-04-26 17:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-22  9:55 Pavel.Janik
2000-04-22 11:09 ` Lars Magne Ingebrigtsen
2000-04-23 20:07   ` Pavel.Janik
2000-04-24 14:31     ` Lars Magne Ingebrigtsen
2000-04-24 17:04       ` Pavel Janik ml.
2000-04-24 18:39         ` Kai Großjohann
2000-04-24 18:56           ` Pavel Janík ml.
2000-04-25 11:04             ` Kai Großjohann
2000-04-25 11:38               ` Lars Magne Ingebrigtsen
2000-04-25 11:35                 ` Kai Großjohann
2000-04-25 20:03                   ` Florian Weimer
2000-04-25 20:15                     ` Kai Großjohann
2000-04-26 17:14                       ` Florian Weimer
2000-04-26 17:29                         ` Shenghuo ZHU [this message]
2000-04-26 18:06                           ` Florian Weimer
2000-04-26 18:15                             ` Shenghuo ZHU
2000-04-25 13:36               ` Pavel Janík ml.
2000-04-25 14:47                 ` Kai Großjohann
2000-04-25 15:31                   ` Pavel Janík ml.
2000-04-25 17:10                     ` Kai Großjohann
2000-04-25 10:45           ` Florian Weimer
2000-04-25 11:11             ` Kai Großjohann
2000-04-25  6:42 ` Jaap-Henk Hoepman
2000-04-26 14:05 ` Erik Toubro Nielsen
2000-04-26 20:59   ` Pavel Janík ml.
2000-04-28  2:00   ` Shenghuo ZHU

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2nu2gon52q.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).