Comparing different versions of the compiled SEF would be easier if a couple of line breaks were added
Ignoring for a moment the question of whether or not one should need or want to compare different versions of a SEF file, it would be a lot easier to do so if the JSON output had a line break after the
Every compile is going to produce a couple of different timestamps, but it would be nice if
diff quickly revealed that those were the only differences.
#1 Updated by Michael Kay 5 months ago
If I need to look at SEF files the first thing I do is apply the Oxygen indenter to them, whether they're XML or JSON.
For both XML and JSON output we're using the standard Saxon serializer to generate the output. It's easy enough to insert an empty text node into the XML form, it's rather harder in the JSON. And the XX compiler actually emits XML and converts that to JSON as the final step.
I propose we close this with no action.
Please register to edit this issue