From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Customizing coding priority Date: Thu, 18 Jan 2007 23:36:23 +0200 Message-ID: References: <17837.26945.133317.830421@kamaloka.dhatu> <17837.55152.906774.97483@relwi-sven.unibe.ch> <17838.42714.915656.255057@relwi-sven.unibe.ch> <17839.40064.616634.841398@relwi-sven.unibe.ch> NNTP-Posting-Host: lo.gmane.org X-Trace: sea.gmane.org 1169156213 26128 80.91.229.12 (18 Jan 2007 21:36:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 18 Jan 2007 21:36:53 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jan 18 22:36:42 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1H7evz-0005kx-CR for geh-help-gnu-emacs@m.gmane.org; Thu, 18 Jan 2007 22:36:35 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H7ew0-00014o-0Z for geh-help-gnu-emacs@m.gmane.org; Thu, 18 Jan 2007 16:36:36 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H7evm-00014S-19 for help-gnu-emacs@gnu.org; Thu, 18 Jan 2007 16:36:22 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H7evk-000146-CA for help-gnu-emacs@gnu.org; Thu, 18 Jan 2007 16:36:21 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H7evk-000143-5b for help-gnu-emacs@gnu.org; Thu, 18 Jan 2007 16:36:20 -0500 Original-Received: from [213.8.233.22] (helo=nitzan.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H7evi-0005L1-1Y for help-gnu-emacs@gnu.org; Thu, 18 Jan 2007 16:36:18 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-84-229-126-51.inter.net.il [84.229.126.51]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id FUW56980 (AUTH halo1); Thu, 18 Jan 2007 23:36:11 +0200 (IST) Original-To: help-gnu-emacs@gnu.org In-reply-to: <17839.40064.616634.841398@relwi-sven.unibe.ch> (message from Sven Bretfeld on Thu, 18 Jan 2007 17:12:48 +0100) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:40434 Archived-At: > From: Sven Bretfeld > Date: Thu, 18 Jan 2007 17:12:48 +0100 > Cc: help-gnu-emacs@gnu.org > > Eli Zaretskii writes: > > You didn't answer my first question: how these umlauts were produced. > > Did you copy them from another text, perhaps? And how is the way you > > produced those umlauts differs from the way you type the > > latin-iso8859-1 characters after the quotation? > > I hope I get your question right. The umlauts that are encoded in > iso-8859-15 appear in the mail by executing the function > vm-reply-include-text. It is bound to the R-key when in an > Mailbox-Summary buffer in vm. It sets up an answer to the email under > the point citing the content of the original. The cited text keeps > umlauts encoded in iso-8859-15. Yes, this answers my question. I understand that these characters come from the mail to which you reply. > Anyway, what Peter and Tom remark sounds strange. There must be some > difference in the umlauts of the two coding systems, at least for > Emacs. Because the iso-8859-15 umlauts of the cited text alway look > different from the ones I type in iso-8859-1. The former are displayed > in another font. Do you have something related in your ~/.emacs init file? Does this problem go away if you invoke Emacs with "emacs -q --no-site-file"? (If doing so prevents you from using VM, then leave only the VM-related customizations on .emacs and comment out everything else.) > Eli, do you think the problem wouldn't exist in Emacs 22? I don't know. I need to understand your problem first. But if it's easy for you to try Emacs 22, I recommend doing so.