Important

You are browsing the documentation for version 4.2 of OroCommerce, OroCRM and OroPlatform, which is no longer maintained. Read version 5.1 (the latest LTS version) of the Oro documentation to get up-to-date information.

See our Release Process documentation for more information on the currently supported and upcoming releases.

Translation and Localization

To serve a global audience, Oro products can be customized as necessary to provide for a multitude of languages and regional customizations. For example, the management can interact with the back-end in one language, while website visitors see content customized for their particular language and currency.

To lean more about translating static and dynamic content, localization parameters, logic, configuration, date, name and address formatting, see the topics below:

• Content and User Interface Translation
  • Standard Symfony Translator
  • Translatable Doctrine Extension
  • LocalizedFallbackValue Entity from OroLocaleBundle
• Translation Configuration
  • Debug Translator
  • Debug JS Translations
• Data Fixtures
  • Classes Description
    • AbstractTranslatableEntityFixture
• Schema Migrations
• Localization
  • System Configuration
  • Configuration Files
    • locale_data.yml
    • name_format.yml
    • address_format.yml
  • Date and Numeric Formatting
  • Name Formatting
  • Address Formatting