On Wed, 2010-11-17 at 17:34 -0500, Gary Schnabl wrote: > On 11/17/2010 12:18 PM, Sigrid Carrera wrote: > > Hi Jean, > > > > I've tried to export the odm to pdf on my netbook. It took quite a > > while (approx. 2 hours or so), but I have the pdf file now. > > > > Can you be a bit more specific, which images disappeared? I haven't > > checked the whole document yet, but for the part that I did check, the > > images are there. > > > > So, did this happen only later in the document? > > > > Thanks for extra hints. > > > > Sigrid > > One approach at book building would be to employ Adobe FrameMaker on the > ODT subdocument files by converting them to DOC and importing them into > a FrameMaker book. That way you could have reliable xrefs to both > external and internal subdocuments and still have other advantages of a > real DTP application. > > OOo is OK with master docs, but FrameMaker is a much better tool for > books and such. Also the Adobe PDF printer file (and Acrobat Pro) has a > myriad of options not available otherwise. > >
That might get our books done, but it's more important to find bugs in OOo and report them. Also, employing a proprietary program to produce our books goes against the philosophy of the OOo project. IF we were going to use an outside program (and I don't support doing that), then we would need to choose an open-source alternative. And for what FM does well, I don't think there are any alternatives. On a purely practical note, I doubt many (if any) other members of the OOo Docs project have a copy of FrameMaker (or would be willing to pay for one), which would seriously limit the number of people able to work on full books. Lastly, you don't know that the x-refs will behave themselves any better in FM unless you have tried with one of our books. If there is a problem in the OOo files, that problem could well persist when they are saved in .doc format and thus persist when brought into FM. --Jean --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
