Daily updates from Odoo
Tuesday, January 21, 2020
5 changes
Resolved issues and error corrections
The base language list now replaces Filipino with Tagalog to better match common language naming and avoid confusion with Finnish browser language detection. This helps prevent Finnish users from being incorrectly directed to Filipino-language pages while keeping the expected Philippines language option available as Tagalog.
Original PR description
This is the second move to replace Filipino by Tagalog language Using Filipino (code fil_PH) is problematic as conflicts with Finnish (code fi_FI) and users having their browser in Finnish were…
This is the second move to replace Filipino by Tagalog language Using Filipino (code fil_PH) is problematic as conflicts with Finnish (code fi_FI) and users having their browser in Finnish were redirected to the Filipino version of the website (cf discussion at opw-2172710). This problem was also raised in other softwares like in the below discssion in Mozilla L10N groups https://groups.google.com/forum/#!topic/mozilla.dev.l10n/TW2qYyDDNoE Quoting the discussion in above thread: > Filipino is the national language of the Philippines, but it is > commonly referred to (and registered as) Tagalog, since most of the > terms therein were derived from it (Tagalog). This commit targets the master (future 14.0 as of today), adds a new Tagalog language and removes the Filipino. In 12.0, only the Tagalog was added at odoo/odoo#43633. As fil_PH is only translated on odoo-com project but remains at 0% in other Transifex project, it is assumed the language switch won't impact too many people.
This update corrects how website, sales, mailing, and web interface templates mark text for translation. It prevents layout or style text from being sent to translators while ensuring real user-facing labels are properly translatable, improving localization quality across Odoo.
Original PR description
This commit fix most `t-set` errors that either led to:
1. unwanted text to be considered as translatable.
eg: `<t t-set="classes">text-left bg-100 p4</t>` would create an
`ir.translation`.
2. text that should be translatable were not.
eg: `<t t-set="text" t-value="'Both'"/>` would not create an
`ir.translation` while it should.
If a text should be translatable, it should never be inside a `t-value`:
- `<t t-set="text">Both</t>`
If a text should not be translatable, it sould either be inside `t-value`,
`t-valuef` or the `<t>` tag should have `t-translation="off"`:
- `<t t-set="classes" t-translation="off">text-left bg-100 p4</t>`
- `<t t-set="classes" t-valuef="text-left bg-100 p4"/>`
- `<t t-set="classes" t-value="'text-left bg-100 p4'"/>`
https://github.com/odoo/odoo/pull/43660
https://github.com/odoo/enterprise/pull/7839
https://github.com/odoo/design-themes/pull/203This fixes the styling of a website button snippet so buttons display as intended again. It helps keep website pages visually consistent and prevents a small design regression from affecting visitors.
This fixes a timing issue where quickly creating a related record while editing order lines could reset or disrupt unsaved line changes. It makes sales and rental form interactions more reliable and also corrects product configurator dialogs so follow-up choices appear in front as expected.
Original PR description
Let's assume a form view containing a many2one with an onchange that updates the value of a one2many. Do a quick create in the many2one. While the name_create request is pending, add a row to the…
Let's assume a form view containing a many2one with an onchange that updates the value of a one2many. Do a quick create in the many2one. While the name_create request is pending, add a row to the one2many but do not leave it. When the name_create returns, and the onchange has been performed, the one2many is reset, and the row is no longer in edition (worse, it could be invalid, i.e. in a state that the user could not have reached in a normal situation). This commit fixes this issue by considering the whole [name_create + onchange] operation as one. This operation is executed in the mutex of the model, so the other request (adding a row to the one2many) is delayed until the many2one value has been correctly set. This fixes an issue with the sale and rental tours (on sale_order), that had been deactivated for a while. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix corrects how template text is marked for translation across several Odoo Enterprise modules. It helps prevent technical labels or styling text from appearing to translators while ensuring real user-facing words are available for translation.
Original PR description
This commit fix most `t-set` errors that either led to:
1. unwanted text to be considered as translatable.
eg: `<t t-set="classes">text-left bg-100 p4</t>` would create an
`ir.translation`.
2. text that should be translatable were not.
eg: `<t t-set="text" t-value="'Both'"/>` would not create an
`ir.translation` while it should.
If a text should be translatable, it should never be inside a `t-value`:
- `<t t-set="text">Both</t>`
If a text should not be translatable, it sould either be inside `t-value`,
`t-valuef` or the `<t>` tag should have `t-translation="off"`:
- `<t t-set="classes" t-translation="off">text-left bg-100 p4</t>`
- `<t t-set="classes" t-valuef="text-left bg-100 p4"/>`
- `<t t-set="classes" t-value="'text-left bg-100 p4'"/>`
https://github.com/odoo/odoo/pull/43660
https://github.com/odoo/enterprise/pull/7839
https://github.com/odoo/design-themes/pull/203