On Wed, Jul 5, 2017 at 4:30 AM, vitalije <[email protected]> wrote:
> Yes, we are discussing dropping Leo's XML format. > Imo, we are discussing adding support for .leo.db files, not removing support for .leo files. > The only advantage of XML is that it is human readable > That can be a big advantage when things go wrong. > I would argue that in fact sqlite file is more human readable than XML if > one uses any of many available tools for reading/manipulating sqlite db > files. It is much easier to understand and change something in sqlite > representation of Leo document than it is in XML version. > That's good to know. I do not want to force Leo users to abandon the .leo format. xml is a standard, and who knows how Leo users are using that format? Do *not* assume that you know the answer to this question! Happily, this discussion is premature. Note to Terry: imo, it's worth virtually any amount of behind-the-scenes effort so that we don't disrupt users' experience. Forking python has been a catastrophe. We don't want anything like that for Leo. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
