From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/77314 Path: news.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: Attach file improvement Date: Thu, 24 Feb 2011 19:26:20 -0800 Organization: Programmerer Ingebrigtsen Message-ID: <87k4goeqw3.fsf@gnus.org> References: <87d3mkb7bu.fsf@myhost.localdomain> <8762scb5ea.fsf@myhost.localdomain> <87aahnaijh.fsf@myhost.localdomain> <871v2z2hyj.fsf@gnus.org> <87ei6y4fn7.fsf@myhost.localdomain> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1298604628 8885 80.91.229.12 (25 Feb 2011 03:30:28 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 25 Feb 2011 03:30:28 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M25640@lists.math.uh.edu Fri Feb 25 04:30:24 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PsoNr-0005MR-N7 for ding-account@gmane.org; Fri, 25 Feb 2011 04:30:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1PsoNp-0007c7-Ph; Thu, 24 Feb 2011 21:30:21 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1PsoNo-0007bi-14 for ding@lists.math.uh.edu; Thu, 24 Feb 2011 21:30:20 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.72) (envelope-from ) id 1PsoNb-0002M2-3r for ding@lists.math.uh.edu; Thu, 24 Feb 2011 21:30:19 -0600 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1PsoNa-0002Zn-Cx for ding@gnus.org; Fri, 25 Feb 2011 04:30:06 +0100 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PsoNY-0005GY-RN for ding@gnus.org; Fri, 25 Feb 2011 04:30:04 +0100 Original-Received: from 109.144.247.156 ([109.144.247.156]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 25 Feb 2011 04:30:04 +0100 Original-Received: from larsi by 109.144.247.156 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 25 Feb 2011 04:30:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 26 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 109.144.247.156 Mail-Copies-To: never User-Agent: Gnus/5.110014 (No Gnus v0.14) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:Z8Dy0KTyVVTgTNG1qJ7WpFN0SVs= X-Spam-Score: 1.5 (+) X-Spam-Report: SpamAssassin (3.3.1 2010-03-16) analysis follows Bayesian score: 0.0000 Ham tokens: 0.000-1729--4335h-0s--0d--H*u:Emacs, 0.000-1661--4164h-0s--0d--H*u:Gnus, 0.000-1602--4016h-0s--0d--H*u:linux, 0.000-1602--4016h-0s--0d--H*UA:linux, 0.000-1544--3871h-0s--0d--H*UA:gnu Spam tokens: 0.995-1--0h-3s--0d--D*yandex.ru, 0.993-1--0h-2s--1d--hobbit Autolearn status: no -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO 2.3 FSL_RU_URL URI: FSL_RU_URL -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:77314 Archived-At: Hobbit writes: > So my autorship is much smaller than it could seem. "Real" weight of > the patch is near 10 lines (if not less). The FSF needs copyright assignment papers in this case. Would you be willing to sign such papers? > Unfortunately, in the cyrillic world things are much more difficult, > because there are several popular charsets which use same codes for > different cyrillic letters. [...] > So how could we know what charset to use without asking a user? Right. But if you just load that file into an Emacs buffer, does it interpret that file correctly according to your settings, or do you have to tell Emacs manually what encoding it is? I guess the latter, if you normally handle files of both encodings. And in that case, perhaps the MIME code should only ask when it's not obvious by looking at the file what encoding it is? -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen