[I18N] *: export latest terms

As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#10313

X-original-commit: bf9bbff058
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
This commit is contained in:
Tiffany Chang (tic)
2024-07-23 15:48:14 +02:00
parent 3c8ba29d5f
commit 8d0e798f33
12 changed files with 9770 additions and 4868 deletions
+39 -39
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-24 07:08+0000\n"
"POT-Creation-Date: 2024-07-23 13:30+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"
@@ -507,7 +507,7 @@ msgstr ""
#: ../../content/administration/odoo_online.rst:3
#: ../../content/administration/supported_versions.rst:29
#: ../../content/administration/upgrade.rst:81
#: ../../content/administration/upgrade.rst:299
#: ../../content/administration/upgrade.rst:296
msgid "Odoo Online"
msgstr ""
@@ -723,7 +723,7 @@ msgstr ""
#: ../../content/administration/odoo_sh.rst:5
#: ../../content/administration/supported_versions.rst:30
#: ../../content/administration/upgrade.rst:111
#: ../../content/administration/upgrade.rst:310
#: ../../content/administration/upgrade.rst:307
msgid "Odoo.sh"
msgstr ""
@@ -3025,7 +3025,7 @@ msgstr ""
#: ../../content/administration/on_premise.rst:5
#: ../../content/administration/upgrade.rst:136
#: ../../content/administration/upgrade.rst:333
#: ../../content/administration/upgrade.rst:330
msgid "On-premise"
msgstr ""
@@ -5467,46 +5467,46 @@ msgid "Upgrading the production database"
msgstr ""
#: ../../content/administration/upgrade.rst:273
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 by `submitting a ticket for an issue related to my future upgrade (I am testing an upgrade) <https://odoo.com/help?stage=migration>`_."
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."
msgstr ""
#: ../../content/administration/upgrade.rst:279
#: ../../content/administration/upgrade.rst:276
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:282
#: ../../content/administration/upgrade.rst:279
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:288
#: ../../content/administration/upgrade.rst:285
msgid "Going into production without first testing may lead to:"
msgstr ""
#: ../../content/administration/upgrade.rst:290
#: ../../content/administration/upgrade.rst:287
msgid "Users failing to adjust to the changes and new features"
msgstr ""
#: ../../content/administration/upgrade.rst:291
#: ../../content/administration/upgrade.rst:288
msgid "Business interruptions (e.g., no longer having the possibility to validate an action)"
msgstr ""
#: ../../content/administration/upgrade.rst:292
#: ../../content/administration/upgrade.rst:289
msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)"
msgstr ""
#: ../../content/administration/upgrade.rst:294
#: ../../content/administration/upgrade.rst:291
msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions."
msgstr ""
#: ../../content/administration/upgrade.rst:301
#: ../../content/administration/upgrade.rst:298
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:306
#: ../../content/administration/upgrade.rst:303
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:312
#: ../../content/administration/upgrade.rst:309
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>` on the :guilabel:`Production` branch."
msgstr ""
@@ -5514,98 +5514,98 @@ msgstr ""
msgid "View from the upgrade tab"
msgstr ""
#: ../../content/administration/upgrade.rst:318
#: ../../content/administration/upgrade.rst:315
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:324
#: ../../content/administration/upgrade.rst:321
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:328
#: ../../content/administration/upgrade.rst:325
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. More information on how to upgrade your custom modules can be found on :doc:`/developer/howtos/upgrade_custom_db`."
msgstr ""
#: ../../content/administration/upgrade.rst:335
#: ../../content/administration/upgrade.rst:332
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:342
#: ../../content/administration/upgrade.rst:339
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:349
#: ../../content/administration/upgrade.rst:346
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:353
#: ../../content/administration/upgrade.rst:350
msgid "In case of an issue with your production database, you can request the assistance of Odoo by `submitting a ticket for an issue related to my upgrade (production) <https://odoo.com/help?stage=post_upgrade>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:360
#: ../../content/administration/upgrade.rst:357
msgid "Service-level agreement (SLA)"
msgstr ""
#: ../../content/administration/upgrade.rst:362
#: ../../content/administration/upgrade.rst:359
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:365
#: ../../content/administration/upgrade.rst:362
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:370
#: ../../content/administration/upgrade.rst:367
msgid "Upgrade services covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:372
#: ../../content/administration/upgrade.rst:369
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:375
#: ../../content/administration/upgrade.rst:372
msgid "the upgrade of all **standard applications**;"
msgstr ""
#: ../../content/administration/upgrade.rst:376
#: ../../content/administration/upgrade.rst:373
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:378
#: ../../content/administration/upgrade.rst:375
msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**."
msgstr ""
#: ../../content/administration/upgrade.rst:381
#: ../../content/administration/upgrade.rst:378
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:385
#: ../../content/administration/upgrade.rst:382
msgid "Upgrade services not covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:387
#: ../../content/administration/upgrade.rst:384
msgid "The following upgrade-related services are **not** included:"
msgstr ""
#: ../../content/administration/upgrade.rst:389
#: ../../content/administration/upgrade.rst:386
msgid "the **cleaning** of pre-existing data and configurations while upgrading;"
msgstr ""
#: ../../content/administration/upgrade.rst:390
#: ../../content/administration/upgrade.rst:387
msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;"
msgstr ""
#: ../../content/administration/upgrade.rst:391
#: ../../content/administration/upgrade.rst:388
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:394
#: ../../content/administration/upgrade.rst:391
msgid "**training** on using the upgraded version's features and workflows."
msgstr ""
#: ../../content/administration/upgrade.rst:397
#: ../../content/administration/upgrade.rst:394
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
msgstr ""
#: ../../content/administration/upgrade.rst:398
#: ../../content/administration/upgrade.rst:395
msgid ":doc:`Supported Odoo versions <supported_versions>`"
msgstr ""