Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <a href="http://php.net/manual/en/book.gettext.php" rel="nofollow noreferrer"><code>Gettext</code></a> family of functions is a good starting point:</p> <blockquote> <p>The gettext functions implement an NLS (Native Language Support) API which can be used to internationalize your PHP applications.</p> </blockquote> <p><a href="http://framework.zend.com/manual/en/zend.translate.html#zend.translate.introduction" rel="nofollow noreferrer"><code>Zend_Translate</code></a> is extremely flexible and has a thread-safe implementation of <code>gettext</code>. The manual states that it addresses the following problems with native internationalization implementations:</p> <blockquote> <ul> <li>Inconsistent API: There is no single API for the different source formats. The usage of gettext for example is very complicated.</li> <li>PHP supports only gettext and native array: PHP itself offers only support for array or gettext. All other source formats have to be coded manually, because there is no native support.</li> <li>No detection of the default language:The default language of the user cannot be detected without deeper knowledge of the backgrounds for the different web browsers.</li> <li>Gettext is not thread-safe: PHP's gettext library is not thread safe, and it should not be used in a multithreaded environment. This is due to problems with gettext itself, not PHP, but it is an existing problem.</li> </ul> </blockquote> <p>It is worth noting that the <a href="http://framework.zend.com" rel="nofollow noreferrer"><code>Zend Framework</code></a> is not a <em>full-stack</em> framework - in other words, you will not need to use the whole thing just to make use of its internationalization API. </p> <p>What I really like about it is its support for <a href="http://framework.zend.com/manual/en/zend.translate.adapter.html#zend.translate.adapter.decision" rel="nofollow noreferrer">multiple adapters for different data sources</a>, which you can easily mix, match, and change only having to apply very light modifications to your application. Hope that helps.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload