Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: sci.crypt
Subject: Re: Seriation
Date: Sat, 1 Feb 2025 15:56:54 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 42
Message-ID: <vnlg86$5q26$1@dont-email.me>
References: <vj1pgp$5u55$1@paganini.bofh.team> <vj2fc0$3bbjk$1@dont-email.me> <vj2os2$ch7p$1@paganini.bofh.team> <vj3cil$3keo5$1@dont-email.me> <vj412r$ehh2$1@paganini.bofh.team> <vj4g54$3sqat$1@dont-email.me> <vj4jup$fhf8$1@paganini.bofh.team> <vnkv1g$1vk4$2@dont-email.me> <vnl22r$i3jp$1@paganini.bofh.team> <vnl2m0$2df5$2@dont-email.me> <vnl3fs$i3jp$4@paganini.bofh.team> <vnl5fc$2df5$3@dont-email.me> <vnl67f$iah8$1@paganini.bofh.team>
Injection-Date: Sat, 01 Feb 2025 16:56:55 +0100 (CET)
Injection-Info: dont-email.me; posting-host="0b71cde63adbf7ddd344d1a8f00a5e74";
	logging-data="190534"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/WF2EM1IsElHeD47a9FJTE"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:qQwG2xDXa+3PLCFs2/Xz3qQRCKA=
Bytes: 3114

Stefan Claas <fgrsna.pynnf@vagrearg.eh> wrote:
> Richard Heathfield wrote:
>> On 01/02/2025 12:19, Stefan Claas wrote:
>> 
>> <snip>
>> 
>> > IIRC when encoding with Umlauts etc.  at the same position the 
>> > original Umlauts will be shown.
>> 
>> Yes.  By design, SCOS and SCOS2 preserve not only whitespace but 
>> anything else they have not been told how to process[1].  We have 
>> seen aob come a cropper by making whitespace significant in Usenet 
>> ciphertexts, and that was precisely the problem I was guarding 
>> against, but it also makes sense only to digest text it knows about 
>> and pass through unmodified everything it doesn't, thus making 
>> copy-and-paste ciphertext in an ASCII medium Just Work.
>> 
>> > This should be not the case IMHO.

You may want to return to the original SCOS posting and reread the 
purpose.  SCOS's purpose, and your purpose, are divergent, so naturally 
SCOS will make some choices that your purpose finds to be incorrect for 
your purpose.

>> It is of course your prerogative to disagree with my design, but it is
>> likewise my prerogative to prefer a deliberately ASCII-only design for
>> use in an ASCII environment such as Usenet.
> 
> Well, maybe only a very few US hosting service are ASCII only in 2025,
> but we should ignore them, as Eurasiens ... ;-) I added also the british
> pound sign and Euro symbol. :-)

Reality is that while Usenet /can/ carry UTF-8 encoded text, the vast 
vast majority of non-binaries Usenet (i.e., the 'text' portion) is 
plain ASCII.  This is mostly "self imposed" as most posters self-limit 
to just the ASCII character set.

Note, I'm not saying this is good or bad (and one can make a very 
coherent argument that in 2025 more non-ascii characters should be 
seeing use) -- rather I'm just pointing out the reality of the current 
use of the medium.