Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Richard Heathfield <rjh@cpax.org.uk>
Newsgroups: sci.crypt
Subject: Re: @ SCOS Message Format ?
Date: Mon, 24 Feb 2025 13:08:49 +0000
Organization: Fix this later
Lines: 48
Message-ID: <vphr11$12o5c$2@dont-email.me>
References: <a936673b2ed0cc59965b531d3bac44b4$1@octade.net>
 <vobg9s$smgg$1@dont-email.me> <vobnr5$tmpm$2@dont-email.me>
 <vobrr2$u49l$2@dont-email.me> <vp8mtf$33amq$1@dont-email.me>
 <vp8pst$33rjg$1@dont-email.me> <vpauc6$3hnj8$1@dont-email.me>
 <vpbr94$3rcsk$1@dont-email.me> <vpc1af$3s42d$1@dont-email.me>
 <vpc3gu$3sf6s$1@dont-email.me> <vpesnp$eqgu$1@dont-email.me>
 <vpeurd$f198$1@dont-email.me> <vphfe9$10s64$1@dont-email.me>
 <vphgvo$118u2$1@dont-email.me> <vphhjl$109m8$3@dont-email.me>
 <vphq95$132l4$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 24 Feb 2025 14:08:50 +0100 (CET)
Injection-Info: dont-email.me; posting-host="660b11caec2332861c3fa1b2145fde54";
	logging-data="1138860"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/+xI15V0AM+dfYPHB7a/RLEnFEYgZJI9tpQajwBKOBcw=="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:jYKwAgouQ2FzXIqUCGOW1AAl3wU=
Content-Language: en-GB
In-Reply-To: <vphq95$132l4$1@dont-email.me>
Bytes: 3154

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