 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Applications / Mac Applications / May 2008Decoding charsets in headers with Mail.app
I recently received an e-mail with a subject of Re: avoir/�tre expression activities? The listserv removed the header that identified the sender's e-mail client, and there are headers for Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8bit However, the subject header looks like it might be UTF-8 encoded Subject: Re: avoir/=?ISO-8859-1?Q?=EF=BF=BDtre_?= expression activities? (the words are 'avoir/être') Can Mail.app (in 10.3.9) be configured to render this properly, or am I just going to have to "deal" with the misconfiguration at the source or listserv ?  SignatureWes Groleau If you put garbage in a computer nothing comes out but garbage. But this garbage, having passed through a very expensive machine, is somehow ennobled and none dare criticize it. > I recently received an e-mail with a subject of > [quoted text clipped - 15 lines] > or am I just going to have to "deal" with the misconfiguration > at the source or listserv ? I have never had that problem in mail.app, perhaps because I chose fonts with my frequently used Unicode characters (Lucida, Helvetica, Monaco), but I don't know of any font that can't handle iso-8859-1 (Latin 1). Are you using a non-standard font for reading mail messages? If not, it must be the fault of the sender encoding in some non-standard way. Can you read my "être"? Signature{\rtf1\mac\ansicpg10000\cocoartf824\cocoasubrtf420 {\fonttbl\f0\fmodern\fcharset77 Courier;} {\colortbl;\red255\green255\blue255;} \margl1440\margr1440\vieww12620\viewh9000\viewkind0 \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\ql\qnatural \f0\fs18 \cf0 --- \ ++====+=====+=====+=====+=====+====+====+=====+=====+=====+=====+====++\ ||Arnold VICTOR, New York City, i. e., <arvimideQ@Wearthlink.net> ||\ ||Arnoldo VIKTORO, Nov-jorkurbo, t. e., <arvimideQ@Wearthlink.net> ||\ ||Remove capital letters from e-mail address for correct address/ ||\ || Forigu majusklajn literojn el e-po\uc0\u349 ta adreso por \u285 usta adreso || \ ++====+=====+=====+=====+=====+====+====+=====+=====+=====+=====+====++\ \pard\pardeftab720\sl280\ql\qnatural \cf0 NOTICE: Due to Presidential Executive Orders, the National Security \ Agency may have read this email without warning, warrant, or notice. \ They may do this without any judicial or legislative oversight. You \ have no recourse or protection.} >> Content-type: text/plain; charset=iso-8859-1 >> Content-transfer-encoding: 8bit >> >> However, the subject header looks like it might be UTF-8 encoded >> >> Subject: Re: avoir/=?ISO-8859-1?Q?=EF=BF=BDtre_?= expression activities? > I have never had that problem in mail.app, perhaps because I chose fonts > with my frequently used Unicode characters (Lucida, Helvetica, Monaco), > but I don't know of any font that can't handle iso-8859-1 (Latin 1). Are > you using a non-standard font for reading mail messages? If not, it must > be the fault of the sender encoding in some non-standard way. Can you > read my "être"? Oh, yes. I almost never have a problem sending and receiving French, Spanish, Chinese, Japanese in e-mail. (Usenet, seems a lot of Spanish speakers are able to read what I post but when they quote, it comes back garbled.) Font isn't an issue--OS X is _very_ reliable at autoswitching to another font when the current font does not have the character. The problem here, now that I think a bit more, is that the sender said "I'm switching to Latin-1" (when it was already in Latin-1) but then it instead switched to UTF-8. Or that's what it looks like--I am not fluent in whatever "language" is =?ISO-8859-1?Q?=..._?= SignatureWes Groleau "To know what you prefer, instead of humbly saying Amen to what the world tells you you should prefer, is to have kept your soul alive." -- Robert Louis Stevenson >>> Content-type: text/plain; charset=iso-8859-1 >>> Content-transfer-encoding: 8bit [quoted text clipped - 24 lines] > Or that's what it looks like--I am not fluent in whatever "language" > is =?ISO-8859-1?Q?=..._?= Curiouser and curiouser. First, I meant to send in Latin 1 but mistakenly sent "être in Unicode so I'm trying again. Second, iso-8859-1 indicates the character set for Latin 1, not for any particular language. It serves for English, Dutch, French, Italian, Spanish, and German. Although Latin 1 has the meagerest set of superscripted characters, it does have circumflexes for vowels, so that couldn't be the source of your problems. You are right about Macs substituting fonts when in need of a character, so the error seems to derive from your sender using a non-standard font and/or character set. Signature++====+=====+=====+=====+=====+====+====+=====+=====+=====+=====+====++ ||Arnold VICTOR, New York City, i. e., <arvimideQ@Wearthlink.net> || ||Arnoldo VIKTORO, Nov-jorkurbo, t. e., <arvimideQ@Wearthlink.net> || ||Remove capital letters from e-mail address for correct address || ++====+=====+=====+=====+=====+====+====+=====+=====+=====+=====+====++ NOTICE: Due to Presidential Executive Orders, the National Security Agency may have read this email without warning, warrant, or notice. They may do this without any judicial or legislative oversight. You have no recourse or protection. >>> Wes Groleau quoted: >>>> Subject: Re: avoir/=?ISO-8859-1?Q?=EF=BF=BDtre_?= expression [quoted text clipped - 7 lines] > when in need of a character, so the error seems to derive from your > sender using a non-standard font and/or character set. Perhaps. I thought the three-byte code might have been UTF-8 for ê but that's C3 AA SignatureWes Groleau Promote multi-use trails in northeast Indiana! http://www.NorthwestAllenTrails.org/ |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.