Re: @ SCOS Message Format ?

On 24/02/2025 12:56, David Entwistle wrote:
<snip>

I can turn this (dis)functionality off,

Or simply not enable it in the first place.

but many users new to USENET and
encryption will not be aware of what is happening.

Then they have an opportunity to learn. Would you deprive them?

I thiunk an easy compromise is already in place. I'd suggest, as an
introduction, SCOSc, for compatibility with any newsreader, is used
without the punctuation characters. I don't see any issues with that, if
no one finds the idea disagreeable.

I do, for reasons I've already given.

On another subject, reading "A12.1 Trigraph Sequences" of the ANSI
standard version of "The C Programming Language", does that apply to
Strings, at preprocessing - where '??=' gets replaced with '#' etc. during
preprocessing? Sorry if this a stupid question - I'm no longer familiar
with C.

Trigraphs have a very high priority. They are replaced in Translation Phase 1, even before line-splicing.
Here's Translation Phase 1 in full:
Physical source file multibyte characters are mapped, in an implementation-defined manner, to the source character set (introducing new-line characters for end-of-line indicators) if necessary. Trigraph sequences are replaced by corresponding single-character internal representations.
That's except in Thunderbird C, of course. In Thunderbird C, trigraphs are handled just after smiley conversion and just before font serif removal.
--
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within