Re: [Evolution] Character encoding in 1.4.x



Howdy Jeff,

On Sat, 2003-09-13 at 12:43, Jeffrey Stedfast wrote:
Well, I'm stumped. The way charsets work in Evolution's composer is
this:
1. everything is actually composed in UTF-8 (unicode can represent all
characters)
2. when the user hits Send, a message is constructed from the contents
of the composer
3. the message body text is first checked to see if it contains any
characters that do not fit within US-ASCII. If it can be represented by
US-ASCII, we're finished.
4. Now we check to see if we can fit the contents into the composer's
charset (each composer allows you to override the default composer
charset). if it works, we use this...
5. Next we check the default composer charset. If yes, then done.
6. Failing the above, we try the user's default mail viewing charset. If
that works, done.
7. if we still haven't found an appropriate charset, we pass the text
through a "guess me" filter which can recognise 10 to 15 charsets or
so... all single-byte charsets such as koi8-r, windows-1251, iso-8859-*
and maybe a few others (I don't have the table in front of me). If none
of those charsets in the table are appropriate, we fall back to UTF-8

Thanks for this explanation.  

When does the 7-bit/8-bit encoding come into effect?

On Sat, 2003-09-13 at 13:12, Russell wrote to Peter: 
On 12 Sep 2003, Peter wrote:
This message looks fine. I use Evolution and have never adjusted the
default character set, which is: Western European, New (ISO-8859-15).
I'm not sure you can even change the character encoding in evolution
(which I believe is UTF-8).

Your message didn't use 8-bit at all, but 7-bit ASCII

  Content-Type: text/plain
  Mime-Version: 1.0
  X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5)
  Content-Transfer-Encoding: 7bit

No character set was listed at all with your message.


On Sat, 2003-09-13 at 13:37, Russell wrote to Me: 
On Fri, 12 Sep 2003, Mike Gifford wrote:

Thanks Peter..  I'm still not sure what's up..  But having 3 folks
complain about a similar problem is making me a bit nervous..  If I
managed to nail this bug down any more I'll let you know..  Might just
be something screwy with sympatico's smtp server.  it's up & down a lot
these days.

  I highly doubt that the Sympatico SMTP server is changing your character
set to Greek:

  Content-Type: text/plain; charset=iso-8859-7
  Mime-Version: 1.0
  X-Mailer: Ximian Evolution 1.4.4
  Content-Transfer-Encoding: 8bit

  Peter had 7bit encoding and text/plain type without a character set 
encoding at all.  iso-8859-7 is  (literally) Greek 
http://czyborra.com/charsets/iso8859.html#ISO-8859-7

Is there somewhere I can just turn off the extra language attribute on the Content-Type?

so... I guess check that your composer charset value is not iso-8859-7.
Go to the Edit->Character Encoding menu in the composer. 

I checked there (thought didn't know that it existed here previously),
and it was Western European..  Never the less the test email was:

Content-Type:  text/plain; charset=iso-8859-7
Organization:  OpenConcept Consulting http://www.openconcept.ca

Mime-Version:  1.0
X-Mailer:  Ximian Evolution 1.4.4 
Date: Sun, 14 Sep 2003 15:46:34 -0400
Content-Transfer-Encoding:  8bit
 

this was just a text message, so not sure.  I just tried sending a html
message and the language wasn't listed at all:


Content-Type:  multipart/alternative; boundary="=-xc59HdlW1Q8mJXmxbICf"
Organization:  OpenConcept Consulting http://www.openconcept.ca

Mime-Version:  1.0
X-Mailer:  Ximian Evolution 1.4.4 

Any way to proceed/trouble shoot this any more?

Mike
-- 
Mike Gifford, OpenConcept Consulting
Free Software for Social Change -> http://www.openconcept.ca
Fair Vote Petition - http://www.fairvotecanada.org/petition.php
The master’s tools will never dismantle the master’s house - A Lorde




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]