Translation

One of the main needs for localization is translating wordings to the another language. PrestaShop is capable of translating wordings to any language, as long as it has the appropriate translations available.

PrestaShop 1.7 features a new translation system, based on the Symfony Translation component.

This system is only available for Core and Native modules.

See here for 3rd party modules.

Overview

The translation system is less complicated than it can seem to be at first glance. To start working with it, you should get familiarized with the following concepts:

Wording
(Also called “message”). An abstraction of a phrase that will be translated to any given language. It’s usually written as plain English, in order to make it easier to understand.
Translation Domain
A group of wordings. Organizing messages in groups allows for an improved contextualization of wordings (Read more).
Message Catalogue
A collection of wordings in a given language. Each supported language has its own catalogue which contains translations for all the wordings in that language.
Default Message Catalogue
The base message catalogue on which the translated message catalogues are based. This is where we add new wordings.
Catalogue Resource
A data source containing a catalogue. It can be an in-memory array, a database, a group of files…
Translator
A service that allows translating wordings to a given language.

How to translate wordings

This section provides an quick reference on how to use the Translator. For more information, read Symfony’s documentation on Using the Translator.

PHP files

To translate wordings in PHP files, you first need an instance of the Translator service (explained below). Then, you can use the trans() method to translate your wording:

echo $translator->trans('This product is no longer available.', [], 'Shop.Notifications.Error');

The trans() method takes three arguments:

  1. The wording to translate. Keep in mind that it has to be exactly the same as the one in the default catalogue, or the translation won’t work.
  2. An array of replacements, if any (Learn more here).
  3. The translation domain for that wording.
Inside controllers

Controllers include a helper method named trans() that calls the translator internally:

$this->trans('This product is no longer available.', [], 'Shop.Notifications.Error');
Outside controllers

If you are outside a controller, and after careful consideration you think you absolutely need some stuff translated, then you can add it as a dependency of your class:

// SomeService.php

namespace PrestaShop\PrestaShop\Core\Foo\Bar;

use Symfony\Component\Translation\TranslatorInterface;

class SomeService
{
    private $translator;

    public function __construct(TranslatorInterface $translator)
    {
        $this->translator = $translator;
    }
}

Then, inject it into your service using the Dependency Container:

# services.yml

prestashop.core.foo.bar.some_service:
    class: 'PrestaShop\PrestaShop\Core\Foo\Bar\SomeService'
    arguments:
        - '@translator'

And finally, use the translator at will:

// SomeService.php

$this->translator->trans('This product is no longer available.', [], 'Shop.Notifications.Error');

Smarty templates

In .tpl files, use the l (lower case “L”) macro:

<div>{l s='This product is no longer available.' d='Shop.Notifications.Error'}</div>

If you have have replacements to peform in your wording, then there are two options:

  1. Anonymous placeholders (eg. %s)

    <div>{l s='List of products by supplier %s' sprintf=[$supplier.name] d='Shop.Theme.Catalog'}</div>

  2. Named placeholders (eg. %my_placeholder%)

    <div>{l s='There are %products_count% items in your cart.' sprintf=['%products_count%' => $cart.products_count] d='Shop.Theme.Checkout'}</div>

Twig templates

In .twig files, you can use the trans filter from Twig:

<div>{{ 'Sort by'|trans({}, 'Admin.Actions') }}</div>

For information on more advanced features, head on to the Official documentation.