Daily updates from Odoo
Tuesday, February 6, 2024
3 changes
New functionality added to Odoo
A new feature has been added that allows users in India to scan QR codes on e-invoiced vendor bills directly in the Accounting app. This streamlines the bill entry process by automatically extracting invoice data from the QR code and creating vendor bills with partner information, reducing manual data entry and improving efficiency.
Original PR description
Now the user can scan the QR code on e-invoiced vendor bills, which allows user the following functionalities: -create a new vendor bill and also will create the partner if not found with help of the data received from qr code and partner autocomplete Functional Steps: - install l10n_in_qr_code_bill_scan - Go to Account app > Vendors > Bills - Go to tree/kanban view - Click on Scan button - Scan E-invoice QR Code task-3626437
This update adds Russian language translations to numerous enterprise modules in Odoo 17.0. The translations were generated using DeepL to provide Russian-speaking users with a fully localized experience across accounting, payment, asset management, and other key business modules. This expansion of language support makes the software more accessible to Russian-speaking organizations.
Original PR description
Enterprise side of what was done in COM PR: https://github.com/odoo/odoo/pull/152285
This update adds comprehensive Russian language translations to Odoo 17.0 across all standard modules. The translations were generated using automated translation tools with manual corrections for technical terms, enabling Russian-speaking users to use the system in their native language. This is the first complete translation pass for Russian support.
Original PR description
Final goal of this PR is to add in a first pass full auto-translation of Odoo into Russian. Steps taken to do so: 1. Re-export all pot files to ensure correct terms to translate + clean them up in…
Final goal of this PR is to add in a first pass full auto-translation of Odoo into Russian. Steps taken to do so: 1. Re-export all pot files to ensure correct terms to translate + clean them up in general due to human error 2. Add missing pot files for modules that were added after the last cleaning/freeze and therefore were also missing from the .tx config file (later PR to follow to add in modules missing from config file, but already have a pot file) 3. 1 large master po file of all the modules exported in steps 1 + 2 were feed into an auto-translator 4. Master po file was split back into respective module's ru.po files (missing ones due to module not being in config file were auto-generated, these modules will be added into the config in a later PR). Note that because msgmerge would not auto-update the existing po files with the new translations for some reason, the metadata of the previous translators was discarded for the sake of automating the splitting of the master po translation file into the individual module ones in a simple way 5. Manual fixes of incorrect translating (i.e. of code terms) were done where noticed, additional bugs may pop up in the future as users use db in Russian more Same process was done for Enterprise. ENT PR: https://github.com/odoo/enterprise/pull/55637 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr