Unicode and the higher planes of existence.

[Richmond]

So there I am wondering about the higher plains (the svarga-lokas . . . 
LOL), so I try
this:

I make a stack with 2 buttons (called 'button 1' and 'button 2' 
respectively)
and 2 fields (called 'f1' and 'f2' repectively) and put the following 
code into button 1:

on mouseUp
   set the useUnicode to true
   set the unicodeText of fld "f1" to numToChar(65940)
end mouseUp

and when I click on the button I get nothing like anything that should 
appear (a capital X with a bar through its middle),
but something that resembles a badly deformed Hebrew 'Ain'.

in button 2 I put the following script:

on mouseUp
   set the useUnicode to true
   put charToNum(fld"f1") into fld "f2"
end mouseUp

and get "404", which is, indeed a sort of funny 'Ain'.

This would seem to suggest 2 things:

1. RR/LC cannot cope with Unicode addresses above the first plane.

2. RR/LC copes with this by truncating the addresses.

Does anybody know of a work around for this?

[this does not affect my work directly, but does interest me both in 
terms of future work, and
relating to the capabilities of RR/LC in general]

Richmond.