|
|
489.
|
|
|
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.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
vorbiscomment/vcomment.c:566
|
|
|
490.
|
|
|
Examples:
vorbiscomment -a in.ogg -c comments.txt
vorbiscomment -a in.ogg -t "ARTIST=Some Guy" -t "TITLE=A Title"
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
vorbiscomment/vcomment.c:573
|
|
|
491.
|
|
|
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).
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
vorbiscomment/vcomment.c:578
|
|
|
493.
|
|
|
vorbiscomment from vorbis-tools
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
vorbiscomment/vcomment.c:662
|
|
|
501.
|
|
|
Error removing erroneous temporary file %s
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
vorbiscomment/vcomment.c:830
|
