Hey all, I wrote a patch that removes the json command in favor of the xml command (see bug #782 for why I did this. Basically it was the approach that took the shortest amount of time and I saw by far more requests for a working xml command than for a working json command). I did not add a baseline test as the account ids etc. change every time the output is generated. Bummer. I decided to push the patch to next. I think it is better to ship one working than two broken commands. I plan to work on a json command eventually.
Now here is where I need your help. Look at the output the xml command gives you (Preferably using something like ./ledger xml | tidy -xml -indent -utf8 | less). Does everything look reasonable? Now is the time to propose any change to the structure as it will be more or less final once 3.0 is released. For example naming of attributes, naming of elements, whether a value should be an attribute or a child node… I checked this both using my own ledger and drewr.dat and everything seems reasonable. But please report if you find missing information. -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
