Subj : Re: Default Character Set when none is defined
To : Rob Swindell
From : Scott Street
Date : Tue Jun 03 2025 09:28 pm
On 03 Jun 2025, Rob Swindell said the following...
RS> Here's what FTS-5003 says about that:
RS> Incoming messages without "CHRS" control lines should be considered
RS> as being written in pure ASCII, but may be treated as being written
RS> in some default character set or character encoding scheme. Such as
RS> IBM codepage 437, IBM codepage 866 or UTF-8. It is recommended that
RS> message readers offer the user the option of manually selecting a
RS> different character set or encoding scheme for these messages on a
RS> per-area, per-message or other basis.
Perfect. I missed that reading the docs; but it does spell out what I had thought.
RS> Interesting question. Are you actually finding non-ASCIi chars in kludge
RS> lines? I'd be curious what those are (the kludge lines/values).
No, not in my small, about 500 messages sample; but I wanted to be prepared.
RS> Maybe FTSC_PUBLIC would be more appropriate for FTN development
RS> questions. I seem to recall a NET_DEV echo too, though I don't think it
RS> gets much participation.
Indeed, thanks for those. I thought I remembered echos specific for development, it's been a while.
Thanks for the reply.
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: <=-{ The Digital Post }-=> (1:266/625)
