Tim Mackey's Weblog
mostly.Net
|
|
Search
Categories
.Net Compact
.Net General
.Net Windows Forms
Asp.Net
Database
General
Mobile
Outdoors
Windows Server 2003
Archive
June, 2010 (2)
May, 2010 (1)
September, 2009 (1)
April, 2009 (1)
March, 2009 (1)
February, 2009 (2)
January, 2009 (1)
December, 2008 (2)
October, 2008 (2)
September, 2008 (1)
August, 2008 (1)
July, 2008 (1)
May, 2008 (2)
April, 2008 (2)
March, 2008 (2)
January, 2008 (4)
December, 2007 (1)
November, 2007 (4)
October, 2007 (3)
September, 2007 (3)
August, 2007 (3)
July, 2007 (5)
June, 2007 (1)
May, 2007 (5)
April, 2007 (4)
March, 2007 (3)
February, 2007 (4)
January, 2007 (3)
December, 2006 (1)
November, 2006 (1)
October, 2006 (3)
September, 2006 (3)
August, 2006 (6)
July, 2006 (2)
April, 2006 (2)
March, 2006 (2)
February, 2006 (4)
January, 2006 (9)
December, 2005 (10)
November, 2005 (3)
October, 2005 (1)
September, 2005 (4)
August, 2005 (6)
June, 2005 (2)
May, 2005 (3)
April, 2005 (3)
March, 2005 (5)
February, 2005 (2)
January, 2005 (3)
December, 2004 (3)
November, 2004 (5)
October, 2004 (3)
September, 2004 (3)
July, 2004 (5)
June, 2004 (3)
May, 2004 (2)
April, 2004 (3)
March, 2004 (7)
Blogroll
Sign In
Thursday, July 17, 2008
Euro symbol character problems...
Thursday, July 17, 2008 5:25:32 PM (GMT Daylight Time, UTC+01:00) (
.Net General
|
Asp.Net
)
if you ever send a string across a web service, and write it out to a file, make sure you specify Encoding.UTF8 explicitly. otherwise characters such as the EURO symbol may not render correctly in some browsers (IE6). it took me ages to pin this down, because everything i read about was about HTTP header charset values, or HTML document charsets, or database encodings. In my case i was using the default encoding and this messed up EURO symbols. I suspect it is because of the string being serialized in the web service, but haven't the time to look into it any further. it's fixed now anyhow.
Comments [3]
| |
Thursday, July 17, 2008 11:17:48 PM (GMT Daylight Time, UTC+01:00)
€ should always work regardless of encoding.
[)amien
Damien Guard
Friday, July 18, 2008 9:08:36 AM (GMT Daylight Time, UTC+01:00)
hi damien. that's true, but my html editor (XStandard) replaces escaped characters like this with their literals.
Also literal characters have several advantages, quote from XStandard "It is not encouraged to use HTML entities, because they are an old fashioned way to escape characters. Entities unnecessarily complicate the maintenance of your markup and they make it more difficult for markup to be processed by XML technologies like DOM parsers and XSLT."
tim mackey
Friday, July 18, 2008 9:09:02 AM (GMT Daylight Time, UTC+01:00)
hi damien. that's true, but my html editor (XStandard) replaces escaped characters like this with their literals.
Also literal characters have several advantages, quote from XStandard "It is not encouraged to use HTML entities, because they are an old fashioned way to escape characters. Entities unnecessarily complicate the maintenance of your markup and they make it more difficult for markup to be processed by XML technologies like DOM parsers and XSLT."
tim mackey
Name
E-mail
Home page
Remember Me
Comment (HTML not allowed)
Enter the code shown (prevents robots):
Live Comment Preview