-={ jeudi, avril 02 2015, 13:20:44 -0700 }=-

Hey Nicholas!

 NB> It was more the fact that CP437 supported ANSI graphics.

ANSI has nothing to do with the codepage/charset.  It is the terminal that
determines ANSI escape code compatibilty.  However the "graphics" you are
probably referring to are the line/box as well as the block characters which in
most ansi encoded files tend to be deplying the cp437 8-bit codes for which
wou't display properly in most codepage/charsets other than the ibm cp ones
such as cp437 (cp866 should work along with other cp* ones), but probably not
the ms cp* ones which might not jive with the ibm ones.

 NB> I'm sure you know this since I believe you said you've used BBS
 NB> software (Maximus?) in the past that supported all of that.

That was a long, long time ago and I never used much ansification, zero in
messages as well as zero 8-bit characters.  Mind you I never did utf8 back then
either.  Also *never* wrote apps that relied on anything other than ascii when
and where humanly readable input/output was a requirement.  The little utf8 I
use these days I limit to humanly readable utf8 characters.

As for ansification, I stick to vga16 colours the little to none I do anything
like that.  However I sill think even that should be up to the enduser and not
the BBS.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.33(1)-release (x86_64-atom-linux-gnu)