Hi Sapphira, I too use Leo for writing. Luckily I discovered Leo over a decade ago and only had legacy txt and doc files to deal with when building a workflow.
Leo's rst handling does exactly what you want. Asciidoctor will convert asciidoc to docbook. Pandoc will convert docbook to rst. I am not sure how robust this would be for your application but once you have your content as rst, you should be good to go. Read through the rst section in the Leo docs to see if it will meet your needs. HTH, Chris On Mon, Aug 20, 2018 at 1:54 AM Sapphira Armageddos < shadowkyogre.pub...@gmail.com> wrote: > Hi everyone! I just discovered Leo yesterday and love it. It makes it a > lot easier to keep track of my characters across settings. > > I'm not sure how to control the output of headlines with @others, though. > There was an example of that in markdown's auto exporter, so I copied that > for asciidoc since the plugin for asciidoc is currently broken (It doesn't > work with the current API, and most of my stories were converted to > asciidoc format when I decided to hop off of Google Drive). > > I attached both the copied exporter and a Leo file showing how I normally > organize stories outside of Leo. Some nodes I want to keep their names, as > they represent important sections of a story (main title, chapter title, so > on so forth). Other nodes, however, I don't want to keep their names since > it detracts. Examples of this are scenes I may want to rearrange into > different chapters later on. > > The @auto nodes indicate file releases for the story and its chapters. > > Reading the documentation for @others suggests that the body is always > glued in the output file, but no option to include the headline in the > output. The closest example to what I'm looking for is the Flatten Outline > export, but it doesn't handle selectively outputting the headline when > needed. > > Is there a filetype agnostic way to do this? Using a write-only @auto node > doesn't seem right. > > (( PS: If you see a similar post appear in leo-editor, it might be because > I double posted this and didn't know if it went through. )) > > -- > 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 leo-editor+unsubscr...@googlegroups.com. > To post to this group, send email to leo-editor@googlegroups.com. > 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
