git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@294396 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Richard Quadling 2010-02-03 14:08:11 +00:00
parent 4c0b2c64d0
commit 1d137d406b
27 changed files with 109 additions and 109 deletions

View file

@ -24,8 +24,8 @@
</term>
<listitem>
<simpara>
Prohibit processing of unassigned codepoints in the input for IDN
functions and do not check if the input conforms to domain name ASCII rules.
Prohibit processing of unassigned codepoints in the input for IDN
functions and do not check if the input conforms to domain name ASCII rules.
</simpara>
</listitem>
</varlistentry>

View file

@ -9,16 +9,16 @@
<!-- {{{ IntlDateFormatter intro -->
<section xml:id="intldateformatter.intro">
&reftitle.intro;
<simpara>
<simpara>
Date Formatter is a concrete class that enables locale-dependent formatting/parsing
of dates using pattern strings and/or canned patterns.
</simpara>
</simpara>
<simpara>
This class represents the ICU date formatting functionality.
It allows users to display dates in a localized format or to parse strings
into PHP date values using pattern strings and/or canned patterns.
</simpara>
<simpara>
This class represents the ICU date formatting functionality.
It allows users to display dates in a localized format or to parse strings
into PHP date values using pattern strings and/or canned patterns.
</simpara>
</section>
<!-- }}} -->

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>string</type><methodname>IntlDateFormatter::format</methodname>
<methodparam><type>mixed</type><parameter>value</parameter></methodparam>
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>string</type><methodname>datefmt_format</methodname>
@ -36,7 +36,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The date formatter resource.
The date formatter resource.
</para>
</listitem>
</varlistentry>
@ -44,9 +44,9 @@
<term><parameter>value</parameter></term>
<listitem>
<para>
Value to format. Can be <type>integer</type> for an Unix timestamp value (seconds since epoch, UTC) or
<type>array</type> for a <function>localtime</function> array.
</para>
Value to format. Can be <type>integer</type> for an Unix timestamp value (seconds since epoch, UTC) or
<type>array</type> for a <function>localtime</function> array.
</para>
</listitem>
</varlistentry>
</variablelist>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>int</type><methodname>IntlDateFormatter::getCalendar</methodname>
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>int</type><methodname>datefmt_get_calendar</methodname>
@ -34,7 +34,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource
The formatter resource
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>int</type><methodname>IntlDateFormatter::getDateType</methodname>
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>int</type><methodname>datefmt_get_datetype</methodname>
@ -35,7 +35,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>int</type><methodname>IntlDateFormatter::getErrorCode</methodname>
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>int</type><methodname>datefmt_get_error_code</methodname>
@ -36,7 +36,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>string</type><methodname>IntlDateFormatter::getErrorMessage</methodname>
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>string</type><methodname>datefmt_get_error_message</methodname>
@ -35,7 +35,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>string</type><methodname>IntlDateFormatter::getLocale</methodname>
<methodparam choice='opt'><type>int</type><parameter>which</parameter></methodparam>
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>string</type><methodname>datefmt_get_locale</methodname>
@ -36,7 +36,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource
The formatter resource
</para>
</listitem>
</varlistentry>

View file

@ -9,23 +9,23 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<methodsynopsis>
<type>string</type><methodname>IntlDateFormatter::getPattern</methodname>
<void />
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>string</type><methodname>datefmt_get_pattern</methodname>
<methodparam><type>IntlDateFormatter</type><parameter>fmt</parameter></methodparam>
<methodparam><type>IntlDateFormatter</type><parameter>fmt</parameter></methodparam>
</methodsynopsis>
<para>
Get pattern used by the formatter.
Get pattern used by the formatter.
</para>
</refsect1>
</refsect1>
<refsect1 role="parameters">
&reftitle.parameters;
@ -35,7 +35,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>int</type><methodname>IntlDateFormatter::getTimeType</methodname>
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>int</type><methodname>datefmt_get_timetype</methodname>
@ -35,7 +35,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>

View file

@ -9,21 +9,21 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>string</type><methodname>IntlDateFormatter::getTimeZoneId</methodname>
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>string</type><methodname>datefmt_get_timezone_id</methodname>
<methodparam><type>IntlDateFormatter</type><parameter>fmt</parameter></methodparam>
</methodsynopsis>
<para>
Get the timezone-id used for the IntlDateFormatter.
Get the timezone-id used for the IntlDateFormatter.
</para>
</refsect1>
@ -35,7 +35,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>bool</type><methodname>IntlDateFormatter::isLenient</methodname>
<void />
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>bool</type><methodname>datefmt_is_lenient</methodname>
@ -35,7 +35,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>

View file

@ -9,7 +9,7 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>array</type><methodname>IntlDateFormatter::localtime</methodname>
@ -17,7 +17,7 @@
<methodparam choice="opt"><type>int</type><parameter role="reference">position</parameter></methodparam>
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>array</type><methodname>datefmt_localtime</methodname>
@ -39,7 +39,7 @@ $parse_pos and consuming as much of the input value as possible.
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource
The formatter resource
</para>
</listitem>
</varlistentry>
@ -47,7 +47,7 @@ $parse_pos and consuming as much of the input value as possible.
<term><parameter>value</parameter></term>
<listitem>
<para>
string to convert to a time
string to convert to a time
</para>
</listitem>
</varlistentry>
@ -55,10 +55,10 @@ $parse_pos and consuming as much of the input value as possible.
<term><parameter>position</parameter></term>
<listitem>
<para>
Position at which to start the parsing in $value (zero-based).
If no error occurs before $value is consumed, $parse_pos will contain -1
otherwise it will contain the position at which parsing ended .
If $parse_pos > strlen($value), the parse fails immediately.
Position at which to start the parsing in $value (zero-based).
If no error occurs before $value is consumed, $parse_pos will contain -1
otherwise it will contain the position at which parsing ended .
If $parse_pos > strlen($value), the parse fails immediately.
</para>
</listitem>
</varlistentry>

View file

@ -9,7 +9,7 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>int</type><methodname>IntlDateFormatter::parse</methodname>
@ -18,7 +18,7 @@
role="reference">position</parameter></methodparam>
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>int</type><methodname>datefmt_parse</methodname>
@ -40,7 +40,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource
The formatter resource
</para>
</listitem>
</varlistentry>
@ -48,7 +48,7 @@
<term><parameter>value</parameter></term>
<listitem>
<para>
string to convert to a time
string to convert to a time
</para>
</listitem>
</varlistentry>
@ -56,11 +56,11 @@
<term><parameter>position</parameter></term>
<listitem>
<para>
Position at which to start the parsing in $value (zero-based).
If no error occurs before $value is consumed, $parse_pos will contain -1
otherwise it will contain the position at which parsing ended (and the error occurred).
This variable will contain the end position if the parse fails.
If $parse_pos > strlen($value), the parse fails immediately.
Position at which to start the parsing in $value (zero-based).
If no error occurs before $value is consumed, $parse_pos will contain -1
otherwise it will contain the position at which parsing ended (and the error occurred).
This variable will contain the end position if the parse fails.
If $parse_pos > strlen($value), the parse fails immediately.
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>bool</type><methodname>IntlDateFormatter::setCalendar</methodname>
<methodparam><type>int</type><parameter>which</parameter></methodparam>
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>bool</type><methodname>datefmt_set_calendar</methodname>
@ -36,7 +36,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>
@ -44,8 +44,8 @@
<term><parameter>which</parameter></term>
<listitem>
<para>
The <link linkend="intl.intldateformatter-constants.calendartypes">calendar</link> to use.
Default is <constant>IntlDateFormatter::GREGORIAN</constant>.
The <link linkend="intl.intldateformatter-constants.calendartypes">calendar</link> to use.
Default is <constant>IntlDateFormatter::GREGORIAN</constant>.
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>bool</type><methodname>IntlDateFormatter::setLenient</methodname>
<methodparam><type>bool</type><parameter>lenient</parameter></methodparam>
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>bool</type><methodname>datefmt_set_lenient</methodname>
@ -39,7 +39,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource
The formatter resource
</para>
</listitem>
</varlistentry>
@ -47,7 +47,7 @@
<term><parameter>lenient</parameter></term>
<listitem>
<para>
Sets whether the parser is lenient or not, default is &false; (strict).
Sets whether the parser is lenient or not, default is &false; (strict).
</para>
</listitem>
</varlistentry>

View file

@ -9,14 +9,14 @@
<refsect1 role="description">
&reftitle.description;
<para>
Object oriented style
Object oriented style
</para>
<methodsynopsis>
<type>bool</type><methodname>IntlDateFormatter::setTimeZoneId</methodname>
<methodparam><type>string</type><parameter>zone</parameter></methodparam>
</methodsynopsis>
<para>
Procedural style
Procedural style
</para>
<methodsynopsis>
<type>bool</type><methodname>datefmt_set_timezone_id</methodname>
@ -36,7 +36,7 @@
<term><parameter>fmt</parameter></term>
<listitem>
<para>
The formatter resource.
The formatter resource.
</para>
</listitem>
</varlistentry>
@ -44,8 +44,8 @@
<term><parameter>zone</parameter></term>
<listitem>
<para>
The time zone ID string of the time zone to use.
If &null; or the empty string, the default time zone for the runtime is used.
The time zone ID string of the time zone to use.
If &null; or the empty string, the default time zone for the runtime is used.
</para>
</listitem>
</varlistentry>

View file

@ -57,7 +57,7 @@ function check( $err_code )
var_export( intl_is_failure( $err_code ) );
echo "\n";
}
check( U_ZERO_ERROR );
check( U_USING_FALLBACK_WARNING );
check( U_ILLEGAL_ARGUMENT_ERROR );

View file

@ -27,7 +27,7 @@
<term><parameter>haystack</parameter></term>
<listitem>
<para>
The string to look in. Must be valid UTF-8.
The string to look in. Must be valid UTF-8.
</para>
</listitem>
</varlistentry>
@ -35,7 +35,7 @@
<term><parameter>needle</parameter></term>
<listitem>
<para>
The string to look for. Must be valid UTF-8.
The string to look for. Must be valid UTF-8.
</para>
</listitem>
</varlistentry>

View file

@ -43,7 +43,7 @@
<term><parameter>before_needle</parameter></term>
<listitem>
<para>
If &true;, grapheme_strstr() returns the part of the
If &true;, grapheme_strstr() returns the part of the
haystack before the first occurrence of the needle.
</para>
</listitem>

View file

@ -43,7 +43,7 @@
<term><parameter>before_needle</parameter></term>
<listitem>
<para>
If &true;, grapheme_strstr() returns the part of the
If &true;, grapheme_strstr() returns the part of the
haystack before the first occurrence of the needle.
</para>
</listitem>

View file

@ -36,7 +36,7 @@
<listitem>
<para>
Start position in default grapheme units.
If $start is non-negative, the returned string will start at the
If $start is non-negative, the returned string will start at the
$start'th position in $string, counting from zero. If $start is negative,
the returned string will start at the $start'th grapheme unit from the
end of string.
@ -48,7 +48,7 @@
<listitem>
<para>
Length in grapheme units.
If $length is given and is positive, the string returned will contain
If $length is given and is positive, the string returned will contain
at most $length grapheme units beginning from $start (depending on the
length of string). If $string is less than or equal to $start grapheme
units long, FALSE will be returned. If $length is given and is negative, then

View file

@ -27,8 +27,8 @@
<methodparam><type>string</type><parameter>header</parameter></methodparam>
</methodsynopsis>
<para>
Tries to find locale that can satisfy the language list that is requested by the
HTTP "Accept-Language" header.
Tries to find locale that can satisfy the language list that is requested by the
HTTP "Accept-Language" header.
</para>
</refsect1>

View file

@ -53,11 +53,11 @@
the subtag is ordered by suffix resulting in variant0 followed by
variant1 followed by variant2 and so on.
</para>
<para>
The 'variant', 'private' and 'extlang' multiple values can be specified both
as array under specific key (e.g. 'variant') and as multiple numbered keys
(e.g. 'variant0', 'variant1', etc.).
</para>
<para>
The 'variant', 'private' and 'extlang' multiple values can be specified both
as array under specific key (e.g. 'variant') and as multiple numbered keys
(e.g. 'variant0', 'variant1', etc.).
</para>
</note>
</para>
</listitem>

View file

@ -86,7 +86,7 @@ var_export( $arr );
array (
0 => 'NEDIS',
1 => 'ROJAZ',
2 => '1901',
2 => '1901',
)
]]>
</screen>

View file

@ -10,26 +10,26 @@
<section xml:id="resourcebundle.intro">
&reftitle.intro;
<simpara>
Localized software products often require sets of data that are to be customized
depending on current locale, e.g.: messages, labels, formatting patterns. ICU
resource mechanism allows to define sets of resources that the application can
load on locale basis, while accessing them in unified locale-independent fashion.
Localized software products often require sets of data that are to be customized
depending on current locale, e.g.: messages, labels, formatting patterns. ICU
resource mechanism allows to define sets of resources that the application can
load on locale basis, while accessing them in unified locale-independent fashion.
</simpara>
<simpara>
This class implements access to ICU resource data files. These files are binary data
arrays which ICU uses to store the localized data.
This class implements access to ICU resource data files. These files are binary data
arrays which ICU uses to store the localized data.
</simpara>
<simpara>
ICU resource bundle can hold simple resources and complex resources. Complex resources
are containers which can be either integer-indexed or string-indexed (just like PHP arrays).
Simple resources can be of the following typos: string, integer, binary data field
or integer array.
ICU resource bundle can hold simple resources and complex resources. Complex resources
are containers which can be either integer-indexed or string-indexed (just like PHP arrays).
Simple resources can be of the following typos: string, integer, binary data field
or integer array.
</simpara>
<simpara>
<classname>ResourceBundle</classname> supports direct access to the data through array access
pattern and iteration via <link linkend="control-structures.foreach">foreach</link>,
as well as access via class methods. The result will be PHP value for simple resources and
<classname>ResourceBundle</classname> object for complex ones. All resources are read-only.
<classname>ResourceBundle</classname> supports direct access to the data through array access
pattern and iteration via <link linkend="control-structures.foreach">foreach</link>,
as well as access via class methods. The result will be PHP value for simple resources and
<classname>ResourceBundle</classname> object for complex ones. All resources are read-only.
</simpara>
</section>
<!-- }}} -->

View file

@ -61,7 +61,7 @@
<term><parameter>bundlename</parameter></term>
<listitem>
<para>
The directory where the data is stored or the name of the .dat file.
The directory where the data is stored or the name of the .dat file.
</para>
</listitem>
</varlistentry>