Hi,
Previously, to create a pdf from a Leo outline, I was using the
@auto-rst to create docs from a Leo, then I convert the output manually
to pdf using rst2latex + pdflatex or, if I want lesser control on pdf
output, just running rst2pdf directly. Now I want a more automatic
process that use buttons, for my less techie friends who are starting to
use leo. Besides using @auto-rst was not an option because in auto-sync
with the output some meta-structure (for example the one in @rst-ignore
nodes) get lost.
So I have opened LeoDocs.leo to try to learn how it works in order to
produce a pdf version of a Smalltalk tutorial I'm writing from a rst
doc, using also Sphinx and getting some advantages, specially related
with code coloring. I saw the rst3 button defined there, so I copied it
to my doc tree and enable it. I see that, in difference to what happens
when I use "@auto-rst filename.rst" nodes, I got a lot of orphan nodes
if I don't nest @file and @rst nodes, something like:
_ @auto-rst somefile.txt
|_@rst somefile.rst
At the end I got the required output with .txt alwas appended, something
like somefile.rst.txt. Is this behavior the intended one? There is any
way to change the .txt extension?
Cheers,
Offray
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
