Re: How to get tin pager to display 'extended' characters

On Wed, Nov 29, 2006 at 05:23:20PM +0100, Urs Janßen wrote:
> On Wed, Nov 29, 2006 at 03:22:36PM +0000, [email protected] wrote:
> > I don't think it's the undeclared_charset issue as I was trying to
> > look at posts with extended characters in that I'd posted myself with
> > a valid ISO-8859-1 character set.
> 
> but as tin didn't know (unset LC_TYPE) what is your local charset it
> assumes us-ascii and replaces all 8bit chars in your posting with ?.
> but you should have seen an errormessage like the following when posting:
> 
> |Warning: Posting is in US-ASCII and contains characters which are not
> |         in your selected MM_NETWORK_CHARSET: ISO-8859-1.
> |         These characters will be replaced by '?' if you post this
> |         article unchanged. To avoid garbling your article please either
> |         edit it and remove those characters or change the setting of
> |         MM_NETWORK_CHARSET to a suitable value for your posting via the
> |         M)enu option.
> 
No, I was originally getting that message but I fixed it by setting
the MM_CHARSET setting in tin to ISO-8859-1.


> (*hmmm* the error-message is misleading (as it is too generic and usualy
> handles the case where the locales are ok, but the selected
> MM_NETWORK_CHARSET doesn't hold all the chars from the locale charset)
> in this case, it should read like:
> 
> Posting will be in US-ASCII, but your article contains characters which are
> not in this charset. These characters will be replaced by '?' if you post
> this To avoid garbling your article please either edit it and remove those
> characters or change the setting of your locales.
> 
I checked by reading back what I had posted and saving it to a file.
The extended characters were correct.  It was only when tin was
displaying posts that it was converting to ???????.

-- 
Chris Green ([email protected])