That is what I thought. I believe my 'discussion' was centered around that documentation and everything I've posted lately deployed CHRS kludges that are indeed covered by that particular document.
MvdV> Same for other character sets like CP437, Latin 1 or ASCII.
I beg to differ. I see all those and more. I don't see UTF-16 or UTF-32 though but do see UTF-8 which doesn't require a BOM for identification.
MvdV> it is not a matter for the FTSC.
Perhaps not the BOM but certainly something worthy of discussion as character sets supported by fts-5003 as they pertain to usage in the Fidonet community and this particular echo flying an echotag FTSC_PUBLIC. From my perspective from the public part, I see nowhere else for such a needed conversation.
Having said that I am ready to concede and have discovered all I need to know about character sets and their usage in Fidonet. I hereby promise not to bring it up any more.
Life is good, Maurice
... Don't cry for me I have vi. --- GNU bash, version 4.3.11(1)-release (x86_64-unknown-linux-gnu) * Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)
