File tree Expand file tree Collapse file tree 1 file changed +6
-2
lines changed
Expand file tree Collapse file tree 1 file changed +6
-2
lines changed Original file line number Diff line number Diff line change @@ -437,7 +437,10 @@ As a high-level language, signatures can be defined in easy to understand
437437syntax and then output consistently via the `json2pronom` utility. Signatures
438438include sensible defaults for whitespace and other aspects that are
439439difficult 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
442445Given a [sample pattern file ](./ pronom_example/ patterns_example.json) a DROID
443446compatible 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
You can’t perform that action at this time.
0 commit comments