On Wed, 2010-10-13 at 18:41 -0400, TJ Frazier wrote: > On 10/13/2010 17:31, Jean Hollis Weber wrote: > > Although I said 2 days ago that I would like to get the Impress Guide > > for V3.2.1 published this weekend, I now amend that to: let's get all > > the Impress Guide chapters reviewed again by Sunday night US Pacific > > Time (which is Monday morning here in eastern Australia). > > > > Then I can final-check and publish the last of them early next week, > > after which I (or someone) can work on compiling the full book. That's a > > lower priority item once the chapters are published. > > > > --Jean > > > Jean, > > I gather that the first step in compiling the full book for a Guide is > to collect all the chapters and the master into one folder. The next > step is to open the master and start looking for problems, particularly > with cross-references. > > Is it reasonably possible for you to save that first-step folder on OOA > somewhere? I want to file an issue on the xref problem, but I need a > good example that QA can download at their convenience. > > Whether such an issue actually gets fixed is strongly dependent on how > "flaky vs. solid" it is; that is, how readily they can reproduce it. > That's my job, to find or make solid errors, if I can. > > The only other thing I could certainly use (but don't absolutely need) > is some notes on where you found problems. Anything like, "Several > starting in Chapter 4" would be a big help; otherwise, I can look for > myself. > > If time doesn't permit for this Guide, please think about it for the future.
TJ, Yes, as soon as I do the .odm (master doc) I can put it in the same OOA folder as the .odt chapter files, or better still I'll make a .zip containing all the files, which can then be extracted into one folder on any machine. That's easy. I just have to remember to do it. <grin> I'll also try to remember to keep some notes on where I encounter problems. I suspect that the problems arise from the convoluted history of some of the files, but a more detailed study of what's happening in the XML would be very good and might give some clues to the cause. Thanks for taking this on! --Jean --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
