Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.c
Subject: Re: Rationale for aligning data on even bytes in a Unix shell file?
Date: Thu, 15 May 2025 07:33:07 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 44
Message-ID: <10045bj$30sk8$3@dont-email.me>
References: <vuih43$2agfa$1@dont-email.me> <vunbgo$2q5u8$1@dont-email.me>
	<vunbjg$2q72n$1@raubtier-asyl.eternal-september.org>
	<vund1f$2rh3j$1@dont-email.me>
	<vungko$2uoa2$1@raubtier-asyl.eternal-september.org>
	<X9MPP.1383458$f81.819466@fx48.iad>
	<vuobri$3o38b$1@raubtier-asyl.eternal-september.org>
	<XtOPP.2986761$t84d.2537581@fx11.iad>
	<vuohq9$3tlhf$1@raubtier-asyl.eternal-september.org>
	<vuoig5$3ub4j$1@dont-email.me>
	<vuorpf$6tnn$1@raubtier-asyl.eternal-september.org>
	<vup2nt$bi1k$2@dont-email.me>
	<vupofl$13pg2$2@raubtier-asyl.eternal-september.org>
	<vuprce$15sqo$2@dont-email.me>
	<vvd6n5$353gs$1@raubtier-asyl.eternal-september.org>
	<vvfbnj$ulpc$1@dont-email.me> <vvflec$11b72$1@dont-email.me>
	<20250507202430.00005bb9@yahoo.com> <vvh8qg$1ha26$2@dont-email.me>
	<vvi3k6$1o09d$1@dont-email.me> <vvj3qe$246ff$1@dont-email.me>
	<87v7qaerg8.fsf@nosuchdomain.example.com> <vvjg9u$28sh0$1@dont-email.me>
	<vvjp47$2bbhn$6@dont-email.me> <vvlfi7$2uri7$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 15 May 2025 09:33:07 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="bb7a4fad6b7693240fa122d276703f33";
	logging-data="3175048"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/pv10uIV7RgWlZMm2WWA3C"
User-Agent: Pan/0.162 (Pokrosvk)
Cancel-Lock: sha1:5wVIo3Rpp6SX7cZ4/nUgxVPo510=
Bytes: 3796

On Fri, 9 May 2025 12:50:10 -0500, BGB wrote:

> On 5/8/2025 9:26 PM, Lawrence D'Oliveiro wrote:
>>
>> On Thu, 8 May 2025 18:50:33 -0500, BGB wrote:
>> 
>>> But, I don't bother with C1 control codes, as they are unused ...
>> 
>> Mostly true. But I think terminal emulators do interpret CSI as
>> equivalent to ESC followed by “[”.
>> 
> Possibly, though generally, ESC+[ is used IME.

Actually, several other C1 controls are also defined as equivalents to 
sequences beginning with ESC.

> Also creates uncertainty, as AFAIK the terminals traditionally operate
> on raw bytes regarding ANSI commands, whereas if the terminal interface
> is UTF-8, a CSI (as a 2-byte encoding) would not be equivalent to 0x9B
> (if encoded as a single byte).

Yeah, I just checked KDE Konsole, and it doesn’t interpret 0x9B (CSI) as 
equivalent to 0x1B followed by “[”.

I suppose I should check if changing the encoding makes any difference to 
this ...

> I was thinking here more of a GUI based editor or pseudo-word processor;
> where Text + ANSI codes could, in theory, serve a similar role to the
> RTF format, although more as extended text rather than a sort of markup
> language (though, modern word processors typically use XML internally,
> as opposed to the more unusual markup scheme that RTF had used).

There’s an old thing called “sixel graphics”, which DEC invented back in 
the day. I found out KDE Konsole supports it! I think some other terminal 
emulators do, too. There is a libsixel library that allows converting 
image formats. You only get 256 colours maximum, but that is still 
potentially quite useful.

> Sometimes, it would also be nice if there was a sort of a standalone
> graphical viewer/editor that used MediaWiki or Markdown or AsciiDoc or
> similar.

    pandoc -f markdown -t pdf «infile» | okular - &