Martin TrigauxandRaphael Collet
257ccdf83c
When a single po file is processed (i.e. direct po import, not read from a i18n directory inside a module), there was no module information on code translations The module information is important for web translations where the list of modules is given in the call to the route '/website/translations' and '/web/webclient/translations' and only the web translations of these specific modules is retrieved and used. To manually import the translations of a custom module (e.g. openerp_enterprise), the base.language.import wizard is typically used and the give .po file is directly imported. For model and model_terms, the module information is easily deducted from the the record external id (<module>.<reference>) but for code translation, we relied on the global variable module_name. The .po file do contain the module information but this information was ignored. Real example: #. module: openerp_enterprise #. openerp-web #: code:addons/openerp_enterprise/static/src/js/odoo_enterprise_start_trial.js:249 #, python-format msgid "Please choose your domain name" msgstr "Veuillez choisir votre nom de domaine" Before this commit, the above translation was imported without the module and was not retrieved in the '/website/translations' call on the /trial page The global module_name is still used when set for backward compatibility. Co-authored-by: Raphael Collet <rco@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
Then follow the developer tutorials