I have an application in which I need to pull the body field from one document into a field on another document. As this is quite a bit of data, I would like to do it asynchronously (plus, that’s how I obtain all of my other data). I am looking for suggestions on how to transform rich text to HTML (with the formatting maintained) using a LS or Java agent. The reason I wish to do this instead of simply using a WQO agent to copy the element from one document to the other is that the size of the data being copied in is making the form load slowly, and a more responsive solution is desired.
Subject: Convert Rich Text to HTML/xml and back again.
You should try to let Notes do it. Maybe you could:
a) Set field properties to store rich text as HTML. This might not be an option though
b) Use java to read the output from HTTP task. So you pass the URL to the document with the field in and then read the HTML output produced by notes
c) Use the DXLexporter to produce XML for the field
Its odd that they dont provide a converter to HTML in LotusScript as they must have all the routines lying around.
Simon
Subject: Convert Rich Text to HTML/xml and back again.
If a third party product is not an issue, our Midas Rich Text LSX is very good at both Rich Text to HTML and HTML to Rich Text (as evidenced by our CoexEdit product, which uses the Midas engine under the covers and does this translation virtually instantaneously when synchronizing rich text and web edits). You might even be able to use CoexEdit and skip the WQO and WQS agents, letting the extension manager handle this under the covers without agents or scripts, etc.
Both are commercial products, and so would cost something, but both are also extremely high performance and fast. Obviously, if you have no budget for it, you’ll need to find something else, but if you have any budget at all, this is probably less expensive than trying to cobble together something that is not as clean or fast. You mentioned once before that Midas might be too expensive for your company’s needs, but that was for a more isolated set of functions, I think, so pardon my intrusion if this still seems out of reach.
If a commercial solution does seem out of the question, you might want to try getting Notes to convert the HTML back and forth using the HTTP task, or possibly by switching to MIME and back, although that will likely not be any faster.
Follow up: As a question, are you sure you want to go from rich text to HTMl to rich text? It sounds like you just need to transfer content from one field to another. I don’t understand why you wouldn’t stick to rich text for that.
Subject: RE: Convert Rich Text to HTML/xml and back again.
Mostly because I wanted to test to see if it would be faster to copy the data between the two documents - the lookup document and the new document being created - as html than with a wqo agent copying the rich text item, which tends to be somewhat slow. I’ve tried doing the MIME conversion and, as suspected, I didn’t notice much of a performance improvement.
Subject: RE: Convert Rich Text to HTML/xml and back again.
I’d focus on trying to find out what is slowing down the transfer of rich text, because that shouldn’t be slow at all. What code are you using for that?