On 27.05.2013 at 14:45 Uhr -0700 Dr. Hawkins apparently wrote:
The error was that on a curly-quote that originated at http://www.leg.state.nv.us/NRS/NRS-021.html#NRS021Sec090 (in "miner's") threw the error. I also got it from double-curly quotes that came from somewhere. If I can limit livecode fields to UTF8, I think it solves my problems.
Are the tables and fields in your postgres database set to unicode encoding, and UTF8 not UTF16, since this is what you are feeding there?
Robert _______________________________________________ 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
