mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-17 01:18:55 +00:00
Fixing bug #25230. Reformatting.
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@138705 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Dallas Wang
parent
abe13cb19a
commit
ff79b75fd0
1 changed files with 39 additions and 39 deletions
|
|
@ -1,5 +1,5 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.9 $ -->
|
||||
<!-- $Revision: 1.10 $ -->
|
||||
<!-- splitted from ./en/functions/image.xml, last change in rev 1.78 -->
|
||||
<refentry id="function.exif-read-data">
|
||||
<refnamediv>
|
||||
|
|
@ -40,7 +40,7 @@
|
|||
</row>
|
||||
<row>
|
||||
<entry>COMPUTED</entry>
|
||||
<entry>html, Width, Height, IsColor and some more if available.
|
||||
<entry>html, Width, Height, IsColor and some more if available.
|
||||
</entry>
|
||||
</row>
|
||||
<row>
|
||||
|
|
@ -74,8 +74,8 @@
|
|||
</para>
|
||||
<para>
|
||||
<parameter>arrays</parameter> specifies whether or not each section
|
||||
becomes an array. The sections <emphasis>FILE</emphasis>,
|
||||
<emphasis>COMPUTED</emphasis> and <emphasis>THUMBNAIL</emphasis> allways
|
||||
becomes an array. The sections <emphasis>COMPUTED</emphasis>,
|
||||
<emphasis>THUMBNAIL</emphasis> and <emphasis>COMMENT</emphasis> allways
|
||||
become arrays as they may contain values whose names are conflict
|
||||
with other sections.
|
||||
</para>
|
||||
|
|
@ -153,72 +153,72 @@ THUMBNAIL.Thumbnail.Height: 1
|
|||
</para>
|
||||
<note>
|
||||
<para>
|
||||
If the image contains any IFD0 data then COMPUTED contains the entry
|
||||
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.
|
||||
</para>
|
||||
<para>
|
||||
When an Exif header contains a Copyright note this itself can contain two
|
||||
values. As the solution is inconsitent in the Exif 2.10 standard the COMPUTED
|
||||
When an Exif header contains a Copyright note this itself can contain two
|
||||
values. As the solution is inconsitent in the Exif 2.10 standard the COMPUTED
|
||||
section will return both entries <emphasis>Copyright.Photographer</emphasis>
|
||||
and <emphasis>Copyright.Editor</emphasis> 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 <emphasis>Copyright</emphasis> Which
|
||||
is either the original copyright string or it is a comma separated list of
|
||||
is either the original copyright string or it is a comma separated list of
|
||||
photo and editor copyright.
|
||||
</para>
|
||||
</note>
|
||||
<note>
|
||||
<para>
|
||||
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 <emphasis>UserCommentEncoding</emphasis> and
|
||||
<emphasis>UserComment</emphasis>. The entry <emphasis>UserComment</emphasis>
|
||||
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 <emphasis>UserCommentEncoding</emphasis> and
|
||||
<emphasis>UserComment</emphasis>. The entry <emphasis>UserComment</emphasis>
|
||||
is available in both cases so it should be used in preference to the value
|
||||
in IFD0 section.
|
||||
</para>
|
||||
<para>
|
||||
If the user comment uses Unicode or JIS encoding and the module mbstring is
|
||||
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.
|
||||
</para>
|
||||
</note>
|
||||
<note>
|
||||
<para>
|
||||
Height and Width are computed the same way <function>getimagesize</function>
|
||||
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 <acronym>HTML</acronym>.
|
||||
Height and Width are computed the same way <function>getimagesize</function>
|
||||
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 <acronym>HTML</acronym>.
|
||||
</para>
|
||||
</note>
|
||||
<note>
|
||||
<para>
|
||||
Starting from PHP 4.3 the function can read all embedded <acronym>IFD</acronym>
|
||||
data including arrays (returned as such). Also the size of an embedded thumbnail
|
||||
is returned in <emphasis>THUMBNAIL</emphasis> subarray and the function
|
||||
<function>exif_read_data</function> can return thumbnails in <acronym>TIFF</acronym>
|
||||
format. Last but not least there is no longer a maximum legth for returned
|
||||
values (not until memory limit is reached).
|
||||
Starting from PHP 4.3 the function can read all embedded <acronym>IFD</acronym>
|
||||
data including arrays (returned as such). Also the size of an embedded thumbnail
|
||||
is returned in <emphasis>THUMBNAIL</emphasis> subarray and the function
|
||||
<function>exif_read_data</function> can return thumbnails in <acronym>TIFF</acronym>
|
||||
format. Last but not least there is no longer a maximum legth for returned
|
||||
values (not until memory limit is reached).
|
||||
</para>
|
||||
</note>
|
||||
<note>
|
||||
<simpara>
|
||||
This function is only available in PHP 4 compiled using
|
||||
<option role="configure">--enable-exif</option>.
|
||||
Its functionality and behaviour has changed in PHP 4.2. Earlier versions
|
||||
are very unstable.
|
||||
</simpara>
|
||||
<simpara>
|
||||
Since PHP 4.3 user comment can automatically change encoding if PHP 4 was
|
||||
compiled using <option role="configure">--enable-mbstring</option>.
|
||||
</simpara>
|
||||
<simpara>
|
||||
This function does not require the GD image library.
|
||||
</simpara>
|
||||
<simpara>
|
||||
See also <function>exif_thumbnail</function> and <function>getimagesize</function>.
|
||||
</simpara>
|
||||
<simpara>
|
||||
This function is only available in PHP 4 compiled using
|
||||
<option role="configure">--enable-exif</option>.
|
||||
Its functionality and behaviour has changed in PHP 4.2. Earlier versions
|
||||
are very unstable.
|
||||
</simpara>
|
||||
<simpara>
|
||||
Since PHP 4.3 user comment can automatically change encoding if PHP 4 was
|
||||
compiled using <option role="configure">--enable-mbstring</option>.
|
||||
</simpara>
|
||||
<simpara>
|
||||
This function does not require the GD image library.
|
||||
</simpara>
|
||||
<simpara>
|
||||
See also <function>exif_thumbnail</function> and <function>getimagesize</function>.
|
||||
</simpara>
|
||||
</note>
|
||||
</refsect1>
|
||||
</refentry>
|
||||
|
|
|
|||
Loading…
Reference in a new issue