On Tue, Mar 24, 2009 at 12:00 PM, Ville M. Vainio <vivai...@gmail.com>wrote:
> > - If leo is not made to work with @thin rst nodes (current situation), > you can *generate* rst files from your outlines. See the difference? > You may have some mechanism of importing external rst files once, but > then you are on your own, editing the leo document and occasionally > "releasing" it - but not really collaborating with the same document > with anyone. Even collaboration with Leo users is questionable, since > the .leo xml files are very bad for merging. @thin files (containing @rst trees) provide the collaboration. The rst3 plugin provides the translation from a node, say from "My section", to:: My section ======== Imo, this is plenty good enough. If you want to collaborate using @edit files, you are certainly free to do so, but please do not ask leoAtFile.py to learn rST markup. Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---