Beschreibung
array
exif_read_data ( string filename [, string sections [, bool arrays [, bool thumbnail]]])
The exif_read_data() function reads the
EXIF headers from a JPEG or
TIFF image file. This way you can read meta data
generated by digital cameras.
filename is the name of the file to read. This
cannot be a URL.
sections is a comma separated list of sections that
need to be present in file to produce a result array. If none of the
requested sections could be found the return value is FALSE.
arrays specifies whether or not each section
becomes an array. The sections COMPUTED,
THUMBNAIL and COMMENT always
become arrays as they may contain values whose names are conflict
with other sections.
thumbnail whether or not to read the thumbnail
itself and not only its tagged data.
Anmerkung:
Exif headers tend to be present in JPEG/TIFF images generated by digital
cameras, but unfortunately each digital camera maker has a different
idea of how to actually tag their images, so you can't always rely on
a specific Exif header being present.
Windows ME/XP both can wipe the Exif headers when connecting to a camera.
More information available at http://www.canon-asia.com/products/digital_cameras/winxp_problems.html.
Anmerkung:
If the image contains any IFD0 data then COMPUTED contains the entry
ByteOrderMotorola which is 0 for little-endian (intel) and 1 for
big-endian (motorola) byte order. This was added in PHP 4.3.0.
When an Exif header contains a Copyright note this itself can contain two
values. As the solution is inconsistent in the Exif 2.10 standard the COMPUTED
section will return both entries Copyright.Photographer
and Copyright.Editor while the IFD0 sections contains
the byte array with the NULL character that splits both entries. Or just the
first entry if the datatype was wrong (normal behaviour of Exif). The
COMPUTED will contain also an entry Copyright Which
is either the original copyright string or it is a comma separated list of
photo and editor copyright.
Anmerkung:
The tag UserComment has the same problem as the Copyright tag. It can store
two values first the encoding used and second the value itself. If so the
IFD section only contains the encoding or a byte array. The COMPUTED section
will store both in the entries UserCommentEncoding and
UserComment. The entry UserComment
is available in both cases so it should be used in preference to the value
in IFD0 section.
If the user comment uses Unicode or JIS encoding and the module mbstring is
available this encoding will automatically changed according to the exif
ini settings in the php.ini. This was added in PHP 4.3.0.
Anmerkung:
Height and Width are computed the same way getimagesize()
does so their values must not be part of any header returned. Also html is
a height/width text string to be used inside normal HTML.
Anmerkung:
Starting from PHP 4.3.0, the function can read all embedded
IFD data including arrays (returned as such). Also
the size of an embedded thumbnail is returned in
THUMBNAIL subarray and the function
exif_read_data() can return thumbnails in
TIFF format. Also as of PHP 4.3.0 there is no longer
a maximum length for returned values (not until memory limit is reached).
Since PHP 4.3,0 user comment can automatically change encoding if PHP was
compiled using --enable-mbstring.