I’ve re-posted the presentation and database for the Rich Text to Web presentation. A couple of things to note:
- The XSL can be accessed by going to Actions and clicking “Open XSL Profile Doc”
- The XSL file makes some assumptions about pathing…such as using the DocTitle field on a document as the sorted key for a view to access the doc. You’ll need to change/genericize for your own implementation if you move this to your dbs
- The agent (CleanHTML_LS) that does all the work happens on QueryClose of the mainnotes form
- That agent needs highest level security rights…suggest you follow Using instructions and sign the db with an id that has rights
- The example document in the db actually renders like hell in the browser. This wasn’t the actual use case we developed for initially, so XSL needs tweaking.
- As we update the XSL for more nuanced presentation capabilities 😉 I’ll add it to the downloads section separately as just a text file download
With those caveats, the db actually does the full course of work. Author a doc in notes, close it, agent fires, creates transformed HTML from Rich Text. Open doc from the Web view in a browser, and view the transformed HTML. Of course, you may feel differently about the level of completeness, but the goal was to show that you can, in fact, get ahold of Rich Text and perform your own transformation on it to control the HTML output. There doesn’t appear to be anything lacking in the DXL information on regular user-authored Rich Text that couldn’t be handled with XSL processing.