Johnny Andersson wrote: > I THINK you can write a macro that does this for you everytime that document > is saved or closed or something like that. However, last time I was looking > for how to start a macro from events like that, I couldn't find it, but I > HAVE seen it somewhere… > > Johnny Andersson > > 2007/3/7, Dan Lewis <[EMAIL PROTECTED]>: > > > > On Wednesday March 07 2007 11:36 am, Stuart McGraw wrote: > > > I have been using Writer for 2 days now, pretty nice! > > > But how do I write a Makefile rule to update my .pdf > > > file when my .odt file changes? Didn't see anything > > > helpful in help or googling. > > > (OOwriter 2.0 running in FC6) > > > Thanks! > > > > My suggestion is that you create a new .pdf everytime you update > > the .odt file. Click the Save icon to save the changes first and then > > click the PDF icon to export the changed file to .pdf. Export it to > > the same file each time. (This overwrites the .pdf file.) It only > > takes one additional click. (You could do the same thing by using > > File > Export as PDF. Although it might give you a few more choices if > > you have special settings you are using in the PDF format.) > > > > Dan
Thanks for the responses. The problem is I don't need or want to update the pdf for every edit of the .odt file. I make a lot of small changes, but eventually do a "make distribution" which does lots of stuff with other files in addition to the Open Office file (which I use for documentation of the other files). This is when I want to be sure the pdf file is current, because the make will package it up with the other stuff. Re Dan's response, relying on me to remember to manually update the pdf is not a good solution (trust me! :-) Dia, for example, (which I use for some of my documentation) has command line options to do an export, so in my makefile I can have Dia update its .png file is it's needed. But for Writer, although I see command line options to print a document, there doesn't seem to be any command line options to export a document. I was hoping there were such options, or would soon be such options, or there was some other way to do this. It would be unfortunate if OO documents can't be integrated into a project build system. I don't want to go back to text READMEs! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
