cvs: phpdoc /en/features cookies.xml error-handling.xml http-auth.xml images.xml
| From: | WonHee Hwang | Date: | Tue, 09 Jan 2001 10:41:17 +0000 |
| Subject: | cvs: phpdoc /en/features cookies.xml error-handling.xml http-auth.xml images.xml | ||
| Groups: | php.doc | ||
| Request: | Send a blank email to phpdoc+get-969333502@lists.php.net to get a copy of this message | ||
regina Tue Jan 9 02:41:17 2001 EDT
Modified files:
/phpdoc/en/features cookies.xml error-handling.xml http-auth.xml
images.xml
Log:
PR:
Submitted by:
Reviewed by:
Obtained from:
Index: phpdoc/en/features/cookies.xml diff -u phpdoc/en/features/cookies.xml:1.2 phpdoc/en/features/cookies.xml:1.3 --- phpdoc/en/features/cookies.xml:1.2 Thu Dec 9 16:34:39 1999 +++ phpdoc/en/features/cookies.xml Tue Jan 9 02:41:17 2001 @@ -1,24 +1,19 @@ - <chapter id="features.cookies"> - <title>Cookies</title> - - <para> - PHP transparently supports HTTP cookies. Cookies are a mechanism - for storing data in the remote browser and thus tracking - or identifying return users. You can set cookies using the - <function>setcookie</function> function. Cookies are part of the - HTTP header, so <function>setcookie</function> must be called before - any output is sent to the browser. This is the same limitation that - <function>header</function> has.</para> - - <para> - Any cookies sent to you from the client will automatically be - turned into a PHP variable just like GET and POST method data. If - you wish to assign multiple values to a single cookie, just add - <emphasis>[]</emphasis> to the cookie name. For more details see - the <function>setcookie</function> function.</para> - - </chapter> - +<chapter id="features.cookies"> + <title>Cookies</title> + <para> + PHPë HTTP Cookie를 í¬ëª íê²(transparently) ì§ìíë¤. + Cookie ë©ì¹´ëì¦ì í¸ëí¹ì´ë ì¬ì©ì ìë³ ë±ì ìí´ ì격 browserì + ì ì¥ë ë°ì´í°ë¥¼ ëë ¤ ë°ë ê³¼ì ì ë§íë¤. + ì¬ë¬ë¶ì cookie를 ì¤ì í기 ìí´ <function>setcookie</function> í¨ì를 ì¬ì©í ì ìë¤. + Cookieë HTTP í¤ëì í ë¶ë¶ì´ë¯ë¡, <function>setcookie</function> í¨ìë ë¸ë¼ì°ì ë¡ + ë³´ë´ë ì´ë¤ ë°ì´í°ë³´ë¤ë ìì ì¬ì©í´ì¼ íë¤. + ì´ ì ì½ì <function>header</function> í¨ìì ê°ì ì ì½ì¼ë¡ ë³´ë©´ ëë¤.</para> + <para> + í´ë¼ì´ì¸í¸ê° ë³´ë´ì¤ 모ë cookieë ìëì ì¼ë¡ GETì´ë POST ë°©ì ë°ì´í°ì ê°ì PHP ë³ìë¡ ë³íëë¤. + ë§ì½ ì¬ë¬ë¶ì´ ëì¼í cookieì ì¬ë¬ ê°ì ì ì¥íê³ ì¶ë¤ë©´ Cookieì´ë¦ì <emphasis>[]</emphasis>를 ëíë©´ ëë¤. + ìì¸í ê²ì <function>setcookie</function> í¨ì ì¤ëª ì 참조íì. + </para> +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml Index: phpdoc/en/features/error-handling.xml diff -u phpdoc/en/features/error-handling.xml:1.10 phpdoc/en/features/error-handling.xml:1.11 --- phpdoc/en/features/error-handling.xml:1.10 Thu Sep 7 07:22:12 2000 +++ phpdoc/en/features/error-handling.xml Tue Jan 9 02:41:17 2001 @@ -1,104 +1,100 @@ - <chapter id="features.error-handling"> - <title>Error Handling</title> - - <para> - There are several types of errors and warnings in PHP. They are: - +<chapter id="features.error-handling"> + <title>Error Handling</title> + <para> + PHPìë ë¤ìê³¼ ê°ì ì¬ë¬ ìë¬ì ê²½ê³ ííê° ìë¤.: <table> - <title>PHP error types</title> - <tgroup cols="4"> - <thead> - <row> - <entry>Value</entry> - <entry>Constant</entry> - <entry>Description</entry> - <entry>Note</entry> - </row> - </thead> - <tbody> - <row> - <entry>1</entry> - <entry>E_ERROR</entry> - <entry>fatal run-time errors</entry> - <entry></entry> - </row> - <row> - <entry>2</entry> - <entry>E_WARNING</entry> - <entry>run-time warnings (non fatal errors)</entry> - <entry></entry> - </row> - <row> - <entry>4</entry> - <entry>E_PARSE</entry> - <entry>compile-time parse errors</entry> - <entry></entry> - </row> - <row> - <entry>8</entry> - <entry>E_NOTICE </entry> - <entry> - run-time notices (less serious than warnings) - </entry> - <entry></entry> - </row> - <row> - <entry>16</entry> - <entry>E_CORE_ERROR</entry> - <entry>fatal errors that occur during PHP's initial startup</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>32</entry> - <entry>E_CORE_WARNING</entry> - <entry> - warnings (non fatal errors) that occur during PHP's initial - startup - </entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>64</entry> - <entry>E_COMPILE_ERROR</entry> - <entry>fatal compile-time errors</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>128</entry> - <entry>E_COMPILE_WARNING</entry> - <entry>compile-time warnings (non fatal errors)</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>256</entry> - <entry>E_USER_ERROR</entry> - <entry>user-generated error message</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>512</entry> - <entry>E_USER_WARNING</entry> - <entry>user-generated warning message</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>1024</entry> - <entry>E_USER_NOTICE </entry> - <entry>user-generated notice message</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry></entry> - <entry>E_ALL</entry> - <entry>all of the above, as supported</entry> - <entry></entry> - </row> - </tbody> - </tgroup> - </table> - </para> - - <para> + <title>PHP error types</title> + <tgroup cols="4"> + <thead> + <row> + <entry>Value</entry> + <entry>Constant</entry> + <entry>Description</entry> + <entry>Note</entry> + </row> + </thead> + <tbody> + <row> + <entry>1</entry> + <entry>E_ERROR</entry> + <entry>Normal Function Errors (ì¼ë°ì ì¸ ìë¬)</entry> + <entry/> + </row> + <row> + <entry>2</entry> + <entry>E_WARNING</entry> + <entry>Normal Warnings (ì¼ë°ì ì¸ ê²½ê³ )</entry> + <entry/> + </row> + <row> + <entry>4</entry> + <entry>E_PARSE</entry> + <entry>Parser Errors (ë¬¸ë² ìë¬)</entry> + <entry/> + </row> + <row> + <entry>8</entry> + <entry>E_NOTICE </entry> + <entry> + Notices (무ìí ì ìë ì림ì´ì§ë§ ë²ê·¸ì ê°ë¥ì±ì ê°ì§ê³ ìë ê²½ì°) + </entry> + <entry/> + </row> + <row> + <entry>16</entry> + <entry>E_CORE_ERROR</entry> + <entry>fatal errors that occur during PHP's initial startup + (PHPê° ì²ì ììë ë ë°ìí ì¹ëª ì ìë¬)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>32</entry> + <entry>E_CORE_WARNING</entry> + <entry>warnings (non fatal errors) that occur during PHP's initial startup + (PHPê° ì²ì ììë ë ë°ìí ì¹ëª ì ì´ì§ ìì ê²½ê³ )</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>64</entry> + <entry>E_COMPILE_ERROR</entry> + <entry>fatal compile-time errors (ì»´íì¼ì ì긴 ì¹ëª ì ìë¬)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>128</entry> + <entry>E_COMPILE_WARNING</entry> + <entry>compile-time warnings (non fatal errors) (ì»´íì¼ì ë°ìí ì¹ëª ì ì´ì§ ìì ê²½ê³ )</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>256</entry> + <entry>E_USER_ERROR</entry> + <entry>user-generated error message (ì¬ì©ìê° ë§ë ìë¬ ë©ì¸ì§)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>512</entry> + <entry>E_USER_WARNING</entry> + <entry>user-generated warning message (ì¬ì©ìê° ë§ë ê²½ê³ ë©ì¸ì§)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>1024</entry> + <entry>E_USER_NOTICE </entry> + <entry>user-generated notice message (ì¬ì©ìê° ë§ë ì림 ë©ì¸ì§)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry/> + <entry>E_ALL</entry> + <entry>all of the above, as supported (ì§ìê°ë¥í ìì ê² ëª¨ë)</entry> + <entry/> + </row> + </tbody> + </tgroup> + </table> + </para> + <para> The above values (either numerical or symbolic) are used to build up a bitmask that specifies which errors to report. You can use the <link linkend="language.operators.bitwise">bitwise operators</link> @@ -107,29 +103,24 @@ <filename>php.ini</filename>, however, and that no bitwise operators will be understood within <filename>php3.ini</filename>. </para> - <para> - In PHP 4, the default <link - linkend="ini.error-reporting">error_reporting</link> setting is + <para> + In PHP 4, the default <link linkend="ini.error-reporting">error_reporting</link> setting is <literal>E_ALL & ~E_NOTICE</literal>, meaning to display all errors and warnings which are not E_NOTICE-level. In PHP 3, the default setting is <literal>(E_ERROR | E_WARNING | E_PARSE)</literal>, meaning the same thing. Note, however, that since constants are not - supported in PHP 3's <filename>php3.ini</filename>, the <link - linkend="ini.error-reporting">error_reporting</link> setting there + supported in PHP 3's <filename>php3.ini</filename>, the <link linkend="ini.error-reporting">error_reporting</link> setting there must be numeric; hence, it is <literal>7</literal>. </para> - - <para> - The initial setting can be changed in the ini file with the <link - linkend="ini.error-reporting">error_reporting</link> directive, in + <para> + The initial setting can be changed in the ini file with the <link linkend="ini.error-reporting">error_reporting</link> directive, in your Apache <filename>httpd.conf</filename> file with the php_error_reporting (php3_error_reporting for PHP 3) directive, and lastly it may be set at runtime within a script by using the <function>error_reporting</function> function. </para> - - <warning> - <para> + <warning> + <para> When upgrading code or servers from PHP 3 to PHP 4 you should check these settings and calls to <function>error_reporting</function> or you might disable @@ -137,39 +128,31 @@ may lead to empty documents without any feedback of what happened or where to look for the problem. </para> - </warning> - - <para> - All <link linkend="language.expressions">PHP expressions</link> can - also be called with the "@" prefix, which turns off error reporting - for that particular expression. If an error occurred during such - an expression and the <link - linkend="ini.track-errors">track_errors</link> feature is enabled, - you can find the error message in the global variable - $php_errormsg. + </warning> + <para> + 모ë <link linkend="language.expressions">PHP ííì(expression)</link>ì "@"를 ìì ë¶ì´ê³ í¸ì¶ëë©´ error reportingì íì§ ìëë¤. + ë§ì½ <link linkend="ini.track-errors">track_errors</link> ìµì ì´ Enabledë¡ ëì´ ìê³ í´ë¹ 문ì¥ìì ìë¬ê° ë°ìíë¤ë©´, + $php_errormsgë¼ë ì ìë³ìì ìë¬ ë©ìì§ê° ë´ê²¨ ìê² ëë¤. </para> - - <warning> - <para> + <warning> + <para> Currently the <link linkend="language.operators.errorcontrol">@ error-control operator</link> prefix will even disable error reporting for critical errors that will terminate script - execution. Among other things, this means that if you use <link - linkend="language.operators.errorcontrol">@</link> to suppress + execution. Among other things, this means that if you use <link linkend="language.operators.errorcontrol">@</link> to suppress errors from a certain function and either it isn't available or has been mistyped, the script will die right there with no indication as to why. </para> - </warning> - - <para> + </warning> + <para> Below we can see an example of using the error handling capabilities in PHP. We define a error handling function which logs the information into a file (using an XML format), and e-mails the developer in case a critical error in the logic happens. <example> - <title>Using error handling in a script</title> - <programlisting role="php"> + <title>Using error handling in a script</title> + <programlisting role="php"> <?php // we will do our own error handling error_reporting(0); @@ -270,23 +253,20 @@ ?> </programlisting> - </example> + </example> This is just a simple example showing how to use the <link linkend="ref.errorfunc">Error Handling and Logging functions</link>. </para> - - <para> + <para> See also <function>error_reporting</function>, <function>error_log</function>, <function>set_error_handler</function>, <function>restore_error_handler</function>, <function>trigger_error</function>, <function>user_error</function> - </para> - - </chapter> - + </para> +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml Index: phpdoc/en/features/http-auth.xml diff -u phpdoc/en/features/http-auth.xml:1.4 phpdoc/en/features/http-auth.xml:1.5 --- phpdoc/en/features/http-auth.xml:1.4 Wed Aug 23 09:55:45 2000 +++ phpdoc/en/features/http-auth.xml Tue Jan 9 02:41:17 2001 @@ -1,26 +1,28 @@ - <chapter id="features.http-auth"> - <title>HTTP authentication with PHP</title> - - <simpara> - The HTTP Authentication hooks in PHP are only available when it is - running as an Apache module and is hence not available in the CGI version. - In an Apache module PHP script, it is possible to use the - <function>Header</function> function to send an "Authentication Required" - message to the client browser causing it to pop up a Username/Password - input window. Once the user has filled in a username and a password, - the URL containing the PHP script will be called again with the variables, - $PHP_AUTH_USER, $PHP_AUTH_PW and $PHP_AUTH_TYPE set to the user - name, password and authentication type respectively. Only "Basic" - authentication is supported at this point. See the <function>Header</function> - function for more information.</simpara> - - <para> - An example script fragment which would force client authentication - on a page would be the following: - +<chapter id="features.http-auth"> + <title>HTTP authentication with PHP</title> + <simpara> + (ìì주. HTTP authenticationì´ë Web Clientìê² IDì Password를 ì ë ¥ë°ì, + ê·¸ IDì Passwordë¡ Web문ìì ì ê·¼ì íê°, ë¶ííë 기ë¥ì ë§íë¤. + ìì¸í ìê³ ì¶ë¤ë©´ RFC1945ì Authentication ë¶ë¶ì ì°¸ê³ í기 ë°ëë¤. + http://pec.etri.re.kr/!qkim/HTTP/ì íê¸ ë²ì 문ìë ìì¼ë 참조íì.) + </simpara> + <simpara> + PHP를 ì¬ì©í HTTP ì¸ì¦ì Apache 모ëë¡ ì¬ì©ë ëë§ ëìíë¤. + CGI ë²ì ¼ììë ì´ ê¸°ë¥ì ì¬ì©í ì ìë¤. + Apache 모ëì PHP ì¤í¬ë¦½í¸ìì <function>Header</function>ë¼ë í¨ì를 ì¬ì©íë©´ + Client ë¸ë¼ì°ì ìê² Usernameê³¼ Password를 ì ë ¥ë°ë ìëì°ë¥¼ ëì°ëë¡ íë + "ì¸ì¦ ì구"("Authentication Required") ë©ìì§ë¥¼ ë³´ë¼ ì ìë¤. + ì¼ë¨ ì¬ì©ìê° Usernameê³¼ Password를 ì ë ¥íë©´, + user name, password, authentication typeì ê°ì ê°ì§ë + $PHP_AUTH_USER, $PHP_AUTH_PW, $PHP_AUTH_TYPEì 3ê°ì ë³ì를 ê°ì§ê³ + í´ë¹ URL(PHP ì¤í¬ë¦½í¸ë¥¼ í¬í¨í)ì´ ë¤ì ë¶ë¦¬ìì§ë¤. + íì¬ authentication typeì "Basic"ë§ì´ ì§ìëë¤. + ìì¸í ì¬ì©ë²ì <function>Header</function> í¨ì를 ì´í´ ë³´ì.</simpara> + <para> + client authenticationì ì¬ì©íì¬ ê·¸ ì ë ¥ë ê°ì ì¶ë ¥íë ìì ê° ìëì ìë¤. : <example> - <title>HTTP Authentication example</title> - <programlisting role="php"> + <title>HTTP Authentication example</title> + <programlisting role="php"> <?php if(!isset($PHP_AUTH_USER)) { Header("WWW-Authenticate: Basic realm=\"My Realm\""); @@ -33,43 +35,36 @@ } ?> </programlisting> - </example></para> - - <para> - Instead of simply printing out the $PHP_AUTH_USER and - $PHP_AUTH_PW, you would probably want to check the username and - password for validity. Perhaps by sending a query to a database, - or by looking up the user in a dbm file.</para> - - <para> - Watch out for buggy Internet Explorer browsers out there. They - seem very picky about the order of the headers. Sending the - <emphasis>WWW-Authenticate</emphasis> header before the - <errorcode>HTTP/1.0 401</errorcode> header seems to do the trick - for now.</para> - - <simpara> - In order to prevent someone from writing a script which reveals - the password for a page that was authenticated through a - traditional external mechanism, the PHP_AUTH variables will not be - set if external authentication is enabled for that particular - page. In this case, the $REMOTE_USER variable can be used to - identify the externally-authenticated user.</simpara> - - <simpara> - Note, however, that the above does not prevent someone who - controls a non-authenticated URL from stealing passwords from - authenticated URLs on the same server.</simpara> - <simpara> - Both Netscape and Internet Explorer will clear the local browser - window's authentication cache for the realm upon receiving a - server response of 401. This can effectively "log out" a user, - forcing them to re-enter their username and password. Some people - use this to "time out" logins, or provide a "log-out" button.</simpara> - <simpara></simpara> - <example> - <title>HTTP Authentication example forcing a new name/password</title> - <programlisting role="php"> + </example> + </para> + <para> + ì¬ë¬ë¶ì $PHP_AUTH_USER ì $PHP_AUTH_PW를 ë¨ìí ì¶ë ¥íë ëì , + ì¬ì©ìì ìë³ì ìí´ usernameê³¼ password를 ì¬ì©í기를 ìí ê²ì´ë¤. + ì´ëë Databaseì Queryíê±°ë ì§ì dbm íì¼ìì ì°¾ìë³´ë ë±ì ë°©ë²ì¼ë¡ ê°ë¥í ê²ì´ë¤.</para> + <para> + Internet Explorer browserììë ë²ê·¸ë¡ ì¸í´ Headerì ììê° ë§¤ì° ê¹ë¤ë¡ë¤. + <emphasis>WWW-Authenticate</emphasis>를 + <errorcode>HTTP/1.0 401</errorcode>ë³´ë¤ ë¨¼ì ë³´ë´ë ê²ì´ íì¬ ê°ë¥í í¸ë¦ì¼ë¡ ë³´ì¸ë¤. + </para> + <simpara> + ë¹ë°ë²í¸ì ì ì¶ì ì°ë ¤íì¬ HTTPìì ì ê³µíë ì¸ì¦ì ì¬ì©íë ëì + 기존ì ì¸ë¶ ë©ì¹´ëì¦ì ì¬ì©í ê²½ì°ìë ë¬¼ë¡ PHP_AUTH ë³ìë ì¤ì ëì§ ìëë¤. + ì´ë°ê²½ì° externally-authenticated user를 íì¸í기 ìí´ $REMOTE_USER ë³ì를 ì¬ì©í ì ìë¤. + </simpara> + <simpara> + ì ìí ì ì ì¸ì¦ì´ íìí íì´ì§ì ì¸ì¦ì´ íììë íì´ì§ê° ê°ì ìë²ìì ì¡´ì¬í ë, + ì¸ì¦ì´ íììë URLì controlí ì ìë ëêµ°ê°ê°, + ì¸ì¦ì´ íìí URLì ìí¸ë¥¼ íì³ë³´ë ê²ì ë§ì ì ìë¤ë ì ì´ë¤. + </simpara> + <simpara> + Netscapeì Internet Explorer 모ë 401ìëµ ì½ë를 ìë²ìì ë°ê²ëë©´ + local browser windowì authentication cache를 clearíë¤. + ì¦, ì´ê²ì "log out"ê°ë ì´ ëë ê²ì¼ë¡, ì¬ì©ìë¤ë¡ íì¬ê¸ usernameê³¼ ìí¸ë¥¼ ë¤ì ì ë ¥íê² íë¤. + ì¼ë¶ë ì´ê²ì íµí´ loginì "time out"ì´ë "log-out"ë²í¼ì ë§ëëë° ì¬ì©íë¤ + </simpara> + <example> + <title>HTTP Authentication example forcing a new name/password</title> + <programlisting role="php"> <?php function authenticate() { Header( "WWW-authenticate: basic realm=\"Test Authentication System\""); @@ -93,20 +88,16 @@ } ?> </programlisting> - </example> - <simpara> - This behavior is not required by the HTTP Basic authentication - standard, so you should never depend on this. Testing with Lynx - has shown that Lynx does not clear the authentication credentials - with a 401 server response, so pressing back and then forward - again will open the resource (as long as the credential - requirements haven't changed).</simpara> - <simpara> - Also note that this does not work using Microsoft's IIS server and - the CGI version of PHP due to a limitation of IIS.</simpara> - - </chapter> - + </example> + <simpara> + ê·¸ë¬ë ì´ ëìì HTTP Basic authentication 기ì¤ì ë³´ì¥ë ê²ì ìëë¯ë¡ ì´ ê¸°ë¥ì ìì¡´íì¬ìë ìëë¤. + Lynxììë 401 ìë² ìëµì ë°ìë authentication ì 보를 clearíì§ ìëë¤. + ë°ë¼ì Backì ëë¥´ê³ ë¤ì Forward ë²í¼ì ëë¬ì ë¤ì ì ê·¼í ì ìë¤.</simpara> + <simpara> + ëí ì´ Authentication 기ë¥ì Microsoft's IIS serverìì + CGI versionì PHP를 ì¬ì©í ê²½ì°ìë IISì ì ì½ì¼ë¡ì¸í´ ëìíì§ ìëë¤. + </simpara> +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml Index: phpdoc/en/features/images.xml diff -u phpdoc/en/features/images.xml:1.5 phpdoc/en/features/images.xml:1.6 --- phpdoc/en/features/images.xml:1.5 Sat Oct 14 06:15:51 2000 +++ phpdoc/en/features/images.xml Tue Jan 9 02:41:17 2001 @@ -1,21 +1,17 @@ - <chapter id="features.images"> - <title>Creating and manipulating images</title> - - <simpara> - PHP is not limited to creating just HTML output. It can also be - used to create and manipulate image files in a variety of different - image formats, including gif, png, jpg, wbmp, and xpm. Even more - convenient, php can output image streams directly to a browser. You - will need to compile PHP with the GD library of image functions for - this to work. GD and PHP may also require other libraries, depending - on which image formats you want to work with. GD stopped supporting - Gif images in version 1.6. +<chapter id="features.images"> + <title>PHPìì ì´ë¯¸ì§ ìì±ê³¼ ìì (Creating and manipulating images)</title> + <simpara> + PHPë ë¨ì§ HTMLì¶ë ¥ì ë§ëë ê²ë§ í ì ìë ê²ì´ ìëë¤. + PHPë GIF image fileë ë§ë¤ ì ìì ìì ë¿ìëë¼, + ì¬ì©í기ì í¸ë¦¬í GIF image streamê¹ì§ ë§ë¤ ì ìë¤. + ì´ë¥¼ ìí´ì ì¬ë¬ë¶ì PHP를 ì»´íì¼ í ë, image í¨ì를 ê°ì§ê³ ìë GD ë¼ì´ë¸ë¬ë¦¬ë¥¼ í¬í¨íì¬ì¼ íë¤. + GDì PHPë ì¬ì©íë ì´ë¯¸ì§ í¬ë§· ííì ë°ë¼ ë¤ë¥¸ ë¼ì´ë¸ë¬ë¦¬ë ì구íë¤. + GDë ë²ì 1.6ë¶í° GIF ì´ë¯¸ì§ ì§ìì íì§ ìëë¤. </simpara> - - <para> - <example> - <title>PNG creation with PHP</title> - <programlisting role="php"> + <para> + <example> + <title>PNG creation with PHP</title> + <programlisting role="php"> <?php Header("Content-type: image/png"); $string=implode($argv," "); @@ -27,20 +23,14 @@ ImageDestroy($im); ?> </programlisting> - </example> - - This example would be called from a page with a tag like: <img - src="button.php?text"> The above button.php script - then takes this "text" string an overlays it on top of a - base image which in this case is "images/button1.png" - and outputs the resulting image. This is a very convenient way to - avoid having to draw new button images every time you want to - change the text of a button. With this method they are - dynamically generated. + </example> + ìì ìì ë <img src="button.php?text"> ì ê°ì tagì´ ìë íì´ì§ë¡ë¶í° ë¶ë ¤ì§ê² ë ê²ì´ë¤. + ê·¸ë¬ë©´ ìììë button.php ì¤í¬ë¦½í¸ë "text"ë¼ë 문ìì´ì + "images/button1.gif"ì ì¤ë²ë ì´ ìì¼ ê²°ê³¼ imageì ì¶ë ¥íë¤. + ì´ë ê² íë©´ ë²í¼ì ë¤ì´ê°ë ê¸ì¨ë¥¼ ë§¤ë² ìì½ê² ë°ê¿ ì¸ ì ìê³ , + ëí ë§¤ë² ì´ë¯¸ì§ íì¼ì ë§ë¤ íìê° ìì´ í¨ì¨ì ì´ê³ ê°ë¨íë¤. </para> - - </chapter> - +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml
Index: phpdoc/en/features/cookies.xml diff -u phpdoc/en/features/cookies.xml:1.2 phpdoc/en/features/cookies.xml:1.3 --- phpdoc/en/features/cookies.xml:1.2 Thu Dec 9 16:34:39 1999 +++ phpdoc/en/features/cookies.xml Tue Jan 9 02:41:17 2001 @@ -1,24 +1,19 @@ - <chapter id="features.cookies"> - <title>Cookies</title> - - <para> - PHP transparently supports HTTP cookies. Cookies are a mechanism - for storing data in the remote browser and thus tracking - or identifying return users. You can set cookies using the - <function>setcookie</function> function. Cookies are part of the - HTTP header, so <function>setcookie</function> must be called before - any output is sent to the browser. This is the same limitation that - <function>header</function> has.</para> - - <para> - Any cookies sent to you from the client will automatically be - turned into a PHP variable just like GET and POST method data. If - you wish to assign multiple values to a single cookie, just add - <emphasis>[]</emphasis> to the cookie name. For more details see - the <function>setcookie</function> function.</para> - - </chapter> - +<chapter id="features.cookies"> + <title>Cookies</title> + <para> + PHPë HTTP Cookie를 í¬ëª íê²(transparently) ì§ìíë¤. + Cookie ë©ì¹´ëì¦ì í¸ëí¹ì´ë ì¬ì©ì ìë³ ë±ì ìí´ ì격 browserì + ì ì¥ë ë°ì´í°ë¥¼ ëë ¤ ë°ë ê³¼ì ì ë§íë¤. + ì¬ë¬ë¶ì cookie를 ì¤ì í기 ìí´ <function>setcookie</function> í¨ì를 ì¬ì©í ì ìë¤. + Cookieë HTTP í¤ëì í ë¶ë¶ì´ë¯ë¡, <function>setcookie</function> í¨ìë ë¸ë¼ì°ì ë¡ + ë³´ë´ë ì´ë¤ ë°ì´í°ë³´ë¤ë ìì ì¬ì©í´ì¼ íë¤. + ì´ ì ì½ì <function>header</function> í¨ìì ê°ì ì ì½ì¼ë¡ ë³´ë©´ ëë¤.</para> + <para> + í´ë¼ì´ì¸í¸ê° ë³´ë´ì¤ 모ë cookieë ìëì ì¼ë¡ GETì´ë POST ë°©ì ë°ì´í°ì ê°ì PHP ë³ìë¡ ë³íëë¤. + ë§ì½ ì¬ë¬ë¶ì´ ëì¼í cookieì ì¬ë¬ ê°ì ì ì¥íê³ ì¶ë¤ë©´ Cookieì´ë¦ì <emphasis>[]</emphasis>를 ëíë©´ ëë¤. + ìì¸í ê²ì <function>setcookie</function> í¨ì ì¤ëª ì 참조íì. + </para> +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml Index: phpdoc/en/features/error-handling.xml diff -u phpdoc/en/features/error-handling.xml:1.10 phpdoc/en/features/error-handling.xml:1.11 --- phpdoc/en/features/error-handling.xml:1.10 Thu Sep 7 07:22:12 2000 +++ phpdoc/en/features/error-handling.xml Tue Jan 9 02:41:17 2001 @@ -1,104 +1,100 @@ - <chapter id="features.error-handling"> - <title>Error Handling</title> - - <para> - There are several types of errors and warnings in PHP. They are: - +<chapter id="features.error-handling"> + <title>Error Handling</title> + <para> + PHPìë ë¤ìê³¼ ê°ì ì¬ë¬ ìë¬ì ê²½ê³ ííê° ìë¤.: <table> - <title>PHP error types</title> - <tgroup cols="4"> - <thead> - <row> - <entry>Value</entry> - <entry>Constant</entry> - <entry>Description</entry> - <entry>Note</entry> - </row> - </thead> - <tbody> - <row> - <entry>1</entry> - <entry>E_ERROR</entry> - <entry>fatal run-time errors</entry> - <entry></entry> - </row> - <row> - <entry>2</entry> - <entry>E_WARNING</entry> - <entry>run-time warnings (non fatal errors)</entry> - <entry></entry> - </row> - <row> - <entry>4</entry> - <entry>E_PARSE</entry> - <entry>compile-time parse errors</entry> - <entry></entry> - </row> - <row> - <entry>8</entry> - <entry>E_NOTICE </entry> - <entry> - run-time notices (less serious than warnings) - </entry> - <entry></entry> - </row> - <row> - <entry>16</entry> - <entry>E_CORE_ERROR</entry> - <entry>fatal errors that occur during PHP's initial startup</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>32</entry> - <entry>E_CORE_WARNING</entry> - <entry> - warnings (non fatal errors) that occur during PHP's initial - startup - </entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>64</entry> - <entry>E_COMPILE_ERROR</entry> - <entry>fatal compile-time errors</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>128</entry> - <entry>E_COMPILE_WARNING</entry> - <entry>compile-time warnings (non fatal errors)</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>256</entry> - <entry>E_USER_ERROR</entry> - <entry>user-generated error message</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>512</entry> - <entry>E_USER_WARNING</entry> - <entry>user-generated warning message</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry>1024</entry> - <entry>E_USER_NOTICE </entry> - <entry>user-generated notice message</entry> - <entry>PHP 4 only</entry> - </row> - <row> - <entry></entry> - <entry>E_ALL</entry> - <entry>all of the above, as supported</entry> - <entry></entry> - </row> - </tbody> - </tgroup> - </table> - </para> - - <para> + <title>PHP error types</title> + <tgroup cols="4"> + <thead> + <row> + <entry>Value</entry> + <entry>Constant</entry> + <entry>Description</entry> + <entry>Note</entry> + </row> + </thead> + <tbody> + <row> + <entry>1</entry> + <entry>E_ERROR</entry> + <entry>Normal Function Errors (ì¼ë°ì ì¸ ìë¬)</entry> + <entry/> + </row> + <row> + <entry>2</entry> + <entry>E_WARNING</entry> + <entry>Normal Warnings (ì¼ë°ì ì¸ ê²½ê³ )</entry> + <entry/> + </row> + <row> + <entry>4</entry> + <entry>E_PARSE</entry> + <entry>Parser Errors (ë¬¸ë² ìë¬)</entry> + <entry/> + </row> + <row> + <entry>8</entry> + <entry>E_NOTICE </entry> + <entry> + Notices (무ìí ì ìë ì림ì´ì§ë§ ë²ê·¸ì ê°ë¥ì±ì ê°ì§ê³ ìë ê²½ì°) + </entry> + <entry/> + </row> + <row> + <entry>16</entry> + <entry>E_CORE_ERROR</entry> + <entry>fatal errors that occur during PHP's initial startup + (PHPê° ì²ì ììë ë ë°ìí ì¹ëª ì ìë¬)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>32</entry> + <entry>E_CORE_WARNING</entry> + <entry>warnings (non fatal errors) that occur during PHP's initial startup + (PHPê° ì²ì ììë ë ë°ìí ì¹ëª ì ì´ì§ ìì ê²½ê³ )</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>64</entry> + <entry>E_COMPILE_ERROR</entry> + <entry>fatal compile-time errors (ì»´íì¼ì ì긴 ì¹ëª ì ìë¬)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>128</entry> + <entry>E_COMPILE_WARNING</entry> + <entry>compile-time warnings (non fatal errors) (ì»´íì¼ì ë°ìí ì¹ëª ì ì´ì§ ìì ê²½ê³ )</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>256</entry> + <entry>E_USER_ERROR</entry> + <entry>user-generated error message (ì¬ì©ìê° ë§ë ìë¬ ë©ì¸ì§)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>512</entry> + <entry>E_USER_WARNING</entry> + <entry>user-generated warning message (ì¬ì©ìê° ë§ë ê²½ê³ ë©ì¸ì§)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry>1024</entry> + <entry>E_USER_NOTICE </entry> + <entry>user-generated notice message (ì¬ì©ìê° ë§ë ì림 ë©ì¸ì§)</entry> + <entry>PHP 4 only</entry> + </row> + <row> + <entry/> + <entry>E_ALL</entry> + <entry>all of the above, as supported (ì§ìê°ë¥í ìì ê² ëª¨ë)</entry> + <entry/> + </row> + </tbody> + </tgroup> + </table> + </para> + <para> The above values (either numerical or symbolic) are used to build up a bitmask that specifies which errors to report. You can use the <link linkend="language.operators.bitwise">bitwise operators</link> @@ -107,29 +103,24 @@ <filename>php.ini</filename>, however, and that no bitwise operators will be understood within <filename>php3.ini</filename>. </para> - <para> - In PHP 4, the default <link - linkend="ini.error-reporting">error_reporting</link> setting is + <para> + In PHP 4, the default <link linkend="ini.error-reporting">error_reporting</link> setting is <literal>E_ALL & ~E_NOTICE</literal>, meaning to display all errors and warnings which are not E_NOTICE-level. In PHP 3, the default setting is <literal>(E_ERROR | E_WARNING | E_PARSE)</literal>, meaning the same thing. Note, however, that since constants are not - supported in PHP 3's <filename>php3.ini</filename>, the <link - linkend="ini.error-reporting">error_reporting</link> setting there + supported in PHP 3's <filename>php3.ini</filename>, the <link linkend="ini.error-reporting">error_reporting</link> setting there must be numeric; hence, it is <literal>7</literal>. </para> - - <para> - The initial setting can be changed in the ini file with the <link - linkend="ini.error-reporting">error_reporting</link> directive, in + <para> + The initial setting can be changed in the ini file with the <link linkend="ini.error-reporting">error_reporting</link> directive, in your Apache <filename>httpd.conf</filename> file with the php_error_reporting (php3_error_reporting for PHP 3) directive, and lastly it may be set at runtime within a script by using the <function>error_reporting</function> function. </para> - - <warning> - <para> + <warning> + <para> When upgrading code or servers from PHP 3 to PHP 4 you should check these settings and calls to <function>error_reporting</function> or you might disable @@ -137,39 +128,31 @@ may lead to empty documents without any feedback of what happened or where to look for the problem. </para> - </warning> - - <para> - All <link linkend="language.expressions">PHP expressions</link> can - also be called with the "@" prefix, which turns off error reporting - for that particular expression. If an error occurred during such - an expression and the <link - linkend="ini.track-errors">track_errors</link> feature is enabled, - you can find the error message in the global variable - $php_errormsg. + </warning> + <para> + 모ë <link linkend="language.expressions">PHP ííì(expression)</link>ì "@"를 ìì ë¶ì´ê³ í¸ì¶ëë©´ error reportingì íì§ ìëë¤. + ë§ì½ <link linkend="ini.track-errors">track_errors</link> ìµì ì´ Enabledë¡ ëì´ ìê³ í´ë¹ 문ì¥ìì ìë¬ê° ë°ìíë¤ë©´, + $php_errormsgë¼ë ì ìë³ìì ìë¬ ë©ìì§ê° ë´ê²¨ ìê² ëë¤. </para> - - <warning> - <para> + <warning> + <para> Currently the <link linkend="language.operators.errorcontrol">@ error-control operator</link> prefix will even disable error reporting for critical errors that will terminate script - execution. Among other things, this means that if you use <link - linkend="language.operators.errorcontrol">@</link> to suppress + execution. Among other things, this means that if you use <link linkend="language.operators.errorcontrol">@</link> to suppress errors from a certain function and either it isn't available or has been mistyped, the script will die right there with no indication as to why. </para> - </warning> - - <para> + </warning> + <para> Below we can see an example of using the error handling capabilities in PHP. We define a error handling function which logs the information into a file (using an XML format), and e-mails the developer in case a critical error in the logic happens. <example> - <title>Using error handling in a script</title> - <programlisting role="php"> + <title>Using error handling in a script</title> + <programlisting role="php"> <?php // we will do our own error handling error_reporting(0); @@ -270,23 +253,20 @@ ?> </programlisting> - </example> + </example> This is just a simple example showing how to use the <link linkend="ref.errorfunc">Error Handling and Logging functions</link>. </para> - - <para> + <para> See also <function>error_reporting</function>, <function>error_log</function>, <function>set_error_handler</function>, <function>restore_error_handler</function>, <function>trigger_error</function>, <function>user_error</function> - </para> - - </chapter> - + </para> +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml Index: phpdoc/en/features/http-auth.xml diff -u phpdoc/en/features/http-auth.xml:1.4 phpdoc/en/features/http-auth.xml:1.5 --- phpdoc/en/features/http-auth.xml:1.4 Wed Aug 23 09:55:45 2000 +++ phpdoc/en/features/http-auth.xml Tue Jan 9 02:41:17 2001 @@ -1,26 +1,28 @@ - <chapter id="features.http-auth"> - <title>HTTP authentication with PHP</title> - - <simpara> - The HTTP Authentication hooks in PHP are only available when it is - running as an Apache module and is hence not available in the CGI version. - In an Apache module PHP script, it is possible to use the - <function>Header</function> function to send an "Authentication Required" - message to the client browser causing it to pop up a Username/Password - input window. Once the user has filled in a username and a password, - the URL containing the PHP script will be called again with the variables, - $PHP_AUTH_USER, $PHP_AUTH_PW and $PHP_AUTH_TYPE set to the user - name, password and authentication type respectively. Only "Basic" - authentication is supported at this point. See the <function>Header</function> - function for more information.</simpara> - - <para> - An example script fragment which would force client authentication - on a page would be the following: - +<chapter id="features.http-auth"> + <title>HTTP authentication with PHP</title> + <simpara> + (ìì주. HTTP authenticationì´ë Web Clientìê² IDì Password를 ì ë ¥ë°ì, + ê·¸ IDì Passwordë¡ Web문ìì ì ê·¼ì íê°, ë¶ííë 기ë¥ì ë§íë¤. + ìì¸í ìê³ ì¶ë¤ë©´ RFC1945ì Authentication ë¶ë¶ì ì°¸ê³ í기 ë°ëë¤. + http://pec.etri.re.kr/!qkim/HTTP/ì íê¸ ë²ì 문ìë ìì¼ë 참조íì.) + </simpara> + <simpara> + PHP를 ì¬ì©í HTTP ì¸ì¦ì Apache 모ëë¡ ì¬ì©ë ëë§ ëìíë¤. + CGI ë²ì ¼ììë ì´ ê¸°ë¥ì ì¬ì©í ì ìë¤. + Apache 모ëì PHP ì¤í¬ë¦½í¸ìì <function>Header</function>ë¼ë í¨ì를 ì¬ì©íë©´ + Client ë¸ë¼ì°ì ìê² Usernameê³¼ Password를 ì ë ¥ë°ë ìëì°ë¥¼ ëì°ëë¡ íë + "ì¸ì¦ ì구"("Authentication Required") ë©ìì§ë¥¼ ë³´ë¼ ì ìë¤. + ì¼ë¨ ì¬ì©ìê° Usernameê³¼ Password를 ì ë ¥íë©´, + user name, password, authentication typeì ê°ì ê°ì§ë + $PHP_AUTH_USER, $PHP_AUTH_PW, $PHP_AUTH_TYPEì 3ê°ì ë³ì를 ê°ì§ê³ + í´ë¹ URL(PHP ì¤í¬ë¦½í¸ë¥¼ í¬í¨í)ì´ ë¤ì ë¶ë¦¬ìì§ë¤. + íì¬ authentication typeì "Basic"ë§ì´ ì§ìëë¤. + ìì¸í ì¬ì©ë²ì <function>Header</function> í¨ì를 ì´í´ ë³´ì.</simpara> + <para> + client authenticationì ì¬ì©íì¬ ê·¸ ì ë ¥ë ê°ì ì¶ë ¥íë ìì ê° ìëì ìë¤. : <example> - <title>HTTP Authentication example</title> - <programlisting role="php"> + <title>HTTP Authentication example</title> + <programlisting role="php"> <?php if(!isset($PHP_AUTH_USER)) { Header("WWW-Authenticate: Basic realm=\"My Realm\""); @@ -33,43 +35,36 @@ } ?> </programlisting> - </example></para> - - <para> - Instead of simply printing out the $PHP_AUTH_USER and - $PHP_AUTH_PW, you would probably want to check the username and - password for validity. Perhaps by sending a query to a database, - or by looking up the user in a dbm file.</para> - - <para> - Watch out for buggy Internet Explorer browsers out there. They - seem very picky about the order of the headers. Sending the - <emphasis>WWW-Authenticate</emphasis> header before the - <errorcode>HTTP/1.0 401</errorcode> header seems to do the trick - for now.</para> - - <simpara> - In order to prevent someone from writing a script which reveals - the password for a page that was authenticated through a - traditional external mechanism, the PHP_AUTH variables will not be - set if external authentication is enabled for that particular - page. In this case, the $REMOTE_USER variable can be used to - identify the externally-authenticated user.</simpara> - - <simpara> - Note, however, that the above does not prevent someone who - controls a non-authenticated URL from stealing passwords from - authenticated URLs on the same server.</simpara> - <simpara> - Both Netscape and Internet Explorer will clear the local browser - window's authentication cache for the realm upon receiving a - server response of 401. This can effectively "log out" a user, - forcing them to re-enter their username and password. Some people - use this to "time out" logins, or provide a "log-out" button.</simpara> - <simpara></simpara> - <example> - <title>HTTP Authentication example forcing a new name/password</title> - <programlisting role="php"> + </example> + </para> + <para> + ì¬ë¬ë¶ì $PHP_AUTH_USER ì $PHP_AUTH_PW를 ë¨ìí ì¶ë ¥íë ëì , + ì¬ì©ìì ìë³ì ìí´ usernameê³¼ password를 ì¬ì©í기를 ìí ê²ì´ë¤. + ì´ëë Databaseì Queryíê±°ë ì§ì dbm íì¼ìì ì°¾ìë³´ë ë±ì ë°©ë²ì¼ë¡ ê°ë¥í ê²ì´ë¤.</para> + <para> + Internet Explorer browserììë ë²ê·¸ë¡ ì¸í´ Headerì ììê° ë§¤ì° ê¹ë¤ë¡ë¤. + <emphasis>WWW-Authenticate</emphasis>를 + <errorcode>HTTP/1.0 401</errorcode>ë³´ë¤ ë¨¼ì ë³´ë´ë ê²ì´ íì¬ ê°ë¥í í¸ë¦ì¼ë¡ ë³´ì¸ë¤. + </para> + <simpara> + ë¹ë°ë²í¸ì ì ì¶ì ì°ë ¤íì¬ HTTPìì ì ê³µíë ì¸ì¦ì ì¬ì©íë ëì + 기존ì ì¸ë¶ ë©ì¹´ëì¦ì ì¬ì©í ê²½ì°ìë ë¬¼ë¡ PHP_AUTH ë³ìë ì¤ì ëì§ ìëë¤. + ì´ë°ê²½ì° externally-authenticated user를 íì¸í기 ìí´ $REMOTE_USER ë³ì를 ì¬ì©í ì ìë¤. + </simpara> + <simpara> + ì ìí ì ì ì¸ì¦ì´ íìí íì´ì§ì ì¸ì¦ì´ íììë íì´ì§ê° ê°ì ìë²ìì ì¡´ì¬í ë, + ì¸ì¦ì´ íììë URLì controlí ì ìë ëêµ°ê°ê°, + ì¸ì¦ì´ íìí URLì ìí¸ë¥¼ íì³ë³´ë ê²ì ë§ì ì ìë¤ë ì ì´ë¤. + </simpara> + <simpara> + Netscapeì Internet Explorer 모ë 401ìëµ ì½ë를 ìë²ìì ë°ê²ëë©´ + local browser windowì authentication cache를 clearíë¤. + ì¦, ì´ê²ì "log out"ê°ë ì´ ëë ê²ì¼ë¡, ì¬ì©ìë¤ë¡ íì¬ê¸ usernameê³¼ ìí¸ë¥¼ ë¤ì ì ë ¥íê² íë¤. + ì¼ë¶ë ì´ê²ì íµí´ loginì "time out"ì´ë "log-out"ë²í¼ì ë§ëëë° ì¬ì©íë¤ + </simpara> + <example> + <title>HTTP Authentication example forcing a new name/password</title> + <programlisting role="php"> <?php function authenticate() { Header( "WWW-authenticate: basic realm=\"Test Authentication System\""); @@ -93,20 +88,16 @@ } ?> </programlisting> - </example> - <simpara> - This behavior is not required by the HTTP Basic authentication - standard, so you should never depend on this. Testing with Lynx - has shown that Lynx does not clear the authentication credentials - with a 401 server response, so pressing back and then forward - again will open the resource (as long as the credential - requirements haven't changed).</simpara> - <simpara> - Also note that this does not work using Microsoft's IIS server and - the CGI version of PHP due to a limitation of IIS.</simpara> - - </chapter> - + </example> + <simpara> + ê·¸ë¬ë ì´ ëìì HTTP Basic authentication 기ì¤ì ë³´ì¥ë ê²ì ìëë¯ë¡ ì´ ê¸°ë¥ì ìì¡´íì¬ìë ìëë¤. + Lynxììë 401 ìë² ìëµì ë°ìë authentication ì 보를 clearíì§ ìëë¤. + ë°ë¼ì Backì ëë¥´ê³ ë¤ì Forward ë²í¼ì ëë¬ì ë¤ì ì ê·¼í ì ìë¤.</simpara> + <simpara> + ëí ì´ Authentication 기ë¥ì Microsoft's IIS serverìì + CGI versionì PHP를 ì¬ì©í ê²½ì°ìë IISì ì ì½ì¼ë¡ì¸í´ ëìíì§ ìëë¤. + </simpara> +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml Index: phpdoc/en/features/images.xml diff -u phpdoc/en/features/images.xml:1.5 phpdoc/en/features/images.xml:1.6 --- phpdoc/en/features/images.xml:1.5 Sat Oct 14 06:15:51 2000 +++ phpdoc/en/features/images.xml Tue Jan 9 02:41:17 2001 @@ -1,21 +1,17 @@ - <chapter id="features.images"> - <title>Creating and manipulating images</title> - - <simpara> - PHP is not limited to creating just HTML output. It can also be - used to create and manipulate image files in a variety of different - image formats, including gif, png, jpg, wbmp, and xpm. Even more - convenient, php can output image streams directly to a browser. You - will need to compile PHP with the GD library of image functions for - this to work. GD and PHP may also require other libraries, depending - on which image formats you want to work with. GD stopped supporting - Gif images in version 1.6. +<chapter id="features.images"> + <title>PHPìì ì´ë¯¸ì§ ìì±ê³¼ ìì (Creating and manipulating images)</title> + <simpara> + PHPë ë¨ì§ HTMLì¶ë ¥ì ë§ëë ê²ë§ í ì ìë ê²ì´ ìëë¤. + PHPë GIF image fileë ë§ë¤ ì ìì ìì ë¿ìëë¼, + ì¬ì©í기ì í¸ë¦¬í GIF image streamê¹ì§ ë§ë¤ ì ìë¤. + ì´ë¥¼ ìí´ì ì¬ë¬ë¶ì PHP를 ì»´íì¼ í ë, image í¨ì를 ê°ì§ê³ ìë GD ë¼ì´ë¸ë¬ë¦¬ë¥¼ í¬í¨íì¬ì¼ íë¤. + GDì PHPë ì¬ì©íë ì´ë¯¸ì§ í¬ë§· ííì ë°ë¼ ë¤ë¥¸ ë¼ì´ë¸ë¬ë¦¬ë ì구íë¤. + GDë ë²ì 1.6ë¶í° GIF ì´ë¯¸ì§ ì§ìì íì§ ìëë¤. </simpara> - - <para> - <example> - <title>PNG creation with PHP</title> - <programlisting role="php"> + <para> + <example> + <title>PNG creation with PHP</title> + <programlisting role="php"> <?php Header("Content-type: image/png"); $string=implode($argv," "); @@ -27,20 +23,14 @@ ImageDestroy($im); ?> </programlisting> - </example> - - This example would be called from a page with a tag like: <img - src="button.php?text"> The above button.php script - then takes this "text" string an overlays it on top of a - base image which in this case is "images/button1.png" - and outputs the resulting image. This is a very convenient way to - avoid having to draw new button images every time you want to - change the text of a button. With this method they are - dynamically generated. + </example> + ìì ìì ë <img src="button.php?text"> ì ê°ì tagì´ ìë íì´ì§ë¡ë¶í° ë¶ë ¤ì§ê² ë ê²ì´ë¤. + ê·¸ë¬ë©´ ìììë button.php ì¤í¬ë¦½í¸ë "text"ë¼ë 문ìì´ì + "images/button1.gif"ì ì¤ë²ë ì´ ìì¼ ê²°ê³¼ imageì ì¶ë ¥íë¤. + ì´ë ê² íë©´ ë²í¼ì ë¤ì´ê°ë ê¸ì¨ë¥¼ ë§¤ë² ìì½ê² ë°ê¿ ì¸ ì ìê³ , + ëí ë§¤ë² ì´ë¯¸ì§ íì¼ì ë§ë¤ íìê° ìì´ í¨ì¨ì ì´ê³ ê°ë¨íë¤. </para> - - </chapter> - +</chapter> <!-- Keep this comment at the end of the file Local variables: mode: sgml