Hi Maurice!

04 Jun 2018 13:52, from Maurice Kinal -> Richard Menedetter:

 RM>> Take a look at FTS5003 http://ftsc.org/docs/fts-5003.001
 MK> I was waiting for you to bring that up.
 MK> The FTSC is not an official body in this case since it holds no claim
 MK> to any character set or encoding.

It defines a fidonet kludge, and clearly states what character set it should be
 encoded/decoded to.
The character set in this case is  "ISO 8859-1 (Western European)"
ISO is a standards organization that DOES standardize character encodings.

It is pretty clear to me.
And maybe you too also have the imagination to delete the dash in your mind.

Let us not debate as of why they inserted the dash there ... it is like it is.

 MK> I noticed you say in a reply to mark lewis;
 RM>> Very view editors will display the extended characters correctly.
 MK> No sh*t!!!  Anyhow vim has absolutely no problems with CORRECTLY
 MK> identified character sets including LATIN1.  ;-)

As you know very well, the problem is not with identifying the character set.
(actually the UTF-8 CHRS kludge is defined and would be perfectly fine to
identify the charset.)
The problem is that most software was written before UTF-8 was defined.
So what we need is an editor that supports UTF-8.
But even if we have that ... this would mean that all others still see garbage.

For English/German LATIN(-)1 covers the bases.
(I am also speaking Hungarian that would require LATIN(-)2 ... but I have
nobody left in Fidonet that speaks that language ... end even if there were
somebody I mostly omit long vocals, so that LATIN(-)1 would be sufficient
there.

CU, Ricsi

--- GoldED+/LNX
 * Origin: The swiftest horse cannot overtake a word once spoken. (2:310/31)