Some alternatives: 1) You can implement your own CF_Document tag based on the same iText java libray that the built-in tag uses;
2) You can use Apache FOP with your own Stylesheet (this is what I'm currently doing, because we are on CFMX 6.1 and we haven't installed iText yet). 3) You can use one of the other commercial tags/solutions that does PDF. I suspect that doing one of the first two will provide an appreciation of how complex a precise and accurate PDF version of an HTML doc can get, but you will at least get more control than you do with the built-in tag. On 7/28/06, Brian Dumbledore <[EMAIL PROTECTED]> wrote: > I read on one of the posts that cfdocument wouldn't succeed showing images on > a https site. It is manadatory our client to have https, but now the images > won't showup in the pdfs. what is the solution? > I am totally tired of cfdocument. It is so buggy and unpredictable, it is a > disgrace to cf. > Ramblings apart, what would be a good alternative for cfdocument? -- CFAJAX docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:247971 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
