This document discusses data localization and translation in OroCRM. It covers topics like:
- Data localization involves adapting a product for a specific country/region by formatting names, addresses, dates, numbers based on locale.
- Translations are stored in YAML files and the database. Messages are extracted from code and templates.
- OroCRM supports formatting names, addresses, dates, numbers, and currencies based on locale settings. It also provides translation on the backend using the translator service and on the frontend using a JavaScript library.
- Administrators can configure localization settings and use CLI commands to extract, download, merge and upload translations to Crowdin for localization. Debugging options are available to help with