Re: Generating LyX docs in a build
Jose': This is perfect. Thank you so much for the build information. Will keep you posted about how it works out. --jane
Re: Generating LyX docs in a build
Jose': This is perfect. Thank you so much for the build information. Will keep you posted about how it works out. --jane
Re: Generating LyX docs in a build
Jose': This is perfect. Thank you so much for the build information. Will keep you posted about how it works out. --jane
Generating LyX docs in a build
Hi there: I have a question that I hope you can help me with. I'm using LyX 1.3.6 on Fedora Core 4 (Linux) with the change bar patch (using dvipost). I create all of the user documentation for our compiler suite (except for the README and man pages) in LyX, and up until now, I've generated PDFs and checked them into our build tree. We automatically build the compiler environment software daily and those PDFs get picked up as a final step in the build. Our buildmaster would like to have the build process generate the final PDFs and only have the .lyx files (and possibly the .tex files) checked in. This way the build process could generate the most current daily PDFs that would be up-to-date with the software. During our production cycle, I use change bars on the docs and generate the PDF using PDF (dvipdfm) from the LyX menu bar, and then about a week before release, I turn the change bars off and generate the PDF using PDF (pdflatex). To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View PDF (dvipdfm) - The command-line equivalent for View PDF (latexpdf) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, --jane -- Jane McKean Technical Documentation PathScale, Inc. jane at pathscale.com
Re: Generating LyX docs in a build
On Friday 02 September 2005 23:33, Jane McKean wrote: To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View PDF (dvipdfm) - The command-line equivalent for View PDF (latexpdf) That is a good question that I have seen answered sometimes on this list. :-) Searching... $ lyx --help Usage: lyx [ command line switches ] [ name.lyx ... ] Command line switches (case sensitive): -help summarize LyX usage -userdir dir try to set user directory to dir -sysdir dirtry to set system directory to dir -geometry WxH+X+Y set geometry of the main window -dbg feature[,feature]... select the features to debug. Type `lyx -dbg' to see the list of features -x [--execute] command where command is a lyx command. -e [--export] fmt where fmt is the export format of choice. -i [--import] fmt file.xxx where fmt is the import format of choice and file.xxx is the file to be imported. -versionsummarize version and build info Check the LyX man page for more details. Now this is the funny part, the _fmt_ key that we are searching for is defined in: Edit-Preferences-File Formats, look then for format. In my case I have 3 defined pdf formats. Using pdf2 I get: $ lyx -e pdf2 spyce.lyx Document exported as PDF (pdflatex) to file `~/thunderbird/level-3/spyce.pdf' $ lyx -e pdf3 spyce.lyx Executing command:dvipdfm -p letter 'spyce.dvi' spyce.dvi - spyce.pdf [1] 55669 bytes written Document exported as PDF (dvipdfm) to file `~/thunderbird/level-3/spyce.pdf' Bingo. :-) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, -- Jane McKean -- José Abílio
Generating LyX docs in a build
Hi there: I have a question that I hope you can help me with. I'm using LyX 1.3.6 on Fedora Core 4 (Linux) with the change bar patch (using dvipost). I create all of the user documentation for our compiler suite (except for the README and man pages) in LyX, and up until now, I've generated PDFs and checked them into our build tree. We automatically build the compiler environment software daily and those PDFs get picked up as a final step in the build. Our buildmaster would like to have the build process generate the final PDFs and only have the .lyx files (and possibly the .tex files) checked in. This way the build process could generate the most current daily PDFs that would be up-to-date with the software. During our production cycle, I use change bars on the docs and generate the PDF using PDF (dvipdfm) from the LyX menu bar, and then about a week before release, I turn the change bars off and generate the PDF using PDF (pdflatex). To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View PDF (dvipdfm) - The command-line equivalent for View PDF (latexpdf) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, --jane -- Jane McKean Technical Documentation PathScale, Inc. jane at pathscale.com
Re: Generating LyX docs in a build
On Friday 02 September 2005 23:33, Jane McKean wrote: To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View PDF (dvipdfm) - The command-line equivalent for View PDF (latexpdf) That is a good question that I have seen answered sometimes on this list. :-) Searching... $ lyx --help Usage: lyx [ command line switches ] [ name.lyx ... ] Command line switches (case sensitive): -help summarize LyX usage -userdir dir try to set user directory to dir -sysdir dirtry to set system directory to dir -geometry WxH+X+Y set geometry of the main window -dbg feature[,feature]... select the features to debug. Type `lyx -dbg' to see the list of features -x [--execute] command where command is a lyx command. -e [--export] fmt where fmt is the export format of choice. -i [--import] fmt file.xxx where fmt is the import format of choice and file.xxx is the file to be imported. -versionsummarize version and build info Check the LyX man page for more details. Now this is the funny part, the _fmt_ key that we are searching for is defined in: Edit-Preferences-File Formats, look then for format. In my case I have 3 defined pdf formats. Using pdf2 I get: $ lyx -e pdf2 spyce.lyx Document exported as PDF (pdflatex) to file `~/thunderbird/level-3/spyce.pdf' $ lyx -e pdf3 spyce.lyx Executing command:dvipdfm -p letter 'spyce.dvi' spyce.dvi - spyce.pdf [1] 55669 bytes written Document exported as PDF (dvipdfm) to file `~/thunderbird/level-3/spyce.pdf' Bingo. :-) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, -- Jane McKean -- José Abílio
Generating LyX docs in a build
Hi there: I have a question that I hope you can help me with. I'm using LyX 1.3.6 on Fedora Core 4 (Linux) with the change bar patch (using dvipost). I create all of the user documentation for our compiler suite (except for the README and man pages) in LyX, and up until now, I've generated PDFs and checked them into our build tree. We automatically build the compiler environment software daily and those PDFs get picked up as a final step in the build. Our buildmaster would like to have the build process generate the final PDFs and only have the .lyx files (and possibly the .tex files) checked in. This way the build process could generate the most current daily PDFs that would be up-to-date with the software. During our production cycle, I use change bars on the docs and generate the PDF using PDF (dvipdfm) from the LyX menu bar, and then about a week before release, I turn the change bars off and generate the PDF using PDF (pdflatex). To accomplish this as part of the build, I need a command line equivalent (and it could be multiple command lines) for each of these methods. - The command-line equivalent for View > PDF (dvipdfm) - The command-line equivalent for View > PDF (latexpdf) Has anyone tried doing something like this? Is anyone currently generating their docs as part of a source code build with build script? Many thanks in advance, --jane -- Jane McKean Technical Documentation PathScale, Inc. jane at pathscale.com
Re: Generating LyX docs in a build
On Friday 02 September 2005 23:33, Jane McKean wrote: > To accomplish this as part of the build, I need a command line > equivalent (and it could be multiple command lines) for each of these > methods. > > - The command-line equivalent for View > PDF (dvipdfm) > > - The command-line equivalent for View > PDF (latexpdf) That is a good question that I have seen answered sometimes on this list. :-) Searching... $ lyx --help Usage: lyx [ command line switches ] [ name.lyx ... ] Command line switches (case sensitive): -help summarize LyX usage -userdir dir try to set user directory to dir -sysdir dirtry to set system directory to dir -geometry WxH+X+Y set geometry of the main window -dbg feature[,feature]... select the features to debug. Type `lyx -dbg' to see the list of features -x [--execute] command where command is a lyx command. -e [--export] fmt where fmt is the export format of choice. -i [--import] fmt file.xxx where fmt is the import format of choice and file.xxx is the file to be imported. -versionsummarize version and build info Check the LyX man page for more details. Now this is the funny part, the _fmt_ key that we are searching for is defined in: Edit->Preferences->File Formats, look then for format. In my case I have 3 defined pdf formats. Using pdf2 I get: $ lyx -e pdf2 spyce.lyx Document exported as PDF (pdflatex) to file `~/thunderbird/level-3/spyce.pdf' $ lyx -e pdf3 spyce.lyx Executing command:dvipdfm -p letter 'spyce.dvi' spyce.dvi -> spyce.pdf [1] 55669 bytes written Document exported as PDF (dvipdfm) to file `~/thunderbird/level-3/spyce.pdf' Bingo. :-) > Has anyone tried doing something like this? Is anyone currently > generating their docs as part of a source code build with build script? > > Many thanks in advance, > > -- > Jane McKean -- José Abílio
