Hi Tomasz, dtterm (and rest of CDE apps) in fact do work with unicode characters, but there are lots of rough edges.
First of all, they do not seem to work with ISO10646-1 encoded XLFD fonts, but require compound font sets , that is each codepage must be provided by separate 8-bit encoded font. Another problem is that dtterm for some reason does not seem use such font sets properly when they are given from command line (or at least I never manged to get it to work). These command lines should work: dtterm -fn 'some font-iso8859-1,some font-iso8859-2,some font-iso8859-3...' or dtterm -fn 'some font-iso8859-*' but I always got something like your second screenshot. However, it does work when CDE is globally configured to use UTF-8, that is by setting the LC_ALL enviroment variable and adding /usr/dt/config/xfonts/en_US.UTF-8/ to font path. Dtlogin does it for you when you choose en_US.UTF-8 as session language. If it does not work for you, check the /usr/dt/config/xfonts/en_US.UTF-8/fonts.alias file. It must define CDE aliases to fonts that exist on your system. The provided file assumes that you have ms core fonts installed and available for X applications as XLFD fonts. In case you want hebrew and arabic (symbols only, RTL is unsupported by underlying Motif library) you may have to add entries for them to /usr/share/X11/locale/en_US.UTF-8/XLC_LOCALE. To give you some encouragement I attach my dtterm screenshot :-) Good luck, Eugene On Sat, Jul 25, 2015 at 11:19 PM, Tomasz Konojacki <m...@xenu.tk> wrote: > Hello, > > I've installed CDE 2.2.3 on 32-bit Slackware today and I have no > problems besides lack of unicode support in dtterm. My LC_ALL is set to > en_US.UTF-8. > > Here's how dtterm launched normally looks like (these strange > characters should read 'ąść' or something like this): > > http://i.imgur.com/hYjj4kK.png > > And that's how it looks launched with "dtterm -xrm '*userFont: > -Misc-Fixed-Medium-R-SemiCondensed--13-120-75-75-C-60-ISO10646-1'": > > http://i.imgur.com/t0zwHNq.png > > Is dtterm supposed to not have unicode support and this is its expected > behaviour, or am I doing something wrong? Google led me to believe > that it's indeed unicode-aware[1][2]. > > [1] - http://docs.oracle.com/cd/E19455-01/806-0169/utf8-107/index.html > [2] - http://sourceforge.net/p/cdesktopenv/mailman/message/31825163/ > > Thanks, > Tomasz > > > > ------------------------------------------------------------------------------ > _______________________________________________ > cdesktopenv-devel mailing list > cdesktopenv-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel >
------------------------------------------------------------------------------
_______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
