Hi,
Talking about being a little bit off-topic, and other tools that manage
the writing workflow, from outlines to pdf, word, LaTeX, the workflow
with Grafoscopio is to export the tree as pandoc's markdown or, if
Pandoc is installed, to export directly to pdf or html. Other formats,
supported by pandoc can be added easily and from there importing to
word. One of the nice things I like about this approach is that is less
verbose that LaTeX, but can be combined with it, for more fine grained
control over the output and the outline markup can be customize for your
particular workflow (I use %keywords, that are inspired by leo
@directives). Experimental Zotero integration is being tested. You can
find more details in the Grafoscopio Manual at [1]
[1]
http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/Books/Manual/manual.pdf
Cheers,
Offray
On 10/04/17 06:15, Israel Hands wrote:
Hi Largo,
Apologies for being a bit off topic but have a look at Scrivener which
uses rtf files but can compile to .doc and .docx (though I have never
used these). Scrivener is excellent for a master document with
multiple sub documents - allowing great flexibility. That is exactly
what Scrivener is designed to do. There's a free 30 day trial and it
runs on MacOs and Windows. And now my question.
I paid for both the Windows and MacOs versions of Scrivener and I love
it - I use its Latex compile options to get to pdf from markdown but
great as it is Scrivener doesn't have the power of Leo, and I would
rather have all my eggs in one basket.
So I'm very interested in your workflow that gets you out of Leo to
pdf via Latex. I'm not at all technical but if there is a
straightforward work flow I'd love to see it. As a simple soul I need
something like Auctex in Emacs - press Ctrl C twice and your document
gets Latexed!
ta
Israel
On Saturday, April 8, 2017 at 3:26:45 AM UTC+1, Largo84 wrote:
Thanks for the suggestions. I messed around several years ago w/
docutils, but since command line tools are always a struggle for
me, I didn't stick with it. Not sure why CLI is so hard for me.
I'll take a look at the plugin also.
Rob.....
On Friday, April 7, 2017 at 9:12:35 PM UTC-4, Edward K. Ream wrote:
On Fri, Apr 7, 2017 at 1:42 PM, Largo84 <[email protected]> wrote:
Any suggestions on how I can use Leo's organizational
strengths to write this knowing that when done, it will
need to export to Word (LibreOffice ODT and maybe RTF
would be OK too)?
Dan Rahmel wrote the leo_to_rtf.py plugin several years ago.
It's listed as experimental.
I just tried this plugin. With Python 3 there is the usual
porting problem: bytes instead of strings. With Python 2, the
plugin writes an .rtf file, but Open Office complains about
the format. It's probably worth a close look.
Edward
--
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]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
--
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.
