Encoding Hawaiian Characters

I'm having difficulty outputting Hawaiian characters from my TPL. Characters such as okina (‘) and kahako (ō) render as "â€˜" and "Å�" respectively. However, I can open the outputted aspx page in Notepad, save out in UTF-8, and it will render as intended.

Notes:
- TPL uses proper meta tag: <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- iwpt_encoding.ipl set to UTF-8
- Fields are *not* VisualFormat
- Characters defined in Unicode 5 standard, okina = ʻ

Any ideas what I could be doing wrong?

Win TS 6.7.1 SP 1 / P1

Find more posts tagged with

Comments

ISCBorisB

I'm having difficulty outputting Hawaiian characters from my TPL. Characters such as okina (‘) and kahako (ō) render as "â€˜" and "Å�" respectively. However, I can open the outputted aspx page in Notepad, save out in UTF-8, and it will render as intended.

Notes:
- TPL uses proper meta tag: <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- iwpt_encoding.ipl set to UTF-8
- Fields are *not* VisualFormat
- Characters defined in Unicode 5 standard, okina = ʻ

Any ideas what I could be doing wrong?

Win TS 6.7.1 SP 1 / P1

How did you specify "ResponseEncoding" in the Web.config?
Note that if your global specification is not UTF-8, you can set it per Page:
<%@Page ... ResponseEncoding="utf-8"%>

access.zip

Gregg Faus

Actually I failed to note that. I tried adding both a global and page level setting.
web.config: <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
OR
Page: <%@ ResponseEncoding="utf-8" %>

Neither worked.

ISCBorisB

Actually I failed to note that. I tried adding both a global and page level setting.
web.config: <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
OR
Page: <%@ ResponseEncoding="utf-8" %>

Neither worked.

Save attached html File somewhere and try to render it. What do you see?
I can see this "okina" stuff, screen-shot enclosed as well

Gregg Faus

What do you see?

Ah, you've got me pointed in the right direction. I saved the attachment out as .htm and .aspx. It rendered fine in HTML, but not ASPX. Somehow the asp.net 2.0 runtime is affecting the output.

Gregg Faus

One more follow-up. Looking with Fiddler I was able to determine one difference between the HTTP header info being sent by IIS. See the difference in bold below:

boo.aspx >
HTTP/1.1 200 OK
Date: Thu, 27 Mar 2008 21:02:46 GMT
Server: Microsoft-IIS/6.0
Cache-Control: private
Content-Type: text/html; charset=utf-8
Expires: 0
Set-Cookie: IWPROXY_PATHTRACK=/iw-mount/default/main/projects/maunakea/WORKAREA/client/web/public_involvement/boo.aspx; path=/
X-AspNet-Version: 2.0.50727
x-iw-ts-vpath: /default/main/projects/maunakea/WORKAREA/client/web/public_involvement/boo.aspx
X-Powered-By: ASP.NET
x-teamsite-url-rewrite: true
P3P: CP="CAO PSA OUR"
Transfer-Encoding: chunked


boo.htm >
HTTP/1.1 200 OK
Date: Thu, 27 Mar 2008 21:03:25 GMT
Server: Microsoft-IIS/6.0
Accept-Ranges: bytes
Cache-Control: no-cache
Content-Type: text/html
Expires: 0
Set-Cookie: IWPROXY_PATHTRACK=/iw-mount/default/main/projects/maunakea/WORKAREA/client/web/public_involvement/boo.htm; path=/
x-iw-ts-vpath: /default/main/projects/maunakea/WORKAREA/client/web/public_involvement/boo.htm
X-Powered-By: ASP.NET
x-teamsite-url-rewrite: true
P3P: CP="CAO PSA OUR"
Transfer-Encoding: chunked

The HTML version is not sent with the charset=utf-8 in the "ContentType" header.