[opendtv] Re: News: The Internet revolution is about to be televised

At 11:07 AM -0800 2/22/05, Kon Wilms wrote:
>
>I use Evolution - same problem. Craig is using a Mac so there's the
>first indicator of trouble (sorry, couldn't resist). Prashant seems to
>like to BASE64 encode his replies and then post those to the list. Out
>of curiosity I decoded one but there was no secret message contained
>within. Drat.
>
>I notice Craig's messages come through incorrectly when his message's
>mime charset type is set to iso-8859-1 and come through correctly when
>set to us-ascii. I deduce that Craig uses multiple email composers and
>one of them is getting whacked with the bit-stick when passing through
>his host/freelist 's servers.
>

Thnaks for this added info. Perhaps we can use it to figure out what 
is happening.

I use Eudora 6.01 for OS-X. I doubt that it is causing the problem, 
but I'm willing to try to change configurations if it will help. I am 
also looking at the 6.2.1 upgrade, but will need to give Qualcom more 
money to avoid the ads.

To the best of my knowledge, this problem never occurs if I am 
writing a message from scratch, or responding to a thread. It only 
happens when I paste content into a message and then try to clean it 
up.

I have Eudora set to send only plain text messages - nothing fancy.

When I drop content into a message I immediately select all, then 
convert everything to plain text. Then I unwrap the selection, which 
usually removes the carriage returns.

I just looked at the article that caused problems this morning and 
there were no visible CRs. If I change the window size everything 
wrapped automatically to the new size as it should. Yet somehow there 
were still hidden characters in the paragraphs that were interpreted 
by the Freelist server as CRs; so it forced the line breaks and added 
the =20 for good measure.

I have Eudora preferences set to turn word wrap on. They highly 
recommend this mode; the manual says it inserts line breaks after 76 
characters when the message is sent.

I can try turning this off to see what happens.

As for the character sets, I cannot find any way to see what the 
outgoing encoding is.

Whoops! Forget what I just wrote: LOOKEE WHAT I FOUND IN THE NEW MANUAL...

However, there are some other things that quoted-printable does. For 
one, since it uses an "=" to mean something special, equals signs 
must themselves be encoded (as "=3D"). Second, no line in 
quoted-printable is allowed to be more than 76 characters long. If 
your mail has a line longer than 76 characters, the quoted-printable 
encoding will break your line in two and put an "=" at the end of the 
first line, to signal to the mail reader at the other end that the 
two lines are really supposed to be all one line. Finally, a few mail 
systems either add spaces to or remove them from the ends of lines. 
So, in quoted-printable, any space at the end of a line gets encoded 
(as "=20"), to protect it from such mail systems.

So =20 means that there is a space at the end of the line.

Tomorrow I will try turning Quote Printables off when I send out 
messages with embedded stories...

As for the different character sets, Eudora typically uses 
iso-8859-1. But if I paste someting into the message that uses a 
different character set, it appears to use that character set.

Thanks for the kick in the butt Kon. Maybe we have a solution!'

Regards
Craig
 
 
----------------------------------------------------------------------
You can UNSUBSCRIBE from the OpenDTV list in two ways:

- Using the UNSUBSCRIBE command in your user configuration settings at 
FreeLists.org 

- By sending a message to: opendtv-request@xxxxxxxxxxxxx with the word 
unsubscribe in the subject line.

Other related posts: