1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
|
.TH EXIFCOM 1
.\"
.\" Copyright (c) 2002, 2003, Eric M. Johnston <emj@postal.net>
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by Eric M. Johnston.
.\" 4. Neither the name of the author nor the names of any co-contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $Id: exifcom.1,v 1.6 2003/01/20 22:51:32 ejohnst Exp $
.\"
.SH NAME
.B exifcom
\- display or set the UserComment tag contained in a JPEG Exif section
.SH SYNOPSIS
.B exifcom
[
.B \-bfinv
] [
.B \-w
.I comment
] [
.B \-s
.I delim
]
.I file ...
.SH DESCRIPTION
When invoked without arguments, the
.B exifcom
utility displays the contents of the Exif UserComment tag contained in
.I file
to the standard output. Otherwise, depending on the options specified,
.B exifcom
will blank the tag or set it to
.IR comment .
Some digital cameras include a standard UserComment tag in the Exif
data added to the image files they produce. This comment tag is
fixed-length and supports multi-byte character sets (though
.B exifcom
does not). Note that not all cameras will include the tag.
The utility is conservative in its approach to writing the UserComment tag.
It does not modify, extend, or otherwise adulterate an image's Exif
metadata structure. When writing the tag it merely changes pre-allocated
bytes. Therefore,
.B exifcom
is at the mercy of the Exif data creator for both the presence of the tag
and its length. It cannot create a UserComment tag when the camera does not
include one, nor can it write a comment longer than the space pre-allocated
by the camera.
.B exifcom
only displays and writes ASCII character set comments.
.SH OPTIONS
.IP -b
Blank the UserComment tag, overwriting both the character code and comment
fields with NUL. The character code specifies how the comment is
represented; it is "undefined" when blank. This is the state to which many
cameras initialize the tag. When used in conjunction with the
.B \-w
option,
.B exifcom
will blank the comment prior to setting it to
.IR comment .
.IP -f
Overwrite or blank existing or unsupported comments without prompting
for confirmation.
.IP -i
Write a prompt to standard error before overwriting or blanking an
existing or unsupported comment. If the response from the standard
input begins with 'y' or 'Y', the comment is overwritten. This option
is default behavior.
.IP -n
Do not overwrite or blank existing or unsupported comments and do not
prompt for confirmation (i.e., automatically answer 'no' to a confirmation
prompt). This option takes precedence over both the
.B \-f
and
.B \-i
options.
.IP -s
Separate field name and value in the verbose and multiple file cases with
the string
.IR delim .
The default is ': '.
.IP -v
Be verbose when printing the contents of the UserComment tag. Besides
the comment itself (if present and supported),
.B exifcom
will display the maximum comment length supported, the character code of
the comment, and the length of the comment.
.IP -w
Set UserComment to the ASCII string
.IR comment .
If
.IR comment
is longer than what the tag supports, it will be truncated to fit.
.SH DIAGNOSTICS
The
.B exifcom
utility exits 0 on success. When displaying a comment from a single file,
if the UserComment tag is missing, it exits 1; if blank, it exits 2; if in
an unsupported character code, it exits 3. Otherwise, it exits 1 if an
error occurs.
.SH "SEE ALSO"
exiftags(1)
.SH STANDARDS
The
.B exifcom
utility was developed using the January 2002 Exif standard, version 2.2
(http://tsc.jeita.or.jp/).
.SH BUGS
If the tag doesn't exist or is too short, too bad.
.SH AUTHOR
The
.B exifcom
utility and this man page were written by Eric M. Johnston <emj@postal.net>.
|
