Hi, I use Pandoc's Markdown [1] for complex texts (technical docs, meeting notes and so on) and Markdeep[2] for quick publishing on the web and sane defaults. I'm now implementing a workflow to translate for the first to the second and vice versa. Pandoc filters give me the flexibility I need in case the original syntax is not good enough to write complex documents and even embedding LaTeX macros without the need to go full LaTeX. I just add the complexity I need when I need it (see for example [3] and its source code [4] that is mostly Pandoc's Markdown with custom filters).
[1] https://pandoc.org/ [2] https://casual-effects.com/markdeep/ [3] https://mutabit.com/repos.fossil/documentaton/uv/es/documentaton-0-2-x-breve.pdf [4] https://mutabit.com/repos.fossil/documentaton/dir?ci=tip&name=es/capitulos Cheers, Offray On 17/10/19 8:52 a. m., Rob wrote: > Curious what other Leonistas use when writing plain text (not coding). > Over the many years of using Leo, I have used markdown (md), > multi-markdown (mmd), rst and org mode (experimented some, but don't > really understand it). Haven't tried asciidoc yet. My current writing > practice is: > > * Write in rst if I need an output document in multiple formats > (LaTeX, html or odt). > * Write in md (or mmd) for quick and easy stuff; just capturing > information and usually store in external files. > * Write directly in LaTeX or html if there's no need to convert to > something else. Leo abbreviations makes this pretty easy. > > As I see it: > > *Plain markdown (GitHub style or multi-markdown)* > * > * > Pros: > > 1. Quick (easy to write). > 2. Very easy to read. > 3. Any plain text editor can open and edit. > 4. Leo supports in @auto-md mode. > 5. Pandoc converts md (and mmd) files easily to any other supported > format (as far as I know). > > Cons: > > 1. Limited syntax for complex documents. > 2. Not ideal for converting to LaTeX or html w/o additional work > (unless it's a simple document). > > *RST (reSTructured Text)* > * > * > Pros: > > 1. Well documented syntax. > 2. Comprehensive (easily supports footnotes, internal and external > links and other key document elements). > 3. Easy to write in @rst nodes in Leo. > 4. Output files from rst3 command are easy to open and read in > external text editors. > 5. Pandoc easily converts output files to any other supported formats. > > Cons: > > 1. Steeper learning curve than plain markdown. > 2. Not as easy to read (unless you understand the syntax). > > Not enough experience w/ org mode and none w/ asciidoc to comment. > There are a few others floating around which I haven't tried yet. > > If you'd like 'weigh in', I'd like to know which are your 'go-to' > plain text writing format(s) and why? What are your use-case > applications and the perceived pros (and perhaps cons) of each? > > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/51074427-c086-4220-8b63-4865d70b5b50%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/51074427-c086-4220-8b63-4865d70b5b50%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/4588717c-fd7e-2a2c-58a1-0e07f15593d6%40riseup.net.
