put uniencode (url "file:translations.txt","utf8") into tTranslations
is how i'm actually getting the stuff from the text file in the first place, but as I said in my first email, this will not work when when split and set to be the custom property. After using the above uniencode function, I can put tTranslations in a field -- and it will display properly. But when split and made into a custom property, I get no results...
T.
On Thursday, May 29, 2003, at 02:50 PM, Jan Schenkel wrote:
--- Toma Tasovac <[EMAIL PROTECTED]> wrote:[snip]
So: what's happening with unicode in custom properties? Why is this not working? Has anybody made it work with other languages? I'd be grateful for any tips...
All best, Toma
Hi Toma,
Have you tried using the 'uniEncode' and 'uniDecode' functions ? I think one of your problems might be the names of the customKeys containing weird characters, so splitting things might be what's causing the problems here.
Hope these thoughts get you closer to a solution.
Jan Schenkel.
=====
"As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld)
__________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
