iText has done great for smallish documents. As has just forcing mime type, and using CSS.
Wil Genovese wrote: > Ya know we do something here similar where we convert html to RTF > which can be read by MS Word without any problems. > > There is an htmltortf.exe program somewhere that we execute from CF5. > Yeah, this is real old legacy code on an old server but the thing > still works for the client. However, this requires Windows. > > Part of moving them to CF8 we have to figure out how to replicate > this. I've been digging for a Java RTF api. I haven't found the grail > yet, but I suspect I've just looked in the wrong places. > > Anyways, this may be a valid way to solve your problem. > > > Wil Genovese > > One man with courage makes a majority. > -Andrew Jackson > > A fine is a tax for doing wrong. A tax is a fine for doing well. > > On Oct 14, 2008, at 3:09 PM, Loathe wrote: > >> Yeah, I'm working on finalizing the formatting requirements for a >> template now. >> >> Then it's unzip the docx and tear it apart to see how I can have cf >> create the xml files. >> >> Jim Davis wrote: >>>> -----Original Message----- >>>> From: Tom Chiverton [mailto:[EMAIL PROTECTED] >>>> Sent: Tuesday, October 14, 2008 10:36 AM >>>> To: cf-talk >>>> Subject: Re: docx (office 2007) from CF? (Cross) >>>> >>>> On Tuesday 14 Oct 2008, Loathe wrote: >>>>> We already have a PDF solution in place. Which is great if they >>>>> just >>>>> need to print the document. They also want to be able to save, >>>>> edit >>>> and >>>>> pass around the document. >>>> Perfectly possible in a PDF file format. Sometimes without paying >>>> Adobe >>>> (OpenOffice v3, for example). >>> I'm just a poor country chicken... but this here "OpenOffice" don't >>> seem >>> like it's Word. >>> >>> Seriously tho' - the requirement is to do this in Word. It's >>> nonsensical to >>> suggest non-Word alternatives. The client-side requirements are >>> immutable. >>> >>> That said, Loath, the link provided should give all the information >>> about >>> the format. I'm sure you've thought of this but I'll say it anyway: >>> don't >>> try to build the doc from scratch. What you've described seems >>> pretty >>> formulaic (complex, but formula) - create a template that contains >>> all the >>> elements and look to add/edit new nodes as needed rather than build >>> from >>> scratch. >>> >>> In my experience with formats like this (I've not done DocX, but I >>> have >>> dealt with similar) the key is to let the native tool do as much of >>> the work >>> as possible. Doing small changes natively then comparing (diffing) >>> that doc >>> to the previous one can be invaluable. >>> >>> While developing test CONSTANTLY because even small changes can have >>> dramatic effects. I also strongly urge to have the output checked >>> out by >>> multiple people: in docs like this there are so many little things >>> to go >>> wrong. The more eyeballs the better. >>> >>> Sorry I can't be more specific. >>> >>> Jim Davis >>> >>> >>> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:313895 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4