uniencode(utf8Text, "unicode") vs uniencode(utf8Text) vs uniencode(utf8Text, "UTF16")
bobs at twft.com
Wed Mar 30 13:34:40 EDT 2011
See, that to me flies in the face of how most functions seem to work. It's understandable that in this instance you cannot expect the function to know or tell what you have in the first place, so passing that in as an argument appears necessary. But as someone else had suggested, what is really needed then is a standard encode function where you pass in what you have and what you want to end up with as arguments. However, as a wise man once said, what it is is what it is.
On Mar 30, 2011, at 10:22 AM, Kee Nethery wrote:
> The uniencode taking something and encoding it into unicode (rather than taking unicode and encoding it into something) explains why uniencode(utf8Text,"unicode") does not work. The second parameter is supposed to be what you have that you want converted into UTF16.
> On Mar 29, 2011, at 5:52 PM, Kee Nethery wrote:
>> Why do uniencode(utf8Text) and uniencode(utf8Text,"UTF16") convert UTF8 text into something whereas uniencode(utf8Text,"unicode") produces no output?
>> Am I doing something wrong or is this a known bug?
>> Kee Nethery
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> I check email roughly 2 to 3 times per day.
> Kagi main office: +1 (510) 550-1336
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode