I'm guessing that openoffice can do full UTF8, or at least the BMP (the main group of characters).
Maybe the easiest thing is to allow full Unicode in your fields. Then convert that to UTF8 and back for the db. I think folks can help with that. Embrace Unicode. An alternative is to tell the db what character set you are using and the same with openoffice. Dar On May 26, 2013, at 4:02 PM, Dr. Hawkins wrote: > On Sun, May 26, 2013 at 3:01 PM, Dr. Hawkins <doch...@gmail.com> wrote: > >> Hmm, to narrow this: I just need something that livecode & postgres can >> agree upon. With the proviso that people are likely to be pasting into my >> livecode fields >> > > Hmm, and it also needs to be something that openoffice can interpret when > it pulls from a db. > > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > 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
