The component Phalcon\Translate aids in creating multilingual applications. Applications using this component, display content in different languages, based on the user's chosen language supported by the application.
This component makes use of adapters to read translation messages from different sources in a unified way.
| Adapter | Description |
|---|---|
Phalcon\Translate\Adapter\NativeArray |
Uses PHP arrays to store the messages. This is the best option in terms of performance. |
Loads Translate Adapter class using adapter option
<?php
use Phalcon\Translate\Factory;
$options = [
'locale' => 'de_DE.UTF-8',
'defaultDomain' => 'translations',
'directory' => '/path/to/application/locales',
'category' => LC_MESSAGES,
'adapter' => 'gettext',
];
$translate = Factory::load($options);Translation strings are stored in files. The structure of these files could vary depending of the adapter used. Phalcon gives you the freedom to organize your translation strings. A simple structure could be:
app/messages/en.php
app/messages/es.php
app/messages/fr.php
app/messages/zh.phpEach file contains an array of the translations in a key/value manner. For each translation file, keys are unique. The same array is used in different files, where keys remain the same and values contain the translated strings depending on each language.
<?php
// app/messages/en.php
$messages = [
'hi' => 'Hello',
'bye' => 'Good Bye',
'hi-name' => 'Hello %name%',
'song' => 'This song is %song%',
];<?php
// app/messages/fr.php
$messages = [
'hi' => 'Bonjour',
'bye' => 'Au revoir',
'hi-name' => 'Bonjour %name%',
'song' => 'La chanson est %song%',
];Implementing the translation mechanism in your application is trivial but depends on how you wish to implement it. You can use an automatic detection of the language from the user's browser or you can provide a settings page where the user can select their language.
A simple way of detecting the user's language is to parse the $_SERVER['HTTP_ACCEPT_LANGUAGE'] contents, or if you wish, access it directly by calling $this->request->getBestLanguage() from an action/controller:
<?php
use Phalcon\Mvc\Controller;
use Phalcon\Translate\Adapter\NativeArray;
class UserController extends Controller
{
protected function getTranslation()
{
// Ask browser what is the best language
$language = $this->request->getBestLanguage();
$messages = [];
$translationFile = 'app/messages/' . $language . '.php';
// Check if we have a translation file for that lang
if (file_exists($translationFile)) {
require $translationFile;
} else {
// Fallback to some default
require 'app/messages/en.php';
}
// Return a translation object $messages comes from the require
// statement above
return new NativeArray(
[
'content' => $messages,
]
);
}
public function indexAction()
{
$this->view->name = 'Mike';
$this->view->t = $this->getTranslation();
}
}The _getTranslation() method is available for all actions that require translations. The $t variable is passed to the views, and with it, we can translate strings in that layer:
<!-- welcome -->
<!-- String: hi => 'Hello' -->
<p><?php echo $t->_('hi'), ' ', $name; ?></p>The _() method is returning the translated string based on the index passed. Some strings need to incorporate placeholders for calculated data i.e. Hello %name%. These placeholders can be replaced with passed parameters in the _() method. The passed parameters are in the form of a key/value array, where the key matches the placeholder name and the value is the actual data to be replaced:
<!-- welcome -->
<!-- String: hi-name => 'Hello %name%' -->
<p><?php echo $t->_('hi-name', ['name' => $name]); ?></p>Some applications implement multilingual on the URL such as http://www.mozilla.org/**es-ES**/firefox/. Phalcon can implement this by using a Router.
The implementation above is helpful but it requires a base controller to implement the _getTranslation() and return the Phalcon\Translate\Adapter\NativeArray component. Additionaly the component needs to be set in the view as seen above in the $t variable.
You can always wrap this functionality in its own class and register that class in the DI container:
<?php
use Phalcon\Mvc\User\Component;
use Phalcon\Translate\Adapter\NativeArray;
class Locale extends Component
{
public function getTranslator()
{
// Ask browser what is the best language
$language = $this->request->getBestLanguage();
/**
* We are using JSON based files for storing translations.
* You will need to check if the file exists!
*/
$translations = json_decode(
file_get_contents('app/messages/' . $language . '.json'),
true
);
// Return a translation object $messages comes from the require
// statement above
return new NativeArray(
[
'content' => $translations,
]
);
}
}This way you can use the component in controllers:
<?php
use Phalcon\Mvc\Controller;
class MyController extends Controller
{
public function indexAction()
{
$name = 'Mike';
$text = $this->locale->_('hi-name', ['name' => $name]);
$this->view->text = $text;
}
}or in a view directly
<?php echo $locale->_('hi-name', ['name' => 'Mike']);The Phalcon\Translate\AdapterInterface interface must be implemented in order to create your own translate adapters or extend the existing ones:
<?php
use Phalcon\Translate\AdapterInterface;
class MyTranslateAdapter implements AdapterInterface
{
/**
* Adapter constructor
*
* @param array $options
*/
public function __construct(array $options);
/**
* @param string $translateKey
* @param array|null $placeholders
* @return string
*/
public function t($translateKey, $placeholders = null);
/**
* Returns the translation string of the given key
*
* @param string $translateKey
* @param array $placeholders
* @return string
*/
public function _(string $translateKey, $placeholders = null): string;
/**
* Returns the translation related to the given key
*
* @param string $index
* @param array $placeholders
* @return string
*/
public function query(string $index, $placeholders = null): string;
/**
* Check whether is defined a translation key in the internal array
*
* @param string $index
* @return bool
*/
public function exists(string $index): bool;
}There are more adapters available for this components in the Phalcon Incubator