From owner-freebsd-ports Wed Jan 8 6: 1:56 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7045137B401 for ; Wed, 8 Jan 2003 06:01:54 -0800 (PST) Received: from eos.telenet-ops.be (eos.telenet-ops.be [195.130.132.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id E75F343EB2 for ; Wed, 8 Jan 2003 06:01:52 -0800 (PST) (envelope-from philip@paeps.cx) Received: from localhost (localhost.localdomain [127.0.0.1]) by eos.telenet-ops.be (Postfix) with SMTP id 7FA8020B48; Wed, 8 Jan 2003 14:33:38 +0100 (CET) Received: from fortuna.home.paeps.cx (D5768746.kabel.telenet.be [213.118.135.70]) by eos.telenet-ops.be (Postfix) with ESMTP id 4CF18200D5; Wed, 8 Jan 2003 14:33:38 +0100 (CET) Received: from juno.home.paeps.cx (juno.home.paeps.cx [10.0.0.2]) by fortuna.home.paeps.cx (Postfix) with ESMTP id 228F55E7; Wed, 8 Jan 2003 14:33:38 +0100 (CET) Received: by juno.home.paeps.cx (Postfix, from userid 1001) id 011CE51; Wed, 8 Jan 2003 14:33:37 +0100 (CET) Date: Wed, 8 Jan 2003 14:33:37 +0100 From: Philip Paeps To: ports@freebsd.org, Seva Gluschenko Subject: Re: ports/46863: tin newsreader improperly deals with charsets Message-ID: <20030108133337.GN89230@juno.home.paeps.cx> Mail-Followup-To: ports@freebsd.org, Seva Gluschenko References: <200301081233.h08CXvfq060888@road.demos.su> <20030108125313.GM89230@juno.home.paeps.cx> <20030108161117.T74164@road.demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20030108161117.T74164@road.demos.su> X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get yourself a real mail client. Try Mutt: User-Agent: Mutt/1.5.1i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2003-01-08 16:13:02 (+0300), Seva Gluschenko wrote: > Message of Philip Paeps at Jan 8 13:53 ... > PP> Tin now uses iconv, and can be configured to 'translate' to a proper charset > PP> when one is not given. In your ~/.tin/attributes file, you could put > PP> something like: > PP> > PP> scope=* > PP> undeclared_charset=iso-8859-1 > > I found nothing related in README (perhaps, inattentive reading?) and an > attempt to define default charset during compile time had no effect. Thank > you for advice, anyway. It's mentioned in tin(5): | undeclared_charset | Assume (broken) articles without MIME charset declaration | have this charset - default is US-ASCII. This attribu | works only on systems with working iconv(3), others might | have to compile tin with --disable-mime-strict-charset. > PP> In any case, over here, iconv deals with charsets quite nicely. Nicer than > PP> the disable-mime-strict-charset switch, I find :-) > > Will see %) Thanks again. Basically, using iconv(3) and undeclared_charset is more flexible than configuring with --disable-mime-strict-charset. If you use the latter, Tin will always try to do something intelligent to messages with undeclared charsets, and you have no real control over it. Using iconv(3) and undeclared_charset settings in your attributes, you can make your own decisions for different 'scopes': scope=ru* undeclared_charset=KIO-8 # something to that effect? scope=pl* undeclared_charset=iso-8859-2 scope=be* undeclared_charset=iso-8859-15 Good luck :-) - Philip -- Philip Paeps Please don't CC me, I am philip@paeps.cx subscribed to the list. To spot the expert, pick the one who predicts the job will take the longest and cost the most. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message