Mercurial Friendly Data Storage

[Marcin Kasperski]

> For instance, if I used XML and a file contained a line "<name>
> Michael Diamond</name>" and it was changed from "<name>Mikahl Dimoond</name>" I
> want my program to be able to identify what changed was the <name> tag, just
> from the change diff.
>
> And so my question is, what are your thoughts on the best way to store this
> data to make Mercurial's job easiest?

I would say that a) textual, b) one where typical edits never reorganise
the file noticeably and c) one where diffs are readable and changes local.

Personally I would prefer JSON to XML, consider YAML but gave even more
attention to formats which use empty lines to separate sections (INI
maybe?) Or just sth like

   My own:

   - pretty: format
   
   - with: spacing

The best suggestion I can make: just create as many variations as you
can, make some edits and see how diff tools you use show them. Then pick
2 most promisting cases and test conflicts and merges.