On Fri, 27 Feb 2015 06:56:44 -0800 (PST)
Todd Mars <
tam...@gmail.com> 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