I see that Leo's user manual is written as single rst file.
Otoh, when I was writing book-long documents (e.g. in LyX/LaTeX), I
usually used master document and put every chapter in a separate file.
Now, I would like to hear some pro/cons of the above two strategies
when using Leo & writing in rst markup?
(Of course, the docs is going to be under VCS - darcs.)
Sincerely,
Gour
--
Gour | Hlapicina, Croatia | GPG key: F96FF5F6
----------------------------------------------------------------
Ville> Pro multiple files: plays better with version control & multiple
Ville> authors.
Thanks.
Ville> At this point I'd probably suggest multiple @auto-rst .txt
Ville> files. Or @thin .txt files if everyone is using Leo.
What about @shadow?
I'm still experimenting with different options and see that Leo (sometimes)
gets confused when I change node options and refuses to write my *.leo file.
Edward> BTW, I have disabled the '@rst leoUsersGuide.txt' node in
Edward> LeoDocs.leo by converting it to '@@rst...' I did this awhile
Edward> ago because it was causing problems. Don't remember the
Edward> details.
Let me tell you that having @@rst above does not bring much clarity to
the Leo noob looking for an optimal setup to have multi-file setup
(the book divided ala latex: front-matter etc.) for a book to be
written in rst markup and automatically convert it via Sphinx to
html/pdf output.
If @@rst does not bring anything it would be better to get removed to
spare us some unnecessary confusion.
Let me tell you that having @@rst above does not bring much clarity to
the Leo noob