Are you getting the data you send to Qooxdoo from a database backend? If so, this also might mess up your encodings. What works best for me using PostgreSQL is:
- Have the database be in UTF8 - Set pg_enable_utf8=>1 in your DBI connect statement - If using strings with none-ASCII from files, make sure to save the file UTF8-encoded. If you need to change the encoding, use the http://search.cpan.org/~dankogai/Encode-2.49/Encode.pm module. Apart from that, I find character encoding extremly cumbersome, never knowing what part of my program and terminal layers are messing things up ... Cheers, Fritz When using DBI, you mi On Mon, 15 Apr 2013, Oleksandr Shneyder wrote: > Hello all, > > I have Unicode issue with perl-rpc server: > > http://qooxdoo.org/contrib/project/rpcperl > > all unicode strings, that RPC-Server returning to application, have > wrong encoding. I can avoid this problem if I encode string with base64 > on server and then decode it in qooxdoo application. But I wonder if > there is a better solution for this issue. > > regards, > Alex > > PS: with python RPC-Server all works just fine. But I really want to use > perl RPC-Server. > -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker +41 62 775 9900 (switch board) Aarweg 15 +41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
