In another post
<https://groups.google.com/d/msg/leo-editor/vIzzE669wk0/PBMNybdpAAAJ>,
Israel Hands asked about a straightforward Leo workflow to use LaTex to get
PDF final output. So, here is mine for whatever it's worth. Readers will
decide for themselves how 'straightforward' it is; it works for me and I
use it a lot. Maybe others will get some benefit from it and maybe some
will offer suggestions to improve it. If there's interest, I can attach a
minimal .leo file that demonstrates some of the following techniques.
*Typical Use case*
I teach a variety of classes in a business environment and need handouts,
teaching aids, worksheets and training manuals that are specifically
customized for each client. These documents are easier to manage, print and
protect using standard PDFs.
*Workflow Overview*
1. Document content comes from a primary resource directory arranged by
topic (not client specific).
2. I have a Resources.leo file that helps me keep that directory
organized.
3. All of the content files are written in LaTex (I use a .txi file
extension of my own invention to indicate the file is an 'input' file only,
not the main output file which uses .tex).
4. I have a Client.leo file for each client in their own directory to
organize work specific to each client.
5. For each document needed for a client project, I create a
Document.tex file from a standard template and change the document
properties as needed for the specific client, project and document.
6. The Document.tex file acts as the presentation 'shell' for the
document and I simply add \input{"\ResourcePath Content.txi"} after the
\begin{document} statement (\ResourcePath is a shortcut command to the
location of the content resource). This shell determines such things as the
document title, document type, client name, header/footer information and
revision date.
7. Since I work primarily in Windows, I use TeXNicCenter
<http://www.texniccenter.org/> to process (typeset) the Document.tex
file to create PDF output. (I do not use TeXNicCenter for editing, only
file processing).
*Workflow Notes and Shortcuts*
1. Years ago, I discovered the incredible exam class for LaTex
<http://www-math.mit.edu/~psh/exam/examdoc.pdf> and now use it almost
exclusively. It makes it much easier to create student and teacher versions
of the same content (eg. handout for students and training manual with
speaking notes for the teacher).
2. I use the new @outline-data tree-abbreviations in Leo to create each
new Document.tex file from a template with variables (very cool!)
3. I created many @data abbreviations in Leo to speed up typing of
standard LaTex structures (would be happy to share them if anyone is
interested).
4. All document content stays in the Resources directory and only
'shell' documents are in the client directories.
5. These shell documents allow for client-specific information to be
added to the headers, footers and in some cases as variables inside the
content area itself (using \theClient variable that I define).
*Software Needed*
1. Leo (of course, and its dependencies).
2. MiKTex for the LaTex distribution and package management (I have it
set to auto-update as needed).
3. TeXNicCenter for processing (typesetting) to PDF output.
Regards,
Rob........
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
