From: Mail@JoesLife.org   
      
   Help!   
      
   I'm learning new things, but I don't even have the words to describe what   
   I'm learning.  It all started when I noticed that some characters would   
   appear as annoying dashed boxes.  I tried to ignore them, but I couldn't.   
      
   I did a little poking around and I found uxterm (a command in the form of   
   a script).  I found that if I opened a "uxterm", that it could print the   
   actual characters instead of the dashed boxes.   
      
   Here is some text you can try this on, if you are interested:   
      
   “Hello” — World…   
   € こんにちは α β γ δ ∑ ∆ √ ∫   
      
   On my Slackware 15.0 the above is mostly unreadable when pasted into an   
   "xterm", but fine and good in the "uxterm".   
      
   What I really needed, though was the ability to open "xterms" that could   
   manage text without making the dashed boxes.  Perhaps I could harness the   
   uxterm command for my purposes?  I didn't succeed.   
      
   I did manage, however to modify an existing script of mine making minor   
   changes.   
      
   I started by adding the "-class UXTerm" and "-u8" tricks from the uxterm   
   script to the xterm invocation in my script, but that wasn't enough.  So   
   I removed my old font ("-fn 7x14") and replaced it with   
      
      -fa 'DejaVu Sans Mono' -fs 10   
      
   Then it worked!  My old script had new life and could manage without   
   dashed boxes.   
      
   But then I discovered that with the above font changes I didn't need "-   
   class UXTerm" or "-u8".  The DejaVu Sans Mono font (size 10) alone was   
   good enough.   
      
   So what was going on? And why did uxterm contain code that I didn't need?   
      
   I was (and am) happy to have a solution.  I just wish I had a better   
   understanding to go with it.   
      
   So here I am.  Can anyone help?   
      
   -Joe   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)