Creating PDFs with content out of a database or user input is a very powerful Seam feature. Currently, the rich:editor control coupled with the p:html or p:html / s:formattedText tags comes close to allowing a user to create relatively complex PDF output. However, there isn't consistency between what the rich:editor creates and what Seam PDF can produce. For example, saving rich:editor input as Seam Text disables the ability to create ordered or unordered lists. Saving it as html, loses the ability to define font characteristics. Possibly a quick fix would be to allow Seam PDF pages to reference a CSS. Another approach might be to modify the s:formattedText tag to handle what the rich:editor creates. I have a strong interest in this, and would be willing to try some solutions if I could get pointed in the correct direction. Thanks.