Subj : Re: Sixels
To   : Warpslide
From : AKAcastor
Date : Wed Mar 20 2024 15:27:54

 W> I used your instructions and converted the apod to .six 
 W> and tried displaying it with Mystic logged in via 
 W> Syncterm but all I got was a wall of text.

Hmm, well a wall of text does sound right for a terminal client that doesn't support sixels - but SyncTerm should display them. (have you confirmed on another BBS that your copy of SyncTerm has sixel support enabled?)

 W> I'm wondering if Mystic doesn't support them or maybe 
 W> there's something else I need to do?

I haven't used Mystic so I don't know if there's any kind of special case there.  On my Maximus system, I am able to just display the sixel file as though it was a text file and the client is able to interpret it.  Maximus itself doesn't recognize sixels but it passes the contents along as it is plain ASCII text.


FYI - Detecting if the connected caller's terminal has sixel support isn't too difficult, but from my tests different terminals respond to different queries.

"\x1b[4c" works with iTerm2
"\x1b[<0c" works with SyncTerm

Read the response which should end with 'c'.  If the response has ;4 in it then
that indicates that sixel is supported.

For sixel detection on my BBS, I send both strings ("\x1b[4c\x1b[<0c") and read
until I receive a 'c' (or time out after a second or two).  If I find ";4" in
the response then I assume sixel support exists.


Chris/akacastor

--- Maximus 3.01
 * Origin: Another Millennium - Canada - another.tel (21:1/162)

.