Genii Weblog

Civility in critiquing the ideas of others is no vice. Rudeness in defending your own ideas is no virtue.

Thu 19 Feb 2009, 10:44 PM
Unfortunately, customers still have layout regions in forms that they email, so I have to render layout regions into MIME.  While it is going pretty well, I am having to go back and re-use both code and techniques that I haven't though about in a decade.

Copyright 2009 Genii Software Ltd.


Thu 19 Feb 2009, 10:04 AM
In this post, I talk again about email, and a relatively common item in email, list items.  But even though there are lots of list issues in Notes MIME rendering, this is a particularly bad example of how content can be lost along with formatting.  Read just the second letter (rendered by Notes MIME), and think about how it implies that the candidate meets ALL of these qualifications.  Would you like to chance that misunderstanding?

I do have a confession to make.  This problem was identified by a beta tester last night after I released Beta 2, and iFidelity didn't handle these well either.  On the other hand, I fixed it last night in what will be Beta 2a that I will release today.  Would you like to bet on whether IBM will fix this in their rendering by Version 9, now that I have publicly identified the problem?

Email created in Notes client with checked and unchecked items

Checked and unchecked bullets in Notes client

Email as it was received in Outlook after being rendered by native Notes engine

Bullets in Outlook after native Notes rendering

Email as it was received in Outlook after being rendered by iFidelity Beta 2a

Bullets in Outlook after iFidelity rendering

Previous Topics in this series

In Part 1, I showed how IBM's rendering of MIME messages could lead your customers to think you were still running Notes R5, and how our upcoming iFidelity (sign up for the beta) would allow you to send out more professional looking email, rendered as it is in Notes.  In Part 2, I showed how content rendered by Domino on the web was likely to make prospective customers think twice, or more, before buying Lotus Notes, and how CoexEdit could dramatically improve that default rendering.  In Part 3, I showed how rendering is made even worse when the rich text is edited on the web, and how CoexEdit can improve that process as well.  In Part 4, I showed how HTML signatures are prone to some of the same rendering issues (as well as different ones) as we have seen elsewhere.  In Part 5, I showed how tabbed tables do not translate well through email, and how iFidelity could help.   In Part 6, I showed how sections could lose titles after Notes client render, and how iFidelity could help there as well. 

Copyright 2009 Genii Software Ltd.