Subj : ANSI & ASCII w/ Golded To : deon From : Accession Date : Tue Dec 12 2023 09:34 pm Hello deon, On Wed, 13 Dec 2023 18:42:36 +1100, you wrote: >> Yes, both. ;) d> Just so that I know that I'm using the correct term - high ansi is above d> 128 (and below 256) right? Sort of. Quoted from Wikipedia: "Extended ASCII is a repertoire of character encodings that include (most of) the original 96 ASCII character set, plus up to 128 additional characters. There is no formal definition of "extended ASCII", and even use of the term is sometimes criticized,[1][2][3] because it can be mistakenly interpreted to mean that the American National Standards Institute (ANSI) had updated its ANSI X3.4-1986 standard to include more characters, or that the term identifies a single unambiguous encoding, neither of which is the case." I suppose the correct term would be "extended ascii", but it has been called "high ascii" also for a long time. >> That's because ANSI should definitely not be posted with a "UTF-8 4" >> CHRS kludge. ANSI should be posted with a CP437 CHRS kludge. Most >> telnet/terminal programs default to CP437 *and* support ANSI. Golded >> only does one of the two (supports CP437, but doesn't support ANSI). d> Hmm... Maybe I should parse the message and force it back to CP437 if d> there is nothing about UTF-8 about it. (For this case, havent seen the d> original message to see if it was UTF-8). Even if there were anything UTF-8 about it, I wouldn't use a UTF-8 CHRS kludge while posting an ANSI. Use CP437, and in not-so-often cases, CP850 if it's a norm on the other side of the pond. Also keep in mind, a lot of people that started with Mystic or Synchronet may not know any better, but where ANSI is displayed fine on their BBS and in their BBSs message bases. Anyone else using Golded, Timed, Msged, any offline readers, or any kind of NNTP readers.. basically anywhere NOT using a BBS that supports reading/writing in message bases, can not view those ANSIs in message bases. Regards, Nick .... "Take my advice, I don't use it anyway." --- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32) * Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0) .