Subj : Re: 100th Anniversary of the Theremin
To   : Charles Pierson
From : Wilfred van Velzen
Date : Tue Dec 08 2020 21:49:03

Hi Charles,

On 2020-12-08 20:21:24, you wrote to August Abolins:

 AA>> Most of the time the "problem" is the two forms of single and double
 AA>> quotes (since there is a an open quote and a closed quote look for
 AA>> each) and the ellipses.
 AA>>
 AA>> Put your quoted material into something like "Notepad++" with an
 AA>> intitial setting ANSI, and then toggle it to UTF-8.  The problem chars
 AA>> will then be obvious:
 AA>> .
 AA>> https://brorabbit.g0x.ru/pic/5fcfcdbb.jpg

 CP> OK. There isn't a text editor for Android which I have found yet that
 CP> does ANSI. Most default to UTF8 although I have found one that has
 CP> USASCII, which does make a mess of some of the characters.

 CP> However, on my MysticBBS board here, which reads the message fine, leads me
 CP> to believe that UTF8  isn't the issue. It must be the lack of CHRS: kludge
 CP> that Wilfred mentioned.

Well if you were using regular quote characters, or could somehow easily convert to them, the ommision of the CHRS kludge line would be ok. And it would be the solution I would prefer, because plain ascii is readable by everybody, while utf-8 is not (even with the kludge).

 CP> Dealing internationally as we are there are always going to be some
 CP> characters that don't always translate correctly.  The name Bjorn, when
 CP> spellled properly doesn't come across correctly, nor does most Cyrillic.

If you indeed want to use those characters, plain ascii won't do...

 CP> So, apparently, I need to find out why these messages are lacking that
 CP> Kludge.

Probably this is why:

 CP> --- Mystic BBS v1.12 A46 2020/08/26 (Raspberry Pi/32)

;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)

.