This update corrects faulty translations in the Swedish language pack for sales templates that were causing system errors when messages were sent in Swedish. The fix ensures that Swedish-speaking users can properly send sales communications without encountering translation-related failures.

Correcting faulty translation of templates that will break the system when messages are sent in Swedish. Reported as support tickit  #3900977.

This pull request contains multiple fixes and improvements across various Odoo modules including web editor link handling, accounting journal synchronization, delivery weight calculations, manufacturing operations, and inventory management. The changes address specific bugs that impact user workflows and system performance, such as incorrect picking weights, missing operation durations, and unnecessary recalculations in inventory systems.

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 update corrects an incorrect placeholder in a translation string within the mail module. The fix ensures that translated messages display properly and consistently across different languages, improving the user experience for non-English users.

This fix corrects errors in the Swedish language translation of sales email templates that were causing emails to fail when sent. The translation contained mistranslated code and unclosed XML tags that prevented proper email generation. This resolves support ticket #3900977.

Current Swedish templates are done wrong and will give error when e-mail is sent out, because code has been translated and XML tags are not closed. There are also multiple lines copied multiple times.

This is the fix for support ticket #3900977.

This fix resolves an issue in the website editor where drop zones (areas to place new content) would disappear when hiding a column in a snippet. The problem occurred because a visibility attribute was incorrectly propagating to parent elements. The fix adjusts how the system determines where to place drop zones, ensuring they remain available even when columns are hidden.

Steps to reproduce the bug:

- In Website edit mode.
- Drop 2 "Columns" snippets.
- Hide one of the columns in the first snippet by clicking on the "Hide
on desktop" button of the "Column" options in the side panel.
- Start to drag another snippet.
- Bug: There is no dropzone between the 2 "Column" snippets.

The issue happens because when the column becomes invisible, after
clicking the button, the attribute `data-invisible="1"` is added to the
column in the DOM thanks the 'snippet_option_visibility_update' event.

However, this event then propagates to the column's parent elements
(`<section>` and `<main>`). So, the attribute `data-invisible="1"` is also
added to the `<section>`, causing the dropzone not to be inserted as
expected. We should investigate this further later because it doesn't
seem consistent. For now, we prefer not to make changes at this level to
avoid introducing other bugs.

In this commit, we change the selector that determines where not to
insert dropzones so that it no longer considers `data-invisible="1"`.
This was added by this commit [1], but it seems unnecessary, and
':not(:visible)' in the selector is sufficient to avoid placing
dropzones between two non-visible elements.

[1]: https://github.com/odoo/odoo/commit/f9bd3033b21dbd1e4487d6d6cd1d8d8fdfbfb2ac

Forward-Port-Of: odoo/odoo#165797