Closed GoogleCodeExporter closed 9 years ago
Well, the reason for this is that one can easily use a third party utility (I
use
Firefox especially) for purposes of viewing XML, despite its original
formatting.
Stripping out whitespaces makes the output smaller (which can really add up for
large
XML documents, depending on if you're using tabs or spaces) and AFAIK doesn't
create
any issues for WPKG.
Unless a strong case can be made to support the use of formatted vs.
unformatted XML
output, I don't see this being added any time soon.
Original comment by msc...@gmail.com
on 10 Nov 2009 at 8:56
Its handy for debugging xml errors when wpkgexpress fails to import an xml file.
Else you get a line 1 error everytime :)
It is a minor issue, I can format the xml manually then import it, but the
extra
step when testing just adds to the tedium.
Original comment by mem.name...@gmail.com
on 24 Nov 2009 at 6:53
There'll be an togglable option to output formatted XML, in the next revision.
Original comment by msc...@gmail.com
on 28 Nov 2009 at 12:08
Excellent, much appreciated :)
Original comment by mem.name...@gmail.com
on 28 Nov 2009 at 4:50
Added in next revision.
Original comment by msc...@gmail.com
on 29 Nov 2009 at 2:02
Original comment by msc...@gmail.com
on 29 Nov 2009 at 3:41
Original issue reported on code.google.com by
mem.name...@gmail.com
on 10 Nov 2009 at 8:43