Re: Unicode under Windows (was RE: Semantics of vector operations)

[Rod Adams]

Austin Hastings wrote:

From: Rod Adams [mailto:[EMAIL PROTECTED]

Question in all this: What does one do when they have to _debug_ some 
code that was written with these lovely Unicode ops, all while stuck in 
an ASCII world?
     

That's why I suggested a standard script for Unicode2Ascii be shipped with the distro.
 

Good Idea, which would also beg an ASCII2Unicode script to reverse the 
process.

Also, isn't it a pain to type all these characters when they are not on 
your keyboard? As a predominately Win2k/XP user in the US, I see all 
these glyphs just fine, but having to remember Alt+0171 for a  
     

is going 
   

to get old fast... I much sooner go ahead and write E<raquo> 
     

and be done 
   

with it.

Thoughts?
     

This has been discussed a bunch of times, but for Windows users 
the very best thing in the US is to change your Start > Settings 
   

Control Panel > Keyboard > Input Locales so that you have the 
     

option of switching over to a "United States-International" IME.

Once you've got that available (I used the Left-Alt+Shift hotkey) 
you can make a map of the keys. The only significant drawback is 
the behavior of the quote character, since it is used to encode 
accent marks. It takes getting used to the quote+space behavior, 
or defining a macro key (hint, hint).
   

(Links Snipped)
 

Thanks for the pointers. I've now set up Win2k so I can easily switch 
between US and United States International. Works nicely.

Now I have to go beat up the Thunderbird guys for trapping the keyboard 
directly and not allowing me to type the chars here.

Thanks Again
-- Rod