Well, c) isn't mutually exclusive of b)...
As an end-user, I don't want an email client that breaks the email that
I receive. That's pretty basic. And given that I have a choice of
programs and that this is a very important factor for me, I'll choose
another one.
As a web designer, I'll have to take OL 2007 into account when
composing HTML email (as I did Netscape 4 back in the day). That
doesn't mean that I have to like it or just accept it. Maybe if there's
enough complaining from customers Microsoft will get its act together
and fix this major glitch in their software.
And realistically, Microsoft is the one who's going to have to change
sooner or later. There's no way that most designers are going to go
back to the dark ages of tables and font tags in order to make their
emails look relatively decent on OL 2007. I predict incremental
improvements in OL 2007's HTML rendering, and I expect that a lot of
designers will take a "just wait for them to fix it" approach rather
than learning how to dumb down their designs in just the right way.
As an example, I have a pretty basic HTML email that's sent to
customers when they place an order on one of our websites. It looks
terrible on OL 2007, but it's readable. Given that it looks great
everywhere else, I don't think I'm going to change it for now, and
we'll see if there's a rendering patch down the road that resolves it
for me.
And in the meantime, I'm going back to OL 2003 so that I can read my
mail the way it was meant to be viewed...
On Nov 28, 7:04 pm, "Patrick Schmid [MVP]" <
[email protected]>
wrote:
Actually, c) is the better option: Educate people about 2007 and tell
them to get their newsletters in shape for it.
2007 is a fact that is going to happen (through OEM sales, corporate
deployments and retail sales) and newsletter authors really don't have a
choice whether they want to adjust their newsletters for it or not. If
they want to reach their entire audience, they have to.
Patrick Schmid [OneNote MVP]
--------------http://pschmid.net
***
Office 2007 RTM Issues:
http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007:
http://pschmid.net/office2007/customize
OneNote 2007:
http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog:
http://pschmid.net/blog/feed
Ouch!
This pretty much sums up my experience as well:
http://joe.hardy.id.au/blog/2006/11/21/broken-html-rendering-in-outlo...
So I've learned that a) I'm not crazy, and b) I should go back to
Office 2003 and try to convince everyone else I know to do the same.
On Nov 28, 6:15 pm, "Patrick Schmid [MVP]" <
[email protected]>
wrote:
Take a look athttp://pschmid.net/blog/2006/10/05/56
I suggest especially to read the blog post linked in the update at the
bottom.
Patrick Schmid [OneNote MVP]
--------------http://pschmid.net
***
Office 2007 RTM Issues:
http://pschmid.net/blog/2006/11/13/80
Office 2007 Beta 2 Technical Refresh (B2TR):
http://pschmid.net/blog/2006/09/18/43
***
Customize Office 2007:
http://pschmid.net/office2007/customize
OneNote 2007:
http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog:
http://pschmid.net/blog/feed
I didn't say that Microsoft had something to hide...? All I said was
that their product isn't working properly for me. So I'm trying to
figure out why...
Unfortunately I don't use any of the programs needed to use the
validation tool you linked to:
------
Download and install Word2007MailHTMLandCSS.exe if you work with:
Microsoft Office SharePoint Designer 2007
Microsoft Expression Web Designer 2007
Microsoft Visual Studio 2005
Download and install Word2007MailHTMLandCSSMacromedia.exe if you work
with:
Macromedia Dreamweaver MX 2004
Macromedia Dreamweaver 8
------
A test email that I tried out in the W3C validators (XHTML and CSS)
does validate as XHTML Transitional, however. And all of the tags that
it uses are fully-supported in the OL 2007 list you sent. So what else
could be going on?
I guess I can track down a copy of Dreamweaver somewhere if
necessary...
On Nov 28, 4:28 pm, "Sue Mosher [MVP-Outlook]"
Outlook 2007 has different (largely better) support for styles than earlier versions, but also blocks certain HTML elements and attributes, mainly those with security implications. It sounds like those newletter and ecommerce message publishers have not tested their output against the new version.
It's not like Microsoft has anything to hide regarding this issue. The documentation is far better than for any previous version and has been out there since August, and I and others with public platforms have been urging newsletter publishers to look at it:
http://msdn2.microsoft.com/en-us/aa338201.aspxhttp://msdn2.microsoft....
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
Terrible means that the emails have missing background colors,
incorrect block sizes, and other major aesthetic disruptions that are
not present in other email clients or if I copy and paste to a text
file and view them in Internet Explorer.
Malformed means that the email had some inherent problem (bad code, or
code not well-designed to be sent via email) that might explain why OL
2007 doesn't display it as intended.
Most of the HTML email that I receive seems to have this issue to some
extent. For example, ZDNet newsletters are all jumbled up, and much
simpler order emails that I receive from different eCommerce programs
have background color issues, don't display fieldset tags properly,
etc. I could give you a code sample if you like, but it really doesn't
seem to be related to any specific email at all.
Is no one else having this problem? Could it be that it's just my PC
(perhaps due to the fact that I beta-tested OL 2007)? I plan to get a
new PC in the next week or so anyway, so I could try reinstalling
everything from scratch then and see if that fixes it.
However, if this is an issue that others are also having with OL 2007,
then I may just go back to Office 2003...- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -