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

[I18N] *: export 15.0 source terms

Browse Source
This commit is contained in:
Martin Trigaux 2022-07-22 11:37:58 +02:00
parent 3c984344d9
commit c1e062c1f4
11 changed files with 4836 additions and 2738 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1244
locale/sources/administration.pot
View File

File diff suppressed because it is too large Load Diff

2456
locale/sources/contributing.pot
View File

File diff suppressed because it is too large Load Diff

2336
locale/sources/finance.pot
View File

File diff suppressed because it is too large Load Diff

104
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-04-08 13:26+0000\n"
"POT-Creation-Date: 2022-07-22 09:36+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"
@ -395,71 +395,111 @@ msgid "Synchronize Google Calendar with Odoo"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:5
msgid "Odoo is perfectly integrated with Google Calendar so that you can see & manage your meetings from both platforms (updates go through both directions)."
msgid "Synchronize Google Calendar with Odoo to see and manage meetings from both platforms (updates go in both directions). This integration helps organize your schedule so you never miss a meeting."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:10
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:9
msgid "Setup in Google"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:11
msgid "Go to `Google APIs platform <https://console.developers.google.com>`__ to generate Google Calendar API credentials. Log in with your Google account."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:12
msgid "Enable Google Calendar API"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:14
msgid "Go to the API & Services page."
msgid "Begin by creating a new Google API project and enabling the Google Calendar API. Then, go to the `Google API Console <https://console.developers.google.com>`_ and log into your Google account."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:19
msgid "Search for *Google Calendar API* and select it."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:18
msgid "If this is your first time visiting this page, Google will prompt you to enter a country and agree to the Terms of Service. Select a country from the drop-down list and agree to the :abbr:`ToS (Terms of Service)`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:27
msgid "Enable the API."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:22
msgid "Next, click :guilabel:`Select a project` and select or create an API project to store credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:32
msgid "Select or create an API project to store the credentials if not yet done before. Give it an explicit name (e.g. Odoo Sync)."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:29
msgid "Give the API Project a clear name like \"Odoo Sync\" so you can easily find it."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:35
msgid "Create credentials."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:31
msgid "Then, open the API Project and click :guilabel:`Enable APIs and Services`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:40
msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:37
msgid "After that, search for *Google Calendar API* using the search bar and select :guilabel:`Google Calendar API` from the search results. Click :guilabel:`Enable`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:46
msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo Calendar) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:45
msgid "Create credentials"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:55
msgid "Go through the Consent Screen step by entering a product name (e.g. Odoo Calendar). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:47
msgid "Now that you have created your API project and enabled the Google Calendar API, you need to create credentials. Begin by clicking :guilabel:`Create Credentials`. Google will then guide you through four steps to create your API credentials."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:60
msgid "Finally you are provided with your **Client ID**. Go to *Credentials* to get the **Client Secret** as well. Both of them are required in Odoo."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:51
msgid "In the first step, :guilabel:`Credential Type`, select the :guilabel:`Google Calendar API` and :guilabel:`User Data` options. Then, click :guilabel:`Next`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:67
msgid "Setup in Odoo"
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:58
msgid "In the second step, :guilabel:`OAuth Consent Screen`, type *Odoo* in the :guilabel:`App name` field, select your email address for the :guilabel:`User support email` field, and type your email address for the :guilabel:`Developer contact information` section. Then, click :guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:69
msgid "Install the **Google Calendar** App from the *Apps* menu or by checking the option in :menuselection:`Settings --> General Settings`."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:63
msgid "Skip the third step, :guilabel:`Scopes`, by clicking :guilabel:`Save and Continue`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:75
msgid "Go to :menuselection:`Settings --> General Settings` and enter your **Client ID** and **Client Secret** in Google Calendar option."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:65
msgid "In the last step, :guilabel:`OAuth Client ID`, select :guilabel:`Website application` for the :guilabel:`Application Type` field and type *My Odoo Database* for the :guilabel:`Name`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:81
msgid "The setup is now ready. Open your Odoo Calendar and sync with Google. The first time you do it you are redirected to Google to authorize the connection. Once back in Odoo, click the sync button again. You can click it whenever you want to synchronize your calendar."
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:68
msgid "Under the :guilabel:`Authorized JavaScript Origins` section, click :guilabel:`+ Add URI` and type your company's Odoo URL address."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:71
msgid "Under the :guilabel:`Authorized redirect URIs` section, click :guilabel:`+ Add URI` and type your company's Odoo URL address followed by */google_account/authentication*. Finally, click :guilabel:`Create` and :guilabel:`Done`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:79
msgid "After successfully creating a new API project, enabling the Google Calendar API, and generating the Google Calendar API credentials, you should now have a Client ID and Client Secret."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:83
msgid "Client ID & Client Secret"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:85
msgid "The **Client ID** and the **Client Secret** are both needed to connect Google Calendar to Odoo. Find the Client ID and the Client Secret by opening the Google Cloud Platform navigation menu and going to :menuselection:`API & Services --> Credentials --> OAuth 2.0 Client IDs`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:89
msgid "As of now you no longer have excuses to miss a meeting!"
msgid "Next, locate the credentials you just created for the Google Calendar API. Then, click on :guilabel:`Edit OAuth Client` (the pencil icon). The page will redirect to the edit page, where you can view the Client ID and the Client Secret."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:98
msgid "Setup in Odoo"
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:100
msgid "Once the Client ID and the Client Secret are located, open the Odoo database and go to :menuselection:`Settings --> General Settings --> Integrations --> Google Calendar`. Check the box next to :guilabel:`Google Calendar`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:108
msgid "Next, copy and paste the Client ID and the Client Secret from the Google Calender API Credentials page into their respective fields below the :guilabel:`Google Calendar` checkbox. Then, click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:112
msgid "Finally, open the Calendar module in Odoo and click on the :guilabel:`Google` sync button to sync Google Calendar with Odoo."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:120
msgid "The first time you sync your Google Calendar with Odoo, the page will redirect to your Google Account. Click :guilabel:`OK` and :guilabel:`Allow` to authorize Odoo to access Google Calendar."
msgstr ""
#: ../../content/applications/general/calendars/google/google_calendar_credentials.rst:127
msgid "Now, Odoo Calendar is successfully synced with Google Calendar!"
msgstr ""
#: ../../content/applications/general/calendars/outlook/outlook_calendar.rst:3
@ -2157,7 +2197,7 @@ msgid "Offering my own services"
msgstr ""
#: ../../content/applications/general/in_app_purchase.rst:68
msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`In-App Purchase </developer/misc/api/iap>`."
msgid "I am more than welcome to offer my own IAP services through Odoo Apps! It is the perfect opportunity to get recurring revenue for an ongoing service use rather than — and possibly instead of — a sole initial purchase. Please, find more information at: :doc:`In-App Purchase </developer/api/iap>`."
msgstr ""
#: ../../content/applications/general/users.rst:7

106
locale/sources/inventory_and_mrp.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-04-08 13:26+0000\n"
"POT-Creation-Date: 2022-07-22 09:36+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"
@ -1532,204 +1532,204 @@ msgid "**Sales Security Lead Time**: the purpose is to be ready shipping that ma
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:41
msgid "**Purchase Security Lead Time**: Margin of error for vendor lead times. When the system generates Purchase Orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays."
msgid "**Purchase Security Lead Time**: margin of error for vendor lead times. When the system generates Purchase Orders for procuring products, they will be scheduled that many days earlier to cope with unexpected vendor delays."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:48
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:46
msgid "**Purchase Delivery Lead Time**: this is the expected time between a PO being confirmed and the receipt of the ordered products. The **Receipt scheduled date - Vendor delivery date** is the default *PO Order By* date."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:53
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:51
msgid "**Days to Purchase**: number of days the purchasing department takes to validate a PO. If another RFQ to the same vendor is already opened, Odoo adds the line to the RFQ instead of creating a new one. Then, the specific date is set on the line."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:58
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:56
msgid "**Manufacturing Lead Time**: this is the expected time it takes to manufacture a product. This lead time is independent of the quantity to produce and does not take the routing time into account."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:63
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:61
msgid "**Manufacturing Security Lead Time**: additional time to mitigate the risk of a manufacturing delay. In case of a *Replenish to Order*, the **Delivery Order scheduled date - Manufacturing Lead Time - Manufacturing Security Lead Time** is the default *Manufacturing Order* planned date."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:70
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:68
msgid "Sales - Lead Times"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:72
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:70
msgid "In the *Sales* app, there is an option called *Delivery Date*. It allows seeing an additional field on the sales orders, *Expected Date*. This one is automatically computed based on the different lead times previously configured."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:81
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:79
msgid "If the set up *Delivery Date* is earlier than the the *Expected Date*, a warning message is displayed."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:89
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:87
msgid "But, for all of this properly working, it is still necessary to configure all the lead times that could occur."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:93
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:91
msgid "Customer Lead Time"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:95
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:93
msgid "The *Customer Lead Time* is the time needed for your product to go from your warehouse to the customer place. It can be configured on any product by going to :menuselection:`Sales --> Products --> Products`. There, open your product form, go in the inventory tab, and add your *Customer Lead Time*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:105
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:103
msgid "For example, product B is ordered on the 2nd of April but the *Customer Lead Time* is two days. In that case, the expected delivery date is the 4th of April."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:110
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:182
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:219
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:108
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:180
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:217
msgid "Security Lead Time"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:112
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:110
msgid "In sales, *Security Lead Time* corresponds to backup days to ensure you are able to deliver the products in time. The purpose is to be ready shipping earlier in order to arrive on time."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:116
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:114
msgid "The number of security days is subtracted from the calculation to compute a scheduled date earlier than the one promised to the customer."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:119
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:117
msgid "To set this up, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature *Security Lead Time for Sales*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:126
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:124
msgid "For example, product B is scheduled to be delivered on the 6th of April but the *Security Lead Time* is one day. In that case, the scheduled date for the delivery order is the 5th of April."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:131
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:129
msgid "Deliver several products"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:133
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:131
msgid "In many cases, customers order several products at the same time. Those can have different lead times but still need to be delivered, at once or separately. Fortunately, Odoo can help you handle these cases easily."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:137
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:135
msgid "From the *Other Info* tab of your *Sale Order*, you can choose between *When all products are ready* and *As soon as possible*. The first one is to deliver products at once, while the second is to deliver them separately."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:142
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:140
msgid "For example, products A and B are ordered at the same time. A has 8 lead days and B has 5. With the first option, the *Expected Date* is calculated based on the product with the most lead days, here A. If the order is confirmed on the 2nd of April, then the *Expected Date* is on the 10th of April."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:148
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:146
msgid "With the second option, the *Expected Date* is calculated based on the product with the least customer lead days. In this example, B is the product with the least lead days. So, the *Expected Date* is on the 7th of April."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:154
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:152
msgid "Purchase - Lead Times"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:157
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:155
msgid "Supplier Lead Time"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:159
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:157
msgid "The *Supplier Lead Time* is the time needed for a product you purchased to be delivered. To configure it, open a product from :menuselection:`Purchase --> Products --> Products` and add a vendor under the *Purchase* tab."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:168
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:166
msgid "By clicking on *Add a line*, a new window is displayed. You can specify the *Delivery Lead Time* there. If done so, the delivery day for every purchase of that product is now equal to *Date of the Purchase Order + Delivery Lead Time*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:178
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:176
msgid "It is possible to add different vendors and, thus, different lead times depending on the vendor."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:184
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:182
msgid "The *Security Lead Time* for purchase follows the same logic as the one for *Sales*, except that you are the customer. Then, it is the margin of error for your supplier to deliver your order."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:188
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:186
msgid "To set up *Security Lead Time* for purchase, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:196
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:194
msgid "Doing so, every time the system generates purchase orders, those are scheduled that many days earlier to cope with unexpected vendor delays."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:200
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:198
msgid "Manufacturing - Lead Times"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:203
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:201
msgid "Manufacturing Lead Time"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:205
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:203
msgid "The *Manufacturing Lead Time* is the time needed to manufacture the product. To specify it, open the *Inventory* tab of your product form and add the number of days the manufacturing takes."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:213
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:211
msgid "When working with *Manufacturing Lead Times*, the *Deadline Start* of the *MO* is **Commitment Date - Manufacturing Lead Time**. For example, the MO’s deadline start date for an order having a commitment date on the 10th of July is June 27th."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:221
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:219
msgid "The *Security Lead Time* for manufacturing allows generating manufacturing orders earlier to cope with the risk of manufacturing delays."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:225
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:223
msgid "To enable it, go to :menuselection:`Manufacturing --> Configuration --> Settings` and tick *Security Lead Time*."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:232
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:230
msgid "For example, a customer orders B with a delivery date scheduled on the 20th of June. The *Manufacturing Lead Time* is 14 days and the *Security Lead Time* is 3 days, so the manufacturing of B needs to start at the latest on the 3rd of June, which is the MO’s planned date."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:238
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:236
msgid "Global Example"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:240
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:238
msgid "Here is a configuration:"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:242
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:240
msgid "1 day of security lead time for Sales"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:243
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:241
msgid "2 days of security lead time for Manufacturing"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:244
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:242
msgid "3 days of manufacturing lead time"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:245
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:243
msgid "1 day of security lead time for Purchase"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:246
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:244
msgid "4 days of supplier lead time"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:248
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:246
msgid "Let’s say that a customer orders B on the 1st of September and the delivery date is planned to be within 20 days (September 20th). In such a scenario, here is when all the various steps are triggered."
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:252
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:250
msgid "**September 1st**: the sales order is created"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:253
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:251
msgid "**September 10th**: the deadline to order components from the supplier because of the manufacturing process (4 days of supplier lead time)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:256
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:254
msgid "**September 13th**: the reception of the product from the supplier (1 day of security lead time for Purchase)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:258
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:256
msgid "**September 14th**: the deadline start date for the manufacturing (19th - 3 days of manufacturing lead time - 2 days of security lead time for Manufacturing)"
msgstr ""
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:261
#: ../../content/applications/inventory_and_mrp/inventory/management/planning/scheduled_dates.rst:259
msgid "**September 19th**: the expected date on the delivery order form (1 day of security lead time for sales)"
msgstr ""

82
locale/sources/legal.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-03-18 14:56+0000\n"
"POT-Creation-Date: 2022-07-22 09:36+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"
@ -34,108 +34,80 @@ msgstr ""
msgid "Terms and Conditions"
msgstr ""
#: ../../content/legal.rst:128
msgid "**English**"
#: ../../content/legal.rst:29
msgid "English"
msgstr ""
#: ../../content/legal.rst:128
#: ../../content/legal.rst:30
msgid "Français"
msgstr ""
#: ../../content/legal.rst:128
#: ../../content/legal.rst:31
msgid "Nederlands"
msgstr ""
#: ../../content/legal.rst:128
#: ../../content/legal.rst:32
msgid "Deutsch"
msgstr ""
#: ../../content/legal.rst:128
#: ../../content/legal.rst:33
msgid "Español"
msgstr ""
#: ../../content/legal.rst:130
msgid "Odoo Enterprise Agreement [#ltoe1]_"
#: ../../content/legal.rst:34
msgid "Odoo Enterprise Agreement [#]_"
msgstr ""
#: ../../content/legal.rst:130
msgid "|view_enterprise_en| |download_enterprise_en|"
msgstr ""
#: ../../content/legal.rst:130
msgid "|view_enterprise_fr| |download_enterprise_fr|"
msgstr ""
#: ../../content/legal.rst:130
#: ../../content/legal.rst:130
#: ../../content/legal.rst:132
#: ../../content/legal.rst:132
#: ../../content/legal.rst:132
#: ../../content/legal.rst:47
#: ../../content/legal.rst:48
#: ../../content/legal.rst:68
#: ../../content/legal.rst:69
#: ../../content/legal.rst:70
msgid "|missing_txt| |missing_pdf|"
msgstr ""
#: ../../content/legal.rst:130
msgid "|view_enterprise_es| |download_enterprise_es|"
msgstr ""
#: ../../content/legal.rst:132
#: ../../content/legal.rst:55
#: ../../content/legal/terms/partnership.rst:5
msgid "Odoo Partnership Agreement"
msgstr ""
#: ../../content/legal.rst:132
msgid "|view_partnership_en| |download_partnership_en|"
msgstr ""
#: ../../content/legal.rst:132
msgid "|view_partnership_fr| |download_partnership_fr|"
msgstr ""
#: ../../content/legal.rst:134
#: ../../content/legal.rst:71
msgid "Terms of Sale"
msgstr ""
#: ../../content/legal.rst:134
msgid "|view_terms_of_sale_en| |download_terms_of_sale_en|"
#: ../../content/legal.rst:88
msgid "Applies to self-hosting, Odoo.SH and Odoo Cloud."
msgstr ""
#: ../../content/legal.rst:134
msgid "|view_terms_of_sale_fr| |download_terms_of_sale_fr|"
#: ../../content/legal.rst:99
msgid "`Archive of older agreements <https://drive.google.com/open?id=1skSTsdAPOBlaIWi_hUkL3tfaoi8Qdspu>`_"
msgstr ""
#: ../../content/legal.rst:136
msgid "Archive of older agreements: `Archive <https://drive.google.com/open?id=1skSTsdAPOBlaIWi_hUkL3tfaoi8Qdspu>`_"
msgstr ""
#: ../../content/legal.rst:138
msgid "Applies to self-hosting, Odoo.SH and Odoo Cloud"
msgstr ""
#: ../../content/legal.rst:142
#: ../../content/legal.rst:102
msgid "Other legal references"
msgstr ""
#: ../../content/legal.rst:144
#: ../../content/legal.rst:104
msgid "`Odoo Cloud Service Level Agreement (SLA) <https://www.odoo.com/cloud-sla>`_"
msgstr ""
#: ../../content/legal.rst:145
#: ../../content/legal.rst:105
msgid "`Odoo Cloud Acceptable Use Policy <https://www.odoo.com/acceptable-use>`_"
msgstr ""
#: ../../content/legal.rst:146
#: ../../content/legal.rst:106
msgid "`Odoo SA's Privacy Policy <https://www.odoo.com/privacy>`_"
msgstr ""
#: ../../content/legal.rst:147
#: ../../content/legal.rst:107
msgid "`Odoo SA's GDPR Compliance Guide <https://www.odoo.com/gdpr>`_"
msgstr ""
#: ../../content/legal.rst:148
#: ../../content/legal.rst:108
msgid ":ref:`cla`"
msgstr ""
#: ../../content/legal.rst:149
#: ../../content/legal.rst:109
msgid ":ref:`germany/gobd`"
msgstr ""

114
locale/sources/productivity.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-03-18 14:56+0000\n"
"POT-Creation-Date: 2022-07-22 09:36+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"
@ -24,6 +24,86 @@ msgstr ""
msgid "Discuss"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced.rst:5
msgid "Advanced"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:3
msgid "Configure ICE servers with Twilio"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:5
msgid "Odoo Discuss uses WebRTC API and peer-to-peer connections for voice and video calls. If one of the call attendees is behind a symmetric NAT, you need to configure an ICE server to establish a connection to the call attendee. To set up an ICE server, first, create a Twilio account for video calls, and then, connect that Twilio account to Odoo."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:11
msgid "Create a Twilio account"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:13
msgid "First, go to `Twilio <https://www.twilio.com_>`_ and click :guilabel:`Sign up` to create a new Twilio account. Next, enter your name and email address, create a password, and accept Twilio's terms of service. Then, click :guilabel:`Start your free trial`. Verify your email address with Twilio, as per their instructions."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:18
msgid "Next, enter your phone number into Twilio. Then, Twilio will send you an SMS text message containing a verification code. Enter the verification code into Twilio to verify your phone number."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:22
msgid "After that, Twilio redirects to a welcome page. Use the following list to answer Twilio's questions:"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:25
msgid "For :guilabel:`Which Twilio product are you here to use?`, select :guilabel:`Video`."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:26
msgid "For :guilabel:`What do you plan to build with Twilio?`, select :guilabel:`Other`."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:27
msgid "For :guilabel:`How do you want to build with Twilio?`, select :guilabel:`With no code at all`."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:28
msgid "For :guilabel:`What is your goal today?`, select :guilabel:`3rd party integrations`."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:34
msgid "If necessary, change the billing country. Finally, click :guilabel:`Get Started with Twilio`."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:37
msgid "Locate the Twilio Account SID and Auth Token"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:39
msgid "To locate the Account SID and Auth Token, go to the Twilio account dashboard. Then, click :guilabel:`Develop` on the sidebar. In the :guilabel:`Account Info` section, locate the :guilabel:`Account SID` and the :guilabel:`Auth Token`. Both of these are needed to connect Twilio to Odoo."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:49
msgid "Connect Twilio to Odoo"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:51
msgid "Open the Odoo database and go to :menuselection:`Settings --> General Settings --> Discuss`. Check the box next to :guilabel:`Use Twilio ICE servers` and enter the Twilio account's :guilabel:`Account SID` and :guilabel:`Auth Token`. Finally, click :guilabel:`Save` to apply these changes."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:61
msgid "Define a list of custom ICE servers"
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:63
msgid "This step is not required for the Twilio configuration. However, if Twilio is not configured or is not working at any given moment, Odoo will fall back on the custom ICE servers list. The user must define the list of custom ICE servers."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:67
msgid "In :menuselection:`Settings --> General Settings --> Discuss`, click the :guilabel:`ICE Servers` button under :guilabel:`Custom ICE server list`."
msgstr ""
#: ../../content/applications/productivity/discuss/advanced/ice_servers.rst:74
msgid "Odoo will redirect to the :guilabel:`ICE servers` page. Here you can define your own list of ICE servers."
msgstr ""
#: ../../content/applications/productivity/discuss/overview.rst:5
msgid "Overview"
msgstr ""
@ -1029,12 +1109,12 @@ msgid "Only a limited amount of *Company Insights* (*Lead Enrichment*) requests
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:83
#: ../../content/applications/productivity/mail_plugins/outlook.rst:78
#: ../../content/applications/productivity/mail_plugins/outlook.rst:93
msgid "Enter your Odoo database URL and click on *Login*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/gmail.rst:89
#: ../../content/applications/productivity/mail_plugins/outlook.rst:90
#: ../../content/applications/productivity/mail_plugins/outlook.rst:105
msgid "If you aren't logged into your database, enter your credentials."
msgstr ""
@ -1086,31 +1166,47 @@ msgstr ""
msgid "Open any email in your Outlook mailbox, click on the *More actions* button, and select *Odoo for Outlook*."
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."
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."
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`."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:90
msgid "Once done, the Outlook panel needs to be opened again."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:99
msgid "Click on *Allow* to open the pop-up window."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:92
#: ../../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:101
#: ../../content/applications/productivity/mail_plugins/outlook.rst:116
msgid "Add a shortcut to the plugin"
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:103
#: ../../content/applications/productivity/mail_plugins/outlook.rst:118
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:106
#: ../../content/applications/productivity/mail_plugins/outlook.rst:121
msgid "In your Outlook mailbox, click on *Settings*, then on *View all Outlook settings*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:112
#: ../../content/applications/productivity/mail_plugins/outlook.rst:127
msgid "Select *Customize actions* under *Mail*, click on *Odoo for Outlook*, and then *Save*."
msgstr ""
#: ../../content/applications/productivity/mail_plugins/outlook.rst:118
#: ../../content/applications/productivity/mail_plugins/outlook.rst:133
msgid "Open any email; the shortcut should be displayed."
msgstr ""

775
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff

81
locale/sources/services.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-03-18 14:56+0000\n"
"POT-Creation-Date: 2022-07-22 09:36+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"
@ -669,6 +669,7 @@ msgid ":doc:`reinvoice_from_project`"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/invoice_time.rst:112
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:102
msgid ":doc:`/applications/inventory_and_mrp/inventory/management/products/uom`"
msgstr ""
@ -677,31 +678,87 @@ msgid "Invoice Time Spent on Tickets (Postpaid Support Services)"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5
msgid "Directly pull the billable time you have tracked on your helpdesk tickets into sales orders and invoices through a project task. It gives you more control over what you charge your client, and it is more efficient."
msgid "The :guilabel:`Timesheet on Ticket` integration provides more control and transparency over how clients are charged, and what they're specifically billed for."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:10
msgid "Configuration"
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:8
msgid "In Odoo, the Helpdesk agent can use the ticket to record timesheets. Once a ticket is solved, the client can be billed for the time spent on the ticket. Odoo will pull from the ticket's timesheet to accurately bill the client."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit` and enable the options *Timesheet on Ticket* and *Time Reinvoicing*."
msgid "Configuration"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15
msgid "Under *Timesheet on Ticket*, choose the *Project* to which tickets (and timesheets) will be linked by default. Open its *External link* to enable the feature *Bill from tasks*."
msgid "To turn on the :guilabel:`Timesheet on Ticket` feature, go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, select a Helpdesk team, and then, click :guilabel:`Edit`. Next, enable the options :guilabel:`Timesheet on Ticket` and :guilabel:`Time Reinvoicing`. Then, click :guilabel:`Save` to apply these changes to the Helpdesk team settings."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:22
msgid "Create a sales order and an invoice"
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:20
msgid "Once the :guilabel:`Timesheet on Ticket` feature is enabled, a :guilabel:`Project` drop-down option will appear below :guilabel:`Timesheet on Ticket`. The :guilabel:`Project` drop-down option will automatically be set to a Project that Odoo created for the Helpdesk team. The tickets' timesheets will be stored in the selected Project."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:24
msgid "Now, once you have recorded the time you spent on the helpdesk ticket, under the *Timesheets* tab, access the task clicking on its name."
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:26
msgid "Create a sales order"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:31
msgid "*Create Sales Order* and proceed to create the invoice."
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:28
msgid "After a ticket comes into the pipeline, go to :menuselection:`Sales --> Create`. Then, add the customer from the ticket to the :guilabel:`Customer` field in the new quotation. In the :guilabel:`Order Lines` tab, create or select a product to charge the customer for the time spent on their Helpdesk ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:33
msgid "If creating a new product from the sales order form, first give the product a name by typing it in the :guilabel:`Product` column. Then, click :guilabel:`Create and edit`."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:36
msgid "First, in the :guilabel:`General Information` tab, set the :guilabel:`Product Type` to :guilabel:`Service` and the :guilabel:`Sales Price` to the Helpdesk agent's service rate. Then, in the :guilabel:`Sales` tab, set the :guilabel:`Service Invoicing Policy` to :guilabel:`Timesheets on tasks`. Finally, click :guilabel:`Save` to create the new product and add it to the quotation."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:41
msgid "Once the product is added, click :guilabel:`Confirm` to turn the quotation into a sales order."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:48
msgid "Record a timesheet"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:50
msgid "To record a timesheet, jump back to the Helpdesk ticket by going to the Helpdesk dashboard and clicking :guilabel:`Tickets` on the team's card (or by going to the Projects dashboard and clicking :guilabel:`Tickets` on the project card). Then, click :guilabel:`Edit` and use the :guilabel:`Timesheets` tab to record the time spent on the ticket."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:60
msgid "The ticket's timesheets can be recorded before or after the sales order is made, the order doesn't matter."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:64
msgid "Link the Helpdesk ticket to the SO"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:66
msgid "Once a timesheet is recorded, the :guilabel:`Sales Order Item` field will appear on the ticket form. To link the :abbr:`SO (Sales Order)` to the ticket, start on the ticket form and click :guilabel:`Edit`. Next, select the :abbr:`SO (Sales Order)` that was created earlier from the drop-down menu. Odoo will automatically filter the sales orders to only show sales orders that are connected to the ticket's customer. Lastly, click :guilabel:`Save` to connect the ticket and the :abbr:`SO (Sales Order)`."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:78
msgid "Modify billing rates"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:80
msgid "If a timesheet entry is recorded, but the agent does not want to bill the client for that time, go to the :guilabel:`Timesheets` tab and toggle on the visibility of the :guilabel:`Sales Order Item` column. When filling out the information for the timesheet entry, make sure to leave the non-billable timesheet entry's :guilabel:`Sales Order Item` field blank."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:85
msgid "If the agent wants to charge a different rate for a timesheet entry, first, add a new product to the connected :abbr:`SO (Sales Order)` priced at the new rate. Then, select the new product in the timesheet entry's :guilabel:`Sales Order Item` field."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:90
msgid "Create the invoice"
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:92
msgid "When the Helpdesk ticket is completed and the client is ready to be billed for time, begin by clicking the :guilabel:`Sales Order` smart button on the ticket form to navigate to the :abbr:`SO (Sales Order)`. The :guilabel:`Delivered` column should match the number of hours recorded on the ticket's timesheet. After checking and filling out the relevant information, click :guilabel:`Create Invoice` to bill the client for the time spent on the ticket. Odoo will automatically generate an invoice to send to the client and the Helpdesk ticket can officially be closed."
msgstr ""
#: ../../content/applications/services/helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:101
msgid ":doc:`invoice_time`"
msgstr ""
#: ../../content/applications/services/project.rst:8

10
locale/sources/sphinx.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-04-08 13:26+0000\n"
"POT-Creation-Date: 2022-07-22 09:36+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"
@ -28,7 +28,7 @@ msgstr ""
msgid "Ask the Odoo Community"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/header.html:11
#: ../../extensions/odoo_theme/layout_templates/header.html:10
msgid "Try Odoo for FREE"
msgstr ""
@ -131,10 +131,14 @@ msgid "You want to contribute to Odoo but don't know where to start? The tutoria
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/homepage.html:102
msgid "Write documentation"
msgid "Coding guidelines"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/homepage.html:107
msgid "Documentation"
msgstr ""
#: ../../extensions/odoo_theme/layout_templates/homepage.html:112
msgid "Content guidelines"
msgstr ""

266
locale/sources/websites.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 15.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2022-03-18 14:56+0000\n"
"POT-Creation-Date: 2022-07-22 09:36+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"
@ -34,11 +34,15 @@ msgid "Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>`
msgstr ""
#: ../../content/applications/websites/ecommerce.rst:19
msgid ":doc:`Website Documentation <website>`"
msgstr ""
#: ../../content/applications/websites/ecommerce.rst:20
#: ../../content/applications/websites/website.rst:20
msgid "`Odoo Tutorials: Website <https://www.odoo.com/slides/website-25>`_"
msgstr ""
#: ../../content/applications/websites/ecommerce.rst:20
#: ../../content/applications/websites/ecommerce.rst:21
#: ../../content/applications/websites/website.rst:21
msgid "`Odoo Tutorials: eCommerce <https://www.odoo.com/slides/ecommerce-26>`_"
msgstr ""
@ -296,59 +300,67 @@ msgid "Maximize my revenue"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:3
msgid "How to sell accessories and optional products (cross-selling)"
msgid "Cross-selling: Accessory and Optional Products"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:5
msgid "You sell computers. Why not stimulating your customers to buy a top-notch screen or an extra-warranty? That's the goal of cross-selling functionalities:"
msgid "Any sales process is an opportunity to maximize revenues. For example, with an extended warranty or some accessories."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:8
msgid "Accessory products on checkout page,"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:9
msgid "Optional products on a new *Add to Cart* screen (not installed by default)."
msgid "To do so, you can use **Cross-selling**, a sales technique consisting in selling a customer something in addition to the product or service they were originally shopping for. It is a great way to maximize the value of each one of your customers."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:12
msgid "Accessory products when checking out"
msgid "It can be done via two different features:"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:14
msgid "Accessories (e.g. for computers: mouse, keyboard) show up when the customer reviews the cart before paying."
msgid ":ref:`Accessory products <cross_selling/accessory>` on the checkout page."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:15
msgid ":ref:`Optional products <cross_selling/optional>` on a new :guilabel:`Add to Cart` screen."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:20
msgid "Select accessories in the *Sales* tab of the product detail page."
msgid "Accessory Products"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:26
msgid "There is an algorithm to figure out the best accessories to display in case several items are added to cart. If any item is the accessory of several products added to cart, it is most likely that it will be atop the list of suggested accessories."
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:22
msgid "**Accessory Products** are products that are displayed when customers review their cart before paying. As an example, you could suggest a mouse or a keyboard when someone buys a computer."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:31
msgid "Optional products when adding to cart"
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:25
msgid "To add *Accessory Products*, go to :menuselection:`Website --> Products --> Products` and, under the :guilabel:`Sales Tab`, add your products to the :guilabel:`Accessory Products` field."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:33
msgid "Optional products are directly related to the item added to cart (e.g. for computers: warranty, OS software, extra components). Whenever the main product is added to cart, such a new screen pops up as an extra step."
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:32
msgid "Now, go to your website and add the product to your cart. On the payment step, you can see your accessory products suggested to the customer."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:40
msgid "To publish optional products:"
msgid "`Odoo Tutorials: Alternative, Accessory, and Optional Products <https://www.odoo.com/slides/slide/alternative-accessory-and-optional-products-637>`_."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:42
msgid "Install *eCommerce Optional Products* addon in *Apps* menu. Remove the default filter to search on addons as well, otherwise only main apps show up."
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:46
msgid "Optional Products"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:48
msgid "Select optional items from the *Sales* tab of the product detail form."
msgid "**Optional products** are products directly related to an item. Each time the product is added to a cart, a pop-up appears, suggesting other products to buy."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:54
msgid "The quantity of optional items added to cart is the same than the main item."
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:51
msgid "To enable optional products, go to :menuselection:`Website --> Configuration --> Settings` and tick :guilabel:`Optional Products`. Then, go to :menuselection:`Website --> Products --> Products` and open the item you want to add an optional product to. In the :guilabel:`Sales tab` of that product, add as many optional products as you want."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:60
msgid "From now, when a customer adds this product to their cart, a pop-up appears and suggests also adding the optional product(s)."
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/cross_selling.rst:68
msgid ":doc:`upselling`"
msgstr ""
#: ../../content/applications/websites/ecommerce/maximizing_revenue/pricing.rst:3
@ -517,10 +529,6 @@ msgstr ""
msgid "Turn on *Alternative Products* from the *Customize* menu of the product web page."
msgstr ""
#: ../../content/applications/websites/ecommerce/publish.rst:5
msgid "Launch my website"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience.rst:5
msgid "Get paid"
msgstr ""
@ -594,7 +602,7 @@ msgid ":doc:`../../../finance/payment_acquirers`"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/payment_acquirer.rst:62
msgid ":ref:`Payment Acquirers: Place a hold on a card <payment_acquirers/capture_amount>`"
msgid ":ref:`Payment Acquirers: Place a hold on a card <payment_acquirers/features/manual_capture>`"
msgstr ""
#: ../../content/applications/websites/ecommerce/shopper_experience/portal.rst:3
@ -884,55 +892,71 @@ msgstr ""
msgid "How to track your website traffic from your Odoo Dashboard"
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:5
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:6
msgid "It is not possible anymore for new Google Analytics accounts to integrate their **Google Analytics Dashboard** inside their **Odoo Dashboard**. Google deprecated **Universal Analytics** which won't be supported anymore in `July 2023 <https://support.google.com/analytics/answer/11583528>`_. They are replacing it with **Analytics 4**. New accounts are already using it."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:12
msgid "**Analytics 4** `doesn't allow <https://issuetracker.google.com/issues/233738709?pli=1>`_ its dashboard to be integrated in external websites."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:15
msgid "You now have to check your Analytics data directly in the Google Platform as it won't be possible in Odoo anymore."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:18
msgid "Accounts created before `October 2020 <https://support.google.com/analytics/answer/11583832>`_ should still be using **Universal Analytics** and be able to integrate their dashboard on external website until the official end of support `around mid 2023 <https://developers.googleblog.com/2022/03/gis-jsweb-authz-migration.html>`_."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:23
msgid "You can follow your traffic statistics straight from your Odoo Website Dashboard thanks to Google Analytics."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:8
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:26
msgid "A preliminary step is creating a Google Analytics account and entering the tracking ID in your Website's settings (see :doc:`google_analytics`)."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:11
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:29
msgid "Go to `Google APIs platform <https://console.developers.google.com>`__ to generate Analytics API credentials. Log in with your Google account."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:14
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:32
msgid "Select Analytics API."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:19
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:37
msgid "Create a new project and give it a name (e.g. Odoo). This project is needed to store your API credentials."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:25
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:43
msgid "Enable the API."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:30
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:48
msgid "Create credentials to use in Odoo."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:35
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:53
msgid "Select *Web browser (Javascript)* as calling source and *User data* as kind of data."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:41
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:59
msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:51
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:69
msgid "Go through the Consent Screen step by entering a product name (e.g. Google Analytics in Odoo). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:56
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:74
msgid "Finally you are provided with your Client ID. Copy and paste it in Odoo."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:61
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:79
msgid "Open your Website Dashboard in Odoo and link your Analytics account to past your Client ID."
msgstr ""
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:67
#: ../../content/applications/websites/website/optimize/google_analytics_dashboard.rst:85
msgid "As a last step, authorize Odoo to access Google API."
msgstr ""
@ -1641,86 +1665,78 @@ msgid "Scalability"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:561
msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link provides an analysis of the major open source CMS and eCommerce compared to Odoo when it comes to high query volumes: `https://www.odoo.com/slides/slide/197 <https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-optimisation-197>`_"
msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:568
msgid "Todo"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:568
msgid "fix above link"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:570
#: ../../content/applications/websites/website/optimize/seo.rst:564
msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:576
#: ../../content/applications/websites/website/optimize/seo.rst:570
msgid "Search Engines Files"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:579
#: ../../content/applications/websites/website/optimize/seo.rst:573
msgid "Sitemap"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:581
#: ../../content/applications/websites/website/optimize/seo.rst:575
msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:585
#: ../../content/applications/websites/website/optimize/seo.rst:579
msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 chunks per file."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:591
#: ../../content/applications/websites/website/optimize/seo.rst:585
msgid "Every sitemap entry has 4 attributes that are computed automatically:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:593
#: ../../content/applications/websites/website/optimize/seo.rst:587
msgid "``<loc>`` : the URL of a page"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:595
#: ../../content/applications/websites/website/optimize/seo.rst:589
msgid "``<lastmod>`` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:600
#: ../../content/applications/websites/website/optimize/seo.rst:594
msgid "``<priority>`` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:607
#: ../../content/applications/websites/website/optimize/seo.rst:601
msgid "Structured Data Markup"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:609
#: ../../content/applications/websites/website/optimize/seo.rst:603
msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:614
#: ../../content/applications/websites/website/optimize/seo.rst:608
msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:617
#: ../../content/applications/websites/website/optimize/seo.rst:611
msgid "Odoo implements micro data as defined in the `schema.org <http://schema.org>`__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:627
#: ../../content/applications/websites/website/optimize/seo.rst:621
msgid "robots.txt"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:629
#: ../../content/applications/websites/website/optimize/seo.rst:623
msgid "When indexing your website, search engines take a first look at the general indexing rules of the a``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:633
#: ../../content/applications/websites/website/optimize/seo.rst:627
msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:636
#: ../../content/applications/websites/website/optimize/seo.rst:630
msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address."
msgstr ""
#: ../../content/applications/websites/website/optimize/seo.rst:640
#: ../../content/applications/websites/website/optimize/seo.rst:634
msgid "You can customize the file *robots* in :ref:`developer mode <developer-mode>` from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades."
msgstr ""
@ -1904,191 +1920,207 @@ msgstr ""
msgid ":doc:`/administration/maintain/domain_names`"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:130
#: ../../content/applications/websites/website/publish/multi_website.rst:129
msgid "If you setup an extra website and specify the domain name you will have to do three things to get this feature to work:"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:132
msgid "Setup an A-record in the DNS configuration of your hosting provider so that \"www.mywebsite2.ext\" is redirected to the IP of your Odoo instance."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:134
msgid "Create an extra Nginx ``server`` block in which you set the ``server_name`` that you've set in the :guilabel:`Website domain` field."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:136
msgid "Reload and restart your Nginx instance to use the new ``server`` block."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:139
msgid "Customize the visitor experience"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:133
#: ../../content/applications/websites/website/publish/multi_website.rst:142
msgid "The customer experience can be customized very profoundly thanks to the menu \\*Customize\\*. All the visual options available there are specific to each website. Go through the different pages to adapt them to this new audience. Focus on workflows, and automatic pages (eCommerce checkout, blogs, events, etc.) as the number of available options is higher there."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:143
#: ../../content/applications/websites/website/publish/multi_website.rst:152
msgid "Publish specific content per website"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:146
#: ../../content/applications/websites/website/publish/multi_website.rst:155
msgid "Like static pages, any content created from the front-end (product, blog post, etc.) is always only published in the current website. You can change that from the edit form view in the backend and leave the *Website* field blank. This will publish it in all the websites."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:154
#: ../../content/applications/websites/website/publish/multi_website.rst:163
msgid "Here are all the objects that you can link to *either one or all the websites*:"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:157
#: ../../content/applications/websites/website/publish/multi_website.rst:166
msgid "Products"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:159
#: ../../content/applications/websites/website/publish/multi_website.rst:168
msgid "Product Categories for eCommerce"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:161
#: ../../content/applications/websites/website/publish/multi_website.rst:170
msgid "Blogs"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:163
#: ../../content/applications/websites/website/publish/multi_website.rst:172
msgid "Slide Channels"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:165
#: ../../content/applications/websites/website/publish/multi_website.rst:174
msgid "Forums"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:167
#: ../../content/applications/websites/website/publish/multi_website.rst:176
msgid "Events"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:169
#: ../../content/applications/websites/website/publish/multi_website.rst:178
msgid "Job Positions"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:172
#: ../../content/applications/websites/website/publish/multi_website.rst:181
msgid "When you create the record from the backend and publish it, typically a product or an event, it is made available in all websites."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:176
#: ../../content/applications/websites/website/publish/multi_website.rst:185
msgid "Publish a page in all websites"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:178
#: ../../content/applications/websites/website/publish/multi_website.rst:187
msgid "A new static page is created and only made available in the current website. You can duplicate it to other websites from :menuselection:`Website --> Configuration --> Pages`. To do so, leave the *Website* field empty."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:182
#: ../../content/applications/websites/website/publish/multi_website.rst:191
msgid "If you want to duplicate it in just one other website, duplicate the page and set the new website."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:188
#: ../../content/applications/websites/website/publish/multi_website.rst:197
msgid "When you edit the page again, the change only affects the current website. A new page is duplicated and tied up to the website. The original page still being linked to all websites."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:193
#: ../../content/applications/websites/website/publish/multi_website.rst:202
msgid "By grouping pages by URL in the page manager, you quickly find the original page behind each edited page."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:200
#: ../../content/applications/websites/website/publish/multi_website.rst:209
msgid "Multi-companies"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:202
#: ../../content/applications/websites/website/publish/multi_website.rst:211
msgid "Each website can be linked to a specific company of your system, in a multi-companies environment."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:208
#: ../../content/applications/websites/website/publish/multi_website.rst:217
msgid "With such a configuration, only company-related data appear on the website (products, jobs, events, etc.)."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:211
#: ../../content/applications/websites/website/publish/multi_website.rst:220
msgid "Website editors can only view and edit the pages of the records they have access to, typically the ones belonging to their current company (and to their subsidiaries, or child companies in Odoo language). And so is it for visitors."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:217
#: ../../content/applications/websites/website/publish/multi_website.rst:226
msgid "If websites are multi-companies, you don’t change company when switching websites. To change the company and see the related content, use the company selector in the menu."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:223
#: ../../content/applications/websites/website/publish/multi_website.rst:232
msgid "Configure your eCommerce website"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:225
#: ../../content/applications/websites/website/publish/multi_website.rst:234
msgid "eCommerce is a crucial feature in the multi-websites environment. We made it so that the entire flow can be customized to fit the very audience of each website."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:230
#: ../../content/applications/websites/website/publish/multi_website.rst:239
msgid "Products only available on one website"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:232
#: ../../content/applications/websites/website/publish/multi_website.rst:241
msgid "We already saw earlier how to publish a specific record in only one website. You will find the \\*Website\\* field in the eCommerce tab of the product edit form. Empty means available in all websites."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:240
#: ../../content/applications/websites/website/publish/multi_website.rst:249
msgid "Products available on *some* websites"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:242
#: ../../content/applications/websites/website/publish/multi_website.rst:251
msgid "To make a product available on some websites, but not all of them, you should duplicate the product for each website."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:245
#: ../../content/applications/websites/website/publish/multi_website.rst:254
msgid "If you need a unique reference to manage in your inventory, you should install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each kit will link each published “virtual” product to the main reference managed in your inventory. That way, any item sold from your website will be converted into the storable item in the delivery order."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:252
#: ../../content/applications/websites/website/publish/multi_website.rst:261
msgid "Pricelists"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:254
#: ../../content/applications/websites/website/publish/multi_website.rst:263
msgid "To manage specific prices by websites, you can activate *Multiple Sales Prices per Product* in Website settings."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:257
#: ../../content/applications/websites/website/publish/multi_website.rst:266
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. See :doc:`../../ecommerce/maximizing_revenue/pricing`."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:260
#: ../../content/applications/websites/website/publish/multi_website.rst:269
msgid "If you need help. Select a website to make a pricelist only available on this website."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:266
#: ../../content/applications/websites/website/publish/multi_website.rst:275
msgid "Leaving the field empty means that you make it work in all websites if *Selectable* is selected. Otherwise, it makes it only available for backend operations of Sales and Point of Sale applications."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:271
#: ../../content/applications/websites/website/publish/multi_website.rst:280
msgid "Payment Acquirers and Delivery Methods"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:273
#: ../../content/applications/websites/website/publish/multi_website.rst:282
msgid "By default, published payment acquirers and delivery methods are deployed in all websites. You could already use specific payment acquirers per country using Geo IP by defining countries in their configuration. Now you can also do it per website by filling in the *Website* field."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:279
#: ../../content/applications/websites/website/publish/multi_website.rst:288
msgid "Customer accounts"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:281
#: ../../content/applications/websites/website/publish/multi_website.rst:290
msgid "There is a setting to choose how to manage customer accounts in Website settings. You can either allow customers to use one account through all the websites or compel them to create one account for each website. This last option is convenient if your websites shouldn’t be related to each other in the visitor mind."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:291
#: ../../content/applications/websites/website/publish/multi_website.rst:300
msgid "Technical hints for customization"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:293
#: ../../content/applications/websites/website/publish/multi_website.rst:302
msgid "If you want to publish custom objects on the website, here are a few tips to make it work with multi websites:"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:297
#: ../../content/applications/websites/website/publish/multi_website.rst:306
msgid "Sitemap: don’t forget the domain in the route to only publish"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:297
#: ../../content/applications/websites/website/publish/multi_website.rst:306
msgid "available records in each website’s sitemap."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:301
#: ../../content/applications/websites/website/publish/multi_website.rst:310
msgid "Access: you should call the method"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:300
#: ../../content/applications/websites/website/publish/multi_website.rst:309
msgid "*can_access_from_current_website* in the controller to make sure the visitor can see a record in the current website."
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:305
#: ../../content/applications/websites/website/publish/multi_website.rst:314
msgid "Search: when a list of records is displayed, don’t forget to specify"
msgstr ""
#: ../../content/applications/websites/website/publish/multi_website.rst:304
#: ../../content/applications/websites/website/publish/multi_website.rst:313
msgid "the domain to only display records available for the current website."
msgstr ""
@ -2125,7 +2157,7 @@ msgid "If you can't/don't want to locate the geoip database in ``/usr/share/GeoI
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:36
msgid ":doc:`CLI documentation </developer/misc/other/cmdline>`."
msgid ":doc:`CLI documentation </developer/cli>`."
msgstr ""
#: ../../content/applications/websites/website/publish/on-premise_geo-ip-installation.rst:39