From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/50917 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: IDNA support installed (was: Re: Oort Gnus v0.16 is released) Date: Wed, 19 Mar 2003 23:56:36 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1048114656 25535 80.91.224.249 (19 Mar 2003 22:57:36 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 19 Mar 2003 22:57:36 +0000 (UTC) Original-X-From: owner-ding@hpc.uh.edu Wed Mar 19 23:57:33 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18vmV2-0006dU-00 for ; Wed, 19 Mar 2003 23:57:33 +0100 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 18vmUW-00028c-00; Wed, 19 Mar 2003 16:57:00 -0600 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 19 Mar 2003 16:58:01 -0600 (CST) Original-Received: from sclp3.sclp.com (sclp3.sclp.com [66.230.238.2]) by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id QAA12716 for ; Wed, 19 Mar 2003 16:57:47 -0600 (CST) Original-Received: (qmail 66692 invoked by alias); 19 Mar 2003 22:56:40 -0000 Original-Received: (qmail 66687 invoked from network); 19 Mar 2003 22:56:40 -0000 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net (HELO yxa.extundo.com) (217.13.230.178) by 66.230.238.6 with SMTP; 19 Mar 2003 22:56:40 -0000 Original-Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.8/8.12.8) with ESMTP id h2JMuaZG018173 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Wed, 19 Mar 2003 23:56:36 +0100 Original-To: ding@gnus.org Mail-Copies-To: nobody X-Payment: hashcash 1.2 0:030319:ding@gnus.org:36a2e34e13e1d478 X-Hashcash: 0:030319:ding@gnus.org:36a2e34e13e1d478 In-Reply-To: (Lars Magne Ingebrigtsen's message of "Tue, 18 Mar 2003 01:01:00 +0100") User-Agent: Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.3.50 (gnu/linux) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:50917 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:50917 Lars Magne Ingebrigtsen writes: > As suggested (off the list), let's aim for a May 1st release date for > Gnus 5.10. Most things in Oort Gnus work, but if there is anything > experimental going on in any parts of the code, or things that you > absolutely want to have in the next Gnus release, try getting it in > during the next couple of weeks. I think it would be nice to have the IDNA support available. It shouldn't be noticable if libidn isn't installed on the system. I have added it to CVS. I'd also like to move in the Elisp SASL Library too, but I haven't been able to reach two of the copyright holders for a few months. :-( ** Support for non-ASCII domain names Message supports non-ASCII domain names in From:, To: and Cc: and will query you whether to perform encoding when you try to send a message. The variable `message-use-idna' controls this. Gnus will also decode non-ASCII domain names in From:, To: and Cc: when you view a message. The variable `gnus-use-idna' controls this. --- 2003-03-19 Simon Josefsson * gnus-art.el (gnus-article-decode-hook): Add IDNA. (gnus-use-idna): New variable. (article-decode-idna-rhs): New function. * message.el (message-use-idna): New variable. (message-mode-field-menu): Add entry for IDNA. (message-idna-inside-rhs-p, message-idna-to-ascii-rhs-1) (message-idna-to-ascii-rhs): New function. (message-generate-headers): Invoke IDNA code. --- IDNA ==== Message is a IDNA-compliant posting agent. The user generally doesn't have to do anything to make the IDNA happen--Message will encode non-ASCII domain names in `From', `To', and `Cc' headers automatically. Until IDNA becomes more well known, Message queries you whether IDNA encoding of the domain name really should occur. Some users might not be aware that domain names can contain non-ASCII now, so this gives them a safety net if they accidently typed a non-ASCII domain name. The `message-use-idna' variable control whether IDNA is used. If the variable is NIL no IDNA encoding will ever happen, if it is set to the symbol ASK the user will be queried (the default), and if set to T IDNA encoding happens automatically. If you want to experiment with the IDNA encoding, you can invoke `M-x message-idna-to-ascii-rhs RET' in the message buffer to have the non-ASCII domain names encoded while you edit the message. Note that you must have GNU Libidn ( installed in order to use this functionality. --- `gnus-use-idna' This variable controls whether Gnus performs IDNA decoding of internationalized domain names inside FROM:, TO: and CC: headers. This requires GNU Libidn (, and this variable is only enabled if you have installed it.