vorbiscomment from vorbis-tools 1.4.0

vorbiscomment from vorbis-tools 1.4.0 by the Xiph.Org Foundation (http://www.xiph.org/) List or edit comments in Ogg Vorbis files. Usage: vorbiscomment [-Vh] vorbiscomment [-lRe] inputfile vorbiscomment <-a|-w> [-Re] [-c file] [-t tag] inputfile [outputfile] Listing options -l, --list List the comments (default if no options are given) Editing options -a, --append Append comments -t "name=value", --tag "name=value" Specify a comment tag on the commandline -w, --write Write comments, replacing the existing ones Miscellaneous options -c file, --commentfile file When listing, write comments to the specified file. When editing, read comments from the specified file. -R, --raw Read and write comments in UTF-8 -e, --escapes Use \n-style escapes to allow multiline comments. -h, --help Display this help -V, --version Output version information and exit If no output file is specified, vorbiscomment will modify the input file. This is handled via temporary file, such that the input file is not modified if any errors are encountered during processing. vorbiscomment handles comments in the format "name=value", one per line. By default, comments are written to stdout when listing, and read from stdin when editing. Alternatively, a file can be specified with the -c option, or tags can be given on the commandline with -t "name=value". Use of either -c or -t disables reading from stdin. Examples: vorbiscomment -a in.ogg -c comments.txt vorbiscomment -a in.ogg -t "ARTIST=Some Guy" -t "TITLE=A Title" NOTE: Raw mode (--raw, -R) will read and write comments in UTF-8 rather than converting to the user's character set, which is useful in scripts. However, this is not sufficient for general round-tripping of comments in all cases, since comments can contain newlines. To handle that, use escaping (-e, --escape).