Thanks Dave and Paul for the QCC report. The ability to automatically detect encoding would really make the "it just works" phrase be more in line with reality, even if it's not right 100% of the time. It would be interesting to know how many of the possible encoding cases might cause guessEncoding to come up with the wrong answer.
In my case, I'm dealing with an SQLite database and there's a PRAGMA statement that tells me when the encoding is. However, I also have to deal with importing csv files where a guessEncoding function would really help. Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Fri, Jan 30, 2015 at 8:25 AM, Dave Kilroy <d...@applicationinsight.com> wrote: > Update: Paul Depuis has submitted an enhancement request, commented on the > Unicode blog posting and got a reply from Fraser (who suggested a > guessEncoding function). More details at > http://forums.livecode.com/viewtopic.php?f=68&t=22949&p=118538#p118538 > > > > ----- > "Some are born coders, some achieve coding, and some have coding thrust > upon them." - William Shakespeare & Hugh Senior > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/Unicode-tp4688182p4688299.html > Sent from the Revolution - User mailing list archive at Nabble.com. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
