On Fri, 27 Feb 2015 06:56:44 -0800 (PST) Todd Mars <[email protected]> wrote:
> Hi! > I'm very pleased reading the design of the @clean implementation! > Very interesting and I'm fascinated by the implications and > applications. So, I'm looking at some word documents that have > outlines that are produced automatically by word processing programs. > 1. blah > a. blah blah > i. blah > ii. blah > iii. Heh, don't think I've ever seen a Word doc. more than a page and half long with a hierarchy that's not fouled up. Even people whose job is basically writing in Word seem unable to make it keep indentation / bullets / numbering consistent for more than a page or so. One Leo -> Word path I've used before, when collaboration leaves me no choice, is via reStructuredText, rst. rst2odt makes an OpenOffice document that OpenOffice can convert to a .doc(x) (if Word can't read .odt, not sure). The conversion can be done from the command line, i.e. an environment in which you author in Leo and output to .doc(x) is doable. Like Jake said the other way might be harder but pandoc http://johnmacfarlane.net/pandoc/ docx -> rst, which you can load in Leo. Except that Word docs. often use "bold + fontsize 18" for headings, rather than actual heading semantics. Cheers -Terry > 1. > 2. > 3. > iv. > b. > c. > 2. > > So how to export and import this from leo outline into perhaps a dox > or something? perhaps the index level would be a headline > auto-produced and the body would be the text blah blah parts. > I know word documents are hopelessly archaic but still used. > > Todd. > > -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
