Jon Trulson <j...@radscan.com> writes: > On 06/25/2018 07:40 AM, Matthew R. Trower wrote: >> Jon Trulson <j...@radscan.com> writes:
>> Hey, as it turns out, XRandR is supported just fine through the current >> multihead code (as much as multihead works at all, anyway). So that's >> cool news. There's still fair bit of polish left to do on multihead in >> general (and on sizing bugs on single-head...). >> > > Do we actually use Xrandr? I know the DtXinerama stuff I wrote only > uses the XINERAMA extension. In theory, with XRANDR we'd be able to > be notified when screens change resolution, new screens are > added/removed, etc. That kind of stuff would be nice to at least > "play nicely" with. Well, no. XRandR systems provide Xinerama compatibility, so the multihead code we have works fine there (I had previously, erroneously, indicated that it did not). This is all I meant. >> CDE actually does run under en_US.UTF-8 locale (this is primarily how I >> run it). Some things are broken --- some of the man pages render a >> little funny, dtinfo main library browser doesn't know what directory to >> pull documents from (although auxilliary components appear to work >> fine). > > Well, I need to understand this more. It sort of works, but doesn't. > I think it's more a hack to just get UTF8 fonts to work... I'm not > clear. Certainly none of the docs are en_US.UTF-8, and many things do > not work (font-wise), like as you mention dtterm. How the greek support you mentioned in another thread relate to this? I'd completely forgotten that we had that. Is it considered a complete working UTF-8 environment? >> I expect that dtterm is not multi-byte capable. > > I know dtterm is MB capable - I remember spending a lot of time > getting the Japanese locales working in the "old days". I remember > there were bugs, but it worked fairly well. dtterm is an odd beast - > try running that in a en_US.UTF-8 locale outside CDE and it's clearly > not doing the right thing, so definitely some work still needs doing > there. Oh, that's excellent --- I had feared this might be difficult to implement. If that's already done... well, maybe I'll have a look at en_US.UTF-8 sooner rather than later. LANG C isn't really an option for me. -mrt ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
