mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 00:48:54 +00:00
emphasis -> literal
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@169460 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
c8b844ebea
commit
3808af7f18
1 changed files with 16 additions and 13 deletions
|
@ -1,10 +1,13 @@
|
|||
<?xml version="1.0" encoding="iso-8859-1"?>
|
||||
<!-- $Revision: 1.4 $ -->
|
||||
<!-- $Revision: 1.5 $ -->
|
||||
<!-- splitted from ./en/functions/image.xml, last change in rev 1.78 -->
|
||||
<refentry id="function.exif-read-data">
|
||||
<refnamediv>
|
||||
<refname>exif_read_data</refname>
|
||||
<refpurpose>Reads the <acronym>EXIF</acronym> headers from <acronym>JPEG</acronym> or <acronym>TIFF</acronym></refpurpose>
|
||||
<refpurpose>
|
||||
Reads the <acronym>EXIF</acronym> headers from
|
||||
<acronym>JPEG</acronym> or <acronym>TIFF</acronym>
|
||||
</refpurpose>
|
||||
</refnamediv>
|
||||
<refsect1>
|
||||
&reftitle.description;
|
||||
|
@ -16,7 +19,7 @@
|
|||
<methodparam choice="opt"><type>bool</type><parameter>thumbnail</parameter></methodparam>
|
||||
</methodsynopsis>
|
||||
<para>
|
||||
The <function>exif_read_data</function> function reads the
|
||||
<function>exif_read_data</function> function reads the
|
||||
<acronym>EXIF</acronym> headers from a <acronym>JPEG</acronym> or
|
||||
<acronym>TIFF</acronym> image file. This way you can read meta data
|
||||
generated by digital cameras.
|
||||
|
@ -28,19 +31,19 @@
|
|||
a specific Exif header being present.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Height</emphasis> and <emphasis>Width</emphasis> are computed the
|
||||
<literal>Height</literal> and <literal>Width</literal> are computed the
|
||||
same way <function>getimagesize</function> does so their values must not be
|
||||
part of any header returned. Also, <emphasis>html</emphasis> is a
|
||||
part of any header returned. Also, <literal>html</literal> is a
|
||||
height/width text string to be used inside normal <acronym>HTML</acronym>.
|
||||
</para>
|
||||
<para>
|
||||
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 <emphasis>Copyright.Photographer</emphasis>
|
||||
and <emphasis>Copyright.Editor</emphasis> while the IFD0 sections contains
|
||||
section will return both entries <literal>Copyright.Photographer</literal>
|
||||
and <literal>Copyright.Editor</literal> 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 also contain the entry <emphasis>Copyright</emphasis> which
|
||||
COMPUTED will also contain the entry <literal>Copyright</literal> which
|
||||
is either the original copyright string, or a comma separated list of the
|
||||
photo and editor copyright.
|
||||
</para>
|
||||
|
@ -48,8 +51,8 @@
|
|||
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>
|
||||
will store both in the entries <literal>UserCommentEncoding</literal> and
|
||||
<literal>UserComment</literal>. The entry <literal>UserComment</literal>
|
||||
is available in both cases so it should be used in preference to the value
|
||||
in IFD0 section.
|
||||
</para>
|
||||
|
@ -139,8 +142,8 @@
|
|||
<listitem>
|
||||
<para>
|
||||
Specifies whether or not each section becomes an array. The
|
||||
<parameter>sections</parameter> <emphasis>COMPUTED</emphasis>,
|
||||
<emphasis>THUMBNAIL</emphasis>, and <emphasis>COMMENT</emphasis>
|
||||
<parameter>sections</parameter> <literal>COMPUTED</literal>,
|
||||
<literal>THUMBNAIL</literal>, and <literal>COMMENT</literal>
|
||||
always become arrays as they may contain values whose names conflict
|
||||
with other sections.
|
||||
</para>
|
||||
|
@ -184,7 +187,7 @@
|
|||
<entry>
|
||||
Can read all embedded <acronym>IFD</acronym> data including arrays
|
||||
(returned as such). Also the size of an embedded thumbnail is
|
||||
returned in a <emphasis>THUMBNAIL</emphasis> subarray, and can
|
||||
returned in a <literal>THUMBNAIL</literal> subarray, and can
|
||||
return thumbnails in <acronym>TIFF</acronym> format. Also, there is
|
||||
no longer a maximum length for returned values (not until the memory
|
||||
limit has been reached)
|
||||
|
|
Loading…
Reference in a new issue