problem with unicode characters.

Question

Hi, I have problem with unicode.. i have multi language project. when i enter the data in local language, in access the data is storing something like this as " ಅಮ್ಮ" but i want those characters of local language to be seen at the bach end..

could you please suggest me ??

am using java, windows vista, and ms-access.. I had set database encoding using properties class n pass it to getConnection method.. Though its not showing what i want.. using like this props.put("charset","utf-8") am using edit-plus editor..

Answer 1

What (programming) language you're using is absolutely vital. Of course, without knowing that, you could still check to make sure all computers you're using the project on are using the same encoding. If you're on a bash shell, you can type echo $LANG and it should probably give you some kind of UTF-8. Bear in mind that many programs, however, will not run in the locale of the shell, but in their own locale (especially C). It's a good idea to know what locale your shell is running, what locale all the programs you use are running, and what that locale means as far as text encoding.

However, that's about as much as I can do without knowing what language your project uses. And, depending on the language, that may be as much as I can help you, but someone else will surely take over for me if we can figure out what language we're working with here.

Answer 2

What text editors are you using? make sure they support Unicode (preferably utf8), also set the database encoding to utf8, and if your language has a special notation for unicode string, use it ( for Java, I think all strings are Unicode, but for example python 2.5 and lower need to use u"...." ).

Answer 3

Is your database configured correctly to use a unicode encoding? It looks like the text is being converted or interpreted incorrectly as a non-unicode format.

Answer 4

You need to check your data at every step, not just by printing it out as a string, but by looking at which unicode characters it consists of. See my debugging unicode page, which is written for C# but can be applied anywhere.

Answer 5

The answer of Jon Skeet is a good one. In addition to that, I want to encourage you to check the whole trip from browser to database, because sometimes the problem is in a really awkward place. In my case, the problem was caused by a bug in the RequestDumperValve in Tomcat.