RE: Storing Devnagari unicode data in MySQL

"Jerry Schwartz" <[email protected]>
Newsgroups gmane.comp.db.mysql.odbc,gmane.comp.db.mysql.general
Message-ID <006e01c801fb$db03d660$910b8320$@com>
Try upgrading to a version 5 of the ODBC connector. It worked for our
Chinese data.

Regards,

Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341

www.the-infoshop.com
www.giiexpress.com
www.etudes-marche.com

> -----Original Message-----
> From: C K [mailto:[email protected]]
> Sent: Friday, September 28, 2007 1:55 PM
> To: [email protected]; [email protected]
> Subject: Storing Devnagari unicode data in MySQL
>
> Namaskar,
>
> I am using Windows Xp SP2 and Mysql 5.0.45 and MyODBC 3.51.19 with
> Microsoft
> Marathi Indic IME 1 version 5.
> I am storing data in both languages i.e. Marathi and English. So I
> changed
> database character set to 'utf8 -- UTF-8 Unicode' and collation to
> 'utf8_unicode_ci'. Also I changed the field properties charset to
> 'utf8' and
> collation to 'utf8_unicode_ci' for all varchar and text fields. I am
> using
> MS Access 2003 as a front-end. When I am entering data in Marathi I can
> read
> and write data in Access tables, but when I am entering data I can view
> data
> in Marathi but after storing it in MySQL tables, I can not read data
> and
> just see question marks for the characters I entered. This is not
> happening
> only when I am storing data using Access as a front-end, but also I
> tried it
> by using other mysqk GUI tools, but i get same wrong results. Can any
> one
> please help me. Please give the reasons behind it and the solution to
> it.
> Thanks for your sincere help.
>
> Regards,
> CPK
>
> --
> Keep your Environment clean and green.




-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.