One thing to consider is what level of change to the file is acceptable? If
it is just to be human read, than the suggestions already given may do what
you want; but it you want to take that result and preserve it for future
use, then the mxj and the encoding/xml based methods may produce unwant
Well, pretty much all the functionality you need is in
clbanning/mxj/xmlseq.go ... so you could cut it out and clean it up a bit.
On Monday, December 11, 2017 at 9:03:12 AM UTC-7, C Banning wrote:
>
> https://godoc.org/github.com/clbanning/mxj#BeautifyXml does that - but
> you've got to lug arou
https://godoc.org/github.com/clbanning/mxj#BeautifyXml does that - but
you've got to lug around a pretty large package just for that functionality.
On Monday, December 11, 2017 at 8:12:38 AM UTC-7, Mandolyte wrote:
>
> At my previous company I had a Go program that would take any XML document
>
