In message <[EMAIL PROTECTED]> on Wed, 17 Jan 2007 16:21:32 +0100 (CET), Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> said:
richard> After having looked through programs like xfontsel and xterm, richard> it seems like the UCS (UTF-8) interpretation somewhere in X richard> (on the server side, I guess) is a little bit lacking. richard> xfontsel converts all UCS codes to Char2b internally, and it richard> looks like xterm does the same, perhaps (the code looks a bit richard> contorted). I've done a lot of experiments, using XwcDrawString(), and saw the exact same problem with the damn apostrophe (U+2019) as with XmbDrawString(). I've talked to others, and everyone seems to agree this is a font problem. We are handling a font *set*, and some fonts may not have all characters while others do, so it's difficult to say where that apostrophe comes from. It's quite possible we need to do the workaround that xterm does with certain characters (U+2019) among others, probably because we're not the only ones ending up with this problem. richard> So ctwm currently get certain characters displayed correctly, richard> such as Zvi's apostrophe. That was supposed to say *in*correctly. So, for now, I'm simply leaving this alone and will take care of other stuff in the RT database. Then, I'm thinking it might be time to release 3.8. Speaking of releases, I'm wondering what else we might want to do with ctwm? There were some atoms that needed supporting, wasn't there? I'm not going to dig through my email folder searching for those right now, but might in the future. Please remind me, that would help a lot! Cheers, Richard
