Subj : Encodings according to fts-5003.001
To   : Nil Alexandrov
From : Rob Swindell
Date : Sat Feb 24 2024 17:28:08

  Re: Encodings according to fts-5003.001
  By: Nil Alexandrov to Rob Swindell on Sat Feb 24 2024 07:55 pm

 > Hello, Rob!
 >
 > Saturday February 24 2024 15:43, from Rob Swindell -> Nil Alexandrov:
 >
 >  >> Your default charset may vary from CP437 AKA ASCII, AKA AMIGA,
 >  >> CP850 AKA
 >  >>  BW>  (albeit FTS-5003.001 says ASCII),
 >  >> AKA CP437.
 >  RS> I'm sure others will correct you too, but ASCII is *not* AKA CP437.
 >
 > My bad, CP437 AKA extended-ASCII. I actually like this topic of different
 > encoding according to fts-5003. IMHO, the supported level field of CHRS
 > kludge is pretty much useless and might be ignored by software cause the
 > identifier aka charset name itself includes the details of how it is sent
 > over the wire. BTW, can we do UTF-16? UTF-32? Level makes no sense.

Indeed, Synchronet/SBBSecho igores the "level" part of the FTN CHRS kludge value and there's been no apparent harm. :-)

I don't think UTF-16 or UTF-32 is supported in FTN. Nor should it be, IMHO.
-- 
                                            digital man (rob)

Breaking Bad quote #18:
All right, Operation: TBD, thanks for nothing Gomey. - Hank Schrader
Norco, CA WX: 70.1øF, 38.0% humidity, 3 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.