Notes rendering engine
About a year hence, it was time to refresh web design of my company’s web site. We decided to stick to new and improved web page standards and thus separate style and scripts from content. All well, but one simple thing. Our CMS never forced it’s users to use HTML in their code. We always relied on Notes rendering engine to render Notes documents body contents to what should be displayed on the web.
Not a good idea. I don’t know, when was the last time, someone at IBM took a look at their rendering engine, but this just isn’t it. Unordered lists don’t close, leading to a total mess of your layout. On numerous occasions, a div tag marked as pass through text got put to the bottom of contents and not at the spot where it was in the body field, leading to some more confusion. And what killed it for me was a sudden br tag flood in the HTML for no apparent reason. All 6 of them were gone when text was put in the same line as pass through text and appeared right after I put the text back in new line. And all of this appeared randomly, which amused me for a while.
So, I guess it is no wonder, why there are so many CMS application in Notes, where content needs to be entered as HTML. However, in my experience, you as a developer or admin of such system can be glad if a content editor knows how to use Lotus Notes.
June 15th, 2009 at 13:01
If you are on R8 you could enable the database option “Enable enhanced HTML generation”. It does not cure everything but it makes things a little better.
June 15th, 2009 at 13:41
Have you tried XPages? Or is this just the old way of rendering document content?
June 15th, 2009 at 18:47
I didn’t try XPages due to obvious reasons:
– We were on R7 back then, so no XPages available
– I need users to enter content in rich text field in Notes client, and AFAIK (and I could be wrong here) XPages are not supported yet in Notes client.
So basically, yeah, it is just old way rendering.
June 15th, 2009 at 18:48
@Henning Heinz: Cheers. Will try that.