Elver Loho wrote: > On 3/7/06, Stefan Hornburg <suppressed> wrote: > >>Elver Loho wrote: >> >>>Hiya! >>> >>>We have a problem here implementing i18n support for our webshop. That >>>is, right now, things 'work' in that we have a MySQL database with all >>>our products in it, including some product names in Russian. >>>(Cyrillic, UTF-8 fields.) >>> >>>However, on the MySQL side, those database fields are currently set as 'latin1'. >> >>I recommend to store UTF-8 as UTF-8 and go from there. Interchange might cause >>trouble them, but we can fix that side. And IMHO it is most important that your >>data base is clean. > > > Um, dude. That's the problem right now with our new table. We're > storing UTF-8 text as UTF-8 in the database. Interchange doesn't issue > 'set names utf8' or 'set character set utf8' in order to read those > fields. How can we tell it to? Hm, I assumed that MySQL returns UTF-8 automatically in your case. Which software versions do you use (MySQL, Perl, DBI, DBD::mysql) ? Bye Racke _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.