NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[I18N] *: export 17.0 translations

Browse Source 
closes odoo/documentation#6727

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
This commit is contained in:
Martin Trigaux 2023-11-30 15:45:47 +01:00
parent 1a44524ab5
commit 8ba87a67ce
11 changed files with 11866 additions and 3391 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

256
locale/sources/administration.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-08 08:46+0000\n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -894,8 +894,8 @@ msgstr ""
#: ../../content/administration/maintain/domain_names.rst:166
#: ../../content/administration/maintain/domain_names.rst:236
#: ../../content/administration/maintain/supported_versions.rst:29
#: ../../content/administration/upgrade.rst:90
#: ../../content/administration/upgrade.rst:305
#: ../../content/administration/upgrade.rst:92
#: ../../content/administration/upgrade.rst:309
msgid "Odoo Online"
msgstr ""
@ -1989,8 +1989,8 @@ msgstr ""
#: ../../content/administration/maintain/domain_names.rst:250
#: ../../content/administration/maintain/supported_versions.rst:30
#: ../../content/administration/odoo_sh.rst:5
#: ../../content/administration/upgrade.rst:120
#: ../../content/administration/upgrade.rst:316
#: ../../content/administration/upgrade.rst:122
#: ../../content/administration/upgrade.rst:320
msgid "Odoo.sh"
msgstr ""
@ -5970,11 +5970,11 @@ msgstr ""
msgid "The documentation will help you go live with your Odoo.sh project in no time."
msgstr ""
#: ../../content/administration/upgrade.rst:5
#: ../../content/administration/upgrade.rst:7
msgid "An upgrade is the process of moving your database from an older version to a newer :doc:`supported version <maintain/supported_versions>` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes with new and improved features, bug fixes, and security patches."
msgstr ""
#: ../../content/administration/upgrade.rst:13
#: ../../content/administration/upgrade.rst:15
msgid "The Rolling Release process allows Odoo Online customers to upgrade their database directly from a message prompt sent to the database administrator as soon as a new version is released. The invitation to upgrade is only sent if no issues are detected during the automatic tests."
msgstr ""
@ -5982,91 +5982,91 @@ msgstr ""
msgid "The upgrade message prompt on the top right of the database"
msgstr ""
#: ../../content/administration/upgrade.rst:20
#: ../../content/administration/upgrade.rst:22
msgid "It is strongly recommended to manually :ref:`test the upgrade first <upgrade/test_your_db>`. Clicking :guilabel:`I want to test first` redirects to `the database manager <https://www.odoo.com/my/databases/>`_, where it is possible to request an upgraded test database and check it for any discrepancies."
msgstr ""
#: ../../content/administration/upgrade.rst:25
#: ../../content/administration/upgrade.rst:27
msgid "It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it immediately triggers the live production database upgrade."
msgstr ""
#: ../../content/administration/upgrade.rst:28
#: ../../content/administration/upgrade.rst:30
msgid "If the Rolling Release process detects an issue with the upgrade, it will be deactivated until the issue is resolved."
msgstr ""
#: ../../content/administration/upgrade.rst:31
#: ../../content/administration/upgrade.rst:33
msgid "An upgrade does not cover:"
msgstr ""
#: ../../content/administration/upgrade.rst:33
#: ../../content/administration/upgrade.rst:35
msgid "Downgrading to a previous version of Odoo"
msgstr ""
#: ../../content/administration/upgrade.rst:34
#: ../../content/administration/upgrade.rst:36
msgid ":doc:`Switching editions <maintain/enterprise>` (e.g., from Community to Enterprise)"
msgstr ""
#: ../../content/administration/upgrade.rst:35
#: ../../content/administration/upgrade.rst:37
msgid ":doc:`Changing hosting type </administration/maintain/hosting_changes>` (e.g., from on-premise to Odoo Online)"
msgstr ""
#: ../../content/administration/upgrade.rst:37
#: ../../content/administration/upgrade.rst:39
msgid "Migrating from another ERP to Odoo"
msgstr ""
#: ../../content/administration/upgrade.rst:40
#: ../../content/administration/upgrade.rst:42
msgid "If your database contains a **custom module**, you must first upgrade its source code to be compatible with the new version of Odoo **before upgrading**."
msgstr ""
#: ../../content/administration/upgrade.rst:47
#: ../../content/administration/upgrade.rst:49
msgid "Upgrading in a nutshell"
msgstr ""
#: ../../content/administration/upgrade.rst:49
#: ../../content/administration/upgrade.rst:51
msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database <upgrade/request-test-database>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:52
#: ../../content/administration/upgrade.rst:54
msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database <upgrade/test_your_db>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:55
#: ../../content/administration/upgrade.rst:57
msgid "Report any issue encountered during the testing to Odoo via the `support page <https://odoo.com/help?stage=migration>`__."
msgstr ""
#: ../../content/administration/upgrade.rst:58
#: ../../content/administration/upgrade.rst:60
msgid "(If applicable) : upgrade the source code of your custom module to be compatible with the new version of Odoo."
msgstr ""
#: ../../content/administration/upgrade.rst:61
#: ../../content/administration/upgrade.rst:63
msgid "Once all issues are resolved and you are confident that the upgraded database can be used as your main database without any issues, plan the upgrade of your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:64
#: ../../content/administration/upgrade.rst:66
msgid "Request the upgrade for the production database, rendering it unavailable for the time it takes to complete the process (see :ref:`upgrading the production database <upgrade/upgrade-prod>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:67
#: ../../content/administration/upgrade.rst:69
msgid "Report any issue encountered during the upgrade to Odoo via the `support page <https://odoo.com/help?stage=post_upgrade>`__."
msgstr ""
#: ../../content/administration/upgrade.rst:76
#: ../../content/administration/upgrade.rst:78
msgid "Obtaining an upgraded test database"
msgstr ""
#: ../../content/administration/upgrade.rst:78
#: ../../content/administration/upgrade.rst:80
msgid "The `Upgrade page <https://upgrade.odoo.com/>`_ is the main platform for requesting an upgraded database. However, depending on the hosting type, you can upgrade from the command line (on-premise), the `Odoo Online database manager <https://odoo.com/my/databases>`_, or your `Odoo.sh project <https://odoo.sh/project>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:84
#: ../../content/administration/upgrade.rst:86
msgid "The Upgrade platform follows the same `Privacy Policy <https://www.odoo.com/privacy>`_ as the other Odoo.com services. Visit the `General Data Protection Regulation page <https://www.odoo.com/gdpr>`_ to learn more about how Odoo handles your data and privacy."
msgstr ""
#: ../../content/administration/upgrade.rst:92
#: ../../content/administration/upgrade.rst:94
msgid "Odoo Online databases can be manually upgraded via the `database manager <https://odoo.com/my/databases>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:95
#: ../../content/administration/upgrade.rst:97
msgid "The database manager displays all databases associated with the user's account. Databases not on the most recent version of Odoo display an arrow in a circle icon next to their name, indicating that they can be upgraded."
msgstr ""
@ -6074,19 +6074,19 @@ msgstr ""
msgid "The database manager with an upgrade button next to the name of a database."
msgstr ""
#: ../../content/administration/upgrade.rst:102
#: ../../content/administration/upgrade.rst:104
msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:"
msgstr ""
#: ../../content/administration/upgrade.rst:104
#: ../../content/administration/upgrade.rst:106
msgid "The **version** of Odoo you want to upgrade to, usually the latest version"
msgstr ""
#: ../../content/administration/upgrade.rst:105
#: ../../content/administration/upgrade.rst:107
msgid "The **email** address that should receive the link to the upgraded database"
msgstr ""
#: ../../content/administration/upgrade.rst:106
#: ../../content/administration/upgrade.rst:108
msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request"
msgstr ""
@ -6094,7 +6094,7 @@ msgstr ""
msgid "The \"Upgrade your database\" popup."
msgstr ""
#: ../../content/administration/upgrade.rst:112
#: ../../content/administration/upgrade.rst:114
msgid "The :guilabel:`Upgrade in progress` tag is displayed next to the database name until completion. Once the process succeeds, an email containing a link to the upgraded test database is sent to the address provided. The database can also be accessed from the database manager by clicking the dropdown arrow before the database name."
msgstr ""
@ -6102,7 +6102,7 @@ msgstr ""
msgid "Clicking the menu arrow displays the upgraded test database."
msgstr ""
#: ../../content/administration/upgrade.rst:122
#: ../../content/administration/upgrade.rst:124
msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process."
msgstr ""
@ -6110,268 +6110,272 @@ msgstr ""
msgid "Odoo.sh project and tabs"
msgstr ""
#: ../../content/administration/upgrade.rst:127
#: ../../content/administration/upgrade.rst:129
msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform <https://upgrade.odoo.com>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:130
#: ../../content/administration/upgrade.rst:132
msgid "Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is put in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup and an **update of all the custom modules** occur. This allows you to test your custom modules on a pristine copy of the upgraded database. The log file of the upgrade process can be found in your newly upgraded staging build by going to :file:`~/logs/upgrade.log`."
msgstr ""
#: ../../content/administration/upgrade.rst:138
#: ../../content/administration/upgrade.rst:140
msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. If there are none, the \"update on commit\" mode is skipped, the upgraded database is built as soon as it is transferred from the upgrade platform, and the upgrade mode is exited."
msgstr ""
#: ../../content/administration/upgrade.rst:150
#: ../../content/administration/upgrade.rst:340
#: ../../content/administration/upgrade.rst:152
#: ../../content/administration/upgrade.rst:344
msgid "On-premise"
msgstr ""
#: ../../content/administration/upgrade.rst:152
#: ../../content/administration/upgrade.rst:154
msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:"
msgstr ""
#: ../../content/administration/upgrade.rst:159
#: ../../content/administration/upgrade.rst:161
msgid "The following command can be used to display the general help and the main commands:"
msgstr ""
#: ../../content/administration/upgrade.rst:165
#: ../../content/administration/upgrade.rst:167
msgid "An upgraded test database can also be requested via the `Upgrade page <https://upgrade.odoo.com/>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:169
#: ../../content/administration/upgrade.rst:171
msgid "For security reasons, only the person who submitted the upgrade request can download it."
msgstr ""
#: ../../content/administration/upgrade.rst:170
#: ../../content/administration/upgrade.rst:172
msgid "For storage reasons, the database's copy is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore."
msgstr ""
#: ../../content/administration/upgrade.rst:172
#: ../../content/administration/upgrade.rst:174
msgid "Before restoring the upgraded database, its filestore must be merged with the production filestore to be able to perform tests in the same conditions as it would be in the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:175
#: ../../content/administration/upgrade.rst:177
msgid "The upgraded database contains:"
msgstr ""
#: ../../content/administration/upgrade.rst:177
#: ../../content/administration/upgrade.rst:179
msgid "A `dump.sql` file containing the upgraded database"
msgstr ""
#: ../../content/administration/upgrade.rst:178
#: ../../content/administration/upgrade.rst:180
msgid "A `filestore` folder containing files extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (e.g., new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore."
msgstr ""
#: ../../content/administration/upgrade.rst:185
#: ../../content/administration/upgrade.rst:187
msgid "You can request multiple test databases if you wish to test an upgrade more than once."
msgstr ""
#: ../../content/administration/upgrade.rst:190
#: ../../content/administration/upgrade.rst:192
msgid "When an upgrade request is completed, an upgrade report is attached to the successful upgrade email, and it becomes available in the Discuss app for users who are part of the \"Administration / Settings\" group. This report provides important information about the changes introduced by the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:198
#: ../../content/administration/upgrade.rst:200
msgid "Testing the new version of the database"
msgstr ""
#: ../../content/administration/upgrade.rst:200
#: ../../content/administration/upgrade.rst:202
msgid "It is essential to spend some time testing the upgraded test database to ensure that you are not stuck in your day-to-day activities by a change in views, behavior, or an error message once the upgrade goes live."
msgstr ""
#: ../../content/administration/upgrade.rst:205
#: ../../content/administration/upgrade.rst:207
msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:"
msgstr ""
#: ../../content/administration/upgrade.rst:208
#: ../../content/administration/upgrade.rst:210
msgid "Scheduled actions are disabled."
msgstr ""
#: ../../content/administration/upgrade.rst:209
#: ../../content/administration/upgrade.rst:211
msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one."
msgstr ""
#: ../../content/administration/upgrade.rst:210
#: ../../content/administration/upgrade.rst:212
msgid "Payment providers and delivery carriers are reset to the test environment."
msgstr ""
#: ../../content/administration/upgrade.rst:212
#: ../../content/administration/upgrade.rst:213
msgid "Bank synchronization is disabled. Should you want to test the synchronization, contact your bank synchronization provider to get sandbox credentials."
msgstr ""
#: ../../content/administration/upgrade.rst:216
msgid "Testing as many of your business flows as possible is strongly recommended to ensure they are working correctly and to get more familiar with the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:215
#: ../../content/administration/upgrade.rst:219
msgid "Basic test checklist"
msgstr ""
#: ../../content/administration/upgrade.rst:217
#: ../../content/administration/upgrade.rst:221
msgid "Are there views that are deactivated in your test database but active in your production database?"
msgstr ""
#: ../../content/administration/upgrade.rst:219
#: ../../content/administration/upgrade.rst:223
msgid "Are your usual views still displayed correctly?"
msgstr ""
#: ../../content/administration/upgrade.rst:220
#: ../../content/administration/upgrade.rst:224
msgid "Are your reports (invoice, sales order, etc.) correctly generated?"
msgstr ""
#: ../../content/administration/upgrade.rst:221
#: ../../content/administration/upgrade.rst:225
msgid "Are your website pages working correctly?"
msgstr ""
#: ../../content/administration/upgrade.rst:222
#: ../../content/administration/upgrade.rst:226
msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:224
#: ../../content/administration/upgrade.rst:228
msgid "Are there any issues with your mail templates?"
msgstr ""
#: ../../content/administration/upgrade.rst:225
#: ../../content/administration/upgrade.rst:229
msgid "Are there any issues with saved translations?"
msgstr ""
#: ../../content/administration/upgrade.rst:226
#: ../../content/administration/upgrade.rst:230
msgid "Are your search filters still present?"
msgstr ""
#: ../../content/administration/upgrade.rst:227
#: ../../content/administration/upgrade.rst:231
msgid "Can you export your data?"
msgstr ""
#: ../../content/administration/upgrade.rst:231
#: ../../content/administration/upgrade.rst:235
msgid "Checking a random product in your product catalog and comparing its test and production data to verify everything is the same (product category, selling price, cost price, vendor, accounts, routes, etc.)."
msgstr ""
#: ../../content/administration/upgrade.rst:234
#: ../../content/administration/upgrade.rst:238
msgid "Buying this product (Purchase app)."
msgstr ""
#: ../../content/administration/upgrade.rst:235
#: ../../content/administration/upgrade.rst:239
msgid "Confirming the reception of this product (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:236
#: ../../content/administration/upgrade.rst:240
msgid "Checking if the route to receive this product is the same in your production database (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:238
#: ../../content/administration/upgrade.rst:242
msgid "Selling this product (Sales app) to a random customer."
msgstr ""
#: ../../content/administration/upgrade.rst:239
#: ../../content/administration/upgrade.rst:243
msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data."
msgstr ""
#: ../../content/administration/upgrade.rst:241
#: ../../content/administration/upgrade.rst:245
msgid "Shipping this product (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:242
#: ../../content/administration/upgrade.rst:246
msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:244
#: ../../content/administration/upgrade.rst:248
msgid "Validating a customer invoice (Invoicing or Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:245
#: ../../content/administration/upgrade.rst:249
msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:247
#: ../../content/administration/upgrade.rst:251
msgid "Checking your reports' results (Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:248
#: ../../content/administration/upgrade.rst:252
msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:249
#: ../../content/administration/upgrade.rst:253
msgid "Making an online order (Website apps) from the product selection in your shop until the checkout process and checking if everything behaves as in your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:252
#: ../../content/administration/upgrade.rst:256
msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo."
msgstr ""
#: ../../content/administration/upgrade.rst:254
#: ../../content/administration/upgrade.rst:258
msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo via the `support page <https://odoo.com/help?stage=migration>`__ by selecting the option related to testing the upgrade. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:259
#: ../../content/administration/upgrade.rst:263
msgid "You might encounter significant differences with standard views, features, fields, and models during testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced by a new version breaks a customization, it is the responsibility of the maintainer of your custom module to make it compatible with the new version of Odoo."
msgstr ""
#: ../../content/administration/upgrade.rst:265
#: ../../content/administration/upgrade.rst:269
msgid "Do not forget to test:"
msgstr ""
#: ../../content/administration/upgrade.rst:267
#: ../../content/administration/upgrade.rst:271
msgid "Integrations with external software (EDI, APIs, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:268
#: ../../content/administration/upgrade.rst:272
msgid "Workflows between different apps (online sales with eCommerce, converting a lead all the way to a sales order, delivery of products, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:270
#: ../../content/administration/upgrade.rst:274
msgid "Data exports"
msgstr ""
#: ../../content/administration/upgrade.rst:271
#: ../../content/administration/upgrade.rst:275
msgid "Automated actions"
msgstr ""
#: ../../content/administration/upgrade.rst:272
#: ../../content/administration/upgrade.rst:276
msgid "Server actions in the action menu on form views, as well as by selecting multiple records on list views"
msgstr ""
#: ../../content/administration/upgrade.rst:278
#: ../../content/administration/upgrade.rst:282
msgid "Upgrading the production database"
msgstr ""
#: ../../content/administration/upgrade.rst:280
#: ../../content/administration/upgrade.rst:284
msgid "Once the :ref:`tests <upgrade/test_your_db>` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day. It can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page <https://odoo.com/help>`__."
msgstr ""
#: ../../content/administration/upgrade.rst:285
#: ../../content/administration/upgrade.rst:289
msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal."
msgstr ""
#: ../../content/administration/upgrade.rst:288
#: ../../content/administration/upgrade.rst:292
msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. Fully rehearsing the upgrade process the day before upgrading the production database is also recommended."
msgstr ""
#: ../../content/administration/upgrade.rst:294
#: ../../content/administration/upgrade.rst:298
msgid "Going into production without first testing may lead to:"
msgstr ""
#: ../../content/administration/upgrade.rst:296
#: ../../content/administration/upgrade.rst:300
msgid "Users failing to adjust to the changes and new features"
msgstr ""
#: ../../content/administration/upgrade.rst:297
#: ../../content/administration/upgrade.rst:301
msgid "Business interruptions (e.g., no longer having the possibility to validate an action)"
msgstr ""
#: ../../content/administration/upgrade.rst:298
#: ../../content/administration/upgrade.rst:302
msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)"
msgstr ""
#: ../../content/administration/upgrade.rst:300
#: ../../content/administration/upgrade.rst:304
msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions."
msgstr ""
#: ../../content/administration/upgrade.rst:307
#: ../../content/administration/upgrade.rst:311
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>`, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`."
msgstr ""
#: ../../content/administration/upgrade.rst:312
#: ../../content/administration/upgrade.rst:316
msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version."
msgstr ""
#: ../../content/administration/upgrade.rst:318
#: ../../content/administration/upgrade.rst:322
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>` on the :guilabel:`Production` branch."
msgstr ""
@ -6379,98 +6383,98 @@ msgstr ""
msgid "View from the upgrade tab"
msgstr ""
#: ../../content/administration/upgrade.rst:324
#: ../../content/administration/upgrade.rst:328
msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately."
msgstr ""
#: ../../content/administration/upgrade.rst:330
#: ../../content/administration/upgrade.rst:334
msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created."
msgstr ""
#: ../../content/administration/upgrade.rst:334
#: ../../content/administration/upgrade.rst:338
msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production."
msgstr ""
#: ../../content/administration/upgrade.rst:342
#: ../../content/administration/upgrade.rst:346
msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:"
msgstr ""
#: ../../content/administration/upgrade.rst:349
#: ../../content/administration/upgrade.rst:353
msgid "An upgraded production database can also be requested via the `Upgrade page <https://upgrade.odoo.com/>`_. Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process."
msgstr ""
#: ../../content/administration/upgrade.rst:356
#: ../../content/administration/upgrade.rst:360
msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:360
#: ../../content/administration/upgrade.rst:364
msgid "In case of an issue with your production database, you can request the assistance of Odoo via the `support page <https://odoo.com/help?stage=post_upgrade>`__ by selecting the option related to the upgrade in production."
msgstr ""
#: ../../content/administration/upgrade.rst:368
#: ../../content/administration/upgrade.rst:372
msgid "Service-level agreement (SLA)"
msgstr ""
#: ../../content/administration/upgrade.rst:370
#: ../../content/administration/upgrade.rst:374
msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database."
msgstr ""
#: ../../content/administration/upgrade.rst:373
#: ../../content/administration/upgrade.rst:377
msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement <upgrade>`. However, this section clarifies what upgrade services you can expect."
msgstr ""
#: ../../content/administration/upgrade.rst:378
#: ../../content/administration/upgrade.rst:382
msgid "Upgrade services covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:380
#: ../../content/administration/upgrade.rst:384
msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:"
msgstr ""
#: ../../content/administration/upgrade.rst:383
#: ../../content/administration/upgrade.rst:387
msgid "the upgrade of all **standard applications**;"
msgstr ""
#: ../../content/administration/upgrade.rst:384
#: ../../content/administration/upgrade.rst:388
msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and"
msgstr ""
#: ../../content/administration/upgrade.rst:386
#: ../../content/administration/upgrade.rst:390
msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**."
msgstr ""
#: ../../content/administration/upgrade.rst:389
#: ../../content/administration/upgrade.rst:393
msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade."
msgstr ""
#: ../../content/administration/upgrade.rst:393
#: ../../content/administration/upgrade.rst:397
msgid "Upgrade services not covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:395
#: ../../content/administration/upgrade.rst:399
msgid "The following upgrade-related services are **not** included:"
msgstr ""
#: ../../content/administration/upgrade.rst:397
#: ../../content/administration/upgrade.rst:401
msgid "the **cleaning** of pre-existing data and configurations while upgrading;"
msgstr ""
#: ../../content/administration/upgrade.rst:398
#: ../../content/administration/upgrade.rst:402
msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;"
msgstr ""
#: ../../content/administration/upgrade.rst:399
#: ../../content/administration/upgrade.rst:403
msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code <studio/automated-actions/action>`; and"
msgstr ""
#: ../../content/administration/upgrade.rst:402
#: ../../content/administration/upgrade.rst:406
msgid "**training** on using the upgraded version's features and workflows."
msgstr ""
#: ../../content/administration/upgrade.rst:405
#: ../../content/administration/upgrade.rst:409
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
msgstr ""
#: ../../content/administration/upgrade.rst:406
#: ../../content/administration/upgrade.rst:410
msgid ":doc:`Supported Odoo versions <maintain/supported_versions>`"
msgstr ""

4
locale/sources/contributing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-08 08:46+0000\n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -2392,7 +2392,7 @@ msgid "Alert blocks (admonitions)"
msgstr ""
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:470
msgid "Seealso"
msgid "See also"
msgstr ""
#: ../../content/contributing/documentation/rst_cheat_sheet.rst:476

6038
locale/sources/developer.pot
View File

File diff suppressed because it is too large Load Diff

2357
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

74
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-08 08:46+0000\n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -2753,7 +2753,7 @@ msgid "Reporting"
msgstr ""
#: ../../content/applications/general/reporting.rst:5
msgid "You can find under the :guilabel:`Reporting` menu of most apps several reports that let you analyze and visualize your records' data."
msgid "You can find several reports under the :guilabel:`Reporting` menu of most apps that let you analyze and visualize the data of your records."
msgstr ""
#: ../../content/applications/general/reporting.rst:11
@ -2776,11 +2776,11 @@ msgstr ""
msgid "Selecting the graph view"
msgstr ""
#: ../../content/applications/general/reporting.rst:34
#: ../../content/applications/general/reporting.rst:33
msgid "Pivot view"
msgstr ""
#: ../../content/applications/general/reporting.rst:36
#: ../../content/applications/general/reporting.rst:35
msgid "The :ref:`pivot view <reporting/using-pivot>` is used to aggregate your records' data and break it down for analysis. The view is often found under the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the **pivot view button** located at the top right to access it."
msgstr ""
@ -2788,23 +2788,23 @@ msgstr ""
msgid "Selecting the pivot view"
msgstr ""
#: ../../content/applications/general/reporting.rst:47
#: ../../content/applications/general/reporting.rst:45
msgid "Choosing measures"
msgstr ""
#: ../../content/applications/general/reporting.rst:49
#: ../../content/applications/general/reporting.rst:47
msgid "After selecting a view, you should ensure only the relevant records are :doc:`filtered <search>`. Next, you should choose what is measured. By default, a measure is always selected. If you wish to edit it, click :guilabel:`Measures` and choose one or, only for pivots, multiple measures."
msgstr ""
#: ../../content/applications/general/reporting.rst:54
#: ../../content/applications/general/reporting.rst:52
msgid "When you select a measure, Odoo aggregates the values recorded on that field for the filtered records. Only numerical fields (:ref:`integer <studio/fields/simple-fields/integer>`, :ref:`decimal <studio/fields/simple-fields/decimal>`, :ref:`monetary <studio/fields/simple-fields/monetary>`) can be measured. In addition, the :guilabel:`Count` option is used to count the total number of filtered records."
msgstr ""
#: ../../content/applications/general/reporting.rst:60
#: ../../content/applications/general/reporting.rst:58
msgid "After choosing what you want to measure, you can define how the data should be :ref:`grouped <search/group>` depending on the dimension you want to analyze. By default, the data is often grouped by *Date > Month*, which is used to analyze the evolution of a measure over the months."
msgstr ""
#: ../../content/applications/general/reporting.rst:65
#: ../../content/applications/general/reporting.rst:63
msgid "When you filter a single time period, the option to compare it against another one appears."
msgstr ""
@ -2812,11 +2812,11 @@ msgstr ""
msgid "Using the comparison option"
msgstr ""
#: ../../content/applications/general/reporting.rst:75
#: ../../content/applications/general/reporting.rst:72
msgid "Select measures"
msgstr ""
#: ../../content/applications/general/reporting.rst:77
#: ../../content/applications/general/reporting.rst:74
msgid "Among other measures, you could add the :guilabel:`Margin` and :guilabel:`Count` measures to the Sales Analysis report. By default, the :guilabel:`Untaxed Amount` measure is selected."
msgstr ""
@ -2824,11 +2824,11 @@ msgstr ""
msgid "Selecting different measures on the Sales Analysis report"
msgstr ""
#: ../../content/applications/general/reporting.rst:85
#: ../../content/applications/general/reporting.rst:81
msgid "Group measures"
msgstr ""
#: ../../content/applications/general/reporting.rst:87
#: ../../content/applications/general/reporting.rst:83
msgid "You could group the measures by :guilabel:`Product Category` at the level of rows on the previous Sales Analysis report example."
msgstr ""
@ -2836,19 +2836,19 @@ msgstr ""
msgid "Adding a group on the Sales Analysis report"
msgstr ""
#: ../../content/applications/general/reporting.rst:97
#: ../../content/applications/general/reporting.rst:92
msgid "Using the pivot view"
msgstr ""
#: ../../content/applications/general/reporting.rst:99
#: ../../content/applications/general/reporting.rst:94
msgid "Grouping data is quintessential to the pivot view. It enables drilling down the data to gain deeper insights. While you can use the :guilabel:`Group By` option to quickly add a group at the level of rows, as shown in the example above, you can also click the plus button (:guilabel:`➕`) next to the :guilabel:`Total` header at the level of rows *and* columns, and then select one of the **preconfigured groups**. To remove one, click the minus button (:guilabel:`➖`)."
msgstr ""
#: ../../content/applications/general/reporting.rst:105
#: ../../content/applications/general/reporting.rst:100
msgid "Once you have added a group, you can add new ones on the opposite axis or the newly created subgroups."
msgstr ""
#: ../../content/applications/general/reporting.rst:109
#: ../../content/applications/general/reporting.rst:104
msgid "You could further divide the measures on the previous Sales Analysis report example by the :guilabel:`Salesperson` group at the level of columns and by the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / Office Furniture` product category."
msgstr ""
@ -2856,39 +2856,39 @@ msgstr ""
msgid "Adding multiple groups on the Sales Analysis report"
msgstr ""
#: ../../content/applications/general/reporting.rst:118
#: ../../content/applications/general/reporting.rst:112
msgid "Switch the rows and columns' groups by clicking the flip axis button (:guilabel:`⇄`)."
msgstr ""
#: ../../content/applications/general/reporting.rst:119
#: ../../content/applications/general/reporting.rst:113
msgid "Click on a measure's label to sort the values by ascending (⏶) or descending (⏷) order."
msgstr ""
#: ../../content/applications/general/reporting.rst:120
#: ../../content/applications/general/reporting.rst:114
msgid "Download a `.xlsx` version of the pivot by clicking the download button (:guilabel:`⭳`)."
msgstr ""
#: ../../content/applications/general/reporting.rst:125
#: ../../content/applications/general/reporting.rst:119
msgid "Using the graph view"
msgstr ""
#: ../../content/applications/general/reporting.rst:127
msgid "Three graphs are available, the bar, line, and pie charts."
#: ../../content/applications/general/reporting.rst:121
msgid "Three graphs are available: the bar, line, and pie charts."
msgstr ""
#: ../../content/applications/general/reporting.rst:129
#: ../../content/applications/general/reporting.rst:123
msgid "**Bar charts** are used to show the distribution or a comparison of several categories. They are especially useful as they can deal with larger data sets."
msgstr ""
#: ../../content/applications/general/reporting.rst:132
#: ../../content/applications/general/reporting.rst:126
msgid "**Line charts** are useful to show changing time series and trends over time."
msgstr ""
#: ../../content/applications/general/reporting.rst:134
#: ../../content/applications/general/reporting.rst:128
msgid "**Pie charts** are used to show the distribution or a comparison of a small number of categories when they form a meaningful whole."
msgstr ""
#: ../../content/applications/general/reporting.rst:139
#: ../../content/applications/general/reporting.rst:133
msgid "Bar chart"
msgstr ""
@ -2896,7 +2896,7 @@ msgstr ""
msgid "Viewing the Sales Analysis report as a bar chart"
msgstr ""
#: ../../content/applications/general/reporting.rst:145
#: ../../content/applications/general/reporting.rst:138
msgid "Line chart"
msgstr ""
@ -2904,7 +2904,7 @@ msgstr ""
msgid "Viewing the Sales Analysis report as a line chart"
msgstr ""
#: ../../content/applications/general/reporting.rst:151
#: ../../content/applications/general/reporting.rst:143
msgid "Pie chart"
msgstr ""
@ -2912,11 +2912,11 @@ msgstr ""
msgid "Viewing the Sales Analysis report as a pie chart"
msgstr ""
#: ../../content/applications/general/reporting.rst:158
#: ../../content/applications/general/reporting.rst:149
msgid "For **bar** and **line** charts, you can use the stacked option when you have at least two groups, which then appear on top of each other instead of next to each other."
msgstr ""
#: ../../content/applications/general/reporting.rst:163
#: ../../content/applications/general/reporting.rst:154
msgid "Stacked bar chart"
msgstr ""
@ -2924,7 +2924,7 @@ msgstr ""
msgid "Stacked bar chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:169
#: ../../content/applications/general/reporting.rst:159
msgid "Regular bar chart"
msgstr ""
@ -2932,7 +2932,7 @@ msgstr ""
msgid "Non-stacked bar chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:175
#: ../../content/applications/general/reporting.rst:164
msgid "Stacked line chart"
msgstr ""
@ -2940,8 +2940,8 @@ msgstr ""
msgid "Stacked line chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:181
#: ../../content/applications/general/reporting.rst:198
#: ../../content/applications/general/reporting.rst:169
#: ../../content/applications/general/reporting.rst:184
msgid "Regular line chart"
msgstr ""
@ -2949,11 +2949,11 @@ msgstr ""
msgid "Non-stacked line chart example"
msgstr ""
#: ../../content/applications/general/reporting.rst:187
#: ../../content/applications/general/reporting.rst:174
msgid "For **line** charts, you can use the cumulative option to sum values, which is especially useful to show the change in growth over a time period."
msgstr ""
#: ../../content/applications/general/reporting.rst:192
#: ../../content/applications/general/reporting.rst:179
msgid "Cumulative line chart"
msgstr ""

172
locale/sources/hr.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-08 08:46+0000\n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -471,27 +471,27 @@ msgstr ""
msgid "All uploaded documents associated with the employee appear in the documents smart-button."
msgstr ""
#: ../../content/applications/hr/payroll.rst:3
#: ../../content/applications/hr/payroll.rst:5
msgid "Payroll"
msgstr ""
#: ../../content/applications/hr/payroll.rst:5
#: ../../content/applications/hr/payroll.rst:7
msgid "Odoo *Payroll* is used to process work entries and create payslips for employees, including both regular pay and commission. Payroll works in conjunction with other Odoo apps, such as *Employees*, *Timesheets*, *Time Off*, and *Attendances*."
msgstr ""
#: ../../content/applications/hr/payroll.rst:9
#: ../../content/applications/hr/payroll.rst:11
msgid "The *Payroll* app helps ensure there are no issues or conflicts when validating work entries, handles country-specific localizations to ensure that payslips follow local rules and taxes, and allows for salary assignments. Payroll configuration is critical to ensure accurate and timely processing of payslips."
msgstr ""
#: ../../content/applications/hr/payroll.rst:15
#: ../../content/applications/hr/payroll.rst:17
msgid "Settings"
msgstr ""
#: ../../content/applications/hr/payroll.rst:17
#: ../../content/applications/hr/payroll.rst:19
msgid "To access the *Settings*, go to :menuselection:`Payroll --> Configuration --> Settings`. Whether or not payslips are posted in accounting, and whether SEPA payments are created, is selected here."
msgstr ""
#: ../../content/applications/hr/payroll.rst:20
#: ../../content/applications/hr/payroll.rst:22
msgid "The :guilabel:`Settings` screen is where localization settings are configured. *Localizations* are country-specific settings pre-configured in Odoo at the creation of the database, and account for all taxes, fees, and allowances for that particular country. The :guilabel:`Localization` section of the :guilabel:`Settings` includes a detailed view of all benefits provided to employees."
msgstr ""
@ -499,36 +499,36 @@ msgstr ""
msgid "Settings available for Payroll."
msgstr ""
#: ../../content/applications/hr/payroll.rst:29
#: ../../content/applications/hr/payroll.rst:31
msgid "Any country-specific localizations are set up in the :guilabel:`Localization` section of the :guilabel:`Settings` screen. All localization items are pre-populated when the country is specified during the creation of the database. It is not recommended to alter the localization settings unless specifically required."
msgstr ""
#: ../../content/applications/hr/payroll.rst:37
#: ../../content/applications/hr/payroll.rst:39
#: ../../content/applications/hr/payroll/work_entries.rst:3
msgid "Work entries"
msgstr ""
#: ../../content/applications/hr/payroll.rst:39
#: ../../content/applications/hr/payroll.rst:41
msgid "A *work entry* is an individual record on an employee's timesheet. Work entries can be configured to account for all types of work and time off, such as :guilabel:`Attendance`, :guilabel:`Sick Time Off`, :guilabel:`Training`, or :guilabel:`Public Holiday`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:44
#: ../../content/applications/hr/payroll.rst:46
msgid ":doc:`Manage work entries <payroll/work_entries>`"
msgstr ""
#: ../../content/applications/hr/payroll.rst:47
#: ../../content/applications/hr/payroll.rst:49
msgid "Work entry types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:49
#: ../../content/applications/hr/payroll.rst:51
msgid "When creating a work entry in the *Payroll* application, or when an employee enters information in the *Timesheets* application, a :guilabel:`Work Entry Type` needs to be selected. The list of :guilabel:`Work Entry Types` is automatically created based on localization settings set in the database."
msgstr ""
#: ../../content/applications/hr/payroll.rst:54
#: ../../content/applications/hr/payroll.rst:56
msgid "To view the current work entry types available, go to :menuselection:`Payroll --> Configuration --> Work Entry Types`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:57
#: ../../content/applications/hr/payroll.rst:59
msgid "Each work entry type has a code to aid in the creation of payslips, and ensure all taxes and fees are correctly entered."
msgstr ""
@ -536,27 +536,27 @@ msgstr ""
msgid "List of all work entry types currently available."
msgstr ""
#: ../../content/applications/hr/payroll.rst:65
#: ../../content/applications/hr/payroll.rst:67
msgid "New work entry type"
msgstr ""
#: ../../content/applications/hr/payroll.rst:67
#: ../../content/applications/hr/payroll.rst:69
msgid "To create a new work entry type, click the :guilabel:`Create` button. Enter the information on the form:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:70
#: ../../content/applications/hr/payroll.rst:72
msgid ":guilabel:`Work Entry Type Name`: The name should be short and descriptive, such as `Sick Time` or `Public Holiday`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:72
#: ../../content/applications/hr/payroll.rst:74
msgid ":guilabel:`Code`: This code appears with the work entry type on timesheets and payslips. Since the code is used in conjunction with the *Accounting* application, it is advised to check with the accounting department for a code to use."
msgstr ""
#: ../../content/applications/hr/payroll.rst:75
#: ../../content/applications/hr/payroll.rst:77
msgid ":guilabel:`Sequence`: The sequence determines the order that the work entry is computed in the payslip list."
msgstr ""
#: ../../content/applications/hr/payroll.rst:77
#: ../../content/applications/hr/payroll.rst:79
msgid "Check boxes: If any of the items in the list applies to the work entry, check off the box by clicking it. If :guilabel:`Time Off` is checked off, a :guilabel:`Time Off Type` field appears. This field has a drop-down menu to select the specific type of time off, or a new type of time off can be entered."
msgstr ""
@ -564,35 +564,35 @@ msgstr ""
msgid "New work entry type form."
msgstr ""
#: ../../content/applications/hr/payroll.rst:86
#: ../../content/applications/hr/payroll.rst:88
msgid ":guilabel:`Rounding`: The rounding method determines how timesheet entries are displayed on the payslip."
msgstr ""
#: ../../content/applications/hr/payroll.rst:89
#: ../../content/applications/hr/payroll.rst:91
msgid ":guilabel:`No Rounding`: A timesheet entry is not modified."
msgstr ""
#: ../../content/applications/hr/payroll.rst:90
#: ../../content/applications/hr/payroll.rst:92
msgid ":guilabel:`Half Day`: A timesheet entry is rounded to the closest half day amount."
msgstr ""
#: ../../content/applications/hr/payroll.rst:91
#: ../../content/applications/hr/payroll.rst:93
msgid ":guilabel:`Day`: A timesheet entry is rounded to the closest full day amount."
msgstr ""
#: ../../content/applications/hr/payroll.rst:94
#: ../../content/applications/hr/payroll.rst:96
msgid "If the working time is set to an 8-hour work day (40-hour work week), and an employee enters a time of 5.5 hours on a timesheet, and :guilabel:`Rounding` is set to :guilabel:`No Rounding`, the entry remains 5.5 hours. If :guilabel:`Rounding` is set to :guilabel:`Half Day`, the entry is changed to 4 hours. If it is set to :guilabel:`Day`, it is changed to 8 hours."
msgstr ""
#: ../../content/applications/hr/payroll.rst:100
#: ../../content/applications/hr/payroll.rst:102
msgid "Working times"
msgstr ""
#: ../../content/applications/hr/payroll.rst:102
#: ../../content/applications/hr/payroll.rst:104
msgid "To view the currently configured working times, go to :menuselection:`Payroll --> Configuration --> Working Times`. The working times that are available for an employee's contracts and work entries are found in this list."
msgstr ""
#: ../../content/applications/hr/payroll.rst:106
#: ../../content/applications/hr/payroll.rst:108
msgid "Working times are company-specific. Each company must identify each type of working time they use. For example, an Odoo database containing multiple companies that use a standard 40-hour work week needs to have a separate working time entry for each company that uses the 40-hour standard work week."
msgstr ""
@ -600,11 +600,11 @@ msgstr ""
msgid "All working times currently set up in the database."
msgstr ""
#: ../../content/applications/hr/payroll.rst:116
#: ../../content/applications/hr/payroll.rst:118
msgid "New working time"
msgstr ""
#: ../../content/applications/hr/payroll.rst:118
#: ../../content/applications/hr/payroll.rst:120
msgid "To create a new working time, click the :guilabel:`Create` button. Enter the information on the form."
msgstr ""
@ -612,43 +612,43 @@ msgstr ""
msgid "New working type form."
msgstr ""
#: ../../content/applications/hr/payroll.rst:125
#: ../../content/applications/hr/payroll.rst:127
msgid "The fields are auto-populated for a regular 40-hour work week but can be modified. First, change the name of the working time by modifying the text in the :guilabel:`Name` field. Next, make any adjustments to the days and times that apply to the new working time."
msgstr ""
#: ../../content/applications/hr/payroll.rst:129
#: ../../content/applications/hr/payroll.rst:131
msgid "In the :guilabel:`Working Hours` tab, modify the :guilabel:`Day of Week`, :guilabel:`Day Period`, and :guilabel:`Work Entry Type` selections by clicking on the drop-down menus in each column and making the desired selection. The :guilabel:`Work From` and :guilabel:`Work To` columns are modified by typing in the time."
msgstr ""
#: ../../content/applications/hr/payroll.rst:135
#: ../../content/applications/hr/payroll.rst:137
msgid "The :guilabel:`Work From` and :guilabel:`Work To` times must be in a 24-hour format. For example, `2:00 PM` would be entered as `14:00`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:138
#: ../../content/applications/hr/payroll.rst:140
msgid "If the working time should be in a two-week configuration, click the :guilabel:`Switch To 2 Week Calendar` button. This creates entries for an :guilabel:`Even week` and an :guilabel:`Odd week`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:142
#: ../../content/applications/hr/payroll.rst:144
msgid "Salary"
msgstr ""
#: ../../content/applications/hr/payroll.rst:147
#: ../../content/applications/hr/payroll.rst:149
msgid "Structure types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:149
#: ../../content/applications/hr/payroll.rst:151
msgid "In Odoo, an employee's payslip is based on *structures* and *structure types*, which both affect how an employee enters timesheets. Each structure type is an individual set of rules for processing a timesheet entry, which consists of different structures nested within it. Structure types define how often an employee gets paid, the working hours, and if wages are based on a salary (fixed) or how many hours the employee worked (varied)."
msgstr ""
#: ../../content/applications/hr/payroll.rst:155
#: ../../content/applications/hr/payroll.rst:157
msgid "For example, a structure type could be `Employee`, and that structure type could have two different structures in it: a `Regular Pay` structure which includes all the separate rules for processing regular pay, as well as a structure for an `End of Year Bonus` which includes the rules only for the end of year bonus. Both the `Regular Pay` structure and `End of Year Bonus` structure are structures within the `Employee` structure type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:161
#: ../../content/applications/hr/payroll.rst:163
msgid "The different structure types can be seen by going to :menuselection:`Payroll --> Configuration --> Structure Types`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:164
#: ../../content/applications/hr/payroll.rst:166
msgid "There are two default structure types configured in Odoo: *Employee* and *Worker*. Typically, *Employee* is used for salaried employees, which is why the wage type is *Monthly Fixed Wage*, and *Worker* is typically used for employees paid by the hour, so the wage type is *Hourly Wage*."
msgstr ""
@ -656,7 +656,7 @@ msgstr ""
msgid "List of all structure types."
msgstr ""
#: ../../content/applications/hr/payroll.rst:172
#: ../../content/applications/hr/payroll.rst:174
msgid "Click the :guilabel:`Create` button to make a new structure type. Most fields are pre-populated, but all fields can be edited. Once the fields are edited, click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry."
msgstr ""
@ -664,19 +664,19 @@ msgstr ""
msgid "New structure type box."
msgstr ""
#: ../../content/applications/hr/payroll.rst:181
#: ../../content/applications/hr/payroll.rst:183
msgid "Structures"
msgstr ""
#: ../../content/applications/hr/payroll.rst:183
#: ../../content/applications/hr/payroll.rst:185
msgid "*Salary structures* are the different ways an employee gets paid within a specific *structure*, and are specifically defined by various rules."
msgstr ""
#: ../../content/applications/hr/payroll.rst:186
#: ../../content/applications/hr/payroll.rst:188
msgid "The amount of structures a company needs for each structure type depends on how many different ways employees are paid, and how their pay is calculated. For example, a common structure that could be useful to add may be a `Bonus`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:190
#: ../../content/applications/hr/payroll.rst:192
msgid "To view all the various structures for each structure type, go to :menuselection:`Payroll --> Configuration --> Structures`."
msgstr ""
@ -684,11 +684,11 @@ msgstr ""
msgid "All available salary structures."
msgstr ""
#: ../../content/applications/hr/payroll.rst:197
#: ../../content/applications/hr/payroll.rst:199
msgid "Each :ref:`structure type <payroll/structure-types>` lists the various structures associated with it. Each structure contains a set of rules that define it."
msgstr ""
#: ../../content/applications/hr/payroll.rst:200
#: ../../content/applications/hr/payroll.rst:202
msgid "Click on a structure to view its :guilabel:`Salary Rules`. These rules are what calculate the payslip for the employee."
msgstr ""
@ -696,15 +696,15 @@ msgstr ""
msgid "Salary structure details for Regular Pay."
msgstr ""
#: ../../content/applications/hr/payroll.rst:208
#: ../../content/applications/hr/payroll.rst:210
msgid "Rules"
msgstr ""
#: ../../content/applications/hr/payroll.rst:210
#: ../../content/applications/hr/payroll.rst:212
msgid "Each structure has a set of *salary rules* to follow for accounting purposes. These rules are configured by the localization, and affect the *Accounting* application, so modifications to the default rules, or the creation of new rules, should only be done when necessary."
msgstr ""
#: ../../content/applications/hr/payroll.rst:214
#: ../../content/applications/hr/payroll.rst:216
msgid "To view all the rules, go to :menuselection:`Payroll app --> Configuration --> Rules`. Click on a structure (such as :guilabel:`Regular Pay`) to view all the rules."
msgstr ""
@ -712,7 +712,7 @@ msgstr ""
msgid "Rules for each salary structure type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:221
#: ../../content/applications/hr/payroll.rst:223
msgid "To make a new rule, click :guilabel:`Create`. A new rule form appears. Enter the information in the fields, then click :guilabel:`Save`."
msgstr ""
@ -720,47 +720,47 @@ msgstr ""
msgid "Enter the information for the new rule."
msgstr ""
#: ../../content/applications/hr/payroll.rst:228
#: ../../content/applications/hr/payroll.rst:230
msgid "The required fields for a rule are:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:230
#: ../../content/applications/hr/payroll.rst:232
msgid ":guilabel:`Name`: Enter a name for the rule."
msgstr ""
#: ../../content/applications/hr/payroll.rst:231
#: ../../content/applications/hr/payroll.rst:233
msgid ":guilabel:`Category`: Select a category the rule applies to from the drop-down menu, or enter a new one."
msgstr ""
#: ../../content/applications/hr/payroll.rst:233
#: ../../content/applications/hr/payroll.rst:235
msgid ":guilabel:`Code`: Enter a code to be used for this new rule. It is recommended to coordinate with the accounting department for a code as this will affect them."
msgstr ""
#: ../../content/applications/hr/payroll.rst:235
#: ../../content/applications/hr/payroll.rst:237
msgid ":guilabel:`Salary Structure`: Select a salary structure the rule applies to from the drop-down menu, or enter a new one."
msgstr ""
#: ../../content/applications/hr/payroll.rst:237
#: ../../content/applications/hr/payroll.rst:239
msgid ":guilabel:`Condition Based on`: In the :guilabel:`General` tab, select from the drop-down menu whether the rule is :guilabel:`Always True` (always applies), a :guilabel:`Range` (applies to a specific range, which is entered beneath the selection), or a :guilabel:`Python Expression` (the code is entered beneath the selection)."
msgstr ""
#: ../../content/applications/hr/payroll.rst:241
#: ../../content/applications/hr/payroll.rst:243
msgid ":guilabel:`Amount Type`: In the :guilabel:`General` tab, select from the drop-down menu whether the amount is a :guilabel:`Fixed Amount`, a :guilabel:`Percentage (%)`, or a :guilabel:`Python Code`. Depending on what is selected, the fixed amount, percentage, or Python code needs to be entered next."
msgstr ""
#: ../../content/applications/hr/payroll.rst:247
#: ../../content/applications/hr/payroll.rst:249
msgid "Rule parameters"
msgstr ""
#: ../../content/applications/hr/payroll.rst:250
#: ../../content/applications/hr/payroll.rst:252
msgid "Currently, the :guilabel:`Rule Parameters` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets."
msgstr ""
#: ../../content/applications/hr/payroll.rst:255
#: ../../content/applications/hr/payroll.rst:257
msgid "Other input types"
msgstr ""
#: ../../content/applications/hr/payroll.rst:257
#: ../../content/applications/hr/payroll.rst:259
msgid "When creating payslips, it is sometimes necessary to add other entries for specific circumstances, like expenses, reimbursements, or deductions. These other inputs can be configured by going to :menuselection:`Payroll --> Configuration --> Other Input Types`."
msgstr ""
@ -768,7 +768,7 @@ msgstr ""
msgid "Other input types for payroll."
msgstr ""
#: ../../content/applications/hr/payroll.rst:265
#: ../../content/applications/hr/payroll.rst:267
msgid "To create a new input type, click the :guilabel:`Create` button. Enter the :guilabel:`Description`, the :guilabel:`Code`, and which structure it applies to in the :guilabel:`Availability in Structure` field. Click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry."
msgstr ""
@ -776,27 +776,27 @@ msgstr ""
msgid "Create a new Input Type."
msgstr ""
#: ../../content/applications/hr/payroll.rst:275
#: ../../content/applications/hr/payroll.rst:277
msgid "Salary package configurator"
msgstr ""
#: ../../content/applications/hr/payroll.rst:277
#: ../../content/applications/hr/payroll.rst:279
msgid "The various options under the :guilabel:`Salary Package Configurator` section of the :menuselection:`Payroll --> Configuration` menu all affect an employee's potential salary. These sections (:guilabel:`Advantages`, :guilabel:`Personal Info`, and :guilabel:`Resume`) specify what benefits can be offered to an employee in their salary package."
msgstr ""
#: ../../content/applications/hr/payroll.rst:282
#: ../../content/applications/hr/payroll.rst:284
msgid "Depending on what information an employee enters (such as deductions, dependents, etc.), their salary is adjusted accordingly. When an applicant applies for a job on the company website, the sections under :guilabel:`Salary Package Configurator` directly affect what the applicant sees, and what is populated as the applicant enters information."
msgstr ""
#: ../../content/applications/hr/payroll.rst:288
#: ../../content/applications/hr/payroll.rst:290
msgid "Advantages"
msgstr ""
#: ../../content/applications/hr/payroll.rst:290
#: ../../content/applications/hr/payroll.rst:292
msgid "When offering potential employees a position, there can be certain *advantages* set in Odoo in addition to the salary to make the offer more appealing (such as extra time off, access to a company car, reimbursement for a phone or internet, etc.)."
msgstr ""
#: ../../content/applications/hr/payroll.rst:294
#: ../../content/applications/hr/payroll.rst:296
msgid "To see the advantages, go to :menuselection:`Payroll --> Configuration --> Advantages`. Advantages are grouped by :guilabel:`Structure type`."
msgstr ""
@ -804,7 +804,7 @@ msgstr ""
msgid "Settings available for payroll."
msgstr ""
#: ../../content/applications/hr/payroll.rst:301
#: ../../content/applications/hr/payroll.rst:303
msgid "To make a new advantage, click the :guilabel:`Create` button. Enter the information in the fields, then click the :guilabel:`Save` button to save the changes, or click :guilabel:`Discard` to delete the entry."
msgstr ""
@ -812,39 +812,39 @@ msgstr ""
msgid "List of advantages employee's can have."
msgstr ""
#: ../../content/applications/hr/payroll.rst:309
#: ../../content/applications/hr/payroll.rst:311
msgid "The required fields for an advantage are:"
msgstr ""
#: ../../content/applications/hr/payroll.rst:311
#: ../../content/applications/hr/payroll.rst:313
msgid ":guilabel:`Name`: Enter the name for the advantage."
msgstr ""
#: ../../content/applications/hr/payroll.rst:312
#: ../../content/applications/hr/payroll.rst:314
msgid ":guilabel:`Advantage Field`: Select from the drop-down menu what field in the payslip this advantage appears under."
msgstr ""
#: ../../content/applications/hr/payroll.rst:314
#: ../../content/applications/hr/payroll.rst:316
msgid ":guilabel:`Advantage Type`: Select from the drop-down menu what type of advantage the benefit is. Select from :guilabel:`Monthly Benefit in Kind`, :guilabel:`Monthly Advantages in Net`, :guilabel:`Monthly Advantages in Cash`, or :guilabel:`Yearly Advantages in Cash`."
msgstr ""
#: ../../content/applications/hr/payroll.rst:317
#: ../../content/applications/hr/payroll.rst:319
msgid ":guilabel:`Salary Structure Type`: Select from the drop-down menu which salary structure type this advantage applies to."
msgstr ""
#: ../../content/applications/hr/payroll.rst:321
#: ../../content/applications/hr/payroll.rst:323
msgid "Personal info"
msgstr ""
#: ../../content/applications/hr/payroll.rst:323
#: ../../content/applications/hr/payroll.rst:325
msgid "Every employee in Odoo has an *employee card* that includes all of their personal information, resume, work information, and documents. To view an employee's card, go to the main :menuselection:`Payroll` app dashboard, and click on the employee's card, or go to :menuselection:`Payroll --> Employees --> Employees` and click on the employee's card. Employee cards can also be viewed by going to the :menuselection:`Employees` app."
msgstr ""
#: ../../content/applications/hr/payroll.rst:330
#: ../../content/applications/hr/payroll.rst:332
msgid "An employee card can be thought of as an employee personnel file."
msgstr ""
#: ../../content/applications/hr/payroll.rst:332
#: ../../content/applications/hr/payroll.rst:334
msgid "The *Personal Information* section lists all of the fields that are available to enter on the employee's card. To access this section, go to :menuselection:`Payroll --> Configuration --> Personal Info`."
msgstr ""
@ -852,7 +852,7 @@ msgstr ""
msgid "Personal information that appear on employee cards to enter."
msgstr ""
#: ../../content/applications/hr/payroll.rst:340
#: ../../content/applications/hr/payroll.rst:342
msgid "To edit an entry, select it from the list. Then, click the :guilabel:`Edit` button, and modify the entry. When done, click :guilabel:`Save` or :guilabel:`Discard` to save the information or cancel the edits."
msgstr ""
@ -860,23 +860,23 @@ msgstr ""
msgid "New personal information entry."
msgstr ""
#: ../../content/applications/hr/payroll.rst:348
#: ../../content/applications/hr/payroll.rst:350
msgid "The two most important fields on the personal info form are :guilabel:`Is Required` and :guilabel:`Display Type`. Checking the :guilabel:`Is Required` box makes the field mandatory on the employee's card."
msgstr ""
#: ../../content/applications/hr/payroll.rst:352
#: ../../content/applications/hr/payroll.rst:354
msgid "The :guilabel:`Display Type` drop-down menu allows for the information to be entered in a variety of ways, from a :guilabel:`Text` box, to a customizable :guilabel:`Radio` button, a :guilabel:`Checkbox`, a :guilabel:`Document`, and more."
msgstr ""
#: ../../content/applications/hr/payroll.rst:356
#: ../../content/applications/hr/payroll.rst:358
msgid "Once the information is entered, click the :guilabel:`Save` button to save the entry."
msgstr ""
#: ../../content/applications/hr/payroll.rst:359
#: ../../content/applications/hr/payroll.rst:361
msgid "Resume"
msgstr ""
#: ../../content/applications/hr/payroll.rst:362
#: ../../content/applications/hr/payroll.rst:364
msgid "Currently, the :guilabel:`Resume` feature found inside the :menuselection:`Payroll app --> Configuration` menu is still in development and only serves a specific use case for Belgian markets. The documentation will be updated when this section has matured to more markets."
msgstr ""

4787
locale/sources/inventory_and_mrp.pot
View File

File diff suppressed because it is too large Load Diff

230
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-08 08:46+0000\n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -334,42 +334,38 @@ msgid "Even after synchronizing the Odoo Calendar with the Outlook calendar, Out
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:106
msgid "After one user syncs their Outlook calendar to the Odoo database, unwanted email notifications are unavoidable because the first synchronized user's events will be in the Odoo Calendar. If the Odoo database is shared amongst multiple users, and another user wants to sync their Outlook calendar with Odoo Calendar, Outlook will again pull the existing Odoo Calendar events during the sync and treat them as new events, causing Outlook to send email invitations to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:113
msgid "In summary, once a user synchronizes their Outlook calendar with the Odoo calendar:"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:115
#: ../../content/applications/productivity/calendar/outlook.rst:108
msgid "Creating an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:116
#: ../../content/applications/productivity/calendar/outlook.rst:109
msgid "Deleting an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:117
#: ../../content/applications/productivity/calendar/outlook.rst:110
msgid "Unarchiving an event in Odoo causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:118
#: ../../content/applications/productivity/calendar/outlook.rst:111
msgid "Archiving an event in Odoo causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:119
#: ../../content/applications/productivity/calendar/outlook.rst:112
msgid "Adding a contact to an event causes Outlook to send an invitation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:120
#: ../../content/applications/productivity/calendar/outlook.rst:113
msgid "Removing a contact from an event causes Outlook to send a cancellation to all event attendees."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:123
#: ../../content/applications/productivity/calendar/outlook.rst:116
msgid "Sync Odoo Calendar and Outlook"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:125
#: ../../content/applications/productivity/calendar/outlook.rst:118
msgid "In the Odoo database, go to the :guilabel:`Calendar` module and click the :guilabel:`Outlook` sync button. The page will redirect to a Microsoft login page, and the user is asked to log in to their account, if they are not already, and grant the required permissions."
msgstr ""
@ -377,19 +373,19 @@ msgstr ""
msgid "The \"Outlook\" sync button in Odoo Calendar."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:133
#: ../../content/applications/productivity/calendar/outlook.rst:126
msgid "The synchronization is a two-way process, meaning that events are reconciled in both accounts (Outlook and Odoo)."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:137
#: ../../content/applications/productivity/calendar/outlook.rst:130
msgid "All users that want to use the synchronization simply need to :ref:`sync their calendar with Outlook <outlook/sync>`. The configuration of Microsoft's Azure account is only done once, as Microsoft Entra ID tenants' Client IDs and Client Secrets are unique, and represent an organization that helps the user to manage a specific instance of Microsoft cloud services for their internal and external users."
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:144
#: ../../content/applications/productivity/calendar/outlook.rst:137
msgid ":doc:`../mail_plugins/outlook`"
msgstr ""
#: ../../content/applications/productivity/calendar/outlook.rst:145
#: ../../content/applications/productivity/calendar/outlook.rst:138
msgid ":doc:`google`"
msgstr ""
@ -822,8 +818,12 @@ msgstr ""
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../content/applications/productivity/iot.rst:17
msgid "The Open Platform Communications (OPC) Unified Architecture (UA) protocol is now supported by the :abbr:`IoT (Internet of Things)` box. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` is an open standard that specifies information exchange for industrial communication on devices, between machines and between systems. This includes communication between information technology and operational technology. :abbr:`OPC (Open Platform Communications)` :abbr:`UA (United Architecture)` can be used with any software platform, on a wide variety of devices, and deployed securely. The :abbr:`IoT (Internet of Things)` box has entered the world of the Industry 4.0 standard and can be utilized in a wide variety of industries, and for things like building automation, packaging, utilities, etc."
msgstr ""
#: ../../content/applications/productivity/iot/config.rst:5
#: ../../content/applications/productivity/mail_plugins/outlook.rst:6
#: ../../content/applications/productivity/mail_plugins/outlook.rst:10
msgid "Configuration"
msgstr ""
@ -2325,7 +2325,7 @@ msgstr ""
#: ../../content/applications/productivity/iot/devices/camera.rst:82
#: ../../content/applications/productivity/iot/devices/footswitch.rst:52
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:90
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:92
#: ../../content/applications/productivity/iot/devices/printer.rst:95
msgid ":ref:`workcenter_iot`"
msgstr ""
@ -2378,19 +2378,19 @@ msgstr ""
msgid "Connect a measurement tool"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:5
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:7
msgid "With Odoo's :abbr:`IoT (Internet of Things)` box, it is possible to connect measurement tools to the Odoo database for use in the *Quality app* on a quality control point/quality check, or for use in a work center during the manufacturing process."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:9
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:11
msgid "Find the list of supported devices here: `Supported devices <https://www.odoo.com/page/iot-hardware>`_."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:13
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15
msgid "Connect with universal serial bus (USB)"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:15
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:17
msgid "To add a device connected by :abbr:`USB (Universal Serial Bus)`, plug the :abbr:`USB (Universal Serial Bus)` cable into the :abbr:`IoT (Internet of Things)` box, and the device appears in the Odoo database."
msgstr ""
@ -2398,11 +2398,11 @@ msgstr ""
msgid "Measurement tool recognized on the IoT box."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:24
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26
msgid "Connect with bluetooth"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:26
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:28
msgid "Activate the Bluetooth functionality on the device (see the device manual for further explanation), and the :abbr:`IoT (Internet of Things)` box automatically connects to the device."
msgstr ""
@ -2410,23 +2410,23 @@ msgstr ""
msgid "Bluetooth indicator on measurement tool."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:35
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37
msgid "Link a measurement tool to a quality control point in the manufacturing process"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:37
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:39
msgid "In the *Quality app*, a device can be set up on a quality control point. To do that, navigate to :menuselection:`Quality app --> Quality Control --> Control Points`, and open the desired control point to which the measurement tool should be linked."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:41
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:43
msgid "From here, edit the control point, by selecting the :guilabel:`Type` field, and clicking :guilabel:`Measure` from the drop-down menu. Doing so reveals a field called :guilabel:`Device`, where the attached device can be selected."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:45
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:47
msgid "Additionally, :guilabel:`Norm` and :guilabel:`Tolerance` can be configured. :guilabel:`Save` the changes, if required."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:48
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:50
msgid "At this point, the measurement tool is linked to the chosen quality control point. The value, which usually needs to be changed manually, is automatically updated while the tool is being used."
msgstr ""
@ -2434,40 +2434,40 @@ msgstr ""
msgid "Measurement tool input in the Odoo database."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:56
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:58
#: ../../content/applications/productivity/iot/devices/printer.rst:60
msgid "Quality control points can also be accessed by navigating to :menuselection:`IoT App --> Devices`, then select the device. There is a :guilabel:`Quality Control Points` tab, where they can be added with the device."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:61
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:63
msgid "On a quality check detail form, the :guilabel:`Type` of check can also be specified to :guilabel:`Measure`. Access a new quality check detail page, by navigating to :menuselection:`Quality app --> Quality Control --> Quality Checks --> New`."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:66
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:68
msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_control_points`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:67
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:69
msgid ":doc:`../../../inventory_and_mrp/quality/quality_management/quality_alerts`"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:70
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72
msgid "Link a measurement tool to a work center in the Manufacturing app"
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:72
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:74
msgid "To link a measurement tool to an action, it first needs to be configured on a work center. To do that, navigate to :menuselection:`Manufacturing app --> Configuration --> Work Centers`. Then, select the desired work center in which the measurement tool will be used."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:76
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:78
msgid "On the work center page, add the device in the :guilabel:`IoT Triggers` tab, under the :guilabel:`Device` column, by selecting :guilabel:`Add a Line`. Then, the measurement tool can be linked to the :guilabel:`Action` drop-down menu option labeled :guilabel:`Take Measure`. A key can be added to trigger the action."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:82
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:84
msgid "It should be noted that the first listed trigger is chosen first. The order matters, and these triggers can be dragged into any order."
msgstr ""
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:86
#: ../../content/applications/productivity/iot/devices/measurement_tool.rst:88
msgid "On the :guilabel:`Work Order` screen, a status graphic indicates whether the database is correctly connected to the measurement tool."
msgstr ""
@ -3747,160 +3747,160 @@ msgstr ""
msgid "Outlook Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:8
#: ../../content/applications/productivity/mail_plugins/outlook.rst:5
msgid "Outlook allows for third-party applications to connect in order to execute database actions from emails. Odoo has a plugin for Outlook that allows for the creation of an opportunity from the email panel."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:12
msgid "The Outlook :doc:`Mail Plugin <../mail_plugins>` needs to be configured both on Odoo and Outlook."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:13
#: ../../content/applications/productivity/mail_plugins/outlook.rst:17
msgid "Enable Mail Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:15
msgid "First, you need to enable the *Mail Plugin* feature in your database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable *Mail Plugin*, and *Save* the configuration."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:21
msgid "Install the Outlook Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:23
msgid "Open your Outlook mailbox and select any email."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:19
msgid "First, enable the *Mail Plugin* feature in the database. Go to :menuselection:`Settings --> General Settings --> Integrations`, enable :guilabel:`Mail Plugin`, and :guilabel:`Save` the configuration."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:25
msgid "Click on the *More actions* button and select *Get Add-ins*."
msgid "Install the Outlook Plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "More actions button in Outlook"
#: ../../content/applications/productivity/mail_plugins/outlook.rst:27
msgid "Download (:menuselection:`Save Page As --> Web Page XML only`) the following XML file to upload later: `https://download.odoocdn.com/plugins/outlook/manifest.xml <https://download.odoocdn.com/plugins/outlook/manifest.xml>`_."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:31
msgid "Select the *My add-ins* tab."
msgid "Next, open the Outlook mailbox, and select any email. After completing this, click on the :guilabel:`More actions` button in the upper right-side and select :guilabel:`Get Add-ins`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "More actions button in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:38
msgid "Following this step, select the :guilabel:`My add-ins` tab on the left-side."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "My add-ins in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:37
msgid "Under *Custom add-ins*, click on *+ Add a custom add-in*, and then on *Add from URL...*"
#: ../../content/applications/productivity/mail_plugins/outlook.rst:44
msgid "Under :guilabel:`Custom add-ins` towards the bottom, click on :guilabel:`+ Add a custom add-in`, and then on :guilabel:`Add from file...`"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Custom add-ins in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:43
msgid "Enter the following URL `https://download.odoocdn.com/plugins/v15/outlook/manifest.xml` and press *OK*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:51
msgid "For the next step, attach the `manifest.xml` file downloaded above, and press :guilabel:`OK`. Next, read the warning and click on :guilabel:`Install`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Entering the add-in URL in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:50
msgid "Read the warning and click on *Install*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Custom add-in installation warning in Outlook"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:59
msgid "Connect your database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:61
msgid "Open any email in your Outlook mailbox, click on the *More actions* button, and select *Odoo for Outlook*."
msgid "Connect the database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:63
msgid "Now, Outlook will be connected to the Odoo database. First, open any email in the Outlook mailbox, click on the :guilabel:`More actions` button in the upper right-side, and select :guilabel:`Odoo for Outlook`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Odoo for Outlook add-in button"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:68
msgid "The right-side panel can now display **Company Insights**. At the bottom, click on *Login*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:71
msgid "The right-side panel can now display **Company Insights**. At the bottom, click on :guilabel:`Login`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Logging in your Odoo database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:75
msgid "Only a limited amount of *Company Insights* (*Lead Enrichment*) requests are available as a trial. This feature requires :ref:`prepaid credits <mail_plugins/pricing>`."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Logging in the Odoo database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:79
msgid "If, after a short while, the panel is still empty, it is possible that your browser cookie settings prevented it from loading. Note that these settings also change if you are in \"Incognito\" mode on your browser."
msgid "Only a limited amount of **Company Insights** (*Lead Enrichment*) requests are available as a trial database. This feature requires :ref:`prepaid credits <mail_plugins/pricing>`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:84
msgid "To fix this issue, configure your browser to always allow cookies on Odoo's plugin page."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:83
msgid "If, after a short while, the panel is still empty, it is possible that the browser cookie settings prevented it from loading. Note that these settings also change if the browser is in \"Incognito\" mode."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:86
msgid "For Google Chrome, you can do so by following the guide at: `https://support.google.com/chrome/answer/95647 <https://support.google.com/chrome/answer/95647#:~:text=Allow%20or%20block%20cookies%20for%20a%20specific%20site>`_ and adding `download.odoo.com` to the list of `Sites that can always use cookies`."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:87
msgid "To fix this issue, configure the browser to always allow cookies on Odoo's plugin page."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:90
msgid "Once done, the Outlook panel needs to be opened again."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:89
msgid "For Google Chrome, change the browser cookie settings by following the guide at: `https://support.google.com/chrome/answer/95647 <https://support.google.com/chrome/answer/95647>`_ and adding `download.odoo.com` to the list of :guilabel:`Sites that can always use cookies`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:93
msgid "Enter your Odoo database URL and click on *Login*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:94
msgid "Once this is complete, the Outlook panel needs to be opened again."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
msgid "Entering your Odoo database URL"
#: ../../content/applications/productivity/mail_plugins/outlook.rst:96
msgid "Now, enter the Odoo database URL and click on :guilabel:`Login`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:99
msgid "Click on *Allow* to open the pop-up window."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Entering the Odoo database URL"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:102
msgid "Next, click on :guilabel:`Allow` to open the pop-up window."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "New window pop-up warning"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:105
msgid "If you aren't logged into your database, enter your credentials."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:108
msgid "If the user isn't logged into the database, enter the credentials. Click on :guilabel:`Allow` to let the Outlook Plugin connect to the database."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:107
msgid "Click on *Allow* to let the Outlook Plugin connect to your database."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Allowing the Outlook Plugin to connect to a database"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:116
#: ../../content/applications/productivity/mail_plugins/outlook.rst:118
msgid "Add a shortcut to the plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:118
#: ../../content/applications/productivity/mail_plugins/outlook.rst:120
msgid "By default, the Outlook Plugin can be opened from the *More actions* menu. However, to save time, it's possible to add it next to the other default actions."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:121
msgid "In your Outlook mailbox, click on *Settings*, then on *View all Outlook settings*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:123
msgid "In the Outlook mailbox, click on :guilabel:`Settings`, then on :guilabel:`View all Outlook settings`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Viewing all Outlook settings"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:127
msgid "Select *Customize actions* under *Mail*, click on *Odoo for Outlook*, and then *Save*."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:130
msgid "Now, select :guilabel:`Customize actions` under :guilabel:`Mail`, click on :guilabel:`Odoo for Outlook`, and then :guilabel:`Save`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:0
#: ../../content/applications/productivity/mail_plugins/outlook.rst:-1
msgid "Odoo for Outlook customized action"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:133
msgid "Open any email; the shortcut should be displayed."
#: ../../content/applications/productivity/mail_plugins/outlook.rst:137
msgid "Following this step, open any email; the shortcut should be displayed."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:144
msgid "Using the plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:146
msgid "Now that the plug-in is installed and operational, all that needs to be done to create a lead is to click on the `O` [Odoo icon] or navigate to :guilabel:`More actions` and click on :guilabel:`Odoo for Outlook`. The side panel will appear on the right-side, and under :guilabel:`Opportunities` click on :guilabel:`New`. A new window with the created opportunity in the Odoo database will populate."
msgstr ""
#: ../../content/applications/productivity/studio.rst:6

1045
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff

40
locale/sources/services.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-08 08:46+0000\n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -1690,7 +1690,7 @@ msgid ":guilabel:`Type`: which matches an Odoo model value to the field (e.g. `C
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:94
msgid ":guilabel:`Input Type`: to determine what time of input the field should be, like `Text`, `Email`, `Telephone` or `URL`."
msgid ":guilabel:`Input Type`: to determine what type of input the field should be, like `Text`, `Email`, `Telephone` or `URL`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/receiving_tickets.rst:96
@ -2332,14 +2332,14 @@ msgid "If a ticket fits the criteria for more than one :abbr:`SLA (Service Level
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:95
msgid "Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the :abbr:`SLA (Service Level Agreement)` tag turns green, and the :guilabel:`Deadline` field disappears from view on the."
msgid "Once a ticket satisfies an :abbr:`SLA (Service Level Agreement)` policy, the :abbr:`SLA (Service Level Agreement)` tag turns green, and the :guilabel:`Deadline` field disappears from view on the ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:-1
msgid "View of a ticket's form emphasizing a satisfied SLA in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:102
#: ../../content/applications/services/helpdesk/overview/sla.rst:103
msgid "If the :abbr:`SLA (Service Level Agreement)` deadline passes and the ticket has not moved to the :guilabel:`Reach Stage`, the :abbr:`SLA (Service Level Agreement)` tag will turn red. Once the :abbr:`SLA (Service Level Agreement)` has failed, the red tag will stay on the ticket, even after the ticket is moved to the :guilabel:`Reach Stage`."
msgstr ""
@ -2347,19 +2347,19 @@ msgstr ""
msgid "View of a ticket's form with a failing and passing SLA in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:112
#: ../../content/applications/services/helpdesk/overview/sla.rst:113
msgid "Analyzing SLA performance"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:114
#: ../../content/applications/services/helpdesk/overview/sla.rst:115
msgid "The :guilabel:`SLA Status Analysis` report tracks how quickly an :abbr:`SLA (Service Level Agreement)` is fulfilled, as well as the success rate of individual policies. Navigate to the report and corresponding pivot table by going to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:120
#: ../../content/applications/services/helpdesk/overview/sla.rst:121
msgid "Using the Pivot view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:122
#: ../../content/applications/services/helpdesk/overview/sla.rst:123
msgid "By default, the report is displayed in a :guilabel:`Pivot` view, and is filtered to show the number of SLAs failed and the failure rate over the last 30 days, grouped by team."
msgstr ""
@ -2367,23 +2367,23 @@ msgstr ""
msgid "View of the SLA status analysis report in Odoo Helpdesk"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:129
#: ../../content/applications/services/helpdesk/overview/sla.rst:130
msgid "To add the number of SLAs passed or in progress, click the :guilabel:`Measures` button to reveal a drop-down menu of reporting criteria, and choose from the options available based on the measurements preferred. Whenever a measurement is picked, a check mark will appear in the drop-down menu to indicate that that measurement is included, and a corresponding new column will emerge in the pivot table to show the relevant calculations."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:135
#: ../../content/applications/services/helpdesk/overview/sla.rst:136
msgid "To add a group to a row or column, click the plus :guilabel:` + ` button next to :guilabel:`Total`, and then select one of the groups. To remove one, click the minus :guilabel:` - ` button and deselect."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:140
#: ../../content/applications/services/helpdesk/overview/sla.rst:141
msgid "Using the Graph view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:142
#: ../../content/applications/services/helpdesk/overview/sla.rst:143
msgid "The :guilabel:`Status Analysis` report can also be viewed as a :guilabel:`Bar`, :guilabel:`Line`, or :guilabel:`Pie` Chart. Toggle between these views by selecting the appropriate icon at the top of the chart."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:148
#: ../../content/applications/services/helpdesk/overview/sla.rst:149
msgid "Bar Chart"
msgstr ""
@ -2391,7 +2391,7 @@ msgstr ""
msgid "View of the SLA status analysis report in bar view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:154
#: ../../content/applications/services/helpdesk/overview/sla.rst:155
msgid "Line Chart"
msgstr ""
@ -2399,7 +2399,7 @@ msgstr ""
msgid "View of the SLA status analysis report in line view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:160
#: ../../content/applications/services/helpdesk/overview/sla.rst:161
msgid "Pie Chart"
msgstr ""
@ -2407,15 +2407,15 @@ msgstr ""
msgid "View of the SLA status analysis report in pie chart view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:167
#: ../../content/applications/services/helpdesk/overview/sla.rst:168
msgid "Both the :guilabel:`Bar Chart` and :guilabel:`Line Chart` can be viewed :guilabel:`Stacked`. This presents two or more groups to appear on top of each other instead of next to each other, making it easier to compare data."
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:172
#: ../../content/applications/services/helpdesk/overview/sla.rst:173
msgid "Using the Cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:174
#: ../../content/applications/services/helpdesk/overview/sla.rst:175
msgid "The :guilabel:`Cohort` view is used to track the changes in data over a period of time. To display the :guilabel:`Status Analysis` report in a :guilabel:`Cohort` view, click the icon in the top right corner above the chart."
msgstr ""
@ -2423,11 +2423,11 @@ msgstr ""
msgid "View of the SLA status analysis report in cohort view"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:183
#: ../../content/applications/services/helpdesk/overview/sla.rst:184
msgid ":ref:`Reporting views <reporting/views>`"
msgstr ""
#: ../../content/applications/services/helpdesk/overview/sla.rst:184
#: ../../content/applications/services/helpdesk/overview/sla.rst:185
msgid ":doc:`Allow customers to close their tickets </applications/services/helpdesk/advanced/close_tickets>`"
msgstr ""

254
locale/sources/websites.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-08 08:46+0000\n"
"POT-Creation-Date: 2023-11-30 14:44+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -4589,6 +4589,162 @@ msgstr ""
msgid "**As a non-Odoo Online user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:3
msgid "Mail groups"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:5
msgid "The **mail groups** feature allows website visitors to have a public discussion by email. They can join a group to receive emails from other group members (i.e., website users who have subscribed to the group) and send new ones to all group members."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:9
msgid "To activate the feature, :ref:`install <general/install>` the :guilabel:`Website Mail Group` (`website_mail_group`) module."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:13
msgid "The **mail groups** feature is not to be confused with the :doc:`../../marketing/email_marketing/mailing_lists` in the Email Marketing app."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:19
msgid "Configuring mail groups"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:21
msgid "To configure mail groups, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:23
msgid "Configure a custom email alias domain by accessing the **General settings**, scrolling down to the :guilabel:`Discuss` section, enabling the :guilabel:`Custom Email Server` feature, and entering the :guilabel:`Alias domain` (e.g., `@mycompany.com`)."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:26
msgid "Go to :menuselection:`Website --> Configuration --> Mailing Lists`, then click :guilabel:`New`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:27
msgid "Specify a :guilabel:`Group Name`, the :guilabel:`Email Alias`, and a :guilabel:`Description`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:28
msgid "Enable :guilabel:`Moderate this group` and specify the :guilabel:`Moderators` if you wish to :ref:`moderate messages <website/mailing_lists/moderate>` from this group. Alternatively, if the group is not moderated, you can define :guilabel:`Responsible Users` who can manage the messages in the group."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:32
msgid "In the :guilabel:`Privacy` tab, define who can subscribe to the mail group:"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:34
msgid ":guilabel:`Everyone`: to make the mail group public so anyone can subscribe to it;"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:35
msgid ":guilabel:`Members only`: to only allow users defined as members to subscribe to the mail group;"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:36
msgid ":guilabel:`Selected group of users`: to only allow users from the :guilabel:`Authorized group` to subscribe to the mail group."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:39
msgid "If the mail group is moderated, you can automatically notify authors when their message is pending moderation by enabling :guilabel:`Automatic notification` in the :guilabel:`Notify Members` tab and writing the :guilabel:`Notification message`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:42
msgid "If you wish to send out guidelines to new subscribers, enable :guilabel:`Send guidelines to new subscribers` and write them in the :guilabel:`Guidelines` tab. This is particularly useful when the mail group is moderated."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:47
msgid "Using mail groups"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:50
msgid "Subscribing/unsubscribing"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:52
msgid "Based on the :ref:`configuration of the mail group <website/mailing_lists/configure_groups>`, users can subscribe to and unsubscribe from mail groups from the website page (`/groups` by default)."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:-1
msgid "Mail group web page."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:58
msgid "Internal users can also do this from :menuselection:`Website --> Configuration --> Mailing Lists`, using the :guilabel:`Join` and :guilabel:`Leave` buttons."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:62
msgid "Sending messages"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:64
msgid "To send messages to a mail group, website users can email the :ref:`mail group's email address <website/mailing_lists/configure_groups>`. Internal users can also create messages directly from Odoo. To do so, go to :menuselection:`Website --> Configuration --> Mailing Lists`, select the mail group, click the :guilabel:`Emails` smart button, and click :guilabel:`New`. Then, fill in the fields and click :guilabel:`Send`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:71
msgid "The list of messages can also be accessed by selecting the group from the `/groups` website page."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:73
msgid "Group members can also unsubscribe from the group, access the mail group page, and send emails to the group using the URLs in the footer of any group email they have received."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:0
msgid "URLs in the footer of a group email."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:82
msgid "Moderating mail group messages"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:84
msgid "If the :guilabel:`Moderate this group` feature has been enabled for the :ref:`mail group <website/mailing_lists/configure_groups>`, one of the :guilabel:`Moderators` must approve the group's messages before they are dispatched to the other members."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:88
msgid "To moderate messages, go to :menuselection:`Website --> Configuration --> Mailing Lists`, select the mail group, and click the :guilabel:`To review` smart button. You can moderate messages using the buttons at the end of the message line or select a message to view its content and moderate it accordingly."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:0
msgid "Moderation buttons in the message line."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:96
msgid "The following actions are available:"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:98
msgid ":guilabel:`Accept`: to accept the email and send it to the mail group members."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:99
msgid ":guilabel:`Reject`: to reject the email. In the pop-up window that opens, click :guilabel:`Reject Silently` to reject the email without notifying the author, or specify an explanation for rejecting the message, then click :guilabel:`Send & Reject` to reject the message and send the explanation to the author."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:103
msgid ":guilabel:`Whitelist`: to whitelist the author, i.e. automatically accept all of their emails. As a result, a :ref:`moderation rule <website/mailing_lists/moderate>` is created for the author's email address with the status :guilabel:`Always allow`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:106
msgid ":guilabel:`Ban`: to blacklist the author, i.e. automatically discard all their emails. In the pop-up window that opens, click :guilabel:`Ban` to ban the author without notifying them, or specify an explanation, then click :guilabel:`Send & Ban` to ban the author and send them the explanation. As a result, a :ref:`moderation rule <website/mailing_lists/moderate>` is created for the author's email address with the status :guilabel:`Permanent ban`."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:113
msgid "Messages can also be moderated from the group's list of messages. Go to :menuselection:`Website --> Groups --> Mailing List Groups`, select the mail group and click the :guilabel:`Emails` smart button."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:120
msgid "Whitelisting/Blacklisting authors"
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:122
msgid "You can whitelist or blacklist an author either directly :ref:`from a mail group message <website/mailing_lists/moderate>`, or by creating a moderation rule. To do so, go to :menuselection:`Website --> Configuration --> Moderation Rules` and click :guilabel:`New`. Then, select the :guilabel:`Group`, specify the author's :guilabel:`Email` and set the :guilabel:`Status` field."
msgstr ""
#: ../../content/applications/websites/website/mail_groups.rst:129
msgid "You can also access the mail group's moderation rules by going to :menuselection:`Website --> Configuration --> Mailing Lists`, selecting the group, then clicking the :guilabel:`Moderations` smart button."
msgstr ""
#: ../../content/applications/websites/website/pages.rst:1
msgid "git:show-content:"
msgstr ""
@ -5702,30 +5858,66 @@ msgid "Website analytics helps website owners understand how people use their si
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:8
msgid "You can track your Odoo website's traffic using :ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use. The Plausible analytics dashboard is also integrated into Odoo and can be accessed via :menuselection:`Website --> Reporting --> Analytics`."
msgid "You can track your Odoo website's traffic using :ref:`website/analytics/plausible` or :ref:`website/analytics/GA`. We recommend using Plausible.io as it is privacy-friendly, lightweight, and easy to use."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:16
msgid "Plausible.io"
#: ../../content/applications/websites/website/reporting/analytics.rst:12
msgid "The Plausible analytics dashboard is also integrated into Odoo and can be accessed via :menuselection:`Website --> Reporting --> Analytics`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:18
msgid "If your database is hosted on Odoo Online, the Plausible.io integration is available in Odoo for free. To enable the feature, go to :menuselection:`Website --> Configuration --> Settings`, then, in the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics` and click :guilabel:`Save`. You can then access your Plausible analytics dashboard by going to :menuselection:`Website --> Reporting --> Analytics`."
msgid "Plausible.io"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:24
msgid "If your database is hosted on Odoo.sh or on-premise, or if you wish to use your own Plausible.io account, proceed as follows:"
#: ../../content/applications/websites/website/reporting/analytics.rst:20
msgid "Odoo hosts its own Plausible.io server and provides a free and ready-to-work Plausible.io solution for **Odoo Online** databases. Go to :menuselection:`Website --> Configuration --> Settings`, and enable the feature in the :guilabel:`SEO` section. Odoo automatically creates and sets up your account. You can start using it by going to :menuselection:`Website --> Reporting --> Analytics`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:27
#: ../../content/applications/websites/website/reporting/analytics.rst:26
msgid "**If you already have a Plausible.io account** and you want to connect it to your Odoo Online database, you must create two `ir.config.parameters` to use Plausible.io's servers. To do so, enable the :ref:`developer mode <developer-mode>` and go to :menuselection:`General Settings --> Technical -- System Parameters`. Click :guilabel:`New` and fill in the following :guilabel:`Key` and :guilabel:`Value` fields:"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:35
msgid "Key"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:36
msgid "Value"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:37
msgid "`website.plausible_script`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:38
msgid "`https://plausible.io/js/plausible.js`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:39
msgid "`website.plausible_server`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:40
msgid "`https://plausible.io`"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:42
msgid "Then, follow the steps below to connect your existing account with Plausible.io servers."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:44
msgid "If your database is hosted on **Odoo.sh** or **On-premise**, or if you wish to use your own Plausible.io account, proceed as follows:"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:47
msgid "Create or sign in to a Plausible account using the following link: `<https://plausible.io/register>`_."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:28
#: ../../content/applications/websites/website/reporting/analytics.rst:48
msgid "If you are creating a new account, go through the registration and activation steps. When asked to provide your website details, add its :guilabel:`Domain` without including `www` (e.g., `example.odoo.com`) and change the :guilabel:`Reporting Timezone` if necessary. Click :guilabel:`Add snippet` to proceed to the next step. Ignore the :guilabel:`Add JavaScript snippet` instructions and click :guilabel:`Start collecting data`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:33
#: ../../content/applications/websites/website/reporting/analytics.rst:53
msgid "Once done, click the Plausible logo in the upper-left part of the page to access your `list of websites <https://plausible.io/sites>`_, then click the gear icon next to the website."
msgstr ""
@ -5733,11 +5925,11 @@ msgstr ""
msgid "Click the gear icon in the list of websites."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:39
#: ../../content/applications/websites/website/reporting/analytics.rst:59
msgid "In the sidebar, select :guilabel:`Visibility`, then click :guilabel:`+ New link`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:40
#: ../../content/applications/websites/website/reporting/analytics.rst:60
msgid "Enter a :guilabel:`Name`, leave the :guilabel:`Password` field empty, as the Plausible analytics dashboard integration in Odoo doesn't support it, then click :guilabel:`Create shared link`."
msgstr ""
@ -5745,7 +5937,7 @@ msgstr ""
msgid "Credentials creation for the new shared link"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:46
#: ../../content/applications/websites/website/reporting/analytics.rst:66
msgid "Copy the shared link."
msgstr ""
@ -5753,44 +5945,44 @@ msgstr ""
msgid "Copy the shared link URL from Plausible.io"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:51
#: ../../content/applications/websites/website/reporting/analytics.rst:98
#: ../../content/applications/websites/website/reporting/analytics.rst:71
#: ../../content/applications/websites/website/reporting/analytics.rst:118
msgid "In Odoo, go to :menuselection:`Website --> Configuration --> Settings`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:52
#: ../../content/applications/websites/website/reporting/analytics.rst:72
msgid "In the :guilabel:`SEO` section, enable :guilabel:`Plausible Analytics`, then paste the :guilabel:`Shared Link` and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:56
#: ../../content/applications/websites/website/reporting/analytics.rst:76
msgid "If you have :doc:`multiple websites <../configuration/multi_website>`, add your websites to your Plausible.io account by going to `<https://plausible.io/sites>`_ and clicking :guilabel:`+ Add website`. In Odoo, in the **Website settings**, make sure to select the website in the :guilabel:`Settings of Website` field before pasting the :guilabel:`Shared link`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:62
#: ../../content/applications/websites/website/reporting/analytics.rst:82
msgid "Odoo automatically pushes two custom goals: `Lead Generation` and `Shop`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:65
#: ../../content/applications/websites/website/reporting/analytics.rst:85
msgid "`Plausible Analytics documentation <https://plausible.io/docs>`_"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:70
#: ../../content/applications/websites/website/reporting/analytics.rst:90
msgid "Google Analytics"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:72
#: ../../content/applications/websites/website/reporting/analytics.rst:92
msgid "To follow your Odoo website's traffic with Google Analytics:"
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:74
#: ../../content/applications/websites/website/reporting/analytics.rst:94
msgid "Create or sign in to a Google account using the following link: `<https://analytics.google.com>`_."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:75
#: ../../content/applications/websites/website/reporting/analytics.rst:95
msgid "If you are setting up Google Analytics for the first time, click :guilabel:`Start measuring` and go through the account creation step."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:77
#: ../../content/applications/websites/website/reporting/analytics.rst:97
msgid "If you already have a Google Analytics account, sign in and click the gear icon in the bottom-left corner of the page to access the **Admin** page. Then, click :guilabel:`+ Create Property`."
msgstr ""
@ -5798,11 +5990,11 @@ msgstr ""
msgid "Measurement ID in Google Analytics."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:84
#: ../../content/applications/websites/website/reporting/analytics.rst:104
msgid "Complete the next steps: `property creation <https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_, business details, and business objectives."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:86
#: ../../content/applications/websites/website/reporting/analytics.rst:106
msgid "When you reach the **Data collection** step, choose the :guilabel:`Web` platform."
msgstr ""
@ -5810,23 +6002,23 @@ msgstr ""
msgid "Choose a platform for your Google Analytics property."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:91
#: ../../content/applications/websites/website/reporting/analytics.rst:111
msgid "Set up your data stream: Specify your :guilabel:`Website URL` and a :guilabel:`Stream name`, then click :guilabel:`Create stream`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:93
#: ../../content/applications/websites/website/reporting/analytics.rst:113
msgid "Copy the :guilabel:`Measurement ID`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:99
#: ../../content/applications/websites/website/reporting/analytics.rst:119
msgid "In the :guilabel:`SEO` section, enable :guilabel:`Google Analytics`, then paste the :guilabel:`Measurement ID` and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:103
#: ../../content/applications/websites/website/reporting/analytics.rst:123
msgid "If you have :doc:`multiple websites <../configuration/multi_website>` with separate domains, it is recommended to create `one property <https://support.google.com/analytics/answer/9304153?hl=en/&visit_id=638278591144564289-3612494643&rd=2#property>`_ per domain. In Odoo, in the **Website settings**, make sure to select the website in the :guilabel:`Settings of Website` field before pasting the :guilabel:`Measurement ID`."
msgstr ""
#: ../../content/applications/websites/website/reporting/analytics.rst:109
#: ../../content/applications/websites/website/reporting/analytics.rst:129
msgid "`Google documentation on setting up Analytics for a website <https://support.google.com/analytics/answer/1008015?hl=en/>`_"
msgstr ""