| Key: |
SVC-412
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Normal
|
| Assignee: |
Unassigned
|
| Reporter: |
Carty Capra
|
| Votes: |
30
|
| Watchers: |
7
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is original of duplicate:
|
|
SVC-4027
llEmail and IM to email mojibake (characters not sent with the righ coding)
|
|
|
|
|
Relates
|
|
|
|
This issue is related to by:
|
|
|
SVC-810 Mail to IM gateway fails if nonstandard ascii characters used
|
|
|
|
 |
|
SVC-391 llEmail and llHTTPRequest do not handle non-ASCII characters
|
|
|
|
|
|
SVC-1144 replies to offline emails can't contain unicode
|
|
|
|
|
|
|
| Linden Lab Issue ID: |
DEV-2257
|
|
Although E-mail messages forwarded from inworld are written in UTF-8 character set, the message header doesn't contain Content-Type field.
According to RFC2046, unspecified Content-Type should be considered as "Content-Type: text/plain; charset=US-ASCII", and most of e-mail clients assumes so.
It is OK for English that only uses 7bit characters, but not good for any other languages that use 8bit characters.
Some conversions are needed to read those messages that are mostly consist of 8bit characters, like Japanese, Chinese, Korean, etc.
Simply adding "Content-Type: text/plain; charset=UTF-8" in the message header will solve this problem.
|
|
Description
|
Although E-mail messages forwarded from inworld are written in UTF-8 character set, the message header doesn't contain Content-Type field.
According to RFC2046, unspecified Content-Type should be considered as "Content-Type: text/plain; charset=US-ASCII", and most of e-mail clients assumes so.
It is OK for English that only uses 7bit characters, but not good for any other languages that use 8bit characters.
Some conversions are needed to read those messages that are mostly consist of 8bit characters, like Japanese, Chinese, Korean, etc.
Simply adding "Content-Type: text/plain; charset=UTF-8" in the message header will solve this problem. |
Show » |
|
Include "Content-Type: text/plain; charset=UTF-8" header in the messages forwarded from second life.
