Skip to content

Commit a43eb34

Browse files
committed
More information on PRONOM output in README
1 parent 66b482d commit a43eb34

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -437,7 +437,10 @@ As a high-level language, signatures can be defined in easy to understand
437437
syntax and then output consistently via the `json2pronom` utility. Signatures
438438
include sensible defaults for whitespace and other aspects that are
439439
difficult for signature developers to consistently anticipate when writing
440-
JSON based signatures.
440+
JSON based signatures. One particular benefit of using `json2pronom` is that
441+
it can automatically output JSON signatures using different
442+
character encodings which use a lot of excess characters difficult for
443+
humans to format correctly into a DROID compatible format.
441444

442445
Given a [sample pattern file](./pronom_example/patterns_example.json) a DROID
443446
compatible snippet can be output as follows (UTF-8 shown for brevity):
@@ -465,7 +468,8 @@ compatible snippet can be output as follows (UTF-8 shown for brevity):
465468

466469
<!--markdownlint-enable-->
467470

468-
Feedback on this utility is welcome.
471+
Feedback on this utility is welcome. Hopefully we can build on this
472+
approach for other structured formats such as XML.
469473

470474
## Output format
471475

0 commit comments

Comments
 (0)