From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pony.its.uwo.ca([129.100.2.63]) (1773 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Fri, 26 Jan 2001 12:33:25 -0500 (EST) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from ignatious (c716099-a.rchdsn1.tx.home.com [24.7.105.70]) by pony.its.uwo.ca (8.10.0/8.10.0) with ESMTP id f0QHXQd11346 for ; Fri, 26 Jan 2001 12:33:27 -0500 (EST) Received: from cpt.kirk (helo=localhost) by ignatious with local-esmtp (Exim 3.12 #1 (Debian)) id 14MCxn-0001Ub-00 for ; Fri, 26 Jan 2001 11:47:07 -0600 Date: Fri, 26 Jan 2001 11:47:07 -0600 (CST) From: Kirk Wood X-Sender: cpt.kirk@ignatious To: speakup@braille.uwo.ca Subject: Re: list guidelines In-Reply-To: <200101261657.IAA22203@viper.wapvi.bc.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: > ok... do you all mind using the default char set? i hate reading that message about invalid char set - some chars may be displayed > incorrectly. i use pine. it's sorta a bug. ... Actually it is NOT a bug. Unlike some programs that give you no notice that you may not get all characters correct, Pine notifies you. It is done on purpose. Now it might be nice to be able to disable this, but since it was designed in, it is not a bug. Something you may wish to do though is change your default character set. This is found in Setup, then Config. It is pretty far down the list and is character-set. It appears after all the sort settings. I would recoment you set it to iso-8859-1. This should eliminate most of the messages. (I almost never see the message.) ======= Kirk Wood Cpt.Kirk@1tree.net Cluelessness There are no stupid questions, but there are a lot of inquisitive idiots