Re: requestEncoding = "ISO-8859-1"

I placed the META tag in the .html page, not the .aspx page, and this
appears to have solved the problem. I have attached the HTML in a text
file, as this email was not very excited about holding html tags. It
includes several Spanish words - don't get too caught up in my inability to
write a coherent sentence. Thank you!

HOWEVER - I'm still baffled on what is the RIGHT solution. Do I hard code
UTF-8 into the meta tag of every form our staff creates? Or do we just
change our web.config to support ISO-8859-1 instead of UTF-8? Both smell
like hacks...

Thanks again.

Mark



"Juan T. Llibre" <nomailreplies@xxxxxxxxxxx> wrote in message
news:%23zO1oPELGHA.3972@xxxxxxxxxxxxxxxxxxxxxxx
Joerg,

We've had this conversation before, but never resolved it.

What I've found, in my experience, is that ASP.NET settings take
precedence over HTML settings and, thus, utf-8 doesn't display
characters 128-255 as you say itshould.

If I include
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
in an aspx page source, the setting which prevails is the one specified
in web.config.

Can you post a complete page example which proves what you're saying ?



Juan T. Llibre
ASP.NET MVP
ASPNETFAQ.COM : http://www.aspnetfaq.com
==================================
"Joerg Jooss" <news-reply@xxxxxxxxxxxxx> wrote in message
news:94fc5071122c48c7fa53174ba20a@xxxxxxxxxxxxxxxxxxxxxxx

Don't be. All that happens is that your HTML form likely doesn't specify
any encoding, thus your
browser assumes ISO-8859-1 by default (check your browser's encoding
option after loading the
form!).
HTML 4.01 even includes an attribute to specify the character encoding
for a submitted web form
("accept-charset"), but last time I checked it was practically
unsupported. What happens instead
is that the original response encoding (ISO-8859-1 assumed if not
specified) is used as subsequent
request encoding.

Therefore, simply mark your static HTML as UTF-8 encoded as well (and of
course encode them
physically using UTF-8 as well!):
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">

That should do the trick.
Joerg Jooss




begin 666 sample_utf8_html_aspx.txt
M[[N_/"%$3T-465!%($A434P@4%5"3$E#("(M+R]7,T,O+T141"!(5$U,(#0N
M,"!4<F%N<VET:6]N86PO+T5.(CX-"CQH=&UL/@T*"3QH96%D/@T*"0D\=&ET
M;&4^/"]T:71L93X-"@D)/&UE=&$@8V]N=&5N=#TB36EC<F]S;V9T(%9I<W5A
M;"!3='5D:6\@+DY%5" W+C$B(&YA;64](D=%3D52051/4B(^#0H)"3QM971A
M(&-O;G1E;G0](E9I<W5A;%-T=61I;RY(5$U,(B!N86UE/2)0<F]G260B/@T*
M"0D\;65T82!C;VYT96YT/2)-:6-R;W-O9G0@5FES=6%L(%-T=61I;R N3D54
M(#<N,2(@;F%M93TB3W)I9VEN871O<B(^#0H)"3QM971A(&AT=' M97%U:78]
M(D-O;G1E;G0M5'EP92(@8V]N=&5N=#TB=&5X="]H=&UL.R!C:&%R<V5T/554
M1BTX(CX-"@D\+VAE860^#0H)/&)O9'D^#0H)"3QF;W)M(&YA;64](DUY1F]R
M;2(@86-T:6]N/2)&;W)M4F5C96EV92YA<W!X(B!M971H;V0](G!O<W0B($E$
M/2)&;W)M,2(^#0H)"0D\4#Y7:&%T)W,@>6]U<B!N86UE/SH@/$E.4%54(&ED
M/2)T97-T,2(@='EP93TB=&5X="(@;F%M93TB=&5S=#$B('9A;'5E/2+"OTUA
MP[%A;F$@<\.S;&\@<,.A9VEN87,@96X@97-P8<.Q;VP_(CX\+U ^#0H)"0D\
M<#Y497-T,CH@/&EN<'5T(&ED/2)T97-T,B(@='EP93TB=&5X="(@;F%M93TB
M=&5S=#(B('9A;'5E/2+8I]F$V+/8N=F(V*_9BMBI(CPO<#X-"@D)"3Q0/CQ)
M3E!55"!I9#TB4W5B;6ET,2(@='EP93TB<W5B;6ET(B!V86QU93TB4W5B;6ET
M(B!N86UE/2)3=6)M:70B/CPO4#X-"@D)"29N8G-P.PT*"0D\+V9O<FT^#0H)
M/"]B;V1Y/@T*/"]H=&UL/@T*#0HM+2TM+2TM+2T@05-06"Y#4R!004=%("TM
M+2TM+2TM+2TM+2TM+2TM+0T*#0IS=')I;F<@5&5S=#$@/2!297%U97-T6R)T
M97-T,2)=.PT*4F5S<&]N<V4N5W)I=&4H(CQB<CY497-T,2!O=71P=70Z("(@
M*R!497-T,2D[#0H-"G-T<FEN9R!497-T,B ](%)E<75E<W1;(G1E<W0R(ET[
M#0I297-P;VYS92Y7<FET92@B/&)R/E1E<W0R(&]U='!U=#H@(B K(%1E<W0R
&*3L-"@T*
`
end

.

Relevant Pages

  • Re: Where to get BeautifulSoup--www.crummy.com appears to be down.
    ... Beautiful Soup uploaded to my website: ... obtaining a sensible parse tree in the face of common HTML errors. ... the encoding of an HTML or XML document, ... appears after this Tag in the document.""" ...
    (comp.lang.python)
  • Re: requestEncoding = "ISO-8859-1"
    ... What I've found, in my experience, is that ASP.NET settings take ... All that happens is that your HTML form likely doesn't specify any encoding, ... HTML 4.01 even includes an attribute to specify the character encoding for a submitted web form ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Character encoding
    ... a lot of editors allow to choose the text encoding ... that in my html code i have to set manually. ... There is a little confusion here: the way a text editor encore the ... HTML can contain a meta tag that specifies the encoding, ...
    (Fedora)
  • Re: Why is ASP.NET changing character encoding of documents?
    ... My default encoding in web.config was iso-8859-1. ... The web.config setting takes precedence over the meta tag. ... >> The below html validates correctly on w3.org's html validator when the file ... >> error below from the validator. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: requestEncoding = "ISO-8859-1"
    ... I placed the META tag in the HTML form file. ... Sorry - how does one encode them physicially using UTF-8 ... I need to pick an encoding that is capable of representing the character 'ö' like UTF-8 or ISO-8859-1. ... But of course one thing always remains true: You must not declare in your HTML page's META tag an encoding that's different from the one you used to save the file. ...
    (microsoft.public.dotnet.framework.aspnet)