NAME
json2yaml.pl : convert JSON to YAML with formatting options.
VERSION
Version 0.29
SYNOPSIS
json2yaml.pl -i "input.json" -o "output.yaml" --(no-)escape-unicode
json2yaml.pl -e < "input.json" > "output.yaml"
# press CTRL-D when done typing JSON to STDIN
# input must be less than 4K long!
json2yaml.pl
# Read input from clipboard or write output to clipboard
# Only in: Unix / Linux / OSX
# (must have already installed xclip or xsel or pbpaste (on OSX))
json2json.pl -e < $(xclip -o)
json2json.pl -e < $(pbaste)
# write the output to the clipboard for further pasting
json2json.pl -i input.json | xclip -i
# clicking mouse's middle-button will paste the result
USAGE
json2yaml.pl
Options:
--i filename
: specify a filename which contains a JSON data structure.--I "string"
: specify a string which contains a JSON data structure.--o outputfilename
: specify the output filename to write the result to, which will be YAML.--escape-unicode
: it will escape all unicode characters, and convert them to something like "\u0386". This is the default option.--no-escape-unicode
: it will NOT escape unicode characters. Output will not contain "\u0386" or "\x{386}" but "α" (that's a greek alpha).
Input can be read from an input file (--i), from a string at the command line (--I) (properly quoted!), from STDIN (which also includes a file redirection json2yaml.pl < inputfile.json > outputfile.yaml
For more information see Data::Roundtrip.
CAVEATS
Under Unix/Linux, the maximum number of characters that can be read on a terminal is 4096. So, in reading-from-STDIN mode beware how much you type or how much you copy-paste onto the script. If it complains about malformed input then this is the case. The workaround is to type/paste onto a file and operate on that using --i afile
or redirection < afile
.
AUTHOR
Andreas Hadjiprocopis, <bliako at cpan.org> / <andreashad2 at gmail.com>