This is a multipart message in MIME format.Ĭontent-Type: text/html charset='US-ASCII' Concatenated (and clipped for brevity), the items then look like: Content-Type: multipart/related boundary='=_related 006CEB9D85257E7C_=' When you add an embedded image in the rich text field, the storage grows to four same-named MIME Part items. When you do either of those, the MIME grows to multiple items and becomes a multi-node tree. Things get a little more complicated when you add embedded images and/or attachments. This simple structure can be abstracted to this tree: There's slightly more to its full storage implementation (like the MIME_Version item), but the MIME Part items are the important bits.

In the simplest case, this ends up a one-element 'tree', which you can see in the document's properties dialog: Content-Type: text/html charset='US-ASCII' Like many things in programming, it is organized as a tree, with each node consisting of a set of headers (generally, things like 'Content-Type: text/html'), content, and children.ĭomino stores the text part of rich text in MIME as HTML. Which is to say, myself when I need to do this again.Īs a quick primer, MIME is a format originally designed for email which has proven generally useful, including for HTTP and, for our needs, internal storage in NSF.

This structure isn't particularly complicated, but there are some interesting aspects to it that are worth explaining for posterity.

My work lately has involved, among other things, processing and creating MIME entities in the format used by Notes for storage as rich text.

Lotus notes richtext extract image