Re: libxt and other applications porting to libxcb

Hi,
The reason for libxaw3dxft is because it is the closest Xaw version that allows
extended fonts, which is a step towards internationalization. 2 reasons why Xaw
is considered obsolete, aside from the state that X11 is in, is lack of
internationalization, and lack of accessibility. Internationalization is
addressed in that. There's many applications which are commonly installed with
X11 anyway, which use libx11. At this point, libxaw3dxft couldn't completely be
ported to libxcb, because there lacks a completed font library in xcb.

Converting libxaw3dxft to libxcb, would allow other unported programs to
continue to use libxaw or libxaw3d.

libxaw3dxft was in a repository of xpaint, however, it's a direct fork of
libxaw3d, and this library is permissively licensed. xpaint was still GPL, but
that has no effect on libxaw3dxft. This program has recently moved from
SourceForge to Github, with a different maintainer. qt and gtk have good
licenses using LGPL (which allows more widespread use than simply GPL), however,
the libxaw family have licenses which are further permissive like most of the
rest of the Xorg repository.

From the old SourceForge repository that contained xpaint, there were also
patches for xaw programs to work with libxaw3dxft.

I take it that, porting libxt and libxaw3dxft to libxcb would mean having a
parallel library which runs alongside libx11. It would be cool to see a legacy
suite go to its full potential in something that at one time was meant to go
towards libxcb.

Maybe a future fork which intends to keep the x11 client alive for computer
systems which won't move to Wayland or which will use Wayland with an x client
shim will be able to do this.

Thank you