🚀 go-pugleaf

In article  <1189314945snz@nospam.demon.co.uk> pete@nospam.demon.co.uk  writes:

[with apologies for following-up to self]

> There's not a lot one (or rather Snews) can do with UTF-8 
> encoding.  I know very little about it, but it appears to use 
> three bytes to encode certain "non-standardised" characters, 
> and to be becoming ever more ubiquitous.  I also don't know how 
> feasible it would be to add UTF-8 support to Snews but would 
> guess at the very least it would be non-trivial.

I've done a bit of utf-8 research (RFC3629 if anyone's interested) 
and ISTM that it is not a charset after all but rather an 
encoding for Unicode characters (and a relatively simple one to 
decode/encode too).  So header lines like e.g.

    Content-Type: text/plain; charset="utf-8"

are something of a misnomer.  Anyway, if there is a simple way to 
map Unicode characters into one of the ISO-8859-x sets that Snews 
already knows about, it might just be possible to do a partial, 
working implementation.  And worthwhile as this encoding seems to 
be growing in use.  The two-byte sequences should be fairly 
straightforward, the three- and four-byte less so :-(

Off to investigate Unicode now...

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