Imports binary property lists to XML format #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This re-implements a (slightly simplified version of) the changes to "Import Binary Property List.tmCommand" that were contained in the now obsolete #2.
With these changes, binary property list files will be presented using Apple's standard XML format, rather than using
pretty_print
's idiosyncratic variant of the ASCII format.This is important for the sake of protecting user data. If the user saves the XML representation back to disk, thereby overwriting the binary version, no data will be lost. In contrast, if the user accidentally saves the output from
pretty_plist
to disk, the property list file will mostly likely be rendered unreadable.In the unlikely event that
plutil
is unavailable, the import process falls back to the previous behaviour.