On Tue, Feb 10, 2026 at 07:48:03AM +0000, Stuart Henderson wrote:
> moving to ports@
> 
> On 2026-02-09, Hugo Villeneuve-Lapointe <hugo@EINTR.net> wrote:
> >
> >
> > I guess I missed the part where this thread lead to luit being removed post
> > 7.8:
> >
> > ----------------------------
> > revision 1.6
> > date: 2025/11/16 19:02:33;  author: matthieu;  state: dead;  lines: +0 -0;  commitid: WvvKs4N8tZSposfc;
> > Remove luit. Already disabled in xterm and unlinked from the build.
> > ----------------------------
> >
> >
> > I just wanted to say I have a niche use for luit.
> >
> > I use luit every time I connect to ancient unix/linux/bsd versions.  To make
> > sure my keyboard doesn't leak UTF-8 codes into systems that cannot deal with
> > it, but can do 8 bits encodings.
> >
> >
> > like: 
> >
> >   luit -encoding 'ISO8859-1' telnet host
> >   luit -encoding 'ISO8859-1' plink -1 host
> >
> >
> > Anyway, that's just me and my odd hobbies and French language.  Definitively
> > not a critical usage.
> >
> >
> > I'll just have to figure out a recipe to compile it on my own from
> > -rOPENBSD_7_8 sources.
> 
> It looks easy enough to add to ports. Does this work for you?
> 

Ok.  but we will not bring back luit(1) support in xterm(1). it will
only be usable in scenarios like the above (or if someone enables luit
support in one of the existing terminal emulators in ports (but none
seem to have that feature).

Also "converters" may be a better CATEGORY
-- 
Matthieu Herrb