Project

Profile

Help

Feature #4810

Comparing different versions of the compiled SEF would be easier if a couple of line breaks were added

Added by Norm Tovey-Walsh 8 months ago. Updated 4 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2020-10-27
Due date:
% Done:

0%

Estimated time:
Applies to JS Branch:
2
Fix Committed on JS Branch:
Fixed in JS Release:
SEF Generated with:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

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 buildDateTime property.

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.

History

#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.

#2 Updated by Norm Tovey-Walsh 5 months ago

  • Status changed from New to Rejected

Yes, closing this with no action is fine. It was just a thought.

#3 Updated by Community Admin 4 months ago

  • Applies to JS Branch 2 added
  • Applies to JS Branch deleted (2.0, Trunk)

Please register to edit this issue

Also available in: Atom PDF Tracking page