On Fri, May 1, 2009 at 1:55 PM, Ville M. Vainio <vivai...@gmail.com> wrote:
> > On Fri, May 1, 2009 at 9:29 PM, Edward K. Ream <edream...@gmail.com> > wrote: > > > There is a question of whether the importer should import the rST file > > into an @rst tree, in such a way that writing that tree (with Leo's > > write command, or with the rst plugin) would faithfully recreate the > > original file. The problem with using Leo's write command is that the > > My opinion, FWIW: > > I don't mind if Leo "normalizes" or completely mangles the rst > document (though extensive mangling should not be necessary). The > important thing is that this should only happen once - that is, once > leo has written out an rst document, reading it back in and writing > out again should not cause changes in the document. This has always been my opinion too. However, it wold be a plus if we can avoid normalization in most cases. > > Use case for this is publishing an rst document that is mostly edited > with leo in version control system. Others may edit it without leo, > and opening such a document with leo again can do some changes to the > document, but not so much as to make investigating the version history > messy. > Seems reasonable. In many cases, though, no normalization would happen. In particular, the underline_characters setting would not likely change, because changing underlining outside of Leo/rst3 is clumsy. 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 -~----------~----~----~----~------~----~------~--~---
