PrestaShop 1.7
Child pages
  • Translations

Versions Compared

Old Version 12

changes.mady.by.user Alexandra Even

Saved on

compared with

New Version 13

changes.mady.by.user Alexandra Even

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Back office translations. The text visible to you and your team from your store's administration panel.
  • Theme translations. The text visible to your customers when browsing your store.
  • Installed modules translations. The content from the modules.
  • E-mail translations. The terms used in the default email templates.
  • Other translations. This category is meant to disappear in a coming version. It contains expressions that haven't been identified as being from the theme or the back office yet.

...

Info
titleDomains structure

While at first it can seem complicated to browse through translations domains, you will quickly understand how it works and you will easily find your way through the domain tree.

Each section (back office or theme) is further divided into functional domains, matching each sections of the back office (or theme).

 

For example, for the back office, the following domains correspond to their matching pages in the interface:

  • AdminCatalog, AdminModules, AdminDesign, AdminShipping, AdminPayment, AdminInternational, AdminShopParam and AdminAdvParameters.
  • AdminOrdersCustomers contains the expressions for the “Orders”, “Customers” and “Customer Service” sections from the back office.

These domains can have several sublevels: Feature, Notification, and Help. It means the following:

  • Feature: everything specific to a functional domain. If you’re in the “Shipping” section, the domain Admin.Shipping.Feature will contain all the expressions displaying in the Shipping menu, that are particular to these pages.
  • Notification: info, success, warning or error messages specific to the functional domain and the pages it includes.
  • Help: help text and placeholders.

On the other side, some domains are more generic:

  • AdminNavigation is about all the strings from the menu, footer, and header or the back office.
  • AdminActions gathers all the call-to-actions, buttons or links that you find on the back office, and that are quite generic (“Save”, “Add”, “Delete”, etc.)
  • AdminNotifications are all the warning, error or success messages that can appear in the back office.They must be general notifications applying to any part of the software (e.g. “Settings updated”).
  • AdminGlobal is where anything which doesn’t fall into the other categories but is still related to the back office will fall, given that can be found in a lot of occurrences (“Max”, “Settings”, “Enabled”, etc.) AND in different parts of the software too.

The same logic can be applied to the theme translations:

  • Shop.Theme ShopTheme and its sublevels (Catalog, CustomerAccount, Checkout, Actions) are the expressions from the default theme and its main sections
  • Shop.Forms ShopForms are specific to the various forms you can find on the default theme
  • Shop.Notifications ShopNotifications are the messages showing up on your shop, whether it is error or success messages.

...

In case of a string with a placeholder, you should make sure that the content of that placeholder will be placed in the correct flow of the sentence, and avoid literal translation.
Numbered placeholders (%1$s, %2$d, etc.) enable translators to rearrange the order of the placeholders in the string while maintaining the information each is replaced with. This way, a French translator could choose to translate "Order #%1$d from %2$s" into "Commande n°%1$s du %2$s" or "Le %2$s, commande n°%1$s".

Modules translations

When you wish to translate a specific module, choose "Installed modules translations", then select the one module you want to edit. It will open a new page with the content from this module, and all its available strings.

Info
Depending on the module you are looking at, the interface could be different. Some modules are using a translation system specific to 1.7, while others are still using the former system from 1.6 version. In the end it doesn't change anything for you, as you will be able to translate your modules just the same.

Email templates

The way email templates translations are handled is a bit different from the other translations.

...