returnInfield

[Lars Brehmer]

Friedrich

I faced the exact same thing when I set all my fields to unicode  
textFont, which Chinese obviously is. I am uncertain whether you can  
somehow use unicode in the simple returnInfield \  find handler,  
because at the same time I decided to put the text of all card fields  
into custom properties which are only displayed as text in the fields  
when the card is called up.  This led me to a far superior find  
system that marks cards that have the string in the customProps and  
then lists the results in a separate window with buttons that go to  
each card that contains the word, or string, and the label each  
button is the word or string I am looking for.  In my case, you can  
search for an English or an Estonian word, but I choose to have the  
result button labels be the Estonian text, but both are possible of  
course.  This involves using the uniEncode and uniDecode commands I  
got from the kind people from this list, and it is incredibly fast  
and efficient this way.  My project is for Estonian vocabulary -  
when, for example, I search for the English word "get," there are,  
for now, 8 matches (things like get dressed, get ready, get, get  
drunk, etc, so i have 8 buttons with 8 different Estonian labels,  
each one goes to the card in question.  I would be glad to show you  
the various scripts I made that allow this.  Contact me offline, if  
you'd like - I've been dying for the chance to really give something  
back, after gettting so much advice and help!

Lars