From: martti.toivonen on
Using 2.8 and its (SE's) internetclasses. The problem is encoding and
decoding breaks the attachments so they cannot be opened with the
proper software. Acrobat reader complains about pdfs and shows only an
empty document. Only the most basic notepad txts come through OK. The
problem is not in the creation of pdfs, I have tried two different pdf-
printers (PDF-XChange and PDFCreator) and both do perfectly good pdfs
that are quite readable prior to sending.

Been able to narrow the problem to ansi -setting: with ansi TRUE the
email CAVO sample sends attachments OK, change it to FALSE and the
problem appears.

The dilemma is that I have quite a big app and cannot suddenly start
using ANSI instead of OEM. The internet classes seem to offer means
regulating the encoding with parameters. Do not have any idea what the
right parameters should be for the encoding to be right. Help, anyone?
mot
From: John Martens on
This should help you to set ANSI on (just for a while).
lAnsi := SetAnsi(TRUE)
* put your coding here
SetAnsi(lAnsi)

John


martti.toivonen(a)utu.fi schreef:
> Using 2.8 and its (SE's) internetclasses. The problem is encoding and
> decoding breaks the attachments so they cannot be opened with the
> proper software. Acrobat reader complains about pdfs and shows only an
> empty document. Only the most basic notepad txts come through OK. The
> problem is not in the creation of pdfs, I have tried two different pdf-
> printers (PDF-XChange and PDFCreator) and both do perfectly good pdfs
> that are quite readable prior to sending.
>
> Been able to narrow the problem to ansi -setting: with ansi TRUE the
> email CAVO sample sends attachments OK, change it to FALSE and the
> problem appears.
>
> The dilemma is that I have quite a big app and cannot suddenly start
> using ANSI instead of OEM. The internet classes seem to offer means
> regulating the encoding with parameters. Do not have any idea what the
> right parameters should be for the encoding to be right. Help, anyone?
> mot
From: martti.toivonen on
Yes, John, you are quite right, I do not have to change the setting
for all of the app, just there where I am sending the email with
attachments.

Somehow I think email should be sending the attachments right even
with ansi set FALSE. One can test this with the sample email client,
set ansi false and pdfs, docs etc will not come through right.

Took me 2 workdays to discover, slow that I am and know nothing about
coding of emails.
mot


On Jul 14, 4:33 pm, John Martens <adsl672...(a)tiscali.nl> wrote:
> This should help you to set ANSI on (just for a while).
> lAnsi := SetAnsi(TRUE)
> * put your coding here
> SetAnsi(lAnsi)
>
> John
>
> martti.toivo...(a)utu.fi schreef:
>
> > Using 2.8 and its (SE's) internetclasses. The problem is encoding and
> > decoding breaks the attachments so they cannot be opened with the
> > proper software. Acrobat reader complains about pdfs and shows only an
> > empty document. Only the most basic notepad txts come through OK. The
> > problem is not in the creation of pdfs, I have tried two different pdf-
> > printers (PDF-XChange and PDFCreator) and both do perfectly good pdfs
> > that are quite readable prior to sending.
>
> > Been able to narrow the problem to ansi -setting: with ansi TRUE the
> > email CAVO sample sends attachments OK, change it to FALSE and the
> > problem appears.
>
> > The dilemma is that I have quite a big app and cannot suddenly start
> > using ANSI instead of OEM. The internet classes seem to offer means
> > regulating the encoding with parameters. Do not have any idea what the
> > right parameters should be for the encoding to be right. Help, anyone?
> > mot

From: John Martens on
It took me quite some hours a couple of week ago when I wanted to save a
file that I downloaded with cHttp.
Works fine with the right ANSI setting and corrupts the file without.

John


martti.toivonen(a)utu.fi schreef:
> Yes, John, you are quite right, I do not have to change the setting
> for all of the app, just there where I am sending the email with
> attachments.
>
> Somehow I think email should be sending the attachments right even
> with ansi set FALSE. One can test this with the sample email client,
> set ansi false and pdfs, docs etc will not come through right.
>
> Took me 2 workdays to discover, slow that I am and know nothing about
> coding of emails.
> mot
>
>
> On Jul 14, 4:33 pm, John Martens <adsl672...(a)tiscali.nl> wrote:
>> This should help you to set ANSI on (just for a while).
>> lAnsi := SetAnsi(TRUE)
>> * put your coding here
>> SetAnsi(lAnsi)
>>
>> John
>>
>> martti.toivo...(a)utu.fi schreef:
>>
>>> Using 2.8 and its (SE's) internetclasses. The problem is encoding and
>>> decoding breaks the attachments so they cannot be opened with the
>>> proper software. Acrobat reader complains about pdfs and shows only an
>>> empty document. Only the most basic notepad txts come through OK. The
>>> problem is not in the creation of pdfs, I have tried two different pdf-
>>> printers (PDF-XChange and PDFCreator) and both do perfectly good pdfs
>>> that are quite readable prior to sending.
>>> Been able to narrow the problem to ansi -setting: with ansi TRUE the
>>> email CAVO sample sends attachments OK, change it to FALSE and the
>>> problem appears.
>>> The dilemma is that I have quite a big app and cannot suddenly start
>>> using ANSI instead of OEM. The internet classes seem to offer means
>>> regulating the encoding with parameters. Do not have any idea what the
>>> right parameters should be for the encoding to be right. Help, anyone?
>>> mot
>