0

I face the following problem :

I have an .aspx page when i copy a gridview from page to another ,i encounter the following problem :

i have some arabic words like this :

رقم اذن الإضافة

It has turned to :

رقم اذن الإضافة

My master page meta data :

 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

How to fix this problem

all arabic data have turned to those strange characters and numbers!! just in design time

,However in run time every thing goes okay .

But when i try to edit , i take a lot of time to detect the right control ! How to fix this problem without rewriting all these arabic characters again ?

Anyname Donotcare
  • 11,113
  • 66
  • 219
  • 392

1 Answers1

2

You would need to use UTF-8 or Windows-1256 encoding for it to show properly, see for example What character encoding should I use for a web page containing mostly Arabic text? Is utf-8 okay?

Community
  • 1
  • 1
jtheman
  • 7,421
  • 3
  • 28
  • 39
  • if i change the metadata to `UTF-8 or Windows-1256` the data will change to the correct one automatically ? – Anyname Donotcare Apr 18 '13 at 08:28
  • the probelm is in design time not on runtime – Anyname Donotcare Apr 18 '13 at 08:40
  • 1
    It can be a little tricky when encoding is inconsistent in the workflow. I recommend using the same encoding through the whole process. Sometimes I just open my standard texteditor and resaves the script file with the correct encoding. If you have an aspx file saved with ISO-8859-1 it will not recognize the contents correctly if you paste in data with for example UTF-8 encoding, or the other way round. You might also have the file saved as Windows-1256 but then showed as ISO (from your META tag). It will affect design but not runtime... – jtheman Apr 18 '13 at 08:57
  • Thanks a lot .`It will affect design but not runtime` but how to fix the design time without writing from the scratch with the correct encoding – Anyname Donotcare Apr 28 '13 at 07:45
  • 1
    Hello again. If you encounter problems that encoding is working in some situation but not in another then there IS encoding inconsistency in your workflow. Find the anomaly and your problem is solved! – jtheman Apr 28 '13 at 20:53