Exchange Server Forums

iso 8859-13 being converted to windows 1257 character set

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Message Routing >> iso 8859-13 being converted to windows 1257 character set

Page: [1]

Message

<< Older Topic Newer Topic >>

iso 8859-13 being converted to windows 1257 character set - 4.Jan.2012 2:38:33 PM

toolmania1

Posts: 4
Joined: 4.Jan.2012
Status: offline

I have been trying to send a message in iso 8859-13 using my Exchange 2007 account. I have been using Mozilla Thunderbird and the Exchange OWA web to try and send this message in the iso 8859-13 character set.

In Thunderbird, I have been selecting the character set under Options -> Character Encoding. After I send the message to my account on the Exchange 2007 server, I check the View Source which shows that the message was in fact sent in the iso 8859-13 character set. So, when the message leaves Thunderbird it is in the correct character set of iso 8859-13. The char-set="iso 8859-13" in the View Source when sent from Thunderbird.

I am not sure if I set the character set correctly in Exchnage OWA, so let's just ignore that for now. Let's just focus on Thunderbird since I can view the source of the message after I send it.

Also, when I do a fetch command in telnet to fetch the message directly from Exchange 2007, I can also see the charset = "windows 1257 ".

So, the "charset=" does not match from the View Source in Thunderbird compared to the "charset" from the fetch command directly against the Exchange 2007 server.

By the way, I moved the message into a new folder, named "folder1", and ran these commands for my fetch, in case you were wondering:

a login username / password
a select inbox/folder1
a fetch 1 (body.peek[header])
a fetch 1 (body.peek[text])

I am mostly concerned about the characters in the "text" fetch command since that is the body of the email. I am aware that 2 fetches need ran in order to obtain the header information as well as the body of the message. In both the "header" and "text", I can see "charset=". In both those cases, the "charset=" will be equal to "windows 1257" instead of "iso 8859-13" when doing the 2 fetches against this message that I moved into the new folder on the Exchange 2007 server. I know that is a lot of information, but I want to be clear about what I found already.

Also, I have a Blackberry device registered to this account also. On this device, the characters in the body of the message show up as question marks. This is because the characters I put in the body of the original message are not in the windows 1257 character set. The characters I put into the body of the original message can be found in the iso 8859-13 character set. So, if Exchange 2007 would have stored this message correctly, then the device would have been able to display the characters in the body of the message correctly instead of displaying question marks.

I have tested some of the other iso 8859 ( from 1 to 16 ) with no problems ( excluding iso 8859 -9, -10, -11, -12, and -14 ). On the Blackberry, in the fetch, and in the View Source in Thunderbird, those character sets appear correctly in all places.

So, in conclusion, I am wondering if anyone knows if there is a problem with Exchange 2007 converting the iso 8859-13 character set into the windows 1257 character in order to store such messages as noted in this situation?