🚀 go-pugleaf

Long, long ago in article <20070725.0853.834302snz@twoplaces.co.uk>
      simon@twoplaces.co.uk "Simon Turner" wrote:
[..]
> When I get back to PCOak, among the many things I'm intending to do is
> put in handling for the common character sets (Windows-1252,
> ISO-8859-1 (which is a subset of Windows-1252) etc.) so that

Or vice versa and "superset"?

> non-7bit-ASCII characters in incoming messages get replaced by their
> nearest equivalent in the local code page before being displayed,
> quoted in replies etc.

I use a small prog what I wrote that reprograms the screen font 
with ISO-8859-1 characters (this is run in a batch file just 
before PCOak) so I have "permanent" ISO-8859 characters displayed.  
Far from a perfect solution as (a) the redefinitions get lost on 
a video refresh (change mode, CLS etc.) and (b) it doesn't work 
in a Win window.  And of course it does nothing for folks using 
screen readers as the character code points are unchanged.

However, I recently hacked Snews with some primitive handling for 
UTF-8 decoding which takes a similar approach to what you suggest 
above, namely mapping some of the more common Unicode/ISO-10646 
punctuation characters to ASCII equivalents.  If you're 
interested I could to email the modified JLW Snews sources to 
you.  FWIW I found this site useful:

  <http://www.cs.tut.fi/~jkorpela/chars.html>

>    PCOak's handling of MIME messages leaves a lot
> to be desired.

Indeed.  Just being able to create an inline attachment would be 
a huge improvement, though I've looked into doing this and it is 
far from trivial :-(

Pete
-- 
   demon.ip.support.pc is for discussion of IP-related issues
   using plain DOS software - See the Which Group FAQ:-
   ftp://ftp.demon.co.uk/pub/doc/general/whichgrp.faq