On 9/26/01 1:47 AM, "Norbert Bollow" <[EMAIL PROTECTED]> wrote:
> It's absolutely necessary for his application to make sure that
> the page will display as a nice page with lots of pictures on it.
Then he's got a problem. E-mail clients vary widely (and horribly) in their
ability to render stuff. He's going to have to do a lot of testing, he'll
probably have to do a special version JUST for his AOL users, since their
system is that different, and it still won't work right in many cases.
If he really, really needs this, he ought to use PDF. However, that's not
necessariyl user-friendly, since you can't assume browsers have a PDF
plug-in installed.
> However I could set things up so that when he sends out an email
> that contains inlined images, then the images will not be
> included in the outgoing email, but instead they'll be stored on
> my one of my servers and the IMG tags updated accordingly,
That works much, much better than doing stuff inline. It also doesn't trip
nearly as many corporate firewalls, and puts a much lower load on the server
and network infrastructure. And generates many fewer complains from users
about downloading huge pieces of e-mail.
> How will the popular HTML-rendering email clients react to this
> kind of IMG tags?
Everyone will react differently. The simpler the HTML, the better. Some will
simply break, too. Have fun.
> What will happen when the message is displayed while offline?
They;ll get broken links, most of the time.
