Re: tin charset problem

1998-10-02 Thread Stef Hoesli Wiederwald
> Has anyone ever seem this error from tin? > > Error: Bad charset for non-7bit encoding (must not be us-ascii) > > I consistently get this error and it won't let me post because of it. The solution: Press M in rtin, choose item 73. MM_CHARSET and set it to ISO-8859-1. Now I can post without rt

Re: tin charset problem

1998-10-01 Thread shaul
> Has anyone ever seem this error from tin? > > Error: Bad charset for non-7bit encoding (must not be us-ascii) > > I consistently get this error and it won't let me post because of it. > I am getting it, and I still hadn't look into it. I am not sure but I think that in the last few weeks thi

tin charset problem

1998-09-30 Thread Cliff Draper
Has anyone ever seem this error from tin? Error: Bad charset for non-7bit encoding (must not be us-ascii) I consistently get this error and it won't let me post because of it. Thanks for any help. -Cliff [EMAIL PROTECTED]

Re: tin charset

1998-09-12 Thread Paul
-BEGIN PGP SIGNED MESSAGE- Type "M" to get a menu of items to configure in tin. Select item 73 (MM_CHARSET), change it to ISO-8859-1. All seems to be happy. On Thu, 10 Sep 1998 [EMAIL PROTECTED] wrote: > Hi, > > I have upgraded to tin 980226-3 (hamm) and need to do one or other of > th

tin charset

1998-09-10 Thread nic-debian
Hi, I have upgraded to tin 980226-3 (hamm) and need to do one or other of the following + change my charset to iso-8859-1, or + change my bitrate to 7bit in order to post messages (currently I get the error msg that the posting is not us-ascii. Does anyone know how to do one of the above? (And wi