Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Advocacy > Re: Problem wit...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 18 of 21 Topic 1480 of 1551
Post > Topic >>

Re: Problem with press release

by chander.ganesan@[EMAIL PROTECTED] (Chander Ganesan) Jun 17, 2008 at 10:40 AM

Josh Berkus wrote:
> Andrew Sullivan wrote:
>> On Sun, Jun 15, 2008 at 07:25:00PM -0700, Josh Berkus wrote:
>>> I'm disputing Bruce's re****t that there *are* any.
>>
>> Well, this is what mutt thinks your MIME encoding is on the message I
>> got:
>>
>> text/plain, 8bit, iso-8859-1
>>
>> Probably the issue is not just that it's not ASCII, but that it's not
>> UTF-8 either.
>
> Interesting.  Ok, time for me to take it up with the KDE guys.  It's 
> probably cut-and-paste from a cvs terminal session into Kmail that's 
> fouling things.
ISO-8859-1 is basically ASCII, it simply adds for additional characters 
after 127 ...  Most mail clients use it, or Windows-1252 (essentially 
the same) today. 

The fact that it's 8bit requires that it be quoted printable encoded, 
since QP is required for sending all the 8 bit characters in 7 bit 
encoding.  AFAIK, iso-8859-1 is the standard character set used by most 
email clients that send ascii messages. 

The =A0 character is a "non breaking space", it's a space that prevents 
a line-wrap from occurring.  My guess is that Bruce's email client 
somehow doesn't understand the non breaking space and as a result 
displays just an <A0> in its place.  I would think this is a problem 
with his mail client, not the message itself, in that it doesn't 
understand iso-8859-1 ...

chander

-- 
Sent via pgsql-advocacy mailing list (pgsql-advocacy@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-advocacy
 




 21 Posts in Topic:
Problem with press release
bruce@[EMAIL PROTECTED]   2008-06-13 14:30:52 
Re: Problem with press release
josh@[EMAIL PROTECTED] (  2008-06-15 13:37:01 
Re: Problem with press release
alvherre@[EMAIL PROTECTED  2008-06-15 16:50:19 
Re: Problem with press release
bruce@[EMAIL PROTECTED]   2008-06-16 06:25:48 
Re: Problem with press release
ajs@[EMAIL PROTECTED] (A  2008-06-16 12:35:53 
Re: Problem with press release
josh@[EMAIL PROTECTED] (  2008-06-17 07:58:56 
Re: Problem with press release
chander@[EMAIL PROTECTED]  2008-06-17 10:45:33 
Re: Problem with press release
stark@[EMAIL PROTECTED]   2008-06-16 00:40:45 
Re: Problem with press release
josh@[EMAIL PROTECTED] (  2008-06-15 19:25:00 
Re: Problem with press release
ajs@[EMAIL PROTECTED] (A  2008-06-16 01:00:59 
Re: Problem with press release
alvherre@[EMAIL PROTECTED  2008-06-16 08:20:46 
Re: Problem with press release
schabi@[EMAIL PROTECTED]   2008-06-16 14:00:27 
Re: Problem with press release
alvherre@[EMAIL PROTECTED  2008-06-16 09:14:41 
Re: Problem with press release
xzilla@[EMAIL PROTECTED]   2008-06-16 11:24:46 
Re: Problem with press release
josh@[EMAIL PROTECTED] (  2008-06-16 10:40:01 
Re: Problem with press release
ajs@[EMAIL PROTECTED] (A  2008-06-16 14:38:09 
Re: Problem with press release
jdevisser@[EMAIL PROTECTE  2008-06-16 14:03:49 
Re: Problem with press release
chander.ganesan@[EMAIL PR  2008-06-17 10:40:47 
Re: Problem with press release
jd@[EMAIL PROTECTED] (&q  2008-06-17 08:02:12 
Re: Problem with press release
bruce@[EMAIL PROTECTED]   2008-06-18 21:10:14 
Re: Problem with press release
ajs@[EMAIL PROTECTED] (A  2008-06-17 11:36:51 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Fri Dec 5 11:24:59 CST 2008.