I spent some time experimenting with html-formatted help commands. I quickly came to the conclusion that this was a bad idea: using <pre> will not look good enough, and it is out of the question to hand-format docs twice.
Instead, Leo will load docutils from leo/extensions if an initial import of docutils fails. That way, newbies will see the best-possible help commands, without having to explicitly install docutils. I'll soon be upping new code with fallback imports using g.importExtension. There seems to be a problem with docutils on Windows with Python 3.x. The docutils docs say that 2to3 is run "on demand", but that doesn't appear to be working. Happily, it took just a few seconds to run 2to3 on the docutils-0.10/build folder, and a few more seconds to copy that to my Python 3.3 folder. This is, iirc, the *first* time I have ever successfully run docutils with Python 3.x. In short, distributing a fallback copy of docutils with Leo makes sense to me. It eliminates dual documentation, and should ensure that all Leo newbies will see good-looking docs. The downside is that the docutils folder is about 2.7 meg. Your comments, please. 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]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
