Thanks Rob,
I agree with you about the limitations of Scrivener to Latex - which are
due to the fact that the process is actually Scrivener MultiMarkDown then
to Latex. This is great because MultiMarkDown is very clean - very
uncluttered compared with the Latex file full of mark up commands. However
it is limiting because you can't just drop in a Latex command in the MMD
file and get it out the other end. I think there is a way but it seemed
very cumbersome to me. This also means there is confusion about what is the
master file - is it the Markdown file in Scrivener or the compiled Latex
file on the OS file system. The worst thing is the temptation to edit the
Latex file directly as now your Scrivener master is out of sync, not good.
But always returning to Scrivener is slower process.
Your work flow sounds good - I can imagine abbreviations would be a big
help and it would be nice to standardise them early on!
Emacs can drive the Latex engine in the background and then sync with a pdf
viewer - I'm sure Leo could do this just as well, if not better.
IH
On Saturday, 3 March 2018 22:51:06 UTC, Largo84 wrote:
>
> Wow, reading Israel's post made me me think I wrote it (except the
> org-mode part). Probably 80+% of my work in Leo is writing content w/ LaTEX
> output. Most of the rest is variations of markdown and RST. I tried moving
> my work to Scrivener and really like it a lot. However, I like Leo better
> (plus it's free and open source) and once I figured out how to link to
> external resources, I never went back to Scrivener. I don't like using
> LaTEX content auto-generated from something else. I end up spending too
> much time cleaning it up. For what it's worth, my work flow with LaTEX
> content is:
>
> 1. I mostly write content directly in LaTEX syntax (it's cleaner and
> easier to edit directly). I created many Leo abbreviations to speed up the
> process (lists, sections, etc.)
> 2. I wrote several outline-data-tree abbreviations to create 'wrapper'
> shells for different kinds of documents (preambles, etc). Then I simply
> input the LaTEX content files (\input{content.tex}}.
> 3. Since I'm mostly on Windows, I use the excellent TeXnic Center
> <http://www.texniccenter.org/> compiler to create the PDF output. (I
> never use it to edit, only to compile.)
> 4. Rarely, if I need to export to something else (xxx.docx or xxx.rtf
> or xxx.html), I write in multi-markdown and use Pandoc to output.
>
> Excellent post and I'd love to share ideas with other Leo/LaTEX users on
> work flow. Perhaps I can steal a few better ideas or trade for some of my
> own.
>
> 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.
