Hi Dan,
As for character's parsing and displaying, it is depend on charset/encoding
rather than culture. Also, 156 is apparently a non-ASCII char(larger than
128) so such char will has different codepoint in different
charset/encoding schema. So what's the charset you're using in your
application to parse text data? I've saw that the code seems contain the
"windows125 2", I assumed that you're using this. Then, you should
explicitly use this encoding schema to parse byte to string or convert
string to byte stream. e.g:
=============== =============== ==
protected void Page_Load(objec t sender, EventArgs e)
{
Encoding enc = Encoding.GetEnc oding("Windows-1252");
string txt = enc.GetString(n ew byte[] { 156 });
Response.Write( "<br/>156: " + txt);
}
=============== =============== ===========
Here are some other related tech articles:
http://www.codeproject.com/aspnet/En..._in_ASPNET.asp http://samples.gotdotnet.com/quickst...eencoding.aspx
Hope this helps.
Regards,
Steven Cheng
Microsoft Online Community Support
=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
