Hello Dhaest,
I have to use windows-1256 because I have a full database of windows-1256 encoded characters. Those characters were used by my old ASP application which is now being converted to ASPX. At the moment I can't think about any method which quickly converts those characters to unicode, but that would be another good solution to come out from this problem.
I have tried the web.config changes you suggested but I keep getting unreadable characters.
Main Topics
Browse All Topics





by: DhaestPosted on 2007-09-24 at 01:54:12ID: 19947086
Do your really have to use windows-1256? Just sticking with UTF-8 is so much more convenient.
256" responseEncoding="windows- 1256" />
/aspnet/En coding_in_ ASPNET.asp ? df=100&fo rumid=3626 4&exp=0&se lect=16440 26
Well, there are quite a few places where encoding comes into play. Have you made the change in web.config?
<globalization requestEncoding="windows-1
Using Character Encoding in ASP.NET
http://www.codeproject.com