Characters non English

[Alhambra Eidos Kiquenet]

Hi

I have two updatepanels on an asp.net page and when there is a postback from
one updatepanel it changes the non english characters in the other and
displays some crap instead.

Characters non english like áÃñÑnº1ªäÄàÂ

display like

áÃÂñÑnº1ªäÄà Â

In the web.config file for the project I have the glopalization set to

<globalization fileEncoding="iso-8859-1" requestEncoding="iso-8859-1"
responseEncoding="iso-8859-1" />


Does anyone have any idea to fix this. I've googled this but have not found
any solution yet

Thanks in advance

What about it ?? Bug in vs2005 ???
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=282229

 

[Anthony Jones]

Hi

I have two updatepanels on an asp.net page and when there is a postback from
one updatepanel it changes the non english characters in the other and
displays some crap instead.

Characters non english like áÁñÑnº1ªäÄàÂ

display like

áÃñÑnº1ªäÄà Â

In the web.config file for the project I have the glopalization set to

<globalization fileEncoding="iso-8859-1" requestEncoding="iso-8859-1"
responseEncoding="iso-8859-1" />

How about simply setting requestEncoding and responseEncoding to "UTF-8".
Also check that your files are actually saved as iso-8859-1. If your files
contain literal text which is 'non-english' consider saving them all as
UTF-8 and changing fileEncoding to "UTF-8" as well.

 

[Alhambra Eidos Kiquenet]

Hi mister,

by another reason, I cannot change web.config and I have to use ISO-8859-1.

Another solution using iso-8859-1 ?? thanks.

--
http://www.alhambra-eidos.es/web2005/index.html
www.kiquenet.net
http://www.setbb.com/putainformatica/viewtopic.php?p=843
www.trabajobasura.com/solusoft

 

[Anthony Jones]

Hi mister,

by another reason, I cannot change web.config and I have to use ISO-8859-1.

Another solution using iso-8859-1 ?? thanks.

The first question that comes to mind is why can't the web.config settings
be changed? However...

In that case you must make sure that your files are saved as ISO-8859-1 (or
Windows-1252) which they will be if saves as ANSI on a machine using the
1252 codepage.

You can specify at the page level :-

<%@ Page ... ResponseEncoding="UTF-8" %>

Strictly speaking the AJAX post-backs should be specifying the charset of is
content which will override any global RequestEncoding, however I've never
tested that using a Fiddler trace.