[MANUAL] Brazilian Portuguese:

- sync to r20843, r20854, r20855


git-svn-id: http://framework.zend.com/svn/framework/standard/trunk@20865 44c647ce-9c0f-0410-b52a-842ac1e357ba

documentation/manual/pt-br/module_specs/Zend_Paginator-Introduction.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 15103 -->
+<!-- EN-Revision: 20843 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.paginator.introduction">
     <title>Introdução</title>
@@ -19,17 +19,20 @@
                     Paginar dados arbitrários, não apenas bancos de dados relacionais
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     Buscar apenas os resultados que precisam ser exibidos
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     Não forçar os usuários a aderirem a apenas uma maneira de exibição dos dados
                     ou renderização dos controles de paginação
                 </para>
             </listitem>
+
             <listitem>
                 <para>
                     Ter uma fraca união entre <classname>Zend_Paginator</classname> e os outros

documentation/manual/pt-br/module_specs/Zend_Search_Lucene-Charset.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 17175 -->
+<!-- EN-Revision: 20854 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.search.lucene.charset">
     <title>Conjunto de Caractere</title>
@@ -13,6 +13,7 @@
             "UTF-8 modificado" usado pelo Java. O núcleo do
             <classname>Zend_Search_Lucene</classname> suporta esta codificação plenamente, com uma
             exceção.
+
             <footnote>
                <para>
                    <classname>Zend_Search_Lucene</classname> suporta somente os caracteres do Plano
@@ -31,21 +32,25 @@
         </para>
 
         <para>
-            Actual input data encoding may be specified through <classname>Zend_Search_Lucene</classname> <acronym>API</acronym>. Data will
-            be automatically converted into UTF-8 encoding.
+            Actual input data encoding may be specified through
+            <classname>Zend_Search_Lucene</classname> <acronym>API</acronym>. Data will be
+            automatically converted into UTF-8 encoding.
         </para>
     </sect2>
 
     <sect2 id="zend.search.lucene.charset.default_analyzer">
         <title>Default text analyzer</title>
+
         <para>
             However, the default text analyzer (which is also used within query parser) uses
             ctype_alpha() for tokenizing text and queries.
         </para>
 
         <para>
-            ctype_alpha() is not UTF-8 compatible, so the analyzer converts text to 'ASCII//TRANSLIT' encoding before
-            indexing. The same processing is transparently performed during query parsing.
+            ctype_alpha() is not UTF-8 compatible, so the analyzer converts text to
+            'ASCII//TRANSLIT' encoding before indexing. The same processing is transparently
+            performed during query parsing.
+
             <footnote>
                <para>
                    Conversion to 'ASCII//TRANSLIT' may depend on current locale and OS.
@@ -56,8 +61,8 @@
         <note>
             <title/>
             <para>
-                Default analyzer doesn't treats numbers as parts of terms. Use corresponding 'Num' analyzer if you don't want words
-                to be broken by numbers.
+                Default analyzer doesn't treats numbers as parts of terms. Use corresponding 'Num'
+                analyzer if you don't want words to be broken by numbers.
             </para>
         </note>
     </sect2>
@@ -66,8 +71,10 @@
         <title>UTF-8 compatible text analyzers</title>
 
         <para>
-            <classname>Zend_Search_Lucene</classname> also contains a set of UTF-8 compatible analyzers: <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8</classname>,
-            <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8Num</classname>, <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8_CaseInsensitive</classname>,
+            <classname>Zend_Search_Lucene</classname> also contains a set of UTF-8 compatible
+            analyzers: <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8</classname>,
+            <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8Num</classname>,
+            <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8_CaseInsensitive</classname>,
             <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Utf8Num_CaseInsensitive</classname>.
         </para>
 
@@ -83,19 +90,23 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault(
         <warning>
             <title/>
             <para>
-                UTF-8 compatible analyzers were improved in Zend Framework 1.5. Early versions of analyzers assumed
-                all non-ascii characters are letters. New analyzers implementation has more accurate behavior.
+                UTF-8 compatible analyzers were improved in Zend Framework 1.5. Early versions of
+                analyzers assumed all non-ascii characters are letters. New analyzers implementation
+                has more accurate behavior.
             </para>
+
             <para>
-                This may need you to re-build index to have data and search queries tokenized in the same way, otherwise search engine
-                may return wrong result sets.
+                This may need you to re-build index to have data and search queries tokenized in the
+                same way, otherwise search engine may return wrong result sets.
             </para>
         </warning>
 
         <para>
-            All of these analyzers need PCRE (Perl-compatible regular expressions) library to be compiled with UTF-8 support turned on.
-            PCRE UTF-8 support is turned on for the PCRE library sources bundled with <acronym>PHP</acronym> source code distribution, but if shared library is used
-            instead of bundled with <acronym>PHP</acronym> sources, then UTF-8 support state may depend on you operating system.
+            All of these analyzers need PCRE (Perl-compatible regular expressions) library to be
+            compiled with UTF-8 support turned on. PCRE UTF-8 support is turned on for the PCRE
+            library sources bundled with <acronym>PHP</acronym> source code distribution, but if
+            shared library is used instead of bundled with <acronym>PHP</acronym> sources, then
+            UTF-8 support state may depend on you operating system.
         </para>
 
         <para>
@@ -111,12 +122,15 @@ if (@preg_match('/\pL/u', 'a') == 1) {
         </para>
 
         <para>
-            Case insensitive versions of UTF-8 compatible analyzers also need <ulink url="http://www.php.net/manual/en/ref.mbstring.php">mbstring</ulink> extension to be enabled.
+            Case insensitive versions of UTF-8 compatible analyzers also need <ulink
+                url="http://www.php.net/manual/en/ref.mbstring.php">mbstring</ulink> extension to
+            be enabled.
         </para>
 
         <para>
-            If you don't want mbstring extension to be turned on, but need case insensitive search, you may use the following approach: normalize source data before indexing
-            and query string before searching by converting them to lowercase:
+            If you don't want mbstring extension to be turned on, but need case insensitive search,
+            you may use the following approach: normalize source data before indexing and query
+            string before searching by converting them to lowercase:
 
             <programlisting language="php"><![CDATA[
 // Indexing

documentation/manual/pt-br/module_specs/Zend_Search_Lucene-Extending.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 18739 -->
+<!-- EN-Revision: 20854 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.search.lucene.extending">
     <title>Extensibilidade</title>
@@ -141,22 +141,24 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault(
         <title>Tokens Filtering</title>
 
         <para>
-            The <classname>Zend_Search_Lucene_Analysis_Analyzer_Common</classname> analyzer also offers a token filtering
-            mechanism.
+            The <classname>Zend_Search_Lucene_Analysis_Analyzer_Common</classname> analyzer also
+            offers a token filtering mechanism.
         </para>
 
         <para>
-            The <classname>Zend_Search_Lucene_Analysis_TokenFilter</classname> class provides an abstract interface for such filters.
-            Your own filters should extend this class either directly or indirectly.
+            The <classname>Zend_Search_Lucene_Analysis_TokenFilter</classname> class provides an
+            abstract interface for such filters. Your own filters should extend this class either
+            directly or indirectly.
         </para>
 
         <para>
-            Any custom filter must implement the <methodname>normalize()</methodname> method which may transform input token or signal that
-            the current token should be skipped.
+            Any custom filter must implement the <methodname>normalize()</methodname> method which
+            may transform input token or signal that the current token should be skipped.
         </para>
 
         <para>
             There are three filters already defined in the analysis subpackage:
+
             <itemizedlist>
                 <listitem>
                     <para>
@@ -180,13 +182,13 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault(
 
         <para>
             The <code>LowerCase</code> filter is already used for
-            <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Text_CaseInsensitive</classname> analyzer
-            by default.
+            <classname>Zend_Search_Lucene_Analysis_Analyzer_Common_Text_CaseInsensitive</classname>
+            analyzer by default.
         </para>
 
         <para>
-            The <code>ShortWords</code> and <code>StopWords</code> filters may be used with pre-defined or custom
-            analyzers like this:
+            The <code>ShortWords</code> and <code>StopWords</code> filters may be used with
+            pre-defined or custom analyzers like this:
 
             <programlisting language="php"><![CDATA[
 $stopWords = array('a', 'an', 'at', 'the', 'and', 'or', 'is', 'am');
@@ -199,7 +201,6 @@ $analyzer->addFilter($stopWordsFilter);
 
 Zend_Search_Lucene_Analysis_Analyzer::setDefault($analyzer);
 ]]></programlisting>
-
             <programlisting language="php"><![CDATA[
 $shortWordsFilter = new Zend_Search_Lucene_Analysis_TokenFilter_ShortWords();
 
@@ -212,8 +213,8 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault($analyzer);
         </para>
 
         <para>
-            The <classname>Zend_Search_Lucene_Analysis_TokenFilter_StopWords</classname> constructor takes an array of stop-words
-            as an input. But stop-words may be also loaded from a file:
+            The <classname>Zend_Search_Lucene_Analysis_TokenFilter_StopWords</classname> constructor
+            takes an array of stop-words as an input. But stop-words may be also loaded from a file:
 
             <programlisting language="php"><![CDATA[
 $stopWordsFilter = new Zend_Search_Lucene_Analysis_TokenFilter_StopWords();
@@ -226,12 +227,14 @@ $analyzer->addFilter($stopWordsFilter);
 Zend_Search_Lucene_Analysis_Analyzer::setDefault($analyzer);
 ]]></programlisting>
 
-            This file should be a common text file with one word in each line. The '#' character marks a line as a comment.
+            This file should be a common text file with one word in each line. The '#' character
+            marks a line as a comment.
         </para>
 
         <para>
-            The <classname>Zend_Search_Lucene_Analysis_TokenFilter_ShortWords</classname> constructor has one optional argument.
-            This is the word length limit, set by default to 2.
+            The <classname>Zend_Search_Lucene_Analysis_TokenFilter_ShortWords</classname>
+            constructor has one optional argument. This is the word length limit, set by default to
+            2.
         </para>
     </sect2>
 
@@ -244,8 +247,8 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault($analyzer);
         </para>
 
         <para>
-            <code>score(q,d) = sum( tf(t in d) * idf(t) * getBoost(t.field in d) * lengthNorm(t.field in d) ) *
-            coord(q,d) * queryNorm(q)</code>
+            <code>score(q,d) = sum( tf(t in d) * idf(t) * getBoost(t.field in d) *
+                lengthNorm(t.field in d) ) * coord(q,d) * queryNorm(q)</code>
         </para>
 
         <para>
@@ -254,9 +257,9 @@ Zend_Search_Lucene_Analysis_Analyzer::setDefault($analyzer);
         </para>
 
         <para>
-            idf(t) -
-            <methodname>Zend_Search_Lucene_Search_Similarity::idf($input, $reader)</methodname> -
-            um fator de pontuação para um termo simples com o índice especificado.
+            idf(t) - <methodname>Zend_Search_Lucene_Search_Similarity::idf($input,
+                $reader)</methodname> - um fator de pontuação para um termo simples com o índice
+            especificado.
         </para>
 
         <para>
@@ -512,10 +515,8 @@ class MyFile extends Zend_Search_Lucene_Storage_File {
     }
 }
 ]]></programlisting>
-
     </sect2>
 </sect1>
-
 <!--
 vim:se ts=4 sw=4 et:
 -->

documentation/manual/pt-br/module_specs/Zend_Search_Lucene-IndexCreation.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 18536 -->
+<!-- EN-Revision: 20854 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.search.lucene.index-creation">
     <title>Construindo Índices</title>
@@ -145,15 +145,16 @@ for ($count = 0; $count < $index->maxDoc(); $count++) {
         <para>
             Os arquivos de segmento de índice Lucene não podem ser atualizados devido ao seu
             projeto. A atualização de um segmento necessita de uma reorganização completa do
-            segmento. Veja os formatos de arquivos de índice Lucene para mais detalhes
-            (<ulink
+            segmento. Veja os formatos de arquivos de índice Lucene para mais detalhes (<ulink
                 url="http://lucene.apache.org/java/2_3_0/fileformats.html">http://lucene.apache.org/java/2_3_0/fileformats.html</ulink>)
+
             <footnote>
                 <para>
                     O formato de arquivo de índice Lucene atualmente suportado é a versão 2.3
                     (desde Zend Framework 1.6).
                 </para>
             </footnote>.
+
             Novos documentos são adicionados ao índice através da criação de um novo segmento.
         </para>
 
@@ -193,12 +194,13 @@ $index->optimize();
             <title>MaxBufferedDocs auto-optimization option</title>
 
             <para>
-                <emphasis>MaxBufferedDocs</emphasis> is a minimal number of documents required before
-                the buffered in-memory documents are written into a new segment.
+                <emphasis>MaxBufferedDocs</emphasis> is a minimal number of documents required
+                before the buffered in-memory documents are written into a new segment.
             </para>
 
             <para>
-                <emphasis>MaxBufferedDocs</emphasis> can be retrieved or set by <code>$index->getMaxBufferedDocs()</code> or
+                <emphasis>MaxBufferedDocs</emphasis> can be retrieved or set by
+                <code>$index->getMaxBufferedDocs()</code> or
                 <code>$index->setMaxBufferedDocs($maxBufferedDocs)</code> calls.
             </para>
 
@@ -211,14 +213,15 @@ $index->optimize();
             <title>MaxMergeDocs auto-optimization option</title>
 
             <para>
-                <emphasis>MaxMergeDocs</emphasis> is a largest number of documents ever merged by addDocument().
-                Small values (e.g., less than 10.000) are best for interactive indexing, as this limits the length
-                of pauses while indexing to a few seconds. Larger values are best for batched indexing and speedier
-                searches.
+                <emphasis>MaxMergeDocs</emphasis> is a largest number of documents ever merged by
+                addDocument(). Small values (e.g., less than 10.000) are best for interactive
+                indexing, as this limits the length of pauses while indexing to a few seconds.
+                Larger values are best for batched indexing and speedier searches.
             </para>
 
             <para>
-                <emphasis>MaxMergeDocs</emphasis> can be retrieved or set by <code>$index->getMaxMergeDocs()</code> or
+                <emphasis>MaxMergeDocs</emphasis> can be retrieved or set by
+                <code>$index->getMaxMergeDocs()</code> or
                 <code>$index->setMaxMergeDocs($maxMergeDocs)</code> calls.
             </para>
 
@@ -231,21 +234,26 @@ $index->optimize();
             <title>MergeFactor auto-optimization option</title>
 
             <para>
-                <emphasis>MergeFactor</emphasis> determines how often segment indices are merged by addDocument().
-                With smaller values, less <acronym>RAM</acronym> is used while indexing, and searches on unoptimized indices are faster,
-                but indexing speed is slower. With larger values, more <acronym>RAM</acronym> is used during indexing, and while searches
-                on unoptimized indices are slower, indexing is faster. Thus larger values (&gt; 10) are best for batch
-                index creation, and smaller values (&lt; 10) for indices that are interactively maintained.
+                <emphasis>MergeFactor</emphasis> determines how often segment indices are merged by
+                addDocument(). With smaller values, less <acronym>RAM</acronym> is used while
+                indexing, and searches on unoptimized indices are faster, but indexing speed is
+                slower. With larger values, more <acronym>RAM</acronym> is used during indexing, and
+                while searches on unoptimized indices are slower, indexing is faster. Thus larger
+                values (&gt; 10) are best for batch index creation, and smaller values (&lt; 10) for
+                indices that are interactively maintained.
             </para>
 
             <para>
-                <emphasis>MergeFactor</emphasis> is a good estimation for average number of segments merged by one auto-optimization pass.
-                Too large values produce large number of segments while they are not merged into new one. It may be a cause of
-                "failed to open stream: Too many open files" error message. This limitation is system dependent.
+                <emphasis>MergeFactor</emphasis> is a good estimation for average number of segments
+                merged by one auto-optimization pass. Too large values produce large number of
+                segments while they are not merged into new one. It may be a cause of "failed to
+                open stream: Too many open files" error message. This limitation is system
+                dependent.
             </para>
 
             <para>
-                <emphasis>MergeFactor</emphasis> can be retrieved or set by <code>$index->getMergeFactor()</code> or
+                <emphasis>MergeFactor</emphasis> can be retrieved or set by
+                <code>$index->getMergeFactor()</code> or
                 <code>$index->setMergeFactor($mergeFactor)</code> calls.
             </para>
 
@@ -254,17 +262,27 @@ $index->optimize();
             </para>
 
             <para>
-                Lucene Java and Luke (Lucene Index Toolbox - <ulink url="http://www.getopt.org/luke/">http://www.getopt.org/luke/</ulink>)
-                can also be used to optimize an index. Latest Luke release (v0.8) is based on Lucene v2.3 and compatible with
-                current implementation of <classname>Zend_Search_Lucene</classname> component (Zend Framework 1.6). Earlier versions of <classname>Zend_Search_Lucene</classname> implementations
-                need another versions of Java Lucene tools to be compatible:
+                Lucene Java and Luke (Lucene Index Toolbox - <ulink
+                    url="http://www.getopt.org/luke/">http://www.getopt.org/luke/</ulink>) can also
+                be used to optimize an index. Latest Luke release (v0.8) is based on Lucene v2.3 and
+                compatible with current implementation of <classname>Zend_Search_Lucene</classname>
+                component (Zend Framework 1.6). Earlier versions of
+                <classname>Zend_Search_Lucene</classname> implementations need another versions of
+                Java Lucene tools to be compatible:
+
                 <itemizedlist>
                     <listitem>
-                        <para>Zend Framework 1.5 - Java Lucene 2.1 (Luke tool v0.7.1 - <ulink url="http://www.getopt.org/luke/luke-0.7.1/"/>)</para>
+                        <para>
+                            Zend Framework 1.5 - Java Lucene 2.1 (Luke tool v0.7.1 - <ulink
+                                url="http://www.getopt.org/luke/luke-0.7.1/"/>)
+                        </para>
                     </listitem>
 
                     <listitem>
-                        <para>Zend Framework 1.0 - Java Lucene 1.4 - 2.1 (Luke tool v0.6 - <ulink url="http://www.getopt.org/luke/luke-0.6/"/>)</para>
+                        <para>
+                            Zend Framework 1.0 - Java Lucene 1.4 - 2.1 (Luke tool v0.6 - <ulink
+                                url="http://www.getopt.org/luke/luke-0.6/"/>)
+                        </para>
                     </listitem>
                 </itemizedlist>
             </para>
@@ -279,7 +297,9 @@ $index->optimize();
         </para>
 
         <para>
-            It's possible to override this with the <methodname>Zend_Search_Lucene_Storage_Directory_Filesystem::setDefaultFilePermissions()</methodname> method:
+            It's possible to override this with the
+            <methodname>Zend_Search_Lucene_Storage_Directory_Filesystem::setDefaultFilePermissions()</methodname>
+            method:
         </para>
 
         <programlisting language="php"><![CDATA[
@@ -311,12 +331,15 @@ Zend_Search_Lucene_Storage_Directory_Filesystem::setDefaultFilePermissions(0660)
             <title>Supported Filesystems</title>
 
             <para>
-                <classname>Zend_Search_Lucene</classname> uses <methodname>flock()</methodname> to provide concurrent searching, index updating and optimization.
+                <classname>Zend_Search_Lucene</classname> uses <methodname>flock()</methodname> to
+                provide concurrent searching, index updating and optimization.
             </para>
 
             <para>
-                According to the <acronym>PHP</acronym> <ulink url="http://www.php.net/manual/en/function.flock.php">documentation</ulink>,
-                "<methodname>flock()</methodname> will not work on NFS and many other networked file systems".
+                According to the <acronym>PHP</acronym> <ulink
+                    url="http://www.php.net/manual/en/function.flock.php">documentation</ulink>,
+                "<methodname>flock()</methodname> will not work on NFS and many other networked file
+                systems".
             </para>
 
             <para>
@@ -325,7 +348,6 @@ Zend_Search_Lucene_Storage_Directory_Filesystem::setDefaultFilePermissions(0660)
         </sect3>
     </sect2>
 </sect1>
-
 <!--
 vim:se ts=4 sw=4 et:
 -->

documentation/manual/pt-br/module_specs/Zend_Search_Lucene-JavaLucene.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 18536 -->
+<!-- EN-Revision: 20854 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.search.lucene.java-lucene">
     <title>Interoperando com Java Lucene</title>
@@ -92,7 +92,6 @@ indexWriter.addDocument(doc);
 ]]></programlisting>
     </sect2>
 </sect1>
-
 <!--
 vim:se ts=4 sw=4 et:
 -->

documentation/manual/pt-br/module_specs/Zend_Service.xml

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- EN-Revision: 20818 -->
+<!-- EN-Revision: 20855 -->
 <!-- Reviewed: no -->
 <sect1 id="zend.service.introduction">
     <title>Introdução</title>
@@ -24,39 +24,93 @@
 
     <itemizedlist>
         <listitem>
-            <para><link linkend="zend.service.akismet">Akismet</link></para>
+            <para>
+                <link linkend="zend.service.akismet">Akismet</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.amazon">Amazon</link></para>
+            <para>
+                <link linkend="zend.service.amazon">Amazon</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.audioscrobbler">Audioscrobbler</link></para>
+            <para>
+                <link linkend="zend.service.audioscrobbler">Audioscrobbler</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.delicious">Del.icio.us</link></para>
+            <para>
+                <link linkend="zend.service.delicious">Del.icio.us</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.flickr">Flickr</link></para>
+            <para>
+                <link linkend="zend.service.flickr">Flickr</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.simpy">Simpy</link></para>
+            <para>
+                <link linkend="zend.service.livedocx">LiveDocx</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.slideshare">SlideShare</link></para>
+            <para>
+                <link linkend="zend.service.nirvanix">Nirvanix</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.strikeiron">StrikeIron</link></para>
+            <para>
+                <link linkend="zend.service.recaptcha">ReCaptcha</link>
+            </para>
         </listitem>
 
         <listitem>
-            <para><link linkend="zend.service.yahoo">Yahoo!</link></para>
+            <para>
+                <link linkend="zend.service.simpy">Simpy</link>
+            </para>
+        </listitem>
+
+        <listitem>
+            <para>
+                <link linkend="zend.service.slideshare">SlideShare</link>
+            </para>
+        </listitem>
+
+        <listitem>
+            <para>
+                <link linkend="zend.service.strikeiron">StrikeIron</link>
+            </para>
+        </listitem>
+
+        <listitem>
+            <para>
+                <link linkend="zend.service.technorati">Technorati</link>
+            </para>
+        </listitem>
+
+        <listitem>
+            <para>
+                <link linkend="zend.service.twitter">Twitter</link>
+            </para>
+        </listitem>
+
+        <listitem>
+            <para>
+                <link linkend="zend.service.windowsazure">Windows Azure</link>
+            </para>
+        </listitem>
+
+        <listitem>
+            <para>
+                <link linkend="zend.service.yahoo">Yahoo!</link>
+            </para>
         </listitem>
     </itemizedlist>