From owner-freebsd-ports Wed Jan 8 4:53:27 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 C92BC37B401 for ; Wed, 8 Jan 2003 04:53:25 -0800 (PST) Received: from tartarus.telenet-ops.be (tartarus.telenet-ops.be [195.130.132.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4E1C43EE6 for ; Wed, 8 Jan 2003 04:53:24 -0800 (PST) (envelope-from philip@paeps.cx) Received: from localhost (localhost.localdomain [127.0.0.1]) by tartarus.telenet-ops.be (Postfix) with SMTP id 7DE55DBCCC; Wed, 8 Jan 2003 13:53:18 +0100 (CET) Received: from fortuna.home.paeps.cx (D5768746.kabel.telenet.be [213.118.135.70]) by tartarus.telenet-ops.be (Postfix) with ESMTP id 482C2DC0AD; Wed, 8 Jan 2003 13:53:18 +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 524B38A; Wed, 8 Jan 2003 13:53:14 +0100 (CET) Received: by juno.home.paeps.cx (Postfix, from userid 1001) id 1E48751; Wed, 8 Jan 2003 13:53:14 +0100 (CET) Date: Wed, 8 Jan 2003 13:53:13 +0100 From: Philip Paeps To: Seva Gluschenko , ports@freebsd.org Subject: Re: ports/46863: tin newsreader improperly deals with charsets Message-ID: <20030108125313.GM89230@juno.home.paeps.cx> Mail-Followup-To: Seva Gluschenko , ports@freebsd.org References: <200301081233.h08CXvfq060888@road.demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <200301081233.h08CXvfq060888@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 15:33:57 (+0300), Seva Gluschenko wrote: > >Description: > When using tin newsreader from ports collection for reading national > newsgroups you're finishing soon with messages full of question marks > because tin was configured for strict MM_CHARSET obeyance. Tin now uses iconv, and can be configured to 'translate' to a proper charset when one is not given. In your ~/.tin/attributes file, you could put something like: scope=* undeclared_charset=iso-8859-1 > Just add --disable-mime-strict-charset to configure options, as follows: Mmm, perhaps adding a conditional for that would be better: .if defined(WITHOUT_TIN_STRICT_CHARSET) CONFIGURE_ARGS+=--disable-mime-strict-charset .endif In any case, over here, iconv deals with charsets quite nicely. Nicer than the disable-mime-strict-charset switch, I find :-) - Philip -- Philip Paeps Please don't CC me, I am philip@paeps.cx subscribed to the list. Law expands in proportion to the resources available for its enforcement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message