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

[I18N] export 13.0 source terms

Browse Source
This commit is contained in:
Martin Trigaux 2020-01-16 09:49:24 +01:00
parent fe93610d45
commit 817384b0cf
25 changed files with 3165 additions and 2298 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
.tx/config
View File

@ -37,6 +37,11 @@ file_filter = locale/<lang>/LC_MESSAGES/expenses.po
source_file = locale/sources/expenses.pot
source_lang = en
[odoo-13-doc.fsm]
file_filter = locale/<lang>/LC_MESSAGES/fsm.po
source_file = locale/sources/fsm.pot
source_lang = en
[odoo-13-doc.general]
file_filter = locale/<lang>/LC_MESSAGES/general.po
source_file = locale/sources/general.pot
@ -82,6 +87,11 @@ file_filter = locale/<lang>/LC_MESSAGES/manufacturing.po
source_file = locale/sources/manufacturing.pot
source_lang = en
[odoo-13-doc.planning]
file_filter = locale/<lang>/LC_MESSAGES/planning.po
source_file = locale/sources/planning.pot
source_lang = en
[odoo-13-doc.point_of_sale]
file_filter = locale/<lang>/LC_MESSAGES/point_of_sale.po
source_file = locale/sources/point_of_sale.pot

2456
locale/sources/accounting.pot
View File

File diff suppressed because it is too large Load Diff

38
locale/sources/crm.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-22 08:57+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -85,10 +85,6 @@ msgstr ""
msgid "Here’s how, from the list view. Select the opportunities or leads you want to merge and the action button will appear. Then, you can select merge."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:66
msgid "..note::"
msgstr ""
#: ../../crm/acquire_leads/convert.rst:67
msgid "It is also possible to merge more than 2 opportunities or leads."
msgstr ""
@ -215,19 +211,19 @@ msgid "Pricing"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:51
msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost us one additional credit. Here is the pricing for this `feature <https://iap.odoo.com/iap/in-app-services/167?>`__, To buy credits you can either go to CRM > Configuration > Settings > Buy Credits; or go to Settings > In-App Purchases>View my Services"
msgid "This is an In-App Purchase feature, each generated lead will cost you one credit. If you choose to get contact information each contact will also cost us one additional credit. Here is the pricing for this `feature <https://iap.odoo.com/iap/in-app-services/167?>`__, To buy credits you can either go to :menuselection:`CRM --> Configuration --> Settings --> Buy Credits`; or go to `Settings --> In-App Purchases --> View my Services`."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:64
#: ../../crm/acquire_leads/lead_mining.rst:65
msgid "The blue box will automatically tell you how many credits are going to be consumed."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:67
#: ../../crm/acquire_leads/lead_mining.rst:68
msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:69
msgid "More information about `In-App Purchases <https://www.odoo.com/documentation/user/13.0/general/in_app_purchase/in_app_purchase.html?highlight=iap>`__, (IAP)."
#: ../../crm/acquire_leads/lead_mining.rst:71
msgid ":doc:`In-App Purchases (IAP) <../../general/in_app_purchase/in_app_purchase>`"
msgstr ""
#: ../../crm/acquire_leads/send_quotes.rst:3
@ -622,12 +618,28 @@ msgstr ""
msgid "In Odoo, the configuration should be done in the user's preferences."
msgstr ""
#: ../../crm/optimize/setup.rst:206
msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file. In our example, 1060. The SIP Password is the secret you chose in the sip.conf file. The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file."
#: ../../crm/optimize/setup.rst:210
msgid "The SIP Login/Browser's Extension is the number you configured previously in the sip.conf file (in our example: 1060)."
msgstr ""
#: ../../crm/optimize/setup.rst:212
msgid "The configuration should also be done in the sale settings under the title \"PBX Configuration\". You need to put the IP you define in the http.conf file and the WebSocket should be: ws://127.0.0.1:8088/ws. The part \"127.0.0.1\" needs to be the same as the IP defined previously and the \"8088\" is the port you defined in the http.conf file."
msgid "The SIP Password is the secret you chose in the sip.conf file."
msgstr ""
#: ../../crm/optimize/setup.rst:214
msgid "The extension of your office's phone is not a required field but it is used if you want to transfer your call from Odoo to an external phone also configured in the sip.conf file."
msgstr ""
#: ../../crm/optimize/setup.rst:217
msgid "The configuration should also be done in the General Settings under the \"Integrations\" section."
msgstr ""
#: ../../crm/optimize/setup.rst:222
msgid "The PBX Server IP should be the same as the IP you define in the http.conf file."
msgstr ""
#: ../../crm/optimize/setup.rst:224
msgid "The WebSocket should be: ws://localhost:XXXX/ws where \"localhost\" needs to be the same as the IP defined previously and \"XXXX\" needs to be the port defined in the http.conf file."
msgstr ""
#: ../../crm/performance.rst:3

64
locale/sources/db_management.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -160,7 +160,7 @@ msgstr ""
msgid "Once you are ready and you have validated all your tests, you can click again on the Upgrade button and confirm by clicking on Upgrade (the button with the little rocket!) to switch your production database to the new version. Your database will then be taken offline within the next 10 minutes and will be upgraded automatically; you receive a confirmation e-mail once the process is completed."
msgstr ""
#: ../../db_management/db_online.rst:139
#: ../../db_management/db_online.rst:140
msgid "Your database will be taken offline during the upgrade (usually between 30min up to several hours for big databases), so make sure to plan your migration during non-business hours."
msgstr ""
@ -204,51 +204,51 @@ msgstr ""
msgid "After a few seconds, you will be logged in your duplicated database. Notice that the url uses the name you chose for your duplicated database."
msgstr ""
#: ../../db_management/db_online.rst:179
#: ../../db_management/db_online.rst:180
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../db_management/db_online.rst:187
#: ../../db_management/db_online.rst:188
msgid "Rename a Database"
msgstr ""
#: ../../db_management/db_online.rst:189
#: ../../db_management/db_online.rst:190
msgid "To rename your database, make sure you are connected to the database you want to rename, access the `database management page <https://www.odoo.com/my/databases>`__ and click **Rename**. You will have to give a new name to your database, then click **Rename Database**."
msgstr ""
#: ../../db_management/db_online.rst:200
#: ../../db_management/db_online.rst:201
msgid "Deleting a Database"
msgstr ""
#: ../../db_management/db_online.rst:202
#: ../../db_management/db_online.rst:203
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../db_management/db_online.rst:204
#: ../../db_management/db_online.rst:205
msgid "When you delete your database all the data will be permanently lost. The deletion is instant and for all the Users. We advise you to do an instant backup of your database before deleting it, since the last automated daily backup may be several hours old at that point."
msgstr ""
#: ../../db_management/db_online.rst:210
#: ../../db_management/db_online.rst:211
msgid "From the `database management page <https://www.odoo.com/my/databases>`__, on the line of the database you want to delete, click on the \"Delete\" button."
msgstr ""
#: ../../db_management/db_online.rst:217
#: ../../db_management/db_online.rst:218
msgid "Read carefully the warning message that will appear and proceed only if you fully understand the implications of deleting a database:"
msgstr ""
#: ../../db_management/db_online.rst:223
#: ../../db_management/db_online.rst:224
msgid "After a few seconds, the database will be deleted and the page will reload automatically."
msgstr ""
#: ../../db_management/db_online.rst:227
#: ../../db_management/db_online.rst:228
msgid "If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../db_management/db_online.rst:229
#: ../../db_management/db_online.rst:230
msgid "It is not possible to delete a database if it is expired or linked to a Subscription. In these cases contact `Odoo Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_online.rst:233
#: ../../db_management/db_online.rst:234
msgid "If you want to delete your Account, please contact `Odoo Support <https://www.odoo.com/help>`__"
msgstr ""
@ -274,7 +274,7 @@ msgstr ""
#: ../../db_management/db_premise.rst:31
#: ../../db_management/db_premise.rst:110
#: ../../db_management/db_premise.rst:143
#: ../../db_management/db_premise.rst:138
msgid "Solutions"
msgstr ""
@ -307,7 +307,7 @@ msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../db_management/db_premise.rst:61
#: ../../db_management/db_premise.rst:176
#: ../../db_management/db_premise.rst:171
msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required."
msgstr ""
@ -359,60 +359,56 @@ msgstr ""
msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users."
msgstr ""
#: ../../db_management/db_premise.rst:115
msgid "or"
#: ../../db_management/db_premise.rst:114
msgid "**Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:117
msgid "**Deactivate users** as explained in this `Documentation <https://www.odoo.com /documentation/user/13.0/db_management/documentation.html#deactivating-users>`__ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:122
msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification <force_ping>` to make the message disappear right away."
msgstr ""
#: ../../db_management/db_premise.rst:129
#: ../../db_management/db_premise.rst:124
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:131
#: ../../db_management/db_premise.rst:126
msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:139
#: ../../db_management/db_premise.rst:134
msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired."
msgstr ""
#: ../../db_management/db_premise.rst:147
#: ../../db_management/db_premise.rst:142
msgid "Renew your subscription: follow the link and renew your subscription - note that"
msgstr ""
#: ../../db_management/db_premise.rst:146
#: ../../db_management/db_premise.rst:141
msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately."
msgstr ""
#: ../../db_management/db_premise.rst:149
#: ../../db_management/db_premise.rst:144
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:151
#: ../../db_management/db_premise.rst:146
msgid "None of those solutions worked for you? Please contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:160
#: ../../db_management/db_premise.rst:155
msgid "Duplicate a database"
msgstr ""
#: ../../db_management/db_premise.rst:162
#: ../../db_management/db_premise.rst:157
msgid "You can duplicate your database by accessing the database manager on your server (<odoo-server>/web/database/manager). In this page, you can easily duplicate your database (among other things)."
msgstr ""
#: ../../db_management/db_premise.rst:170
#: ../../db_management/db_premise.rst:165
msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line."
msgstr ""
#: ../../db_management/db_premise.rst:179
msgid "The database uuid is currently accessible from the menu **Settings > Technical > System Parameters**, we advise you to use a `uuid generator <https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button."
#: ../../db_management/db_premise.rst:174
msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator <https://www.uuidgenerator.net>`_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button."
msgstr ""
#: ../../db_management/documentation.rst:7

156
locale/sources/ecommerce.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-07 17:13+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -618,11 +618,13 @@ msgid "To perform ficticious transactions you can use fake card numbers provided
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:76
#: ../../ecommerce/shopper_experience/paypal.rst:206
msgid ":doc:`payment`"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:77
#: ../../ecommerce/shopper_experience/payment.rst:111
#: ../../ecommerce/shopper_experience/paypal.rst:207
msgid ":doc:`payment_acquirer`"
msgstr ""
@ -756,7 +758,7 @@ msgid "Odoo can also be used for more advanced payment processes like installmen
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:102
msgid "Such a customization service is made on-demand by our technical experts based on your own requirements. A business advisor can reach you out for such matter. `Contact us. <https://www.odoo.com/page/contactus>`__"
msgid "Such a customization service is made on-demand by our technical experts based on your own requirements. A business advisor can reach you out for such matter. `Contact us <https://www.odoo.com/page/contactus>`_."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:109
@ -819,23 +821,23 @@ msgstr ""
msgid "When the order is confirmed you can also have an invoice automatically issued and paid. This fully-automated made for businesses that invoice orders straight on."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53
msgid "If you choose this mode you are requested to select a payment journal in order to record payments in your books. This payment is automatically reconcilied with the invoice, marking it as paid. Select your **bank account** if you get paid immediately on your bank account. If you don't you can create a specific journal for the payment acquirer (type = Bank). That way, you can track online payments in an intermediary account of your books until you get paid into your bank account (see `How to register credit card payments <../../accounting/receivables/customer_payments/credit_cards.html>`__)."
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:54
msgid "If you choose this mode you are requested to select a payment journal in order to record payments in your books. This payment is automatically reconcilied with the invoice, marking it as paid. Select your **bank account** if you get paid immediately on your bank account. If you don't you can create a specific journal for the payment acquirer (type = Bank). That way, you can track online payments in an intermediary account of your books until you get paid into your bank account (see :doc:`../../accounting/receivables/customer_payments/credit_cards`)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:63
msgid "Capture the payment after the delivery"
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
msgid "With this mode, the order is confirmed but the amount is kept on hold. Once the delivery processed, you can capture the payment from Odoo. This mode is only available with Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:71
msgid "To capture the payment, open the transaction from the order. Then click *Capture Transaction*."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:77
msgid "With other payment acquirers, you can manage the capture in their own interfaces, not from Odoo."
msgstr ""
@ -852,213 +854,201 @@ msgid "Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:14
msgid "A business account is needed to get paid with Paypal. Create a `Paypayl Business Account <https://www.paypal.com/us/merchantsignup/applicationChecklist?signupType=CREATE_NEW_ACCOUNT&productIntentId=wp_standard>`__ or upgrade your Personal account to a Business account. Go to the Paypal settings and click on *Upgrade to a Business account*. Then follow the few configuration steps."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:18
msgid "Settings in Paypal"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:21
msgid "First, let’s see how to set up your Paypal account in order to build a seamless customer experience with Odoo."
msgid "A business account is needed to get paid with Paypal. Create a `Paypal Business Account <https://www.paypal.com/us/merchantsignup/ applicationChecklist?signupType=CREATE_NEW_ACCOUNT&productIntentId=wp_standard>`_ or upgrade your Personal account to a Business account. Go to the Paypal settings and click on *Upgrade to a Business account*. Then follow the few configuration steps."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:23
msgid "Log in and open the settings. Go to *Products & Services > Website payments* and click *Update* on *Website preferences*."
msgid "Settings in Paypal"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:29
#: ../../ecommerce/shopper_experience/paypal.rst:26
msgid "First, let’s see how to set up your Paypal account in order to build a seamless customer experience with Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:28
msgid "Log in and open the settings. Go to :menuselection:`Products & Services --> Website payments` and click **Update** on **Website preferences**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:34
msgid "Auto Return"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:31
msgid "*Auto Return* automatically redirects your customers to Odoo once the payment is processed. Check *Auto Return* and enter your domain name \"/shop/confirmation\" as *Return URL* (e.g. https://yourcompany.odoo.com/shop/confirmation)."
#: ../../ecommerce/shopper_experience/paypal.rst:36
msgid "*Auto Return* automatically redirects your customers to Odoo once the payment is processed. Check *Auto Return* and enter your domain name with the suffix ``/shop/confirmation`` as *Return URL* (e.g. ``https://yourcompany.odoo.com/shop/confirmation``)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:36
#: ../../ecommerce/shopper_experience/paypal.rst:41
msgid "This URL is requested in Paypal but not used in practice as Odoo transmits it at each transaction. Don’t worry if you manage several sales channels or Odoo databases."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:44
#: ../../ecommerce/shopper_experience/paypal.rst:49
msgid "Payment Data Transfer (PDT)"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:46
#: ../../ecommerce/shopper_experience/paypal.rst:51
msgid "*Payment Data Transfer* delivers the payment confirmation to Odoo as soon as it is processed. Without it, Odoo cannot end the sales flow. This setting must be activated as well. When saving, an *Identity Token* is generated. You will be later requested to enter it in Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:54
#: ../../ecommerce/shopper_experience/paypal.rst:59
msgid "Paypal Account Optional"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:56
#: ../../ecommerce/shopper_experience/paypal.rst:61
msgid "We advise you to not prompt customers to log in with a Paypal account when they get to pay. Let them pay with debit/credit cards as well, or you might lose some deals. Make sure this setting is turned on."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:63
#: ../../ecommerce/shopper_experience/paypal.rst:68
msgid "Instant Payment Notification (IPN)"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:65
#: ../../ecommerce/shopper_experience/paypal.rst:70
msgid "PDT sends order confirmations once and only once. As a result, your site must be running when it happens; otherwise, it will never receive the message. That’s why we advise to activate the *Instant Payment Notification* (IPN) on top. With IPN, delivery of order confirmations is virtually guaranteed since IPN resends a confirmation until your site acknowledges receipt."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:72
#: ../../ecommerce/shopper_experience/paypal.rst:77
msgid "To activate IPN, get back to *Website payments* menu and click *Update* in *Instant Payment Notification*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:75
msgid "The *Notification URL* to set is your domain name + “payment/paypal/ipn” (e.g. https://yourcompany.odoo.com/payment/paypal/ipn)."
#: ../../ecommerce/shopper_experience/paypal.rst:79
msgid "The *Notification URL* to set is your domain name + “payment/paypal/ipn” (e.g. ``https://yourcompany.odoo.com/payment/paypal/ipn``)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:81
#: ../../ecommerce/shopper_experience/paypal.rst:85
msgid "Payment Messages Format"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:83
#: ../../ecommerce/shopper_experience/paypal.rst:87
msgid "If you use accented characters (or anything else than basic Latin characters) for your customer names, addresses... you MUST configure the encoding format of the payment request sent by Odoo to Paypal."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:89
#: ../../ecommerce/shopper_experience/paypal.rst:93
msgid "If you don't configure this setting, some transactions fail without notice."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:91
#: ../../ecommerce/shopper_experience/paypal.rst:95
msgid "To do so, open:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:93
#: ../../ecommerce/shopper_experience/paypal.rst:97
msgid "`this page for a test account <https://sandbox.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:95
#: ../../ecommerce/shopper_experience/paypal.rst:99
msgid "`this page for a production account <https://www.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:97
#: ../../ecommerce/shopper_experience/paypal.rst:101
msgid "Then, click *More Options* and set the two default encoding formats as **UTF-8**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:105
#: ../../ecommerce/shopper_experience/paypal.rst:109
msgid "Your Paypal account is ready!"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:107
msgid "If you want your customers to pay without creating a Paypal account, **Paypal Account Optional** needs to be turned on."
#: ../../ecommerce/shopper_experience/paypal.rst:112
msgid "If you want your customers to pay without creating a Paypal account, *Paypal Account Optional* needs to be turned on."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:113
msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `paypal documentation. <https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/encryptedwebpayments/#encrypted-website-payments-ewp>`__"
#: ../../ecommerce/shopper_experience/paypal.rst:118
msgid "For Encrypted Website Payments & EWP_SETTINGS error, please check the `Paypal documentation <https://developer.paypal.com/docs/ classic/paypal-payments-standard/integration-guide/encryptedwebpayments/ #encrypted-website-payments-ewp>`_."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:117
#: ../../ecommerce/shopper_experience/paypal.rst:124
msgid "Settings in Odoo"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:120
#: ../../ecommerce/shopper_experience/paypal.rst:127
msgid "Activation"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:122
#: ../../ecommerce/shopper_experience/paypal.rst:129
msgid "Activate *Paypal* from the config bar of Sales, Invoicing and eCommerce apps, or from the configuration menu of *Payment Acquirers*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:126
#: ../../ecommerce/shopper_experience/paypal.rst:133
msgid "Credentials"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:128
#: ../../ecommerce/shopper_experience/paypal.rst:135
msgid "Odoo requires three Paypal credentials:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:130
#: ../../ecommerce/shopper_experience/paypal.rst:137
msgid "*Email ID* is your login email address in Paypal."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:132
msgid "*Merchant ID* can be found in the settings of your Paypal account, in *Profile > About the business*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:134
msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above."
#: ../../ecommerce/shopper_experience/paypal.rst:138
msgid "*Merchant ID* can be found in the settings of your Paypal account, in :menuselection:`Profile --> About the business`."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:140
msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:146
msgid "Transaction fees"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:142
#: ../../ecommerce/shopper_experience/paypal.rst:148
msgid "You can charge extra fees to your customers for paying with Paypal; This to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:145
#: ../../ecommerce/shopper_experience/paypal.rst:151
msgid "To activate this, go to the Configuration tab of Paypal configuration in Odoo and check *Add Extra Fees*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:151
#: ../../ecommerce/shopper_experience/paypal.rst:157
msgid "You can refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`__ to set up fees."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:154
msgid "..note:: `Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/index_en.htm>`__ are not allowed to charge extra fees for paying with credit cards."
#: ../../ecommerce/shopper_experience/paypal.rst:161
msgid "`Traders in the EU <https://europa.eu/youreurope/citizens/consumers/shopping/pricing-payments/ index_en.htm>`_ are not allowed to charge extra fees for paying with credit cards."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:158
#: ../../ecommerce/shopper_experience/paypal.rst:165
msgid "Go live!"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:160
#: ../../ecommerce/shopper_experience/paypal.rst:167
msgid "Your configuration is ready to roll. Make sure *Production* mode is on. Then publish the payment method by clicking the *Published* button right next to it."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:169
#: ../../ecommerce/shopper_experience/paypal.rst:176
msgid "Paypal is now available in your payment form available in eCommerce, Sales and Invoicing apps. Customers are redirected to Paypal website when hitting *Pay Now*. They get back to a confirmation page in Odoo once the payment is processed."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:178
#: ../../ecommerce/shopper_experience/paypal.rst:185
msgid "Test environment"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:180
#: ../../ecommerce/shopper_experience/paypal.rst:187
msgid "You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:182
#: ../../ecommerce/shopper_experience/paypal.rst:189
msgid "Log in to `Paypal Developer Site <https://developer.paypal.com/>`__ with your Paypal credentials."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:184
#: ../../ecommerce/shopper_experience/paypal.rst:191
msgid "This will create two sandbox accounts:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:186
#: ../../ecommerce/shopper_experience/paypal.rst:193
msgid "A business account (to use as merchant, e.g. `pp.merch01-facilitator@example.com <mailto:pp.merch01-facilitator@example.com>`__)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:188
#: ../../ecommerce/shopper_experience/paypal.rst:195
msgid "A default personal account (to use as shopper, e.g. `pp.merch01-buyer@example.com <mailto:pp.merch01-buyer@example.com>`__)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:190
#: ../../ecommerce/shopper_experience/paypal.rst:197
msgid "Log in to Paypal Sandbox with the merchant account and follow the same configuration instructions. Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test Environment*. Also, make sure the automatic invoicing is not activated in your eCommerce settings, to not generate invoices when a fictitious transaction is completed."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:196
#: ../../ecommerce/shopper_experience/paypal.rst:203
msgid "Run a test transaction from Odoo using the sandbox personal account."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:198
msgid "See also"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:200
msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/13.0/ecommerce/shopper_experience/payment.html>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:202
msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/13.0/ecommerce/shopper_experience/payment_acquirer.html>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their customer account"
msgstr ""

4
locale/sources/expense.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-07 17:13+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -118,7 +118,7 @@ msgid "How to submit expenses to managers"
msgstr ""
#: ../../expense/expense.rst:90
msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action > Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it."
msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action --> Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it."
msgstr ""
#: ../../expense/expense.rst:100

269
locale/sources/fsm.pot Normal file
View File

@ -0,0 +1,269 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../fsm.rst:5
msgid "Field Service"
msgstr ""
#: ../../fsm/create_quotations.rst:3
msgid "Create quotations from tasks"
msgstr ""
#: ../../fsm/create_quotations.rst:4
msgid "Allowing quotations to be created from tasks delivers a more efficient service as it allows space for preventive actions, while making the flow easy for employees."
msgstr ""
#: ../../fsm/create_quotations.rst:8
#: ../../fsm/customize_worksheets.rst:9
#: ../../fsm/onsite_tasks_from_sales_orders.rst:9
#: ../../fsm/plan_onsite.rst:8
msgid "Enable the feature"
msgstr ""
#: ../../fsm/create_quotations.rst:9
msgid "First, go to :menuselection:`Field Service --> Configuration --> Settings` and enable the option *Extra Quotations*."
msgstr ""
#: ../../fsm/create_quotations.rst:16
msgid "Second, go to :menuselection:`Configuration --> Projects` and enable *Extra Quotations*."
msgstr ""
#: ../../fsm/create_quotations.rst:21
msgid "You can now create *New Quotations* directly from your tasks."
msgstr ""
#: ../../fsm/customize_worksheets.rst:3
msgid "Customize worksheet reports"
msgstr ""
#: ../../fsm/customize_worksheets.rst:4
msgid "Personalizing your customer reports, also called *worksheets*, allows you to have different descriptions of the work for each type of intervention. It speeds up the flow for your employees while giving customers a detailed summary, which can be reviewed and signed onsite."
msgstr ""
#: ../../fsm/customize_worksheets.rst:10
msgid "Go to :menuselection:`Field Service --> Configuration` and enable :menuselection:`Worksheet Templates --> Save`."
msgstr ""
#: ../../fsm/customize_worksheets.rst:18
msgid "Designing worksheets"
msgstr ""
#: ../../fsm/customize_worksheets.rst:19
msgid "Under :menuselection:`Configuration --> Worksheet Templates`, click on *Create* and start to *Design Worksheet Template*. You will be redirected to the *Studio* application."
msgstr ""
#: ../../fsm/customize_worksheets.rst:27
msgid "With the freedom of *Studio*, drag and drop fields to create a report tailored to your needs. Once you are done, click on *Close* and get an overview of the work done."
msgstr ""
#: ../../fsm/customize_worksheets.rst:30
msgid "*Worksheets* is where you can see how many times the worksheet has been used/completed under a task. *Analysis* examines all the worksheets under that given template and generates a graph."
msgstr ""
#: ../../fsm/customize_worksheets.rst:38
msgid "`Studio Basics <https://www.odoo.com/slides/slide/studio-basics-710?fullscreen=1>`_"
msgstr ""
#: ../../fsm/invoicing_time.rst:3
msgid "Invoicing time and material to customers"
msgstr ""
#: ../../fsm/invoicing_time.rst:4
msgid "Track the exact time spent on a task and give customers the ability to sign their worksheet report onsite. Invoice customers as soon as the work is complete, leaving you, and the customer, with the confidence that they will be charged for the exact right hours and material used."
msgstr ""
#: ../../fsm/invoicing_time.rst:9
msgid "Get the exact time spent on a task"
msgstr ""
#: ../../fsm/invoicing_time.rst:10
msgid "Click on *Start* to launch the timer. You can *Pause* at any moment and *Resume* when you would like to continue."
msgstr ""
#: ../../fsm/invoicing_time.rst:17
msgid "Click on *Stop* once the work is done to confirm the total time spent and add a description."
msgstr ""
#: ../../fsm/invoicing_time.rst:24
msgid "Sign and send reports & validate stock-picking"
msgstr ""
#: ../../fsm/invoicing_time.rst:25
msgid "Now, fill your *Worksheet* and add the used products clicking on *Products*."
msgstr ""
#: ../../fsm/invoicing_time.rst:31
msgid "Click on *Start* if you need to record additional time for the same activity. The time recorded will be added to the already created and signed worksheet. Then, create a new invoice for the time added."
msgstr ""
#: ../../fsm/invoicing_time.rst:34
msgid "*Mark as done* to close the task and to invoice your intervention. It also validates the stock-picking keeping your inventory up-to-date."
msgstr ""
#: ../../fsm/invoicing_time.rst:37
msgid "*Sign Report* generates a detailed worksheet report for the customer to sign. Send it through email clicking on *Send Report*."
msgstr ""
#: ../../fsm/invoicing_time.rst:41
msgid "Invoice your time and material"
msgstr ""
#: ../../fsm/invoicing_time.rst:42
msgid "Under :menuselection:`All Tasks --> To Invoice`, find a list of all tasks marked as done but that have not been invoiced. Convenient feature as it allows accountants to easily access all finished tasks at once."
msgstr ""
#: ../../fsm/invoicing_time.rst:52
msgid "Invoice all tasks at once selecting them all and going to :menuselection:`Action --> Create Invoice`."
msgstr ""
#: ../../fsm/invoicing_time.rst:60
msgid ":doc:`../project/advanced/feedback`"
msgstr ""
#: ../../fsm/keep_track.rst:3
msgid "Keeping track of stock"
msgstr ""
#: ../../fsm/keep_track.rst:4
msgid "The integration with the Inventory application makes possible to track the material used and automatically keep your stock up to date."
msgstr ""
#: ../../fsm/keep_track.rst:8
msgid "Set up your Field Service project"
msgstr ""
#: ../../fsm/keep_track.rst:9
msgid "Go to :menuselection:`Field Service --> Configuration --> Projects` and make sure the option *Products on Tasks* is enabled."
msgstr ""
#: ../../fsm/keep_track.rst:15
msgid "Now, add the materials used in the intervention to the worksheet, and once the task is *Marked as done*, the stock-picking is automatically validated and the inventory evaluation is automatically updated."
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:3
msgid "Manage your employees’ schedules and time off"
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:4
msgid "The integration with the *Time off* application allows you to quickly see your employees’ availabilities. It will avoid conflicts and errors between employees schedules and interventions."
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:8
msgid "Effortlessly see employees’ time off"
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:9
msgid "No configuration needs to be done. Once the employees’ time has been validated in the *Time off* application, cells will be grayed for those days in your Gantt view."
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:13
msgid "It also adapts to the working calendar of the employee. Example: the employee works part-time (from Monday to Wednesday). So, Thursday and Friday will also be greyed, in addition to the weekends."
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:20
msgid "Easily manage employees’ schedules"
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:21
msgid "From the Gantt view (under *Planning by User, Project or Worksheet*), click on the plus sign to add a new task or on the magnifying glass to plan an existing one."
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:29
msgid "Unassigned tasks"
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:30
msgid "If you need to plan an intervention but you do not know yet who will take care of it, you can leave the task unassigned. It will still be shown in the Gantt view. Simply drag and drop the responsible person he can be assigned."
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:39
msgid "Create projects per team, or per working site, and have a more accurate and dynamic database."
msgstr ""
#: ../../fsm/manage_employees_schedule.rst:42
msgid ":doc:`../project/configuration/setup`"
msgstr ""
#: ../../fsm/onsite_tasks_from_sales_orders.rst:3
msgid "Create onsite interventions tasks from Sales Orders"
msgstr ""
#: ../../fsm/onsite_tasks_from_sales_orders.rst:4
msgid "By allowing your sales team to open onsite interventions tasks will create a seamless experience for your customers. It also allows them to first receive a quotation with the materials that will be used plus the service price to be approved before the work even starts."
msgstr ""
#: ../../fsm/onsite_tasks_from_sales_orders.rst:10
msgid "Go to :menuselection:`Sales --> Products --> Create` or edit an existing one. Select: under :menuselection:`General Information --> Product Type: Service`; under :menuselection:`Sales --> Service Invoicing Policy: Timesheet on task --> Service Tracking: Create a task in an existing project --> Project --> Worksheet Template --> Save`."
msgstr ""
#: ../../fsm/onsite_tasks_from_sales_orders.rst:19
msgid "Now, once you have *Confirmed* a *quotation*, a task will be created in the respective project you have chosen."
msgstr ""
#: ../../fsm/onsite_tasks_from_sales_orders.rst:28
msgid "One of the greatest benefits here is that you can have different *Worksheets Templates* under the same project and product, for example."
msgstr ""
#: ../../fsm/plan_onsite.rst:3
msgid "Plan onsite interventions from Helpdesk Tickets"
msgstr ""
#: ../../fsm/plan_onsite.rst:4
msgid "The integration with the Helpdesk application lets your helpdesk team manage interventions requests directly. It speeds up processes as you can plan field services tasks from tickets."
msgstr ""
#: ../../fsm/plan_onsite.rst:9
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> Edit` and enable :menuselection:`Onsite Interventions --> Save`."
msgstr ""
#: ../../fsm/plan_onsite.rst:15
msgid "Now once your helpdesk team needs, they have the option to *Plan Intervention* from tickets."
msgstr ""
#: ../../fsm/planning_itinerary.rst:3
msgid "Planning an itinerary"
msgstr ""
#: ../../fsm/planning_itinerary.rst:5
msgid "Having an itinerary being shown based on the chronological order of the activities and on the best route to take, makes employees’ life easier and the workload more efficient."
msgstr ""
#: ../../fsm/planning_itinerary.rst:9
msgid "Have an itinerary displayed directly in Odoo"
msgstr ""
#: ../../fsm/planning_itinerary.rst:10
msgid "Go to *Settings* and under *Map view* click on *Get token*."
msgstr ""
#: ../../fsm/planning_itinerary.rst:15
msgid "Click on :menuselection:`Start mapping for free --> fill the Username, email and password fields --> agree with their Terms of Service and Privacy Policy --> Get started`. You will be redirected to your account. Scrolling the page down you will find *Access tokens*. Copy the *Default public token*."
msgstr ""
#: ../../fsm/planning_itinerary.rst:24
msgid "Back in Odoo, paste it on :menuselection:`Token --> Save`."
msgstr ""
#: ../../fsm/planning_itinerary.rst:29
msgid "Now, your maps will show the itinerary based on the scheduled time and best route."
msgstr ""
#: ../../fsm/planning_itinerary.rst:36
msgid "This is an optional feature, as you can still have access to a map view without a Mapbox account."
msgstr ""

344
locale/sources/general.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -37,38 +37,38 @@ msgid "How to allow users to sign in with their Google account"
msgstr ""
#: ../../general/auth/google.rst:5
msgid "Connect to your Google account and go to `https://console.developers.google.com/ <https://console.developers.google.com/>`_."
msgid "Connect to your Google account and go to the `Google API Dashboard <https://console.developers.google.com/>`_."
msgstr ""
#: ../../general/auth/google.rst:7
#: ../../general/auth/google.rst:8
msgid "Click on **Create Project** and enter the project name and other details."
msgstr ""
#: ../../general/auth/google.rst:15
#: ../../general/auth/google.rst:16
msgid "Click on **Use Google APIs**"
msgstr ""
#: ../../general/auth/google.rst:20
#: ../../general/auth/google.rst:21
msgid "On the left side menu, select the sub menu **Credentials** (from **API Manager**) then select **OAuth consent screen**."
msgstr ""
#: ../../general/auth/google.rst:25
#: ../../general/auth/google.rst:26
msgid "Fill in your address, email and the product name (for example odoo) and then save."
msgstr ""
#: ../../general/auth/google.rst:30
#: ../../general/auth/google.rst:31
msgid "Then click on **Add Credentials** and select the second option (OAuth 2.0 Client ID)."
msgstr ""
#: ../../general/auth/google.rst:38
#: ../../general/auth/google.rst:39
msgid "Check that the application type is set on **Web Application**. Now configure the allowed pages on which you will be redirected."
msgstr ""
#: ../../general/auth/google.rst:40
#: ../../general/auth/google.rst:41
msgid "To achieve this, complete the field **Authorized redirect URIs**. Copy paste the following link in the box: http://mydomain.odoo.com/auth_oauth/signin. Then click on **Create**"
msgstr ""
#: ../../general/auth/google.rst:48
#: ../../general/auth/google.rst:49
msgid "Once done, you receive two information (your Client ID and Client Secret). You have to insert your Client ID in the **General Settings**."
msgstr ""
@ -137,7 +137,7 @@ msgid "Remove columns you don't need. We advise to not remove the *ID* one (see
msgstr ""
#: ../../general/base_import/adapt_template.rst:15
#: ../../general/base_import/import_faq.rst:26
#: ../../general/base_import/import_faq.rst:25
msgid "Set a unique ID to every single record by dragging down the ID sequencing."
msgstr ""
@ -201,319 +201,319 @@ msgstr ""
msgid "There you are provided with templates you can easily populate with your own data. Such templates can be imported in one click; The data mapping is already done."
msgstr ""
#: ../../general/base_import/import_faq.rst:22
#: ../../general/base_import/import_faq.rst:21
msgid "How to adapt the template"
msgstr ""
#: ../../general/base_import/import_faq.rst:24
#: ../../general/base_import/import_faq.rst:23
msgid "Add, remove and sort columns to fit at best your data structure."
msgstr ""
#: ../../general/base_import/import_faq.rst:25
#: ../../general/base_import/import_faq.rst:24
msgid "We advise to not remove the **ID** one (see why in the next section)."
msgstr ""
#: ../../general/base_import/import_faq.rst:31
#: ../../general/base_import/import_faq.rst:30
msgid "When you add a new column, Odoo might not be able to map it automatically if its label doesn't fit any field in Odoo. Don't worry! You can map new columns manually when you test the import. Search the list for the corresponding field."
msgstr ""
#: ../../general/base_import/import_faq.rst:39
#: ../../general/base_import/import_faq.rst:38
msgid "Then, use this field's label in your file in order to make it work straight on the very next time."
msgstr ""
#: ../../general/base_import/import_faq.rst:44
#: ../../general/base_import/import_faq.rst:43
msgid "How to import from another application"
msgstr ""
#: ../../general/base_import/import_faq.rst:46
#: ../../general/base_import/import_faq.rst:45
msgid "In order to re-create relationships between different records, you should use the unique identifier from the original application and map it to the **ID** (External ID) column in Odoo. When you import another record that links to the first one, use **XXX/ID** (XXX/External ID) to the original unique identifier. You can also find this record using its name but you will be stuck if at least 2 records have the same name."
msgstr ""
#: ../../general/base_import/import_faq.rst:54
#: ../../general/base_import/import_faq.rst:53
msgid "The **ID** will also be used to update the original import if you need to re-import modified data later, it's thus good practice to specify it whenever possible."
msgstr ""
#: ../../general/base_import/import_faq.rst:60
#: ../../general/base_import/import_faq.rst:59
msgid "I cannot find the field I want to map my column to"
msgstr ""
#: ../../general/base_import/import_faq.rst:62
#: ../../general/base_import/import_faq.rst:61
msgid "Odoo tries to find with some heuristic, based on the first ten lines of the files, the type of field for each column inside your file. For example if you have a column only containing numbers, only the fields that are of type *Integer* will be displayed for you to choose from. While this behavior might be good and easy for most cases, it is also possible that it goes wrong or that you want to map your column to a field that is not proposed by default."
msgstr ""
#: ../../general/base_import/import_faq.rst:71
#: ../../general/base_import/import_faq.rst:70
msgid "If that happens, you just have to check the ** Show fields of relation fields (advanced)** option, you will then be able to choose from the complete list of fields for each column."
msgstr ""
#: ../../general/base_import/import_faq.rst:79
#: ../../general/base_import/import_faq.rst:78
msgid "Where can I change the date import format?"
msgstr ""
#: ../../general/base_import/import_faq.rst:81
#: ../../general/base_import/import_faq.rst:80
msgid "Odoo can automatically detect if a column is a date, and it will try to guess the date format from a set of most commonly used date formats. While this process can work for many date formats, some date formats will not be recognized. This can cause confusion due to day-month inversions; it is difficult to guess which part of a date format is the day and which part is the month in a date such as '01-03-2016'."
msgstr ""
#: ../../general/base_import/import_faq.rst:83
#: ../../general/base_import/import_faq.rst:86
msgid "To view which date format Odoo has found from your file you can check the **Date Format** that is shown when clicking on **Options** under the file selector. If this format is incorrect you can change it to your liking using the *ISO 8601* to define the format."
msgstr ""
#: ../../general/base_import/import_faq.rst:86
#: ../../general/base_import/import_faq.rst:91
msgid "If you are importing an excel (.xls, .xlsx) file, you can use date cells to store dates as the display of dates in excel is different from the way it is stored. That way you will be sure that the date format is correct in Odoo whatever your locale date format is."
msgstr ""
#: ../../general/base_import/import_faq.rst:91
#: ../../general/base_import/import_faq.rst:96
msgid "Can I import numbers with currency sign (e.g.: $32.00)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:93
#: ../../general/base_import/import_faq.rst:98
msgid "Yes, we fully support numbers with parenthesis to represent negative sign as well as numbers with currency sign attached to them. Odoo also automatically detect which thousand/decimal separator you use (you can change those under **options**). If you use a currency symbol that is not known to Odoo, it might not be recognized as a number though and it will crash."
msgstr ""
#: ../../general/base_import/import_faq.rst:95
#: ../../general/base_import/import_faq.rst:103
msgid "Examples of supported numbers (using thirty-two thousands as an example):"
msgstr ""
#: ../../general/base_import/import_faq.rst:97
#: ../../general/base_import/import_faq.rst:105
msgid "32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:98
#: ../../general/base_import/import_faq.rst:106
msgid "32000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:99
#: ../../general/base_import/import_faq.rst:107
msgid "32,000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:100
#: ../../general/base_import/import_faq.rst:108
msgid "-32000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:101
#: ../../general/base_import/import_faq.rst:109
msgid "(32000.00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:102
#: ../../general/base_import/import_faq.rst:110
msgid "$ 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:103
#: ../../general/base_import/import_faq.rst:111
msgid "(32000.00 €)"
msgstr ""
#: ../../general/base_import/import_faq.rst:105
#: ../../general/base_import/import_faq.rst:113
msgid "Example that will not work:"
msgstr ""
#: ../../general/base_import/import_faq.rst:107
#: ../../general/base_import/import_faq.rst:115
msgid "ABC 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:108
#: ../../general/base_import/import_faq.rst:116
msgid "$ (32.000,00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:113
#: ../../general/base_import/import_faq.rst:119
msgid "What can I do when the Import preview table isn't displayed correctly?"
msgstr ""
#: ../../general/base_import/import_faq.rst:115
#: ../../general/base_import/import_faq.rst:121
msgid "By default the Import preview is set on commas as field separators and quotation marks as text delimiters. If your csv file does not have these settings, you can modify the File Format Options (displayed under the Browse CSV file bar after you select your file)."
msgstr ""
#: ../../general/base_import/import_faq.rst:117
#: ../../general/base_import/import_faq.rst:125
msgid "Note that if your CSV file has a tabulation as separator, Odoo will not detect the separations. You will need to change the file format options in your spreadsheet application. See the following question."
msgstr ""
#: ../../general/base_import/import_faq.rst:122
#: ../../general/base_import/import_faq.rst:130
msgid "How can I change the CSV file format options when saving in my spreadsheet application?"
msgstr ""
#: ../../general/base_import/import_faq.rst:124
msgid "If you edit and save CSV files in speadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in 'Save As' dialog box > Check the box 'Edit filter settings' > Save)."
msgstr ""
#: ../../general/base_import/import_faq.rst:126
msgid "Microsoft Excel will allow you to modify only the encoding when saving (in 'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)."
msgstr ""
#: ../../general/base_import/import_faq.rst:131
msgid "What's the difference between Database ID and External ID?"
msgstr ""
#: ../../general/base_import/import_faq.rst:133
msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides 3 mechanisms. You must use one and only one mechanism per field you want to import."
msgstr ""
#: ../../general/base_import/import_faq.rst:135
msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:"
#: ../../general/base_import/import_faq.rst:132
msgid "If you edit and save CSV files in spreadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in :menuselection:`'Save As' dialog box --> Check the box 'Edit filter settings' --> Save`)."
msgstr ""
#: ../../general/base_import/import_faq.rst:137
msgid "Country: the name or code of the country"
msgstr ""
#: ../../general/base_import/import_faq.rst:138
msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column"
msgstr ""
#: ../../general/base_import/import_faq.rst:139
msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)"
msgid "Microsoft Excel will allow you to modify only the encoding when saving (in :menuselection:`'Save As' dialog box --> click 'Tools' dropdown list --> Encoding tab`)."
msgstr ""
#: ../../general/base_import/import_faq.rst:141
msgid "For the country Belgium, you can use one of these 3 ways to import:"
msgid "What's the difference between Database ID and External ID?"
msgstr ""
#: ../../general/base_import/import_faq.rst:143
msgid "Country: Belgium"
msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides three mechanisms. You must use one and only one mechanism per field you want to import."
msgstr ""
#: ../../general/base_import/import_faq.rst:144
msgid "Country/Database ID: 21"
msgstr ""
#: ../../general/base_import/import_faq.rst:145
msgid "Country/External ID: base.be"
msgstr ""
#: ../../general/base_import/import_faq.rst:147
msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:"
msgstr ""
#: ../../general/base_import/import_faq.rst:149
msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually."
#: ../../general/base_import/import_faq.rst:148
msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:150
msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)"
msgid "Country: the name or code of the country"
msgstr ""
#: ../../general/base_import/import_faq.rst:151
msgid "Use Country/External ID: Use External ID when you import data from a third party application."
msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column"
msgstr ""
#: ../../general/base_import/import_faq.rst:153
msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories."
#: ../../general/base_import/import_faq.rst:152
msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)"
msgstr ""
#: ../../general/base_import/import_faq.rst:155
msgid "`CSV file for categories <../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_."
msgid "For the country Belgium, you can use one of these 3 ways to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:157
msgid "`CSV file for Products <../../_static/example_files/External_id_3rd_party_application_products.csv>`_."
msgid "Country: Belgium"
msgstr ""
#: ../../general/base_import/import_faq.rst:158
msgid "Country/Database ID: 21"
msgstr ""
#: ../../general/base_import/import_faq.rst:159
msgid "Country/External ID: base.be"
msgstr ""
#: ../../general/base_import/import_faq.rst:161
msgid "What can I do if I have multiple matches for a field?"
msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:"
msgstr ""
#: ../../general/base_import/import_faq.rst:163
msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy."
#: ../../general/base_import/import_faq.rst:164
msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually."
msgstr ""
#: ../../general/base_import/import_faq.rst:165
msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'."
#: ../../general/base_import/import_faq.rst:166
msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)"
msgstr ""
#: ../../general/base_import/import_faq.rst:170
msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?"
#: ../../general/base_import/import_faq.rst:169
msgid "Use Country/External ID: Use External ID when you import data from a third party application."
msgstr ""
#: ../../general/base_import/import_faq.rst:172
msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file."
#: ../../general/base_import/import_faq.rst:171
msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories."
msgstr ""
#: ../../general/base_import/import_faq.rst:174
msgid "`CSV file for Manufacturer, Retailer <../../_static/example_files/m2m_customers_tags.csv>`_."
#: ../../general/base_import/import_faq.rst:176
msgid ":download:`CSV file for categories <../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`."
msgstr ""
#: ../../general/base_import/import_faq.rst:179
msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?"
msgid ":download:`CSV file for Products <../../_static/example_files/External_id_3rd_party_application_products.csv>`."
msgstr ""
#: ../../general/base_import/import_faq.rst:181
msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an addtional row that does not have any information in the fields relative to the order. As an example, here is purchase.order_functional_error_line_cant_adpat.CSV file of some quotations you can import, based on demo data."
#: ../../general/base_import/import_faq.rst:183
msgid "What can I do if I have multiple matches for a field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:184
msgid "`File for some Quotations <../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_."
#: ../../general/base_import/import_faq.rst:185
msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy."
msgstr ""
#: ../../general/base_import/import_faq.rst:186
msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:"
#: ../../general/base_import/import_faq.rst:191
msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'."
msgstr ""
#: ../../general/base_import/import_faq.rst:188
msgid "`Purchase orders with their respective purchase order lines <../../_static/example_files/o2m_purchase_order_lines.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:190
msgid "The following CSV file shows how to import customers and their respective contacts:"
msgstr ""
#: ../../general/base_import/import_faq.rst:192
msgid "`Customers and their respective contacts <../../_static/example_files/o2m_customers_contacts.csv>`_."
#: ../../general/base_import/import_faq.rst:195
msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:197
msgid "Can I import several times the same record?"
msgstr ""
#: ../../general/base_import/import_faq.rst:199
msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very usefull as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not."
msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file."
msgstr ""
#: ../../general/base_import/import_faq.rst:201
msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application."
msgid ":download:`CSV file for Manufacturer, Retailer <../../_static/example_files/m2m_customers_tags.csv>`"
msgstr ""
#: ../../general/base_import/import_faq.rst:206
msgid "What happens if I do not provide a value for a specific field?"
#: ../../general/base_import/import_faq.rst:205
msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:208
msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value."
#: ../../general/base_import/import_faq.rst:207
msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an additional row that does not have any information in the fields relative to the order. As an example, here is ``purchase.order_functional_error_line_cant_adpat.CSV`` file of some quotations you can import, based on demo data."
msgstr ""
#: ../../general/base_import/import_faq.rst:213
msgid "How to export/import different tables from an SQL application to Odoo?"
msgstr ""
#: ../../general/base_import/import_faq.rst:215
msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)."
#: ../../general/base_import/import_faq.rst:214
msgid ":download:`File for some Quotations <../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`."
msgstr ""
#: ../../general/base_import/import_faq.rst:217
msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique accoss all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')"
msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:"
msgstr ""
#: ../../general/base_import/import_faq.rst:219
msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a <a href=\"/base_import/static/csv/database_import_test.sql\">dump of such a PostgreSQL database</a>)"
#: ../../general/base_import/import_faq.rst:220
msgid ":download:`Purchase orders with their respective purchase order lines <../../_static/example_files/o2m_purchase_order_lines.csv>`."
msgstr ""
#: ../../general/base_import/import_faq.rst:221
msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:"
#: ../../general/base_import/import_faq.rst:223
msgid "The following CSV file shows how to import customers and their respective contacts:"
msgstr ""
#: ../../general/base_import/import_faq.rst:227
msgid "This SQL command will create the following CSV file::"
#: ../../general/base_import/import_faq.rst:225
msgid ":download:`Customers and their respective contacts <../../_static/example_files/o2m_customers_contacts.csv>`."
msgstr ""
#: ../../general/base_import/import_faq.rst:234
msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:"
#: ../../general/base_import/import_faq.rst:229
msgid "Can I import several times the same record?"
msgstr ""
#: ../../general/base_import/import_faq.rst:231
msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very usefull as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not."
msgstr ""
#: ../../general/base_import/import_faq.rst:236
msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application."
msgstr ""
#: ../../general/base_import/import_faq.rst:240
msgid "It will produce the following CSV file::"
msgid "What happens if I do not provide a value for a specific field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:248
msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the orignial database)."
#: ../../general/base_import/import_faq.rst:242
msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value."
msgstr ""
#: ../../general/base_import/import_faq.rst:250
#: ../../general/base_import/import_faq.rst:247
msgid "How to export/import different tables from an SQL application to Odoo?"
msgstr ""
#: ../../general/base_import/import_faq.rst:249
msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)."
msgstr ""
#: ../../general/base_import/import_faq.rst:253
msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique across all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')"
msgstr ""
#: ../../general/base_import/import_faq.rst:259
msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a :download:`dump of such a PostgreSQL database <../../_static/example_files/database_import_test.sql>`)"
msgstr ""
#: ../../general/base_import/import_faq.rst:264
msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:"
msgstr ""
#: ../../general/base_import/import_faq.rst:270
msgid "This SQL command will create the following CSV file:"
msgstr ""
#: ../../general/base_import/import_faq.rst:279
msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:"
msgstr ""
#: ../../general/base_import/import_faq.rst:285
msgid "It will produce the following CSV file:"
msgstr ""
#: ../../general/base_import/import_faq.rst:295
msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the original database)."
msgstr ""
#: ../../general/base_import/import_faq.rst:301
msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two CSV files, you will have 4 contacts and 3 companies. (the firsts two contacts are linked to the first company). You must first import the companies and then the persons."
msgstr ""
@ -525,68 +525,68 @@ msgstr ""
msgid "General guide about In-App Purchase (IAP) Services"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:4
#: ../../general/in_app_purchase/in_app_purchase.rst:5
msgid "In-App Purchases (IAP) gives access to additional services through Odoo. For instance, it allows me to send SMS Text Messages or to send Invoices by post directly from my database."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:7
#: ../../general/in_app_purchase/in_app_purchase.rst:9
msgid "Buying Credits"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:8
msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to *Settings> Odoo IAP > View my Services*."
#: ../../general/in_app_purchase/in_app_purchase.rst:11
msgid "Each IAP Service relies on prepaid credits to work and has its own pricing. To consult my current balance or to recharge my account, go to :menuselection:`Settings --> Odoo IAP --> View my Services`."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:13
#: ../../general/in_app_purchase/in_app_purchase.rst:19
msgid "If I am on Odoo Online (SAAS) and have the Enterprise version, I benefit from free credits to test our IAP features."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:16
#: ../../general/in_app_purchase/in_app_purchase.rst:23
msgid "IAP accounts"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:17
msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones by going to *Settings app > Activate the Developer Mode > Technical Settings > IAP Accoun*."
#: ../../general/in_app_purchase/in_app_purchase.rst:25
msgid "Credits to use IAP services are stored on IAP accounts, which are specific to each service and database. By default, IAP accounts are common to all companies, but can be restricted to specific ones by going to :menuselection:`Settings app --> Activate the Developer Mode --> Technical Settings --> IAP Account`."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:23
#: ../../general/in_app_purchase/in_app_purchase.rst:34
msgid "IAP Portal"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:24
msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from *Settings app > Odoo IAP > View my Services*. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low."
#: ../../general/in_app_purchase/in_app_purchase.rst:36
msgid "The IAP Portal is a platform regrouping my IAP Services. It is accessible from :menuselection:`Settings app --> Odoo IAP --> View my Services`. From there, I can view my current balance, recharge my credits, review my consumption and set a reminder to when credits are low."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:30
#: ../../general/in_app_purchase/in_app_purchase.rst:44
msgid "Get notified when credits are low"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:31
msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through *Settings app> Odoo IAP > View my Services*, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!"
#: ../../general/in_app_purchase/in_app_purchase.rst:46
msgid "To be notified when it’s time to recharge my credits, I’ll go to my IAP Portal through :menuselection:`Settings app --> Odoo IAP --> View my Services`, unfold a service and mark the Receive threshold warning option. Then, I’ll provide a minimum amount of credits and email addresses. Now, every time that the limit is reached, an automatic reminder will be sent to by email!"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:38
#: ../../general/in_app_purchase/in_app_purchase.rst:56
msgid "IAP services available"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:39
#: ../../general/in_app_purchase/in_app_purchase.rst:58
msgid "Different services are available depending on the hosting type of your Database:"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:41
#: ../../general/in_app_purchase/in_app_purchase.rst:60
msgid "*Odoo Online (SAAS)*: only the IAP services provided by Odoo can be used (i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:43
#: ../../general/in_app_purchase/in_app_purchase.rst:62
msgid "*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by Odoo and by third-party apps can be used."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:46
#: ../../general/in_app_purchase/in_app_purchase.rst:66
msgid "Offering my own services"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:47
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: `In-App Purchase <https://www.odoo.com/documentation/master/webservices/iap.html>`_"
#: ../../general/in_app_purchase/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: `In-App Purchase <https://www.odoo.com/documentation/13.0/webservices/iap.html>`_"
msgstr ""
#: ../../general/odoo_basics.rst:3
@ -618,14 +618,14 @@ msgid "When you’re done editing the page and have clicked on **SAVE**, an invi
msgstr ""
#: ../../general/odoo_basics/add_user.rst:32
msgid "Remember that each additional user will increase your subscription fees. Refer to our `*Pricing page* <https://www.odoo.com/pricing>`__ for more information."
msgid "Remember that each additional user will increase your subscription fees. Refer to our `Pricing page <https://www.odoo.com/pricing>`_ for more information."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:39
msgid "You can also add a new user on the fly from your dashboard. From the above screenshot, enter the email address of the user you would like to add and click on **INVITE**. The user will receive an email invite containing a link to set his password. You will then be able to define his accesses rights under the :menuselection:`Settings --> Users menu`."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:45
#: ../../general/odoo_basics/add_user.rst:46
msgid "`Deactivating Users <../../db_management/documentation.html#deactivating-users>`_"
msgstr ""

112
locale/sources/getting_started.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -25,7 +25,7 @@ msgid "This document summarizes Odoo Online's services, our Success Pack impleme
msgstr ""
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:14
@ -45,178 +45,178 @@ msgid "**Meetings optimization**: The Odoo consultant is not involved in the pro
msgstr ""
#: ../../getting_started/documentation.rst:39
msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the `Odoo documentation <http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the :doc:`Odoo documentation <../index>`, `The elearning platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:51
msgid "To make sure all the stakeholders involved are always aligned, it is necessary to define and to make the project scope evolve as long as the project implementation is pursuing."
msgstr ""
#: ../../getting_started/documentation.rst:53
#: ../../getting_started/documentation.rst:55
msgid "**A clear definition of the initial project scope**: A clear definition of the initial needs is crucial to ensure the project is running smoothly. Indeed, when all the stakeholders share the same vision, the evolution of the needs and the resulting decision-making process are more simple and more clear."
msgstr ""
#: ../../getting_started/documentation.rst:59
#: ../../getting_started/documentation.rst:61
msgid "**Phasing the project**: Favoring an implementation in several coherent phases allowing regular production releases and an evolving takeover of Odoo by the end users have demonstrated its effectiveness over time. This approach also helps to identify gaps and apply corrective actions early in the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
#: ../../getting_started/documentation.rst:68
msgid "**Adopting standard features as a priority**: Odoo offers a great environment to implement slight improvements (customizations) or more important ones (developments). Nevertheless, adoption of the standard solution will be preferred as often as possible in order to optimize project delivery times and provide the user with a long-term stability and fluid scalability of his new tool. Ideally, if an improvement of the software should still be realized, its implementation will be carried out after an experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
#: ../../getting_started/documentation.rst:82
msgid "Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
#: ../../getting_started/documentation.rst:84
msgid "The gap between the reality of an implementation and the expectations of future users is a crucial factor. Three important aspects must be taken into account from the beginning of the project:"
msgstr ""
#: ../../getting_started/documentation.rst:86
#: ../../getting_started/documentation.rst:88
msgid "**Align with the project approach**: Both a clear division of roles and responsibilities and a clear description of the operating modes (validation, problem-solving, etc.) are crucial to the success of an Odoo implementation. It is therefore strongly advised to take the necessary time at the beginning of the project to align with these topics and regularly check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:94
#: ../../getting_started/documentation.rst:96
msgid "**Focus on the project success, not on the ideal solution**: The main goal of the SPoC and the Consultant is to carry out the project entrusted to them in order to provide the most effective solution to meet the needs expressed. This goal can sometimes conflict with the end user's vision of an ideal solution. In that case, the SPoC and the consultant will apply the 80-20 rule: focus on 80% of the expressed needs and take out the remaining 20% of the most disadvantageous objectives in terms of cost/benefit ratio (those proportions can of course change over time). Therefore, it will be considered acceptable to integrate a more time-consuming manipulation if a global relief is noted. Changes in business processes may also be proposed to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:108
#: ../../getting_started/documentation.rst:110
msgid "**Specifications are always EXPLICIT**: Gaps between what is expected and what is delivered are often a source of conflict in a project. In order to avoid being in this delicate situation, we recommend using several types of tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:113
#: ../../getting_started/documentation.rst:115
msgid "**The GAP Analysis**: The comparison of the request with the standard features proposed by Odoo will make it possible to identify the gap to be filled by developments/customizations or changes in business processes."
msgstr ""
#: ../../getting_started/documentation.rst:118
#: ../../getting_started/documentation.rst:120
msgid "**The User Story**: This technique clearly separates the responsibilities between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, and the Consultant who will provide a response to the HOW."
msgstr ""
#: ../../getting_started/documentation.rst:126
#: ../../getting_started/documentation.rst:128
msgid "`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A simplified version, a prototype of what is expected to agree on the main lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
#: ../../getting_started/documentation.rst:132
msgid "**The Mockup**: In the same idea as the Proof of Concept, it will align with the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:133
#: ../../getting_started/documentation.rst:135
msgid "To these tools will be added complete transparency on the possibilities and limitations of the software and/or its environment so that all project stakeholders have a clear idea of what can be expected/achieved in the project. We will, therefore, avoid basing our work on hypotheses without verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:139
#: ../../getting_started/documentation.rst:141
msgid "*This list can, of course, be completed by other tools that would more adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:145
#: ../../getting_started/documentation.rst:147
msgid "The purpose of the QuickStart methodology is to ensure quick ownership of the tool for end users. Effective communication is therefore crucial to the success of this approach. Its optimization will, therefore, lead us to follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:150
#: ../../getting_started/documentation.rst:152
msgid "**Sharing the project management documentation**: The best way to ensure that all stakeholders in a project have the same level of knowledge is to provide direct access to the project's tracking document (Project Organizer). This document will contain at least a list of tasks to be performed as part of the implementation for which the priority level and the manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:158
#: ../../getting_started/documentation.rst:160
msgid "The Project Organizer is a shared project tracking tool that allows both detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
#: ../../getting_started/documentation.rst:162
#: ../../getting_started/documentation.rst:164
msgid "**Report essential information**: In order to minimize the documentation time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:166
#: ../../getting_started/documentation.rst:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:168
#: ../../getting_started/documentation.rst:170
msgid "Project statuses will only be established when an important milestone is reached;"
msgstr ""
#: ../../getting_started/documentation.rst:171
#: ../../getting_started/documentation.rst:173
msgid "Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
#: ../../getting_started/documentation.rst:177
msgid "Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:177
#: ../../getting_started/documentation.rst:179
msgid "Odoo is a software known for its flexibility and its important evolution capacity. However, a significant amount of development contradicts a fast and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""
#: ../../getting_started/documentation.rst:182
#: ../../getting_started/documentation.rst:184
msgid "**Develop only for a good reason**: The decision to develop must always be taken when the cost-benefit ratio is positive (saving time on a daily basis, etc.). For example, it will be preferable to realize a significant development in order to reduce the time of a daily operation, rather than an operation to be performed only once a quarter. It is generally accepted that the closer the solution is to the standard, the lighter and more fluid the migration process, and the lower the maintenance costs for both parties. In addition, experience has shown us that 60% of initial development requests are dropped after a few weeks of using standard Odoo (see \"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:194
#: ../../getting_started/documentation.rst:196
msgid "**Replace, without replicate**: There is a good reason for the decision to change the management software has been made. In this context, the moment of implementation is THE right moment to accept and even be a change initiator both in terms of how the software will be used and at the level of the business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:204
#: ../../getting_started/documentation.rst:206
msgid "Whether developments are made or not in the implementation, it is crucial to test and validate the correspondence of the solution with the operational needs of the company."
msgstr ""
#: ../../getting_started/documentation.rst:208
#: ../../getting_started/documentation.rst:210
msgid "**Role distribution**: In this context, the Consultant will be responsible for delivering a solution corresponding to the defined specifications; the SPoC will have to test and validate that the solution delivered meets the requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
#: ../../getting_started/documentation.rst:216
msgid "**Change management**: When a change needs to be made to the solution, the noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:218
#: ../../getting_started/documentation.rst:220
msgid "A difference between the specification and the delivered solution - This is a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:222
#: ../../getting_started/documentation.rst:225
msgid "A difference between the specification and the imperatives of operational reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
#: ../../getting_started/documentation.rst:231
msgid "Importing the history of transactional data is an important issue and must be answered appropriately to allow the project running smoothly. Indeed, this task can be time-consuming and, if its priority is not well defined, prevent production from happening in time. To do this as soon as possible, it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:234
#: ../../getting_started/documentation.rst:237
msgid "**Not to import anything**: It often happens that after reflection, importing data history is not considered necessary, these data being, moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
#: ../../getting_started/documentation.rst:239
#: ../../getting_started/documentation.rst:242
msgid "**To import a limited amount of data before going into production**: When the data history relates to information being processed (purchase orders, invoices, open projects, for example), the need to have this information available from the first day of use in production is real. In this case, the import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:246
#: ../../getting_started/documentation.rst:249
msgid "**To import after production launch**: When the data history needs to be integrated with Odoo mainly for reporting purposes, it is clear that these can be integrated into the software retrospectively. In this case, the production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
msgid "When your project is put in production, our support teams take care of your questions or technical issues."
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:258
msgid "When your project is put in production, our support teams take care of your questions or technical issues."
msgstr ""
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr ""

124
locale/sources/helpdesk.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-10 14:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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,63 +24,63 @@ msgstr ""
msgid "After sales features: refund, coupon, return, repair, onsite interventions"
msgstr ""
#: ../../helpdesk/after_sales.rst:4
#: ../../helpdesk/after_sales.rst:5
msgid "As my business grows, having the tools to allow my helpdesk team to record, track and manage issues raised easy and efficiently, is key. Odoo’s Helpdesk app allows me to generate credit notes, return products, grant coupons, do repairs and plan onsite interventions from a ticket’s page."
msgstr ""
#: ../../helpdesk/after_sales.rst:7
#: ../../helpdesk/after_sales.rst:10
msgid "Set up the After Sales services"
msgstr ""
#: ../../helpdesk/after_sales.rst:8
msgid "Go to *Configuration > Helpdesk Teams* and enable the After Sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*."
#: ../../helpdesk/after_sales.rst:12
msgid "Go to :menuselection:`Configuration --> Helpdesk Teams` and enable the After Sales options: *Refunds, Returns, Coupons, Repairs and Onsite Interventions*."
msgstr ""
#: ../../helpdesk/after_sales.rst:14
#: ../../helpdesk/after_sales.rst:19
msgid "Generate credit notes from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:15
#: ../../helpdesk/after_sales.rst:21
msgid "I can use a credit note to refund a customer or adjust the amount due. For that, I’ll simply go to my ticket page, click on *Refund* and select the corresponding *Invoice*. Clicking on *Reverse* the credit note will be generated, and I can *Post* it while still being in the *Helpdesk* app."
msgstr ""
#: ../../helpdesk/after_sales.rst:22
#: ../../helpdesk/after_sales.rst:29
msgid "Allow product returns from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:23
#: ../../helpdesk/after_sales.rst:31
msgid "The process of a product return from my customer back to my warehouse will be taken into action when, at the ticket page, I choose the option *Return*."
msgstr ""
#: ../../helpdesk/after_sales.rst:29
#: ../../helpdesk/after_sales.rst:38
msgid "Grant coupons from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:30
msgid "First, be sure to have your *Coupon Program* planned at the *Sales or Website* app. At the *Helpdesk* app, I will open my ticket and click on *Coupon*, choose the *Coupon Program > Generate*."
#: ../../helpdesk/after_sales.rst:40
msgid "First, be sure to have your *Coupon Program* planned at the *Sales or Website* app. At the *Helpdesk* app, I will open my ticket and click on *Coupon*, choose the :menuselection:`Coupon Program --> Generate`."
msgstr ""
#: ../../helpdesk/after_sales.rst:37
#: ../../helpdesk/after_sales.rst:48
msgid "Repairs from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:38
#: ../../helpdesk/after_sales.rst:50
msgid "Clicking on *Repair* option, on my ticket page, a new repair order form will be shown. Fill up the rest of the fields as needed and choose the next step."
msgstr ""
#: ../../helpdesk/after_sales.rst:44
#: ../../helpdesk/after_sales.rst:57
msgid "Plan onsite interventions from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:45
#: ../../helpdesk/after_sales.rst:59
msgid "At the ticket page, I can now configure my onsite interventions exactly the same way I would do being on the *Field Service* app, clicking on *Plan Intervention*."
msgstr ""
#: ../../helpdesk/after_sales.rst:52
#: ../../helpdesk/after_sales.rst:66
msgid "`Coupons <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>`_"
msgstr ""
#: ../../helpdesk/after_sales.rst:53
#: ../../helpdesk/after_sales.rst:67
msgid ":doc:`../manufacturing/repair/repair`"
msgstr ""
@ -88,44 +88,44 @@ msgstr ""
msgid "Allow customers to close their tickets"
msgstr ""
#: ../../helpdesk/close_tickets.rst:4
#: ../../helpdesk/close_tickets.rst:5
msgid "Allowing customers to close their tickets gives them autonomy and minimize misunderstandings about when an issue is considered solved, or not. It makes communication and actions more efficient."
msgstr ""
#: ../../helpdesk/close_tickets.rst:7
#: ../../helpdesk/close_tickets.rst:9
msgid "Configure the feature"
msgstr ""
#: ../../helpdesk/close_tickets.rst:8
msgid "To configure the feauture go to *Helpdesk > Settings > Helpdesk Teams > Edit* and enable *Ticket closing*."
#: ../../helpdesk/close_tickets.rst:11
msgid "To configure the feature go to :menuselection:`Helpdesk --> Settings --> Helpdesk Teams --> Edit` and enable *Ticket closing*."
msgstr ""
#: ../../helpdesk/close_tickets.rst:14
msgid "In order to designate to which stage the ticket will migrate to once it is closed, go to *Overview > Tickets*."
#: ../../helpdesk/close_tickets.rst:18
msgid "In order to designate to which stage the ticket will migrate to once it is closed, go to :menuselection:`Overview --> Tickets`."
msgstr ""
#: ../../helpdesk/close_tickets.rst:20
msgid "You can either create a new kanban stage or work with an existing one. For both scenarios, go to *Settings > Edit Stage* and enable *Closing Stage*."
#: ../../helpdesk/close_tickets.rst:25
msgid "You can either create a new kanban stage or work with an existing one. For both scenarios, go to :menuselection:`Settings --> Edit Stage` and enable *Closing Stage*."
msgstr ""
#: ../../helpdesk/close_tickets.rst:26
#: ../../helpdesk/close_tickets.rst:32
msgid "If a closing stage is not specified, by default, the ticket will be transferred to the last stage; contrarily, if you have more than one stage set as closing, the ticket will be put in the first one."
msgstr ""
#: ../../helpdesk/close_tickets.rst:30
#: ../../helpdesk/close_tickets.rst:35
msgid "The Costumer Portal"
msgstr ""
#: ../../helpdesk/close_tickets.rst:31
#: ../../helpdesk/close_tickets.rst:37
msgid "Now, once the user logs in to his Portal, the option *Close this ticket* is available."
msgstr ""
#: ../../helpdesk/close_tickets.rst:39
#: ../../helpdesk/close_tickets.rst:44
msgid "Get reports on tickets closed by costumers"
msgstr ""
#: ../../helpdesk/close_tickets.rst:40
msgid "To do an analysis of the tickets that have been closed by costumers go to *Reporting > Tickets > Filters > Add Custom filter > Closed by partner > Applied*."
#: ../../helpdesk/close_tickets.rst:46
msgid "To do an analysis of the tickets that have been closed by costumers go to :menuselection:`Reporting --> Tickets --> Filters --> Add Custom filter --> Closed by partner --> Applied`."
msgstr ""
#: ../../helpdesk/getting_started.rst:3
@ -201,94 +201,94 @@ msgid "Live Chat allows your customers to submit a ticket via Live Chat on your
msgstr ""
#: ../../helpdesk/getting_started.rst:86
msgid "The final option to submit tickets is thru an API connection. View the documentation `*here* <https://www.odoo.com/documentation/13.0/webservices/odoo.html>`__."
msgid "The final option to submit tickets is through an API connection. View the documentation `here <https://www.odoo.com/documentation/13.0/webservices/odoo.html>`_."
msgstr ""
#: ../../helpdesk/getting_started.rst:91
#: ../../helpdesk/getting_started.rst:90
msgid "Tickets have been created, now what?"
msgstr ""
#: ../../helpdesk/getting_started.rst:93
#: ../../helpdesk/getting_started.rst:92
msgid "Now your employees can start working on them! If you have selecting a manual assignation method then your employees will need to assign themselves to tickets using the \"Assign To Me\" button on the top left of a ticket or by adding themselves to the \"Assigned to\" field."
msgstr ""
#: ../../helpdesk/getting_started.rst:101
#: ../../helpdesk/getting_started.rst:100
msgid "If you have selected \"Random\" or \"Balanced\" assignation method, your tickets will be assigned to a member of that Helpdesk team."
msgstr ""
#: ../../helpdesk/getting_started.rst:104
#: ../../helpdesk/getting_started.rst:103
msgid "From there they will begin working on resolving the tickets! When they are completed, they will move the ticket to the solved stage."
msgstr ""
#: ../../helpdesk/getting_started.rst:108
#: ../../helpdesk/getting_started.rst:107
msgid "How do I mark this ticket as urgent?"
msgstr ""
#: ../../helpdesk/getting_started.rst:110
#: ../../helpdesk/getting_started.rst:109
msgid "On your tickets you will see stars. You can determine how urgent a ticket is but selecting one or more stars on the ticket. You can do this in the Kanban view or on the ticket form."
msgstr ""
#: ../../helpdesk/getting_started.rst:117
#: ../../helpdesk/getting_started.rst:116
msgid "To set up a Service Level Agreement Policy for your employees, first activate the setting under \"Settings\""
msgstr ""
#: ../../helpdesk/getting_started.rst:123
#: ../../helpdesk/getting_started.rst:122
msgid "From here, select \"Configure SLA Policies\" and click \"Create\"."
msgstr ""
#: ../../helpdesk/getting_started.rst:125
#: ../../helpdesk/getting_started.rst:124
msgid "You will fill in information like the Helpdesk team, what the minimum priority is on the ticket (the stars) and the targets for the ticket."
msgstr ""
#: ../../helpdesk/getting_started.rst:132
#: ../../helpdesk/getting_started.rst:131
msgid "What if a ticket is blocked or is ready to be worked on?"
msgstr ""
#: ../../helpdesk/getting_started.rst:134
#: ../../helpdesk/getting_started.rst:133
msgid "If a ticket cannot be resolved or is blocked, you can adjust the \"Kanban State\" on the ticket. You have 3 options:"
msgstr ""
#: ../../helpdesk/getting_started.rst:137
#: ../../helpdesk/getting_started.rst:136
msgid "Grey - Normal State"
msgstr ""
#: ../../helpdesk/getting_started.rst:139
#: ../../helpdesk/getting_started.rst:138
msgid "Red - Blocked"
msgstr ""
#: ../../helpdesk/getting_started.rst:141
#: ../../helpdesk/getting_started.rst:140
msgid "Green - Ready for next stage"
msgstr ""
#: ../../helpdesk/getting_started.rst:143
#: ../../helpdesk/getting_started.rst:142
msgid "Like the urgency stars you can adjust the state in the Kanban or on the Ticket form."
msgstr ""
#: ../../helpdesk/getting_started.rst:150
#: ../../helpdesk/getting_started.rst:149
msgid "How can my employees log time against a ticket?"
msgstr ""
#: ../../helpdesk/getting_started.rst:152
#: ../../helpdesk/getting_started.rst:151
msgid "First, head over to \"Settings\" and select the option for \"Timesheet on Ticket\". You will see a field appear where you can select the project the timesheets will log against."
msgstr ""
#: ../../helpdesk/getting_started.rst:159
#: ../../helpdesk/getting_started.rst:158
msgid "Now that you have selected a project, you can save. If you move back to your tickets, you will see a new tab called \"Timesheets\""
msgstr ""
#: ../../helpdesk/getting_started.rst:165
#: ../../helpdesk/getting_started.rst:164
msgid "Here you employees can add a line to add work they have done for this ticket."
msgstr ""
#: ../../helpdesk/getting_started.rst:169
#: ../../helpdesk/getting_started.rst:168
msgid "How to allow your customers to rate the service they received"
msgstr ""
#: ../../helpdesk/getting_started.rst:171
#: ../../helpdesk/getting_started.rst:170
msgid "First, you will need to activate the ratings setting under \"Settings\""
msgstr ""
#: ../../helpdesk/getting_started.rst:176
#: ../../helpdesk/getting_started.rst:175
msgid "Now, when a ticket is moved to its solved or completed stage, it will send an email to the customer asking how their service went."
msgstr ""
@ -404,27 +404,27 @@ msgstr ""
msgid "Turn helpdesk hours into invoices directly from a project task"
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:4
#: ../../helpdesk/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."
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:7
#: ../../helpdesk/reinvoice_from_project.rst:10
msgid "Configuration"
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:8
msgid "Go to *Helpdesk > Configuration > Helpdesk team > Edit* and enable the options *Timesheet on Ticket* and *Time Reinvoicing*. Under *Timesheet on Ticket*, choose the *Project* to which the tickets (and timesheets) will be linked by default. Open its *External link* to enable the feature *Bill from tasks*."
#: ../../helpdesk/reinvoice_from_project.rst:12
msgid "Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit` and enable the options *Timesheet on Ticket* and *Time Reinvoicing*. Under *Timesheet on Ticket*, choose the *Project* to which the tickets (and timesheets) will be linked by default. Open its *External link* to enable the feature *Bill from tasks*."
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:17
#: ../../helpdesk/reinvoice_from_project.rst:22
msgid "Create a sales order and an invoice"
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:18
#: ../../helpdesk/reinvoice_from_project.rst:24
msgid "Now, once you added the time you spent on the helpdesk ticket, under the *Timesheets* tab, access the task clicking on its name."
msgstr ""
#: ../../helpdesk/reinvoice_from_project.rst:25
#: ../../helpdesk/reinvoice_from_project.rst:31
msgid "*Create Sales Order* and proceed to create the invoice."
msgstr ""

258
locale/sources/inventory.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-10 14:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -88,7 +88,7 @@ msgid "Create a Barcode Nomenclature"
msgstr ""
#: ../../inventory/barcode/operations/barcode_nomenclature.rst:15
msgid "Odoo supports Barcode Nomenclatures, which determine the mapping and interpretation of the encoded information. You can configure your barcode nomenclature being in **debug** mode. To do so, go to *Inventory > Configuration > Barcode Nomenclature*."
msgid "Odoo supports Barcode Nomenclatures, which determine the mapping and interpretation of the encoded information. You can configure your barcode nomenclature being in **debug** mode. To do so, go to :menuselection:`Inventory --> Configuration --> Barcode Nomenclature`."
msgstr ""
#: ../../inventory/barcode/operations/barcode_nomenclature.rst:20
@ -373,7 +373,7 @@ msgid "Configuration"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:14
msgid "To use this feature, you first need to activate the *Barcode* functionality via *Inventory > Settings > Barcode Scanner*. Once you have ticked the feature, you can hit save."
msgid "To use this feature, you first need to activate the *Barcode* functionality via :menuselection:`Inventory --> Settings --> Barcode Scanner`. Once you have ticked the feature, you can hit save."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:22
@ -381,38 +381,38 @@ msgid "Set Product Barcodes"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:24
msgid "You can easily assign barcodes to your different products via the *Inventory* app. To do so, go to *Settings > Configure Products Barcodes*."
msgid "You can easily assign barcodes to your different products via the *Inventory* app. To do so, go to :menuselection:`Settings --> Configure Products Barcodes`."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:31
#: ../../inventory/barcode/setup/software.rst:30
msgid "Then, you have the possibility to assign barcodes to your products directly at creation on the product form."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:41
#: ../../inventory/barcode/setup/software.rst:40
msgid "Be careful to add barcodes directly on the product variants and not on the template product. Otherwise, you won’t be able to differentiate them."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:46
#: ../../inventory/barcode/setup/software.rst:45
msgid "Set Locations Barcodes"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:48
msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in *Inventory > Configuration > Locations*."
#: ../../inventory/barcode/setup/software.rst:47
msgid "If you manage multiple locations, you will find useful to attribute a barcode to each location and stick it on the location. You can configure the locations barcodes in :menuselection:`Inventory --> Configuration --> Locations`."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:59
#: ../../inventory/barcode/setup/software.rst:58
msgid "You can easily print the barcode you allocate to the locations via the *Print* menu."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:63
#: ../../inventory/barcode/setup/software.rst:62
msgid "Barcode Formats"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:65
#: ../../inventory/barcode/setup/software.rst:64
msgid "Most retail products use EAN-13 barcodes. They cannot be made up without proper authorization. You must pay the International Article Numbering Association a fee in exchange for an EAN code sequence."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:69
#: ../../inventory/barcode/setup/software.rst:68
msgid "Still, as Odoo supports any string as a barcode, you can always define your own barcode format for internal use."
msgstr ""
@ -555,15 +555,15 @@ msgid "Configure Drop-Shipping"
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:54
msgid "Activate the functionality in the *Purchase* application by going to *Configuration > Settings*."
msgid "Activate the functionality in the *Purchase* application by going to :menuselection:`Configuration --> Settings`."
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:60
msgid "Then, go to the *Inventory* app, in *Configuration > Settings* to activate the *Multi-Step Routes* feature. It will allow you to make the *Route* field appear on the sale order lines to specify you send a product via drop-shipping."
msgid "Then, go to the *Inventory* app, in :menuselection:`Configuration --> Settings` to activate the *Multi-Step Routes* feature. It will allow you to make the *Route* field appear on the sale order lines to specify you send a product via drop-shipping."
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:68
msgid "Now, in the *Sales* app, go to *Products > Products*. Select the product you would like to drop-ship and add a vendor pricelist which contains the right supplier, via the purchase tab."
msgid "Now, in the *Sales* app, go to :menuselection:`Products --> Products`. Select the product you would like to drop-ship and add a vendor pricelist which contains the right supplier, via the purchase tab."
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:76
@ -695,7 +695,7 @@ msgstr ""
#: ../../inventory/management/delivery/one_step.rst:9
#: ../../inventory/management/incoming/one_step.rst:9
msgid "However, if advanced routes have been activated and you set another incoming configuration on your warehouse, you can set it back to the one-step receipt configuration. To do so, go to *Configuration > Warehouses* and edit the warehouse in question."
msgid "However, if advanced routes have been activated and you set another incoming configuration on your warehouse, you can set it back to the one-step receipt configuration. To do so, go to :menuselection:`Configuration --> Warehouses` and edit the warehouse in question."
msgstr ""
#: ../../inventory/management/delivery/one_step.rst:14
@ -747,7 +747,7 @@ msgid "In Odoo, you have the possibility to deliver your products in different p
msgstr ""
#: ../../inventory/management/delivery/packaging_type.rst:11
msgid "First, you need to activate the *Delivery Packages* feature in the *Inventory app > Configuration > Settings*."
msgid "First, you need to activate the *Delivery Packages* feature in the :menuselection:`Inventory app --> Configuration --> Settings`."
msgstr ""
#: ../../inventory/management/delivery/packaging_type.rst:18
@ -967,7 +967,7 @@ msgstr ""
#: ../../inventory/management/delivery/three_steps.rst:29
#: ../../inventory/management/incoming/three_steps.rst:29
msgid "To activate *multi-step routes*, open the *inventory app*, and go to *Configuration > Settings* and activate the option. By default, activating *multi-step routes* will also activate *Storage Locations*."
msgid "To activate *multi-step routes*, open the *inventory app*, and go to :menuselection:`Configuration --> Settings` and activate the option. By default, activating *multi-step routes* will also activate *Storage Locations*."
msgstr ""
#: ../../inventory/management/delivery/three_steps.rst:38
@ -977,7 +977,7 @@ msgstr ""
#: ../../inventory/management/delivery/three_steps.rst:40
#: ../../inventory/management/incoming/three_steps.rst:40
msgid "Now that *Multi-Step Routes* is activated, go to *Configuration > Warehouse* and open the one you will use to deliver in 3 steps. Then, you can select the option *Pack good, send goods in output and then deliver (3 steps)* as *Outgoing Shipments*."
msgid "Now that *Multi-Step Routes* is activated, go to :menuselection:`Configuration --> Warehouse` and open the one you will use to deliver in 3 steps. Then, you can select the option *Pack good, send goods in output and then deliver (3 steps)* as *Outgoing Shipments*."
msgstr ""
#: ../../inventory/management/delivery/three_steps.rst:48
@ -987,7 +987,7 @@ msgstr ""
#: ../../inventory/management/delivery/three_steps.rst:51
#: ../../inventory/management/incoming/three_steps.rst:51
msgid "Of course, you can rename them if you want. To do so, go to *Configuration > Locations* and select the one you want to rename. Change its name and hit save."
msgid "Of course, you can rename them if you want. To do so, go to :menuselection:`Configuration --> Locations` and select the one you want to rename. Change its name and hit save."
msgstr ""
#: ../../inventory/management/delivery/three_steps.rst:56
@ -1077,7 +1077,7 @@ msgstr ""
#: ../../inventory/management/delivery/two_steps.rst:26
#: ../../inventory/management/incoming/two_steps.rst:26
msgid "To allow *multi-step routes*, go to *Configuration > Settings* and activate the feature. By default, activating *multi-step routes* will also activate *Storage Locations*."
msgid "To allow *multi-step routes*, go to :menuselection:`Configuration --> Settings` and activate the feature. By default, activating *multi-step routes* will also activate *Storage Locations*."
msgstr ""
#: ../../inventory/management/delivery/two_steps.rst:34
@ -1087,12 +1087,12 @@ msgstr ""
#: ../../inventory/management/delivery/two_steps.rst:36
#: ../../inventory/management/incoming/two_steps.rst:36
msgid "Once *multi-step routes* is activated, you can go to *Configuration > Warehouse* and enter the warehouse which will use receipt in 2 steps. Then, you can select the option *Receive goods in input and then stock (2 steps)* for *Incoming Shipments*."
msgid "Once *multi-step routes* is activated, you can go to :menuselection:`Configuration --> Warehouse` and enter the warehouse which will use receipt in 2 steps. Then, you can select the option *Receive goods in input and then stock (2 steps)* for *Incoming Shipments*."
msgstr ""
#: ../../inventory/management/delivery/two_steps.rst:45
#: ../../inventory/management/incoming/two_steps.rst:44
msgid "Activating this option will lead to the creation of a new *Input* location. If you want to rename it, you can go to *Configuration > Locations > Select Input* and update its name."
msgid "Activating this option will lead to the creation of a new *Input* location. If you want to rename it, you can go to :menuselection:`Configuration --> Locations --> Select Input` and update its name."
msgstr ""
#: ../../inventory/management/delivery/two_steps.rst:54
@ -1194,6 +1194,10 @@ msgstr ""
msgid ":doc:`../delivery/inventory_flow`"
msgstr ""
#: ../../inventory/management/incoming/handle_receipts.rst:69
msgid ":doc:`../../../purchase/purchases/rfq/analyze`"
msgstr ""
#: ../../inventory/management/incoming/two_steps.rst:68
msgid "Process the receipt and the internal transfer"
msgstr ""
@ -1277,7 +1281,7 @@ msgid "Application configuration"
msgstr ""
#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:19
msgid "To use expiration dates tracking, open the *Inventory* application and go to *Configuration > Settings* and activate the *Lots & Serial Numbers* and *Expiration Dates* features."
msgid "To use expiration dates tracking, open the *Inventory* application and go to :menuselection:`Configuration --> Settings` and activate the *Lots & Serial Numbers* and *Expiration Dates* features."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:27
@ -1320,7 +1324,7 @@ msgid "Expiration Alerts"
msgstr ""
#: ../../inventory/management/lots_serial_numbers/expiration_dates.rst:60
msgid "You can access all your expiration alerts from the *inventory* app. To do so, go to *Master Data > Lots/Serial Numbers*. There, you can use the pre-existing filter that shows all the lots/serial numbers that exceeded their alert date."
msgid "You can access all your expiration alerts from the *inventory* app. To do so, go to :menuselection:`Master Data --> Lots/Serial Numbers`. There, you can use the pre-existing filter that shows all the lots/serial numbers that exceeded their alert date."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:3
@ -1348,7 +1352,7 @@ msgid "Application Configuration"
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:23
msgid "First, you need to activate the tracking of lot numbers. To do so, go to *Inventory > Configuration > Settings* and tick *Lots & Serial Numbers*. Then, click on save."
msgid "First, you need to activate the tracking of lot numbers. To do so, go to :menuselection:`Inventory --> Configuration --> Settings` and tick *Lots & Serial Numbers*. Then, click on save."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:31
@ -1360,7 +1364,7 @@ msgid "Now, you have to configure which products you want to track by serial num
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:36
msgid "Go to *Master Data > Products* and open the product of your choice. There, click on *Edit* and select *Tracking by Lots* in the inventory tab."
msgid "Go to :menuselection:`Master Data --> Products` and open the product of your choice. There, click on *Edit* and select *Tracking by Lots* in the inventory tab."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:47
@ -1401,7 +1405,7 @@ msgid "Operation Types"
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:95
msgid "Of course, you also have the possibility to define how you will manage lots for each operation type. To do so, open the *Inventory* app and go to *Configuration > Operation Types*."
msgid "Of course, you also have the possibility to define how you will manage lots for each operation type. To do so, open the *Inventory* app and go to :menuselection:`Configuration --> Operation Types`."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:99
@ -1417,7 +1421,7 @@ msgid "The lot number given to the products allows you to keep track of where th
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:117
msgid "To track an item, open the *Inventory* module and, in *Master Data > Lots/Serial Numbers*, click on the lot number corresponding to your search."
msgid "To track an item, open the *Inventory* module and, in :menuselection:`Master Data --> Lots/Serial Numbers`, click on the lot number corresponding to your search."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/lots.rst:124
@ -1441,11 +1445,11 @@ msgid "If you want to do it or run very advanced traceability, the Odoo double-e
msgstr ""
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:20
msgid "First, you need to activate the serial numbers tracking. To do so, go to *Configuration > Settings* in the *Inventory* application. Then, enable the feature and hit save."
msgid "First, you need to activate the serial numbers tracking. To do so, go to :menuselection:`Configuration --> Settings` in the *Inventory* application. Then, enable the feature and hit save."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:30
msgid "Now, you have to configure the products you want to track by serial numbers. To do so, go to *Master Data > Products* and open the product of your choice. Edit it and select *Tracking By Unique Serial Number* in the *Inventory tab*. Then, click on save."
msgid "Now, you have to configure the products you want to track by serial numbers. To do so, go to :menuselection:`Master Data --> Products` and open the product of your choice. Edit it and select *Tracking By Unique Serial Number* in the *Inventory tab*. Then, click on save."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:42
@ -1499,7 +1503,7 @@ msgid "Operation types"
msgstr ""
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:108
msgid "You also have the possibility to define how you will manage lots for each operation type. To define it, go to *Configuration > Operation Types* in the *Inventory* app."
msgid "You also have the possibility to define how you will manage lots for each operation type. To define it, go to :menuselection:`Configuration --> Operation Types` in the *Inventory* app."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:112
@ -1519,10 +1523,10 @@ msgid "Using serial numbers allows you to keep track of where the products were
msgstr ""
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:130
msgid "Tracking an item is easy: open the *Inventory* app, and go to *Master Data > Lots/Serial Numbers* and click on the serial number corresponding to your search. Then, open the *Traceability* information. There, you will see in which documents the serial number has been used."
msgid "Tracking an item is easy: open the *Inventory* app, and go to :menuselection:`Master Data --> Lots/Serial Numbers` and click on the serial number corresponding to your search. Then, open the *Traceability* information. There, you will see in which documents the serial number has been used."
msgstr ""
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:142
#: ../../inventory/management/lots_serial_numbers/serial_numbers.rst:140
msgid "And, if you want to locate a serial number, you can do so by clicking on the *Location* button available on the serial number form."
msgstr ""
@ -1575,7 +1579,7 @@ msgid "Of course, Odoo has the ability to manage those consignee stocks through
msgstr ""
#: ../../inventory/management/misc/owned_stock.rst:20
msgid "To use this feature, go to *Inventory > Configuration > Settings* in the inventory app. Then, enable the *Consignment* feature in the *Traceability* section. Now, hit save."
msgid "To use this feature, go to :menuselection:`Inventory --> Configuration --> Settings` in the inventory app. Then, enable the *Consignment* feature in the *Traceability* section. Now, hit save."
msgstr ""
#: ../../inventory/management/misc/owned_stock.rst:28
@ -1615,11 +1619,11 @@ msgid "When you install the *Inventory* app, Odoo automatically creates a scrap
msgstr ""
#: ../../inventory/management/misc/scrap.rst:24
msgid "Of course, you can create new scrap areas if needed. To do so, go to *Inventory > Configuration > Settings* and activate the *Storage Locations* feature."
msgid "Of course, you can create new scrap areas if needed. To do so, go to :menuselection:`Inventory --> Configuration --> Settings` and activate the *Storage Locations* feature."
msgstr ""
#: ../../inventory/management/misc/scrap.rst:31
msgid "Now, go to *Configuration > Locations* and create your scrap location."
msgid "Now, go to :menuselection:`Configuration --> Locations` and create your scrap location."
msgstr ""
#: ../../inventory/management/misc/scrap.rst:34
@ -1639,7 +1643,7 @@ msgid "Scrap from receipt"
msgstr ""
#: ../../inventory/management/misc/scrap.rst:47
msgid "Scrapping products from receipts is easy. Go to *Inventory > Dashboard > Receipts* or click on *1 TO PROCESS* under the receipts location."
msgid "Scrapping products from receipts is easy. Go to :menuselection:`Inventory --> Dashboard --> Receipts` or click on *1 TO PROCESS* under the receipts location."
msgstr ""
#: ../../inventory/management/misc/scrap.rst:53
@ -1655,7 +1659,7 @@ msgid "Scrap from delivery order"
msgstr ""
#: ../../inventory/management/misc/scrap.rst:70
msgid "To scrap products from a delivery order, go to *Inventory > Dashboard > Delivery orders* or click on *1 TO PROCESS*."
msgid "To scrap products from a delivery order, go to :menuselection:`Inventory --> Dashboard --> Delivery orders` or click on *1 TO PROCESS*."
msgstr ""
#: ../../inventory/management/misc/scrap.rst:76
@ -1671,7 +1675,7 @@ msgid "Scrap from an internal transfer"
msgstr ""
#: ../../inventory/management/misc/scrap.rst:95
msgid "To do this, the flow is almost the same. In fact, you just have to go to *Inventory > Dashboard > Internal Transfers*."
msgid "To do this, the flow is almost the same. In fact, you just have to go to :menuselection:`Inventory --> Dashboard --> Internal Transfers`."
msgstr ""
#: ../../inventory/management/misc/scrap.rst:101
@ -1803,7 +1807,7 @@ msgid "The idea is to subtract the numbers of security days from the calculation
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:97
msgid "To set up your security dates, go to *Inventory > Configuration > Settings* and enable the feature."
msgid "To set up your security dates, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature."
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:104
@ -1819,7 +1823,7 @@ msgid "When the system generates purchase orders for procuring products, they wi
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:114
msgid "To find purchase lead time, go to *Inventory > Configuration > Settings* and enable the feature."
msgid "To find purchase lead time, go to :menuselection:`Inventory --> Configuration --> Settings` and enable the feature."
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:121
@ -1831,7 +1835,7 @@ msgid "The security lead time for manufacturing allows generating manufacturing
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:127
msgid "To configure it, go to *Manufacturing > Configuration > Settings* and enable the *Security Lead Time* option. Then, hit save."
msgid "To configure it, go to :menuselection:`Manufacturing --> Configuration --> Settings` and enable the *Security Lead Time* option. Then, hit save."
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:136
@ -1839,7 +1843,7 @@ msgid "Sometimes, the internal transfers that a product might do may also influe
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:141
msgid "To specify them, go to *Inventory > Configuration > Routes* and add a push rule to set a delay. Of course, you need to activate *Multi-step Routes* to use this feature."
msgid "To specify them, go to :menuselection:`Inventory --> Configuration --> Routes` and add a push rule to set a delay. Of course, you need to activate *Multi-step Routes* to use this feature."
msgstr ""
#: ../../inventory/management/planning/scheduled_date.rst:149
@ -1919,7 +1923,7 @@ msgid "Run the scheduler manually"
msgstr ""
#: ../../inventory/management/planning/schedulers.rst:36
msgid "To start the scheduler manually, go to *Inventory > Operations > Run Schedulers*. The scheduler uses all the relevant parameters defined for products, suppliers and the company to prioritize the different production orders, deliveries and supplier purchases."
msgid "To start the scheduler manually, go to :menuselection:`Inventory --> Operations --> Run Schedulers`. The scheduler uses all the relevant parameters defined for products, suppliers and the company to prioritize the different production orders, deliveries and supplier purchases."
msgstr ""
#: ../../inventory/management/planning/schedulers.rst:45
@ -1927,11 +1931,11 @@ msgid "Configure and run the scheduler (for advanced users)"
msgstr ""
#: ../../inventory/management/planning/schedulers.rst:47
msgid "To use this feature, you have to enable the debug mode. To do so, go to *Settings > Activate the developer mode*."
msgid "To use this feature, you have to enable the debug mode. To do so, go to :menuselection:`Settings --> Activate the developer mode`."
msgstr ""
#: ../../inventory/management/planning/schedulers.rst:53
msgid "Then, go to *Settings > Technical > Automation > Scheduled Actions* and modify the *Run MRP Scheduler Configuration*. There, you can set the starting time of the scheduler."
msgid "Then, go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and modify the *Run MRP Scheduler Configuration*. There, you can set the starting time of the scheduler."
msgstr ""
#: ../../inventory/management/products.rst:3
@ -2017,7 +2021,7 @@ msgid "You can set up Odoo to work with different units of measure for one produ
msgstr ""
#: ../../inventory/management/products/uom.rst:18
msgid "In the *Inventory* application, go to *Configuration > Settings*. In the *Products* section, activate *Units of Measure*, then *Save*."
msgid "In the *Inventory* application, go to :menuselection:`Configuration --> Settings`. In the *Products* section, activate *Units of Measure*, then *Save*."
msgstr ""
#: ../../inventory/management/products/uom.rst:25
@ -2025,7 +2029,7 @@ msgid "Create New Units of Measure"
msgstr ""
#: ../../inventory/management/products/uom.rst:27
msgid "In the *Inventory* application go to *Configuration > UoM*. There, hit *Create*. As an example, we will create a Box of 6 units that we will use for the Egg product."
msgid "In the *Inventory* application go to :menuselection:`Configuration --> UoM`. There, hit *Create*. As an example, we will create a Box of 6 units that we will use for the Egg product."
msgstr ""
#: ../../inventory/management/products/uom.rst:34
@ -2037,7 +2041,7 @@ msgid "Specify Units of Measure on your Products"
msgstr ""
#: ../../inventory/management/products/uom.rst:45
msgid "In the *Inventory application > Master Data > Products*, open the product which you would like to change the purchase/sale unit of measure, and click on *Edit*."
msgid "In the :menuselection:`Inventory application --> Master Data --> Products`, open the product which you would like to change the purchase/sale unit of measure, and click on *Edit*."
msgstr ""
#: ../../inventory/management/products/uom.rst:49
@ -2109,7 +2113,7 @@ msgid "The package is the physical container in which you put one or several pro
msgstr ""
#: ../../inventory/management/products/usage.rst:43
msgid "To separate a delivery into different packages you will have to set the done qunatity to the desired package quantity then click on \"PUT IN PACK\", do this for each package."
msgid "To separate a delivery into different packages you will have to set the done quantity to the desired package quantity then click on \"PUT IN PACK\", do this for each package."
msgstr ""
#: ../../inventory/management/products/usage.rst:54
@ -2153,7 +2157,7 @@ msgid "Reordering Rules"
msgstr ""
#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:26
msgid "The *Reordering Rules* configuration is available through the menu *Inventory > Master Data > Reordering Rules*. There, click on *Create* to set minimum and maximum stock values for a given product."
msgid "The *Reordering Rules* configuration is available through the menu :menuselection:`Inventory --> Master Data --> Reordering Rules`. There, click on *Create* to set minimum and maximum stock values for a given product."
msgstr ""
#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:33
@ -2177,7 +2181,7 @@ msgid "Don't forget to select the product type *storable* in the product form. A
msgstr ""
#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:69
msgid "The *Make To Order* configuration is available on your product form through your *Inventory module > Master Data > Products* (or in any other module where products are available)."
msgid "The *Make To Order* configuration is available on your product form through your :menuselection:`Inventory module --> Master Data --> Products` (or in any other module where products are available)."
msgstr ""
#: ../../inventory/management/replenishment_strategies/min_stock_rule_vs_mto.rst:73
@ -2197,7 +2201,7 @@ msgid "In order to be able to resupply from another warehouse, you need to activ
msgstr ""
#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:16
msgid "You can then access your warehouses via \\*Inventory > Configuration > Warehouses\\*. Create the necessary warehouses following this `*documentation* <https://docs.google.com/document/d/14xNFdUOAbfzdloqXcjq67T8qjjlY7pu4Db6BbR4_fdA/edit>`__. Enter the warehouse which should be resupplied by another one. You will have the possibility to directly indicate through which warehouse it gets resupplied."
msgid "You can then access your warehouses via :menuselection:`Inventory --> Configuration --> Warehouses`. Create the necessary warehouses following this :doc:`documentation <../warehouses/warehouse_creation>`. Enter the warehouse which should be resupplied by another one. You will have the possibility to directly indicate through which warehouse it gets resupplied."
msgstr ""
#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:26
@ -2205,7 +2209,7 @@ msgid "By activating this option, a new route will now be available on your prod
msgstr ""
#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:34
msgid "For the demonstration, I set a reordering rule with a minimum of 5 units in stock and a maximum of 10 units in stock, having currently 0 units on hand. I will run the scheduler by going to \\*Inventory > Operations > Run scheduler\\*."
msgid "For the demonstration, I set a reordering rule with a minimum of 5 units in stock and a maximum of 10 units in stock, having currently 0 units on hand. I will run the scheduler by going to :menuselection:`Inventory --> Operations --> Run scheduler`."
msgstr ""
#: ../../inventory/management/replenishment_strategies/virtual_warehouses.rst:42
@ -2229,7 +2233,7 @@ msgid "Landed costs can only be applied to products with a FIFO or AVCO costing
msgstr ""
#: ../../inventory/management/reporting/integrating_landed_costs.rst:17
msgid "First, you need to go in *Inventory > Configuration > Settings* and activate the landed costs feature. You can also determine the default journal in which the landed cost accounting entries will be recorded."
msgid "First, you need to go in :menuselection:`Inventory --> Configuration --> Settings` and activate the landed costs feature. You can also determine the default journal in which the landed cost accounting entries will be recorded."
msgstr ""
#: ../../inventory/management/reporting/integrating_landed_costs.rst:25
@ -2265,7 +2269,7 @@ msgid "I can access the journal entry that has been created by the landed cost b
msgstr ""
#: ../../inventory/management/reporting/integrating_landed_costs.rst:63
msgid "You are not forced to start from the vendor bill, you can also go in *Inventory > Operations > Landed Costs* and directly create the landed cost from there."
msgid "You are not forced to start from the vendor bill, you can also go in :menuselection:`Inventory --> Operations --> Landed Costs` and directly create the landed cost from there."
msgstr ""
#: ../../inventory/management/reporting/inventory_valuation_config.rst:5
@ -2560,7 +2564,7 @@ msgid "Manual Inventory Valuation"
msgstr ""
#: ../../inventory/management/reporting/inventory_valuation_config.rst:190
msgid "In this case, goods receipts and deliveries won’t have any direct impact on your accounting books. Periodically, you create a manual journal entry representing the value of what you have in stock. To know that value, go in Inventory > Reporting > Inventory Valuation."
msgid "In this case, goods receipts and deliveries won’t have any direct impact on your accounting books. Periodically, you create a manual journal entry representing the value of what you have in stock. To know that value, go in :menuselection:`Inventory --> Reporting --> Inventory Valuation`."
msgstr ""
#: ../../inventory/management/reporting/inventory_valuation_config.rst:195
@ -2916,7 +2920,7 @@ msgid "The inventory valuation report"
msgstr ""
#: ../../inventory/management/reporting/using_inventory_valuation.rst:70
msgid "The summary of this is accessible via the inventory valuation report (accessible from *Inventory > Reporting > Inventory Valuation*). It gives you, product per product, the value of your stock. By clicking on the button *Inventory At Date*, you can have the same information for a past date."
msgid "The summary of this is accessible via the inventory valuation report (accessible from :menuselection:`Inventory --> Reporting --> Inventory Valuation`). It gives you, product per product, the value of your stock. By clicking on the button *Inventory At Date*, you can have the same information for a past date."
msgstr ""
#: ../../inventory/management/warehouses.rst:3
@ -2968,11 +2972,11 @@ msgid "Create a New Location"
msgstr ""
#: ../../inventory/management/warehouses/location_creation.rst:8
msgid "In order to be able to create different locations, you will need to activate *Multi-Locations* in the settings which can be done from the *Inventory application > Configuration > Settings*."
msgid "In order to be able to create different locations, you will need to activate *Multi-Locations* in the settings which can be done from the :menuselection:`Inventory application --> Configuration --> Settings`."
msgstr ""
#: ../../inventory/management/warehouses/location_creation.rst:15
msgid "In the *Inventory application*, you can now go to *Configuration > Locations* and hit *Create* in order to create a new location."
msgid "In the *Inventory application*, you can now go to :menuselection:`Configuration --> Locations` and hit *Create* in order to create a new location."
msgstr ""
#: ../../inventory/management/warehouses/location_creation.rst:21
@ -3000,11 +3004,11 @@ msgid "In order to create a new warehouse, you should activate the *Multi-Wareho
msgstr ""
#: ../../inventory/management/warehouses/warehouse_creation.rst:12
msgid "In order to do so, go to the *Inventory app > Configuration > Settings*."
msgid "In order to do so, go to the :menuselection:`Inventory app --> Configuration --> Settings`."
msgstr ""
#: ../../inventory/management/warehouses/warehouse_creation.rst:18
msgid "You can then go to *Inventory > Configuration > Warehouses* and hit *Create* to add a new warehouse."
msgid "You can then go to :menuselection:`Inventory --> Configuration --> Warehouses` and hit *Create* to add a new warehouse."
msgstr ""
#: ../../inventory/management/warehouses/warehouse_creation.rst:24
@ -3035,7 +3039,7 @@ msgstr ""
#: ../../inventory/overview/process/deliver_from_stock.rst:8
#: ../../inventory/overview/process/initial_stock.rst:5
#: ../../inventory/overview/process/receive_in_stock.rst:5
msgid "The first step to use the inventory application is to create products in your database via the menu *Master Data > Products*. Click the Create button and enter the name of your product."
msgid "The first step to use the inventory application is to create products in your database via the menu :menuselection:`Master Data --> Products`. Click the Create button and enter the name of your product."
msgstr ""
#: ../../inventory/overview/process/deliver_from_stock.rst:15
@ -3080,7 +3084,7 @@ msgid "Inventory Adjustment for Multiple Products"
msgstr ""
#: ../../inventory/overview/process/initial_stock.rst:21
msgid "Once you have created all your *storable products*, you can create an *inventory adjustment* to determine their current stock level in Odoo. You therefore need to go to *Operations > Inventory Adjustments* and create a new one."
msgid "Once you have created all your *storable products*, you can create an *inventory adjustment* to determine their current stock level in Odoo. You therefore need to go to :menuselection:`Operations --> Inventory Adjustments` and create a new one."
msgstr ""
#: ../../inventory/overview/process/initial_stock.rst:29
@ -3168,43 +3172,43 @@ msgstr ""
msgid "For more information on how to organize your warehouse, read our blog: `What is cross-docking and is it for me? <https://www.odoo.com/blog/business-hacks-1/post/what-is-cross-docking-and-is-it-for-me-270>`__"
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:15
msgid "In the *Inventory* app, open *Configuration > Settings* and activate the *Multi-Step Routes*."
#: ../../inventory/routes/concepts/cross_dock.rst:16
msgid "In the *Inventory* app, open :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:21
#: ../../inventory/routes/concepts/cross_dock.rst:22
msgid "Doing so will also enable the *Storage Locations* feature."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:23
msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to *Inventory > Configuration > Warehouses* and edit your warehouse."
#: ../../inventory/routes/concepts/cross_dock.rst:24
msgid "Now, both *Incoming* and *Outgoing* shipments should be configured to work with 2 steps. To adapt the configuration, go to :menuselection:`Inventory --> Configuration --> Warehouses` and edit your warehouse."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:28
msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in *Inventory > Configuration > Routes*."
#: ../../inventory/routes/concepts/cross_dock.rst:31
msgid "This modification will lead to the creation of a *Cross-Docking* route that can be found in :menuselection:`Inventory --> Configuration --> Routes`."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:34
#: ../../inventory/routes/concepts/cross_dock.rst:38
msgid "Configure products with Cross-Dock Route"
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:36
#: ../../inventory/routes/concepts/cross_dock.rst:40
msgid "Create the product that uses the *Cross-Dock Route* and then, in the inventory tab, select the routes *Buy* and *Cross-Dock*. Now, in the purchase tab, specify the vendor to who you buy the product and set a price for it."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:44
#: ../../inventory/routes/concepts/cross_dock.rst:48
msgid "Once done, create a sale order for the product and confirm it. Odoo will automatically create two transfers which will be linked to the sale order. The first one is the transfer from the *Input Location* to the *Output Location*, corresponding to the move of the product in the *Cross-Dock* area. The second one is the delivery order from the *Output Location* to your *Customer Location. Both are in state *Waiting Another Operation* because we still need to order the product to our supplier."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:52
#: ../../inventory/routes/concepts/cross_dock.rst:56
msgid "Now, go to the *Purchase* app. There, you will find the purchase order that has been automatically triggered by the system. Validate it and receive the products in the *Input Location*."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:60
#: ../../inventory/routes/concepts/cross_dock.rst:64
msgid "When the products have been received from the supplier, you can go back to your initial sale order and validate the internal transfer from *Input* to *Output*."
msgstr ""
#: ../../inventory/routes/concepts/cross_dock.rst:68
#: ../../inventory/routes/concepts/cross_dock.rst:72
msgid "The delivery order is now ready to be processed and can be validated too."
msgstr ""
@ -3220,95 +3224,95 @@ msgstr ""
msgid "First of all you have to select the multi locations option. Go to :menuselection:`Configuration --> Settings` in the **Inventory application**. Then tick the **Manage several locations per warehouse** option. Please don't forget to **apply** your changes."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:22
#: ../../inventory/routes/concepts/inter_warehouse.rst:21
msgid "This option should also be ticked if you wish to manage different locations and routes in your warehouse."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:26
#: ../../inventory/routes/concepts/inter_warehouse.rst:25
msgid "Creating a new warehouse"
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:28
#: ../../inventory/routes/concepts/inter_warehouse.rst:27
msgid "The next step is to create your new warehouse. In the Inventory application click on :menuselection:`Configuration --> Warehouse Management --> Warehouses`. You are now able to create your warehouse by clicking on **Create**."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:33
#: ../../inventory/routes/concepts/inter_warehouse.rst:32
msgid "Fill in a **Warehouse Name** and a **Short Name**. The short name is 5 characters maximum."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:41
msgid "please note that the **Short Name** is very important as it will appear on your transfer orders and other warehouse documents. It might be smart to use an understandable one (e.g.: WH/[first letters of location])."
#: ../../inventory/routes/concepts/inter_warehouse.rst:39
msgid "Please note that the **Short Name** is very important as it will appear on your transfer orders and other warehouse documents. It might be smart to use an understandable one (e.g.: WH/[first letters of location])."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:46
#: ../../inventory/routes/concepts/inter_warehouse.rst:44
msgid "If you go back to your dashboard, new operations will automatically have been generated for your new warehouse."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:53
#: ../../inventory/routes/concepts/inter_warehouse.rst:51
msgid "Creating a new inventory"
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:55
#: ../../inventory/routes/concepts/inter_warehouse.rst:53
msgid "If you create a new warehouse you might already have an existing physical inventory in it. In that case you should create an inventory in Odoo, if not you can skip this step."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:59
#: ../../inventory/routes/concepts/inter_warehouse.rst:57
msgid "Go into the inventory application, select :menuselection:`Inventory Control --> Inventory Adjustment`. You can then create a new inventory by clicking on **Create**. Fill in the **Inventory Reference**, **Date** and be sure to select the right warehouse and location."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:67
#: ../../inventory/routes/concepts/inter_warehouse.rst:65
msgid "Next, click on **Start Inventory**. A new window will open where you will be able to input your existing products. Select add an item and indicate the **Real Quantity** available in the warehouse. The theoretical quantity can not be changed as it represents a computed quantity from purchase and sales orders."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:76
#: ../../inventory/routes/concepts/inter_warehouse.rst:74
msgid "Don't forget to validate your inventory once you have recorder the state of all yours product."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:80
#: ../../inventory/routes/concepts/inter_warehouse.rst:78
msgid "Create an internal transfer"
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:82
#: ../../inventory/routes/concepts/inter_warehouse.rst:80
msgid "The final step is to create your internal transfer. If you want to tranfer 2 units of a product from your first warehouse to another one in Brussels, proceed as follows:"
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:86
#: ../../inventory/routes/concepts/inter_warehouse.rst:84
msgid "From your dashboard, select a internal movement of one of the two warehouses. To do so, click on :menuselection:`More --> Transfer`."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:92
#: ../../inventory/routes/concepts/inter_warehouse.rst:90
msgid "A new window will open where you will be able to select the source location zone (in this case our \"old warehouse\") and the destination location zone (in this case our \"new\" warehouse located in Brussels)."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:96
#: ../../inventory/routes/concepts/inter_warehouse.rst:94
msgid "Add the products you want to transfer by clicking on **Add an Item** and don't forget to **Validate** or **Mark as TODO** once you are done."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:102
#: ../../inventory/routes/concepts/inter_warehouse.rst:100
msgid "If you select **Validate**, Odoo will process all quantities to transfer."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:104
#: ../../inventory/routes/concepts/inter_warehouse.rst:102
msgid "If you select **Mark as TODO**, Odoo will put the transfer in **Waiting Availability** status. Click on **Reserve** to reserve the amount of products in your source warehouse."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:108
#: ../../inventory/routes/concepts/inter_warehouse.rst:106
msgid "It is also possible to manually transfer each product:"
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:110
#: ../../inventory/routes/concepts/inter_warehouse.rst:108
msgid "Via your dashboard, select the transfer order in the source location."
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:115
#: ../../inventory/routes/concepts/inter_warehouse.rst:113
msgid "Select the right transfer order"
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:120
#: ../../inventory/routes/concepts/inter_warehouse.rst:118
msgid "3. Click on the little pencil logo in the lower right corner in order to open the operation details window. In this new window you can manually indicate how much products you process"
msgstr ""
#: ../../inventory/routes/concepts/inter_warehouse.rst:129
#: ../../inventory/routes/concepts/inter_warehouse.rst:126
msgid "If you decide to partially process the transfer order (e.g. a part of the products can't be shipped yet due to an unexpected event), Odoo will automatically ask if you wish to create a **backorder**. Create a backorder if you expect to process the remaining products later, do not create a backorder if you will not supply/receive the remaining products."
msgstr ""
@ -3333,7 +3337,7 @@ msgid "Procurement rules settings"
msgstr ""
#: ../../inventory/routes/concepts/procurement_rule.rst:37
msgid "The procurement rules are set on the routes. In the inventory application, go to Configuration > Routes."
msgid "The procurement rules are set on the routes. In the inventory application, go to :menuselection:`Configuration --> Routes`."
msgstr ""
#: ../../inventory/routes/concepts/procurement_rule.rst:40
@ -3636,30 +3640,30 @@ msgid "If, for example, a warehouse contains volatile substances, it is importan
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:12
msgid "In the *Inventory* app, go to *Configuration > Settings* and activate the *Multi-Step Routes*. By doing so, the *Storage Locations* will be automatically activated."
msgid "In the *Inventory* app, go to :menuselection:`Configuration --> Settings` and activate the *Multi-Step Routes*. By doing so, the *Storage Locations* will be automatically activated."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:18
#: ../../inventory/routes/strategies/putaway.rst:19
msgid "Setting up a Putaway Rule"
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:20
#: ../../inventory/routes/strategies/putaway.rst:21
msgid "In some cases, like for a retail shop storing vegetables and fruits, we have to store products in different locations to maintain product quality."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:22
#: ../../inventory/routes/strategies/putaway.rst:23
msgid "Let’s suppose there are one warehouse location *WH/Stock* and two sub-locations *WH/Stock/Vegatable* and *WH/Stock/Fruits*."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:24
msgid "To manage those locations, we will create putaway rules. To do so, open the *Inventory* app and go to *Configuration > Putaway Rules*. Then, click on create and configure your first rule indicating the main location the product will enter before being redirected to the right location."
#: ../../inventory/routes/strategies/putaway.rst:25
msgid "To manage those locations, we will create putaway rules. To do so, open the *Inventory* app and go to :menuselection:`Configuration --> Putaway Rules`. Then, click on create and configure your first rule indicating the main location the product will enter before being redirected to the right location."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:27
#: ../../inventory/routes/strategies/putaway.rst:31
msgid "The putaway rules can be defined either per product or per product category."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:32
#: ../../inventory/routes/strategies/putaway.rst:36
msgid "Now, if I purchase apples and carrots to my supplier, they will be grouped in the same receipt but redirected to the right location automatically, thanks to putaway rules. This information is available from *Inventory Report*, under the reporting menu."
msgstr ""
@ -4483,58 +4487,58 @@ msgid "If you already have a UPS account, you can add it to your online profile
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:39
msgid "1. Log in to the UPS.com site (`http://www.ups.com <http://www.ups.com/>`__) using your UPS.com User ID and Password."
msgid "Log in to the `UPS.com website <http://www.ups.com/>`_) using your UPS.com User ID and Password."
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:43
#: ../../inventory/shipping/setup/ups_credentials.rst:41
msgid "Click the **My UPS** tab."
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:45
#: ../../inventory/shipping/setup/ups_credentials.rst:43
msgid "Click the **Account Summary** link."
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:47
#: ../../inventory/shipping/setup/ups_credentials.rst:45
msgid "4. Click the **Add an Existing UPS Account** link in the **UPS Account Details** section of the page."
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:50
#: ../../inventory/shipping/setup/ups_credentials.rst:48
msgid "5. In the **Add New Account** screen, enter the **UPS Account Number**, **Account Name**, and **Postal Code** fields. The country defaults to United States.q"
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:54
#: ../../inventory/shipping/setup/ups_credentials.rst:52
msgid "Click the **Next** button to continue."
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:57
#: ../../inventory/shipping/setup/ups_credentials.rst:55
msgid "Get an Access Key"
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:59
#: ../../inventory/shipping/setup/ups_credentials.rst:57
msgid "After you have added your UPS account number to your user profile you can request an Access Key from UPS using the steps below:"
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:62
msgid "1. Go to the **UPS Developer Kit** web page `https://www.ups.com/upsdeveloperkit?loc=en\\_US <https://www.ups.com/upsdeveloperkit?loc=en_US>`__"
#: ../../inventory/shipping/setup/ups_credentials.rst:60
msgid "Go to the `UPS Developer Kit web page <https://www.ups.com/upsdeveloperkit?loc=en_US>`_"
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:65
#: ../../inventory/shipping/setup/ups_credentials.rst:61
msgid "Log into UPS.com with your user ID and password"
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:67
#: ../../inventory/shipping/setup/ups_credentials.rst:62
msgid "Click on the link **Request an access key**."
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:69
#: ../../inventory/shipping/setup/ups_credentials.rst:63
msgid "Verify your contact information"
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:71
#: ../../inventory/shipping/setup/ups_credentials.rst:64
msgid "Click the **Request Access Key** button."
msgstr ""
#: ../../inventory/shipping/setup/ups_credentials.rst:73
#: ../../inventory/shipping/setup/ups_credentials.rst:66
msgid "The **Access Key** will be provided to you on the web page, and an email with the Access Key will be sent to the email address of the primary contact."
msgstr ""

10
locale/sources/iot.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-10 14:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -105,7 +105,7 @@ msgid "Updating your SD Card with Etcher"
msgstr ""
#: ../../iot/config/flash_sdcard.rst:11
msgid "Go to Balena’s website and download `Etcher <http://wwww.balena.org>`__, It’s a free and open-source utility used for burning image files. Install and launch it."
msgid "Go to Balena’s website and download `Etcher <https://www.balena.io/>`__, It’s a free and open-source utility used for burning image files. Install and launch it."
msgstr ""
#: ../../iot/config/flash_sdcard.rst:15
@ -140,8 +140,8 @@ msgstr ""
msgid "If your IoT Box image is from an earlier version, then you will have to reflash the SD card of your IoT Box to update the image (the latest image can be found `here <http://nightly/odoo.com>`__)."
msgstr ""
#: ../../iot/config/iot_notfound.rst:23
msgid "You can find the documentation about SD card flashing here (`here <https://docs.google.com/document/d/1bqKsZhWqMqI4mhv4ltF61M_QPiBCHygYjjvkhsCTdaY/edit>`__)."
#: ../../iot/config/iot_notfound.rst:24
msgid ":doc:`flash_sdcard`"
msgstr ""
#: ../../iot/config/pos.rst:3
@ -233,7 +233,7 @@ msgid "**Wi-Fi**: The current version of the IoT Box has Wi-Fi built in. Make su
msgstr ""
#: ../../iot/config/pos.rst:73
msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes."
msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in :menuselection:`Point of Sale --> Configuration --> PoS`, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes."
msgstr ""
#: ../../iot/config/pos.rst:77

84
locale/sources/manufacturing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -101,54 +101,54 @@ msgid "You can use BoMs without routings. You will use this if you choose to man
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:24
msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the *Master Data* menu > *Products* and create both the finished product and the component."
msgid "Before creating your *BoM*, you have to create the product using the *BoM* and, at least, one of the components. Go to the :menuselection:`Master Data menu --> Products` and create both the finished product and the component."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:29
#: ../../manufacturing/management/bill_configuration.rst:28
msgid "Once done, go to the *Bills of Materials* menu under *Master Data*. Now, create it. Choose the product from the dropdown menu and add your components and the quantity. In this case, keep the default *BoM* type, which is *Manufacture this Product*."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:38
#: ../../manufacturing/management/bill_configuration.rst:37
msgid "Using the same BoM to describe Variants"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:40
#: ../../manufacturing/management/bill_configuration.rst:39
msgid "As said above, you can use *BoM* for *Product Variants*. It is basically the same as for the standard product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:43
#: ../../manufacturing/management/bill_configuration.rst:42
msgid "If your *BoM* is for one variant only, then specify which one in the *Product Variant* field. If not, specify the variant it is consumed for on each component line. You can add several variants for each component."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:52
#: ../../manufacturing/management/bill_configuration.rst:51
msgid "Adding a routing"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:54
#: ../../manufacturing/management/bill_configuration.rst:53
msgid "You can add routing to your *BoM*. You will do this if you need to define a series of operations required by your manufacturing process. To use it, enable the *Work Orders* feature in the *Manufacturing* app settings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:63
#: ../../manufacturing/management/bill_configuration.rst:62
msgid "Each *BoM* can have only one routing while each routing can be used multiple times."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:66
#: ../../manufacturing/management/bill_configuration.rst:65
msgid "Now that you have created your routing, add it to your *BoM*. You can select when, in the work operations, your components are consumed with the dropdown menu."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:74
#: ../../manufacturing/management/bill_configuration.rst:73
msgid "Adding By-Products"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:76
#: ../../manufacturing/management/bill_configuration.rst:75
msgid "In Odoo, a *by-product* is any product produced by a *BoM* in addition to the primary product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:79
#: ../../manufacturing/management/bill_configuration.rst:78
msgid "To add *by-products* to a *BoM*, you will first need to enable them from the *Manufacturing* app settings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:85
#: ../../manufacturing/management/bill_configuration.rst:84
msgid "Once the feature is enabled, you can add your *By-Products* to your *BoMs*. You can add as many *By-Products* as you want. Just keep in mind that you need to register during which operation your by-product is produced."
msgstr ""
@ -501,27 +501,19 @@ msgid "Subcontract the manufacturing"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:5
msgid "Some businesses subcontract the production of some finished products through subcontractors. This can be easily managed through Odoo."
msgid "Some businesses subcontract the production of finished products through subcontractors. This can be easily managed through Odoo."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:11
msgid "Go to the *Manufacturing app > Configuration > Settings* and tick the box *Subcontracting*."
msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and tick the box *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:17
msgid "You can now define subcontracted *Bill of Materials*. Therefore, you need to go to *Manufacturing > Master Data > Bill of Materials* and hit *Create*. In this *BoM*, list the components which will be used by the subcontractor to manufacture the subcontracted finished product. Specify that the *BoM* type is *Subcontracting*."
msgid "You can now define subcontracted *Bill of Materials*. Therefore, you need to go to :menuselection:`Manufacturing --> Master Data --> Bill of Materials` and hit *Create*. In this *BoM*, list the components which will be used by the subcontractor to manufacture the subcontracted finished product. Specify that the *BoM* type is *Subcontracting* and define one or several subcontractors who will provide you the product."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:22
msgid "You can also define subcontractors on the BoM."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:24
msgid "If no subcontractor is set, the BoM can be used by any subcontractor"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:26
msgid "If some are set, the BoM can only be used for those subcontractors"
#: ../../manufacturing/management/subcontracting.rst:29
msgid "And... the configuration part is already done!"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:32
@ -581,35 +573,43 @@ msgid "For option B, you can simply create the receipt manually with a partner o
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:73
msgid "Resupply the subcontractor with the components"
msgid "Receive or buy a subcontracted product with tracked components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:75
msgid "There are 3 ways to manage the resupply of your subcontractor with the components:"
msgid "In case the subcontracted product you receive from your subcontractor contains tracked components, you will need to specify the *serial/lot numbers* of the components in question for traceability. This operation is included in the receipt of the subcontracted product."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:80
msgid "**Manually**: You create a delivery order in which you set the"
msgid "On the receipt, you see a *Record Components* button appearing when necessary. If you click on it, a *Produce* wizard opens in which you will have to enter the *serial/lot numbers* of the components, and the finished product if it is also tracked, like in the below example."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:79
msgid "subcontractor as a partner and you choose the components to deliver."
#: ../../manufacturing/management/subcontracting.rst:91
msgid "Once this information has been entered, you will see a new icon on the receipt stock move, which will allow you to find back the components which are part of the finished product."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:89
msgid "**With reordering rules**: You can define a *reordering rule*"
#: ../../manufacturing/management/subcontracting.rst:99
msgid "Resupply the subcontractor with the components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:86
msgid "on the *Subcontracting location* to ensure that they are always enough components sent to your subcontractors. When the reordering rule is triggered, a delivery order is created for the product is automatically created."
#: ../../manufacturing/management/subcontracting.rst:101
msgid "There are 3 ways to manage the resupply of your subcontractor with the components:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:97
msgid "**On order**: You can also deliver the components to your"
#: ../../manufacturing/management/subcontracting.rst:104
msgid "**Manually**: You create a delivery order in which you set the subcontractor as a partner and you choose the components to deliver."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:95
msgid "subcontractors each time you order a subcontracted product. For this, you need to tick the route *Resupply Subcontractor on Order* on the wanted components."
#: ../../manufacturing/management/subcontracting.rst:110
msgid "You therefore need to activate *Multi-locations* in the inventory settings."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:115
msgid "**With reordering rules**: You can define a *reordering rule* on the *Subcontracting location* to ensure that they are always enough components sent to your subcontractors. When the reordering rule is triggered, a delivery order is created for the product is automatically created."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:120
msgid "**On order**: You can also deliver the components to your subcontractors each time you order a subcontracted product. For this, you need to tick the route *Resupply Subcontractor on Order* on the wanted components."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:3
@ -661,7 +661,7 @@ msgid "The Master Production Schedule (MPS) is a valuable tool to plan your prod
msgstr ""
#: ../../manufacturing/management/use_mps.rst:11
msgid "Go to the *Manufacturing app > Configuration > Settings* and activate the Master Production Schedule feature before hitting save."
msgid "Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` and activate the Master Production Schedule feature before hitting save."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:18
@ -669,7 +669,7 @@ msgid "In the manufacturing settings, you can define the time range of your MPS
msgstr ""
#: ../../manufacturing/management/use_mps.rst:20
msgid "Now, go in *Planning > Master Production Schedule* and click on add a product. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities to replenish."
msgid "Now, go in :menuselection:`Planning --> Master Production Schedule` and click on add a product. You can now define your safety stock target (= the stock you want to have on hand at the end of the period) and the minimum and maximum quantities to replenish."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:29

4
locale/sources/mobile.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -29,6 +29,6 @@ msgid "As of Odoo 12.0, 13.0 or above, there is no more complex configuration to
msgstr ""
#: ../../mobile/firebase.rst:13
msgid "Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification (OCN)* and make sure that **Push Notifications** is checked."
msgid "Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud Notification (OCN)` and make sure that **Push Notifications** is checked."
msgstr ""

114
locale/sources/planning.pot Normal file
View File

@ -0,0 +1,114 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../planning.rst:5
msgid "Planning"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:3
msgid "Create a schedule and make encoding easier"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:4
msgid "Organize regular schedules or forecast projects in a long term basis. Create shifts to manage your tasks, assign employees, and stay organized at a high level."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:8
msgid "Organize your team by roles"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:9
msgid "Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to the *Employees* application, select the respective employee, and under *Work Information* select the *Default Planning Role*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:18
msgid "Make shifts recurrent"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:19
msgid "While creating a shift, select *Repeat* and configure as needed, saving you from the need of re-planning it."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:28
msgid "Repeated shifts are generated for the next six months. A modification is possible in developer mode, from *Settings*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:32
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:36
msgid "Save shifts as templates"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:37
msgid "If creating a shift on the fly and knowing that you will use that template in the future, click on *Save as a Template*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:46
msgid "To create a template in advance, go to :menuselection:`Configuration --> Shifts Templates --> Create`."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:51
msgid "Duplicate a planning from the previous week"
msgstr ""
#: ../../planning/duplicate_a_planning.rst:52
msgid "When in the Gantt view, either under *Schedule by Employee, Role or Project*, instead of re-planning shifts that have been planned before, simply click on *Copy Previous Week*."
msgstr ""
#: ../../planning/duplicate_a_planning.rst:61
msgid "The integration with the *Time off* and *Employee* applications, show you grayed cells to the days when the employee does not work and is on vacation time, for example."
msgstr ""
#: ../../planning/send_planned_shifts.rst:3
msgid "Send planned shifts and give employees autonomy over shifts"
msgstr ""
#: ../../planning/send_planned_shifts.rst:4
msgid "If you are not on top of your tasks and shifts you might fall behind, loosing productivity. Allowing your employees to have a say over shifts helps you to be on top of your workload, and gives them flexibility."
msgstr ""
#: ../../planning/send_planned_shifts.rst:9
msgid "Publish and send the planned week by email"
msgstr ""
#: ../../planning/send_planned_shifts.rst:10
msgid "Once you have your shifts planned, click on *Send Schedule*. Select *Include Open shift* if you would like the *Unassigned* shifts to be seen."
msgstr ""
#: ../../planning/send_planned_shifts.rst:17
msgid "Choose if you just want to *Publish* or *Publish and Send*. If you *Publish and Send*, employees will get an email that will redirect them to their planned tasks:"
msgstr ""
#: ../../planning/send_planned_shifts.rst:25
msgid "Employees will not be able to see shifts until they have been published."
msgstr ""
#: ../../planning/send_planned_shifts.rst:29
msgid "Let employees unassign themselves from shifts"
msgstr ""
#: ../../planning/send_planned_shifts.rst:30
msgid "Go to *Configuration* and enable *Allow Unassignment*. From now on, when an employee opens his tasks, he can indicate his unavailability clicking on *I am unavailable*. The shift will be opened again, allowing someone else to take it."
msgstr ""
#: ../../planning/send_planned_shifts.rst:45
msgid "Employees have portal access; users have access to the database."
msgstr ""

44
locale/sources/point_of_sale.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-12-26 09:17+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -740,58 +740,58 @@ msgid "Connect a Payment Terminal"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:17
msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to `this documentation <https://www.odoo.com/documentation/user/12.0/iot.html>`__."
msgid "Connecting an Ingenico Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to the :doc:`IoT documentation <../../iot/config/connect>`."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:22
msgid "Once the IoT Box is up and running, you’ll need to link your payment terminal to your PoS. Open the Point of Sale app and go to *Configuration > Point of Sale*. Select a PoS, tick the IoT Box Device option and select your payment terminal."
#: ../../point_of_sale/payment/ingenico.rst:21
msgid "Once the IoT Box is up and running, you’ll need to link your payment terminal to your PoS. Open the *Point of Sale* app and go to :menuselection:`Configuration --> Point of Sale`. Select a PoS, tick the IoT Box Device option and select your payment terminal."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:31
#: ../../point_of_sale/payment/ingenico.rst:30
msgid "Configure the Lane/5000 for Ingenico BENELUX"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:33
msgid "Click on the F button of the terminal, then go in the *PoS Menu* > settings menu and enter the settings password."
#: ../../point_of_sale/payment/ingenico.rst:32
msgid "Click on the F button of the terminal, then go in the :menuselection:`PoS Menu --> Settings` and enter the settings password."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:36
#: ../../point_of_sale/payment/ingenico.rst:35
msgid "Now, click on connexion change and TCP/IP. Type the IP of your *IoT Box* (you can find it on the form view of your IoT Box). Then, enter 9000 as port. The terminal will restart. Once it is done, go on your *IoT Box* form in Odoo and verify that the terminal has been found."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:45
#: ../../point_of_sale/payment/ingenico.rst:44
msgid "Configure the payment method"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:47
#: ../../point_of_sale/payment/ingenico.rst:46
msgid "First, go in the general settings of the POS app, and activate the Ingenico setting."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:53
msgid "Go back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for Ingenico, select the payment terminal option Ingenico, and select your payment terminal device."
#: ../../point_of_sale/payment/ingenico.rst:52
msgid "Go back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Ingenico, select the payment terminal option Ingenico, and select your payment terminal device."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:62
#: ../../point_of_sale/payment/ingenico.rst:61
msgid "Pay with a payment terminal"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:64
#: ../../point_of_sale/payment/ingenico.rst:63
msgid "In your *PoS interface*, when processing a payment, select a *Payment Method* using a payment terminal. Check that the amount in the tendered column is the one that has to be sent to the payment terminal and click on *Send*. When the payment is successful, the status will change to *Payment Successful*."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:73
#: ../../point_of_sale/payment/ingenico.rst:72
msgid "If you want to cancel the payment request, click on cancel. You can still retry to send the payment request."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:76
#: ../../point_of_sale/payment/ingenico.rst:75
msgid "If there is any issue with the payment terminal, you can still force the payment using the *Force Done*. This will allow you to validate the order in Odoo even if the connexion between the terminal and Odoo has issues."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:82
#: ../../point_of_sale/payment/ingenico.rst:81
msgid "This option will only be available if you received an error message telling you the connexion failed."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:85
#: ../../point_of_sale/payment/ingenico.rst:84
#: ../../point_of_sale/payment/six.rst:103
msgid "Once your payment is processed, on the payment record, you’ll find the type of card that has been used and the transaction ID."
msgstr ""
@ -809,11 +809,11 @@ msgid "Please note SIX/Worldine is currently only available for UE customers."
msgstr ""
#: ../../point_of_sale/payment/six.rst:17
msgid "Connecting a SIX/Worldline Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to `this documentation <https://www.odoo.com/documentation/user/12.0/iot.html>`__."
msgid "Connecting a SIX/Worldline Payment Terminal to Odoo is a feature that requires an IoT Box. For more information on how to connect an IoT Box to your database, please refer to the :doc:`IoT documentation <../../iot/config/connect>`."
msgstr ""
#: ../../point_of_sale/payment/six.rst:22
msgid "Once the *IoT Box* is up and running, you’ll need to link it to your PoS. Open the Point of Sale app and go to *Configuration > Point of Sale*. Select a PoS, tick the IoT Box Device option and select your payment terminal."
msgid "Once the *IoT Box* is up and running, you’ll need to link it to your PoS. Open the Point of Sale app and go to :menuselection:`Configuration --> Point of Sale`. Select a PoS, tick the IoT Box Device option and select your payment terminal."
msgstr ""
#: ../../point_of_sale/payment/six.rst:30
@ -838,7 +838,7 @@ msgid "First, go in the general settings of the POS app, and activate the SIX se
msgstr ""
#: ../../point_of_sale/payment/six.rst:55
msgid "Back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for SIX, select the payment terminal option SIX, and select your payment terminal device."
msgid "Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for SIX, select the payment terminal option SIX, and select your payment terminal device."
msgstr ""
#: ../../point_of_sale/payment/six.rst:64
@ -887,7 +887,7 @@ msgid "First, go in the general settings of the POS app, and activate the Vantiv
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:24
msgid "Back in *Point of Sale > Configuration > Point of Sale*, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials."
msgid "Back in :menuselection:`Point of Sale --> Configuration --> Point of Sale`, go in the payments section and access your payment methods. Create a new payment method for Vantiv, select the payment terminal option Vantiv, and create new Vantiv credentials."
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:32

10
locale/sources/portal.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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,8 +24,8 @@ msgstr ""
msgid "In this section of the portal, you will find all the communications between you and Odoo: documents such as quotations, sales orders, invoices and subscriptions."
msgstr ""
#: ../../portal/my_odoo_portal.rst:11
msgid "To access this section, you have to log with your username and password to `Odoo <https://www.odoo.com/my/home>`__ . If you are already logged in, just click on your name on the top-right corner and select \"My Account\"."
#: ../../portal/my_odoo_portal.rst:12
msgid "To access this section, you have to log with your username and password to `Odoo <https://www.odoo.com/my/home>`_. If you are already logged in, just click on your name on the top-right corner and select \"My Account\"."
msgstr ""
#: ../../portal/my_odoo_portal.rst:20
@ -96,8 +96,8 @@ msgstr ""
msgid "If you want to remove the credit cards that are saved, you can do so by clicking on \"Manage your payment methods\" at the bottom of the page. Click \"Delete\" to delete the payment method."
msgstr ""
#: ../../portal/my_odoo_portal.rst:101
msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\". You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed, and you will no longer be able to access the database."
#: ../../portal/my_odoo_portal.rst:102
msgid "At the date of the next invoice, if there is no payment information provided or if your credit card has expired, the status of your subscription will change to \"To Renew\". You will then have 7 days to provide a valid method of payment. After this delay, the subscription will be closed, and you will no longer be able to access the database."
msgstr ""
#: ../../portal/my_odoo_portal.rst:108

4
locale/sources/practical.pot
View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"

4
locale/sources/purchase.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -77,7 +77,7 @@ msgid "See below a template of the columns used."
msgstr ""
#: ../../purchase/purchases/master/import.rst:33
msgid "`Template download <https://docs.google.com/spreadsheets/d/1N8c_eejLV_8NhYMGCfZau_oGCnRkUIT9nwdX7n0shhY/edit#gid=964193981>`__"
msgid ":download:`Click here to download the template <../../../_static/example_files/vendor_pricelists_template.csv>`"
msgstr ""
#: ../../purchase/purchases/master/suppliers.rst:3

10
locale/sources/quality.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -124,7 +124,7 @@ msgid "Create the Quality Control Point"
msgstr ""
#: ../../quality/checks/quality_mo.rst:18
msgid "To create a quality control point, open the quality app and go to *Control > Control Points*. There, hit create. Make sure to select *Manufacturing* as operation and choose the type of quality check you want to perform."
msgid "To create a quality control point, open the quality app and go to :menuselection:`Control --> Control Points`. There, hit create. Make sure to select *Manufacturing* as operation and choose the type of quality check you want to perform."
msgstr ""
#: ../../quality/checks/quality_mo.rst:27
@ -146,7 +146,7 @@ msgid "If you want to access all your quality checks, you can do this by opening
msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid "If you want to create a *Quality Control Point*, open the *Quality* app and go to *Control > Control Points*. Then, click on create. Make sure to select *Manufacturing* as operation and select the work order operation on which the quality check should be performed."
msgid "If you want to create a *Quality Control Point*, open the *Quality* app and go to :menuselection:`Control --> Control Points`. Then, click on create. Make sure to select *Manufacturing* as operation and select the work order operation on which the quality check should be performed."
msgstr ""
#: ../../quality/checks/quality_mo.rst:64
@ -166,7 +166,7 @@ msgid "Perform Quality Checks on Transfers"
msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid "To create a *Quality Control Point*, open the *Quality* application. Then, go to *Quality Control > Control Points > Create*. Now, you can define the quality control point you want to apply to a specific product. Don’t forget to select a transfer operation type."
msgid "To create a *Quality Control Point*, open the *Quality* application. Then, go to :menuselection:`Quality Control --> Control Points --> Create`. Now, you can define the quality control point you want to apply to a specific product. Don’t forget to select a transfer operation type."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:19
@ -202,7 +202,7 @@ msgid "Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:8
msgid "If it is the first *Quality Control Point* that you create, know that you need to open the *Quality* app. Then, go to *Quality Control > Control Points*. Once there, you have to define the product on which the quality control will take place, as well as the operation at which it should take place."
msgid "If it is the first *Quality Control Point* that you create, know that you need to open the *Quality* app. Then, go to :menuselection:`Quality Control --> Control Points`. Once there, you have to define the product on which the quality control will take place, as well as the operation at which it should take place."
msgstr ""
#: ../../quality/control/control_points.rst:14

813
locale/sources/sales.pot
View File

File diff suppressed because it is too large Load Diff

170
locale/sources/sms_marketing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -45,7 +45,7 @@ msgid "Build an SMS mailing"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:19
msgid "Go to *SMS Marketing > Create*."
msgid "Go to :menuselection:`SMS Marketing --> Create`."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:24
@ -125,7 +125,7 @@ msgid "Creating my own list of contacts, or importing it, is useful when I want
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:9
msgid "Go to *Contacts lists > Contacts lists > Create*. I’ll choose a name for my *Mailing list*, and activate the option *Public* if I would like to make the mailing list accessible to my recipients in the unsubscription page to allow them to update their subscription preferences."
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`. I’ll choose a name for my *Mailing list*, and activate the option *Public* if I would like to make the mailing list accessible to my recipients in the unsubscription page to allow them to update their subscription preferences."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:12
@ -149,7 +149,7 @@ msgid "Blacklist"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:30
msgid "If I’m coming from another software and have a list of clients who have already asked to be blacklisted from my news, I can import those entries in my database. For that, I’ll go to *Configuration > Phone Blacklist > Import*."
msgid "If I’m coming from another software and have a list of clients who have already asked to be blacklisted from my news, I can import those entries in my database. For that, I’ll go to :menuselection:`Configuration --> Phone Blacklist --> Import`."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:3
@ -165,78 +165,78 @@ msgid "Organize Email Marketing and SMS campaigns"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:10
msgid "First, make sure to have the necessary feature activated. Go to the *Email Marketing app > Configuration > Settings> activate the option Mailing Campaigns*."
msgid "First, make sure to have the necessary feature activated. Go to the :menuselection:`Email Marketing app --> Configuration --> Settings --> activate the option Mailing Campaigns`."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:15
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:16
msgid "Now, I’ll also have the menu *Campaigns* included in my *SMS Marketing* page, allowing me to have an overview of my SMS mailings and my email marketing ones."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:20
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:21
msgid "This feature is especially useful if I have aggregated campaigns, as I have a global reporting view. In addition to that, I can create stages in my kanban view to better organize the work being done."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:26
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:27
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:27
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:28
msgid "Sending SMSs through the contact’s form is available by default in Odoo. It makes my work easier if I need to send an SMS to a specific contact, for example. For that, I’ll go to the *Contacts* app, select the contact and click on the *SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:33
msgid "If I’d like to send a message in a batch here, I could go to *List View > select all the contacts > Action > Send SMS*."
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:34
msgid "If I’d like to send a message in a batch here, I could go to :menuselection:`List View --> select all the contacts --> Action --> Send SMS`."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:39
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:41
msgid "Set up SMS Templates"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:40
msgid "To set up *SMS Templates*, I’ll go to the *Settings* app and activate the *developer mode*. Now, back to *Settings* app, I’ll go to *Technical > Phone/SMS section > SMS Templates* and create the content I need."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:48
msgid "Use *Dynamic Placeholders* to adapt automatically the content of the SMS to the context."
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:42
msgid "To set up *SMS Templates*, I’ll go to the *Settings* app and activate the *developer mode*. Now, back to *Settings* app, I’ll go to :menuselection:`Technical --> Phone/SMS section --> SMS Templates` and create the content I need."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:52
msgid "SMS Text Messaging is available throughout Odoo! Here are some of our extra notable integrations:"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:54
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:55
msgid "*Subscription*: alert customers about their subscription."
msgid "Use *Dynamic Placeholders* to adapt automatically the content of the SMS to the context."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:56
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:57
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgid "SMS Text Messaging is available throughout Odoo! Here are some of our extra notable integrations:"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:58
msgid "*Inventory*: send an automatic confirmation when a delivery order is done."
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:59
msgid "*Sign*: receive a validation code to verify your identity before signing a document online."
msgid "*Subscription*: alert customers about their subscription."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:60
msgid "*SEPA debit payment provider*: send a verification code to your customers."
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:61
msgid "*Studio*: send an SMS according to your needs by using automated actions."
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:62
msgid "*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:63
msgid "*Sign*: receive a validation code to verify your identity before signing a document online."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:64
msgid "*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:65
msgid "*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:67
msgid "For more information about SMS integrations in Odoo and a list of frequently asked questions, go to `Pricing and FQA <fqapricing.html>`__."
msgstr ""
@ -252,123 +252,123 @@ msgstr ""
msgid "SMS Text Messaging is an In-App Purchase (IAP) service which requires prepaid credits to work. The price of an SMS depends on the destination and the length of the message. With 1 credit, I can send up to 92 SMSs."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:9
#: ../../sms_marketing/fqapricing.rst:11
msgid "**For more information, please consult our FAQ page**: `Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:11
msgid "To buy credits I will go to *Settings > Buy Credits* (under *Send SMS*); or go to *Settings > View my Services* (under *Odoo IAP*)."
#: ../../sms_marketing/fqapricing.rst:14
msgid "To buy credits I will go to :menuselection:`Settings --> Buy Credits` (under *Send SMS*); or go to :menuselection:`Settings --> View my Services` (under *Odoo IAP*)."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:18
#: ../../sms_marketing/fqapricing.rst:23
msgid "If you are on Odoo Online (SAAS) and have the Enterprise version, you benefit from free trial credits to test the feature."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:21
#: ../../sms_marketing/fqapricing.rst:27
msgid "FAQ"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:22
#: ../../sms_marketing/fqapricing.rst:28
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:24
#: ../../sms_marketing/fqapricing.rst:30
msgid "No, your credits won’t expire."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:26
#: ../../sms_marketing/fqapricing.rst:32
msgid "**Can I send an SMS to a phone number (which is not a mobile phone) because I see the icon in front of the field “phone”?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:28
#: ../../sms_marketing/fqapricing.rst:35
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:30
#: ../../sms_marketing/fqapricing.rst:37
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:32
#: ../../sms_marketing/fqapricing.rst:39
msgid "Yes."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:34
#: ../../sms_marketing/fqapricing.rst:41
msgid "**Can the recipient answer to me?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:36
#: ../../sms_marketing/fqapricing.rst:43
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:38
#: ../../sms_marketing/fqapricing.rst:45
msgid "**What happens if I send multiple SMS but I do not have enough credits to send them all?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:40
#: ../../sms_marketing/fqapricing.rst:47
msgid "The whole transaction is counted as a single one, so no SMS will be sent until you have enough credits to send them all."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:42
#: ../../sms_marketing/fqapricing.rst:50
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:44
msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of SMS sent is available under Settings> Activate the developer mode > Technical > SMS."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:46
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:48
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:50
msgid "**If I have a number that does not exist in the list of recipients, will I lose credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:52
msgid "Not if the phone number is in the wrong format (e.g. too many digits). Otherwise, if the SMS is sent to the wrong person or to a fake number, the credit will be lost."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:54
msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**"
msgid "Yes, the SMS is logged as a note under the chatter of the corresponding record, and a complete history of SMS sent is available under :menuselection:`Settings --> Activate the developer mode --> Technical --> SMS`."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:56
msgid "The SMS will not be delivered to that kind of number, so you won’t be charged."
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:58
msgid "**Can I identify the numbers that do not exist when I send several SMSs?**"
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:60
msgid "Only the ones that have an invalid format."
msgid "**If I have a number that does not exist in the list of recipients, will I lose credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:62
msgid "**How does the GDPR regulation affect this service?**"
msgid "Not if the phone number is in the wrong format (e.g. too many digits). Otherwise, if the SMS is sent to the wrong person or to a fake number, the credit will be lost."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:64
msgid "Please find our Privacy Policy here: `Odoo IPA Purchase Privacy Policy <https://iap.odoo.com/privacy#sms>`__"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:66
msgid "**How many types of SMS exist and how many characters make 1 SMS?**"
#: ../../sms_marketing/fqapricing.rst:65
msgid "**What happens if I send my SMS to a paying number (e.g.: a contest to win a ticket for a festival)?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:68
msgid "There are 2 types of SMS message:"
msgid "The SMS will not be delivered to that kind of number, so you won’t be charged."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:70
msgid "**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:72
msgid "Only the ones that have an invalid format."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:74
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:76
msgid "Please find our Privacy Policy here: `Odoo IPA Purchase Privacy Policy <https://iap.odoo.com/privacy#sms>`__"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:79
msgid "**How many types of SMS exist and how many characters make 1 SMS?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:81
msgid "There are 2 types of SMS message:"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:83
msgid "*Standard* (GSM-7): contains only characters from the GSM-7 set, which can be seen in the following picture."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:75
#: ../../sms_marketing/fqapricing.rst:89
msgid "*Unicode*: contains at least one character that is not in the previous table. For Standard SMS the size limit is 160 characters, and for Unicode is 70. Above these limits, the content is divided into a multi-part message. The system will inform you in real-time about the number of SMS your message represents."
msgstr ""

12
locale/sources/social_marketing.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -53,12 +53,8 @@ msgstr ""
msgid "Engagement: Number of times people have engaged with your posts"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:35
msgid "Stories: Number of times people who have engaged with your channel"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:35
msgid "have created stories on their friend’s or follower’s feed (Shares, Retweet,..)"
#: ../../social_marketing/social_marketing/social_marketing.rst:34
msgid "Stories: Number of times people who have engaged with your channel have created stories on their friend’s or follower’s feed (Shares, Retweet,..)"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:37
@ -102,7 +98,7 @@ msgid "Configure your own Facebook and Twitter developer accounts"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:93
msgid "By default, the Social application is already configured with a Facebook and Twitter developer accounts but you can use your own if necessary. Activate the developer mode, go to Configuration > Settings and enter your own API keys."
msgid "By default, the Social application is already configured with a Facebook and Twitter developer accounts but you can use your own if necessary. Activate the developer mode, go to :menuselection:`Configuration --> Settings` and enter your own API keys."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:102

135
locale/sources/support.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-12-26 09:17+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -261,182 +261,177 @@ msgid "Edit an existing page"
msgstr ""
#: ../../support/user_doc.rst:17
msgid "As our documentation is maintained on GitHub, you'll need a free `GitHub account <https://help.github.com/en/articles/signing-up-for-a-new-github-account>`_."
msgstr ""
#: ../../support/user_doc.rst:18
msgid "Pick a page in our `user documentation <https://www.odoo.com/documentation/user>`_. **Please take care of choosing the right version of Odoo.**"
msgid "As our documentation is maintained on GitHub, you'll need a free `GitHub account <https://github.com/join>`_."
msgstr ""
#: ../../support/user_doc.rst:19
msgid "Pick a page in our :doc:`user documentation <../index>`. **Please take care of selecting the right version of Odoo.**"
msgstr ""
#: ../../support/user_doc.rst:21
msgid "Click on **Edit on Github** in the left menu."
msgstr ""
#: ../../support/user_doc.rst:25
msgid "If this is the first time you edit our documentation, click on **Fork repository**, else you won't see this step."
#: ../../support/user_doc.rst:27
msgid "If this is the first time you edit our documentation, click on **Fork repository**, otherwise you won't see this step."
msgstr ""
#: ../../support/user_doc.rst:26
#: ../../support/user_doc.rst:29
msgid "Use Github's editor to add your text. Text is tagged with a simple syntax called `RST <http://docutils.sourceforge.net/rst.html>`_. Don't worry, it's not so hard to learn 🤓... See the following section of this document for a quick overview of RST commands."
msgstr ""
#: ../../support/user_doc.rst:32
#: ../../support/user_doc.rst:37
msgid "Click on **Preview changes** to review your contribution in a human-readable format."
msgstr ""
#: ../../support/user_doc.rst:38
#: ../../support/user_doc.rst:43
msgid "In the **Propose file change** section, add a short title to your contribution. The title should summarize your changes. You may use the second box to add an extended description if your contribution requires a longer explanation."
msgstr ""
#: ../../support/user_doc.rst:44
#: ../../support/user_doc.rst:51
msgid "Submit your contribution by clicking on **Propose file change**."
msgstr ""
#: ../../support/user_doc.rst:45
#: ../../support/user_doc.rst:52
msgid "Click on **Create pull request**."
msgstr ""
#: ../../support/user_doc.rst:46
#: ../../support/user_doc.rst:53
msgid "Wait for an Odoo maintainer to add your contribution. Thank you for your help!"
msgstr ""
#: ../../support/user_doc.rst:49
#: ../../support/user_doc.rst:56
msgid "There is no automatic port of your edit to another version of the documentation."
msgstr ""
#: ../../support/user_doc.rst:51
#: ../../support/user_doc.rst:58
msgid "If your change should apply to multiple versions of Odoo, please warn us in your contribution message."
msgstr ""
#: ../../support/user_doc.rst:55
#: ../../support/user_doc.rst:62
msgid "RST Cheat Sheet"
msgstr ""
#: ../../support/user_doc.rst:57
#: ../../support/user_doc.rst:66
msgid "Here is a summary of the markup elements you may use while editing our documentation."
msgstr ""
#: ../../support/user_doc.rst:60
#: ../../support/user_doc.rst:69
msgid "Code"
msgstr ""
#: ../../support/user_doc.rst:60
#: ../../support/user_doc.rst:69
msgid "Display"
msgstr ""
#: ../../support/user_doc.rst:60
#: ../../support/user_doc.rst:69
msgid "Comments"
msgstr ""
#: ../../support/user_doc.rst:62
#: ../../support/user_doc.rst:71
msgid "Text in *italics*"
msgstr ""
#: ../../support/user_doc.rst:66
#: ../../support/user_doc.rst:75
msgid "Text in **bold** letters"
msgstr ""
#: ../../support/user_doc.rst:70
#: ../../support/user_doc.rst:76
#: ../../support/user_doc.rst:79
#: ../../support/user_doc.rst:85
msgid "Numbered"
msgstr ""
#: ../../support/user_doc.rst:71
#: ../../support/user_doc.rst:77
#: ../../support/user_doc.rst:80
#: ../../support/user_doc.rst:86
msgid "Bullet"
msgstr ""
#: ../../support/user_doc.rst:72
#: ../../support/user_doc.rst:78
#: ../../support/user_doc.rst:81
#: ../../support/user_doc.rst:87
msgid "List"
msgstr ""
#: ../../support/user_doc.rst:70
#: ../../support/user_doc.rst:76
#: ../../support/user_doc.rst:79
#: ../../support/user_doc.rst:85
msgid "Must be surrounded by white lines."
msgstr ""
#: ../../support/user_doc.rst:82
#: ../../support/user_doc.rst:91
msgid "This is `a hyper link <https://www.odoo.com>`_."
msgstr ""
#: ../../support/user_doc.rst:82
#: ../../support/user_doc.rst:91
msgid "Here is `how to enter backticks on your keyboard <https://superuser.com/a/254077>`_."
msgstr ""
#: ../../support/user_doc.rst:85
#: ../../support/user_doc.rst:94
msgid "Don't forget terminal *underscore*."
msgstr ""
#: ../../support/user_doc.rst:90
#: ../../support/user_doc.rst:99
msgid "There are many more commands available, see `comprehensive documentation <http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html>`_ of RST."
msgstr ""
#: ../../support/user_doc.rst:94
#: ../../support/user_doc.rst:104
msgid "Add images to your documents"
msgstr ""
#: ../../support/user_doc.rst:98
#: ../../support/user_doc.rst:108
msgid "This procedure is possible only for users who have **push** access on the documentation repository (eg: mainly, Odoo maintainers). We are working on improving this."
msgstr ""
#: ../../support/user_doc.rst:101
#: ../../support/user_doc.rst:111
msgid "First of all, prepare your screenshots."
msgstr ""
#: ../../support/user_doc.rst:103
#: ../../support/user_doc.rst:113
msgid "They must be good-quality PNG images."
msgstr ""
#: ../../support/user_doc.rst:104
#: ../../support/user_doc.rst:114
msgid "Crop your screenshots to display only the relevant part of the screen. Large screenshots are hard to read and don't display well in a documentation."
msgstr ""
#: ../../support/user_doc.rst:106
#: ../../support/user_doc.rst:116
msgid "Always take your screenshots on a demo instance of Odoo; **never** include any personal data."
msgstr ""
#: ../../support/user_doc.rst:108
#: ../../support/user_doc.rst:118
msgid "Upload them to the ``media/`` directory which is located next to the page you are editing. If the directory does not exist, create it."
msgstr ""
#: ../../support/user_doc.rst:109
#: ../../support/user_doc.rst:119
msgid "When editing your page, use this code piece in order to load your image:"
msgstr ""
#: ../../support/user_doc.rst:117
#: ../../support/user_doc.rst:127
msgid "Submit your changes"
msgstr ""
#: ../../support/user_doc.rst:128
#: ../../support/user_doc.rst:137
msgid "Technical Details for Nerds"
msgstr ""
#: ../../support/user_doc.rst:130
msgid "Advanced users may, of course, fork and clone `the GitHub repository <https://github.com/odoo/documentation-user>`_. Then submit a pull request with the canonical Git/GitHub workflow."
#: ../../support/user_doc.rst:139
msgid "Advanced users may, of course, fork and clone the `GitHub repository <https://github.com/odoo/documentation-user>`_. Then submit a pull request with the canonical Git/GitHub workflow."
msgstr ""
#: ../../support/user_doc.rst:133
#: ../../support/user_doc.rst:142
msgid "See our `README <https://github.com/odoo/documentation-user/blob/13.0/README.rst>`_ file about building the documentation."
msgstr ""
#: ../../support/user_doc.rst:138
#: ../../support/user_doc.rst:147
msgid "Developer documentation"
msgstr ""
#: ../../support/user_doc.rst:140
#: ../../support/user_doc.rst:149
msgid "Documentation that targets developers of Odoo apps is maintained alongside `the source code of Odoo <https://github.com/odoo/odoo/tree/13.0/doc>`_."
msgstr ""
#: ../../support/user_doc.rst:143
#: ../../support/user_doc.rst:152
msgid "User documentation might contain technicalities yet, when they are related to configuration and everyday use of Odoo."
msgstr ""
#: ../../support/user_doc.rst:149
#: ../../support/where_can_i_get_support.rst:36
msgid "*Last revision of this page:* |date|"
msgstr ""
#: ../../support/what_can_i_expect.rst:8
msgid "What can I expect from the support service?"
msgstr ""
@ -533,43 +528,43 @@ msgstr ""
msgid "Users who have a valid Odoo Enterprise subscription may always contact our support teams through our `support form <https://www.odoo.com/help>`_, no matter the hosting type you chose (Odoo Online, Odoo.sh or on your own server)."
msgstr ""
#: ../../support/where_can_i_get_support.rst:14
#: ../../support/where_can_i_get_support.rst:16
msgid "Please include in your request:"
msgstr ""
#: ../../support/where_can_i_get_support.rst:16
msgid "your subscription number,"
msgstr ""
#: ../../support/where_can_i_get_support.rst:17
msgid "if your database is hosted by Odoo (Odoo Online or Odoo.sh), please also send the URL of your database."
#: ../../support/where_can_i_get_support.rst:18
msgid "your subscription number"
msgstr ""
#: ../../support/where_can_i_get_support.rst:19
msgid "the URL of your database if your database is hosted by Odoo (Odoo Online or Odoo.sh)"
msgstr ""
#: ../../support/where_can_i_get_support.rst:21
msgid "Our agents will get back to you as soon as possible."
msgstr ""
#: ../../support/where_can_i_get_support.rst:23
#: ../../support/where_can_i_get_support.rst:25
msgid "Odoo Community"
msgstr ""
#: ../../support/where_can_i_get_support.rst:25
#: ../../support/where_can_i_get_support.rst:27
msgid "*Odoo Community users don't get access to the support service.*"
msgstr ""
#: ../../support/where_can_i_get_support.rst:27
#: ../../support/where_can_i_get_support.rst:29
msgid "Here are some resources that might help you:"
msgstr ""
#: ../../support/where_can_i_get_support.rst:29
#: ../../support/where_can_i_get_support.rst:31
msgid "Our `documentation pages <https://www.odoo.com/page/docs>`_."
msgstr ""
#: ../../support/where_can_i_get_support.rst:30
#: ../../support/where_can_i_get_support.rst:32
msgid "Ask your question on the `community forum <https://www.odoo.com/forum/help-1>`_."
msgstr ""
#: ../../support/where_can_i_get_support.rst:31
msgid "`Buy Odoo Enterprise <https://www.odoo.com/help>`_ to get the support and bugfix services."
#: ../../support/where_can_i_get_support.rst:33
msgid "`Buy Odoo Enterprise <https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ to get the support and bugfix services."
msgstr ""

214
locale/sources/website.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-21 10:39+0100\n"
"POT-Creation-Date: 2020-01-16 09:46+0100\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"
@ -49,10 +49,10 @@ msgid "Go to the *Configuration* menu of your Odoo's Website app. In the setting
msgstr ""
#: ../../website/optimize/google_analytics.rst:27
msgid "To make your first steps in Google Analytics, refer to `Google Documentation. <https://support.google.com/analytics/answer/1008015?hl=en/>`__"
msgid "To make your first steps in Google Analytics, refer to `Google Documentation <https://support.google.com/analytics/answer/1008015?hl=en/>`_."
msgstr ""
#: ../../website/optimize/google_analytics.rst:31
#: ../../website/optimize/google_analytics.rst:32
msgid ":doc:`google_analytics_dashboard`"
msgstr ""
@ -169,15 +169,15 @@ msgid "**Odoo Blogs**: write great contents."
msgstr ""
#: ../../website/optimize/seo.rst:62
msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `https://www.odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`__"
msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`_"
msgstr ""
#: ../../website/optimize/seo.rst:66
msgid "**Odoo Forum**: let your community create contents for you. Example: `https://odoo.com/forum/1 <https://odoo.com/forum/1>`__ (accounts for 30% of Odoo.com landing pages)"
msgid "**Odoo Forum**: let your community create contents for you. Example: `odoo.com/forum/1 <https://odoo.com/forum/1>`_ (accounts for 30% of Odoo.com landing pages)"
msgstr ""
#: ../../website/optimize/seo.rst:70
msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `https://www.odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`__ (1000 pages created per month)"
msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`_ (1000 pages created per month)"
msgstr ""
#: ../../website/optimize/seo.rst:76
@ -237,7 +237,7 @@ msgid "Test Your Website"
msgstr ""
#: ../../website/optimize/seo.rst:131
msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `https://www.woorank.com <https://www.woorank.com>`__"
msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `woorank.com <https://www.woorank.com>`_"
msgstr ""
#: ../../website/optimize/seo.rst:136
@ -737,7 +737,7 @@ msgid "Browser Caching"
msgstr ""
#: ../../website/optimize/seo.rst:548
msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `http://localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website."
msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website."
msgstr ""
#: ../../website/optimize/seo.rst:555
@ -749,78 +749,78 @@ msgid "Scalability"
msgstr ""
#: ../../website/optimize/seo.rst:562
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). 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>`_"
msgstr ""
#: ../../website/optimize/seo.rst:568
#: ../../website/optimize/seo.rst:571
msgid "Here is the slide that summarizes the scalability of Odoo Website & eCommerce."
msgstr ""
#: ../../website/optimize/seo.rst:574
#: ../../website/optimize/seo.rst:577
msgid "Search Engines Files"
msgstr ""
#: ../../website/optimize/seo.rst:577
#: ../../website/optimize/seo.rst:580
msgid "Sitemap"
msgstr ""
#: ../../website/optimize/seo.rst:579
#: ../../website/optimize/seo.rst:582
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 ""
#: ../../website/optimize/seo.rst:583
#: ../../website/optimize/seo.rst:586
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 ""
#: ../../website/optimize/seo.rst:589
#: ../../website/optimize/seo.rst:592
msgid "Every sitemap entry has 4 attributes that are computed automatically:"
msgstr ""
#: ../../website/optimize/seo.rst:591
#: ../../website/optimize/seo.rst:594
msgid "``<loc>`` : the URL of a page"
msgstr ""
#: ../../website/optimize/seo.rst:593
#: ../../website/optimize/seo.rst:596
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 ""
#: ../../website/optimize/seo.rst:598
#: ../../website/optimize/seo.rst:601
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 ""
#: ../../website/optimize/seo.rst:605
#: ../../website/optimize/seo.rst:608
msgid "Structured Data Markup"
msgstr ""
#: ../../website/optimize/seo.rst:607
#: ../../website/optimize/seo.rst:610
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 ""
#: ../../website/optimize/seo.rst:612
#: ../../website/optimize/seo.rst:615
msgid "Google supports a number of rich snippets for content types, including: Reviews, People, Products, Businesses, Events and Organizations."
msgstr ""
#: ../../website/optimize/seo.rst:615
#: ../../website/optimize/seo.rst:618
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 ""
#: ../../website/optimize/seo.rst:625
#: ../../website/optimize/seo.rst:628
msgid "robots.txt"
msgstr ""
#: ../../website/optimize/seo.rst:627
#: ../../website/optimize/seo.rst:630
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 ""
#: ../../website/optimize/seo.rst:631
#: ../../website/optimize/seo.rst:634
msgid "User-agent: \\* Sitemap: https://www.odoo.com/sitemap.xml"
msgstr ""
#: ../../website/optimize/seo.rst:634
#: ../../website/optimize/seo.rst:637
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 ""
#: ../../website/optimize/seo.rst:638
#: ../../website/optimize/seo.rst:641
msgid "You can customize the file *robots* in 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 ""
@ -968,19 +968,23 @@ msgstr ""
msgid "It is not required anymore: Odoo generates the certificate for you automatically, using integration with `Let's Encrypt Certificate Authority and ACME protocol <https://letsencrypt.org/how-it-works/>`__. In order to get this, simply add your domain name in your customer portal (a separate certificate is generated for each domain name specified)."
msgstr ""
#: ../../website/publish/domain_name.rst:92
msgid "If you already use CloudFlare or a similar service, you can keep using it or simply change for Odoo. The choice is yours."
#: ../../website/publish/domain_name.rst:93
msgid "**Please note that the certificate generation may take up to 24h.**"
msgstr ""
#: ../../website/publish/domain_name.rst:95
msgid "If you already use CloudFlare or a similar service, you can keep using it or simply change for Odoo. The choice is yours."
msgstr ""
#: ../../website/publish/domain_name.rst:98
msgid "My website is indexed twice by Google"
msgstr ""
#: ../../website/publish/domain_name.rst:97
#: ../../website/publish/domain_name.rst:100
msgid "If you set up a custom domain *mydomain.com* name for *mydatabase.odoo.com*, Google indexes your website under both names. This is a limitation of the Odoo cloud platforms/"
msgstr ""
#: ../../website/publish/domain_name.rst:102
#: ../../website/publish/domain_name.rst:105
msgid ":doc:`../../discuss/email_servers`"
msgstr ""
@ -1017,7 +1021,7 @@ msgid "Once the theme is selected, you can start to build the homepage of your w
msgstr ""
#: ../../website/publish/multi_website.rst:48
msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (CNAME) and to authorize it Odoo-side. `Read <https://www.odoo.com/documentation/user/online/website/publish/domain_name.html>`__"
msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (``CNAME``) and to authorize it Odoo-side. See :doc:`domain_name`."
msgstr ""
#: ../../website/publish/multi_website.rst:52
@ -1025,7 +1029,7 @@ msgid "Create the menu"
msgstr ""
#: ../../website/publish/multi_website.rst:54
msgid "The new website has a default menu with all the installed applications. To edit it, click *Pages > Edit Menu*. Moving forward you only edit the menu of the current website."
msgid "The new website has a default menu with all the installed applications. To edit it, click :menuselection:`Pages --> Edit Menu`. Moving forward you only edit the menu of the current website."
msgstr ""
#: ../../website/publish/multi_website.rst:59
@ -1037,258 +1041,258 @@ msgid "As easy as ABC! There is a website switcher in the right corner of the ed
msgstr ""
#: ../../website/publish/multi_website.rst:71
msgid "When switching, you are redirected to the same domain path on the other website (e.g.,/shop/myproduct). If this URL is not used, you will be redirected to a 404 page but suggested to create a new page from there."
msgstr ""
#: ../../website/publish/multi_website.rst:74
msgid "Add features"
msgid "When switching, you are redirected to the same domain path on the other website (e.g., ``/shop/myproduct``). If this URL is not used, you will be redirected to a 404 page but prompted to create a new page from there."
msgstr ""
#: ../../website/publish/multi_website.rst:76
msgid "Add features"
msgstr ""
#: ../../website/publish/multi_website.rst:78
msgid "The website apps you install (e.g., Slides, Blogs) are made available on all your websites. You can, of course, keep them hidden in one website by removing the menu item."
msgstr ""
#: ../../website/publish/multi_website.rst:80
#: ../../website/publish/multi_website.rst:82
msgid "Each website comes with a high range of specific options in the settings. First, select the website to configure."
msgstr ""
#: ../../website/publish/multi_website.rst:86
#: ../../website/publish/multi_website.rst:88
msgid "Then, take a look at the options flagged with the earth icon. It means they only impact the very website you are working on."
msgstr ""
#: ../../website/publish/multi_website.rst:92
#: ../../website/publish/multi_website.rst:94
msgid "You can, for instance, set specific :"
msgstr ""
#: ../../website/publish/multi_website.rst:94
#: ../../website/publish/multi_website.rst:96
msgid "languages,"
msgstr ""
#: ../../website/publish/multi_website.rst:96
#: ../../website/publish/multi_website.rst:98
msgid "domain names,"
msgstr ""
#: ../../website/publish/multi_website.rst:98
#: ../../website/publish/multi_website.rst:100
msgid "social media links,"
msgstr ""
#: ../../website/publish/multi_website.rst:100
#: ../../website/publish/multi_website.rst:102
msgid "customer portal mode (B2C vs. B2B),"
msgstr ""
#: ../../website/publish/multi_website.rst:102
#: ../../website/publish/multi_website.rst:104
msgid "dedicated live chat channels,"
msgstr ""
#: ../../website/publish/multi_website.rst:104
#: ../../website/publish/multi_website.rst:106
msgid "etc."
msgstr ""
#: ../../website/publish/multi_website.rst:106
#: ../../website/publish/multi_website.rst:108
msgid "The other options are global and apply to all your websites."
msgstr ""
#: ../../website/publish/multi_website.rst:109
#: ../../website/publish/multi_website.rst:111
msgid "Manage domain names"
msgstr ""
#: ../../website/publish/multi_website.rst:111
msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using Geo IP."
#: ../../website/publish/multi_website.rst:113
msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using GeoIP."
msgstr ""
#: ../../website/publish/multi_website.rst:120
msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *Geoip* library."
msgstr ""
#: ../../website/publish/multi_website.rst:123
msgid "`Read the full documenation about domain names here <https://www.odoo.com/documentation/user/online/website/publish/domain_name.html>`__,"
#: ../../website/publish/multi_website.rst:122
msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *GeoIP* library."
msgstr ""
#: ../../website/publish/multi_website.rst:126
msgid "Customize the visitor experience"
msgid ":doc:`domain_name`"
msgstr ""
#: ../../website/publish/multi_website.rst:129
msgid "Customize the visitor experience"
msgstr ""
#: ../../website/publish/multi_website.rst:132
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 ""
#: ../../website/publish/multi_website.rst:139
#: ../../website/publish/multi_website.rst:142
msgid "Publish specific content per website"
msgstr ""
#: ../../website/publish/multi_website.rst:142
#: ../../website/publish/multi_website.rst:145
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 ""
#: ../../website/publish/multi_website.rst:150
#: ../../website/publish/multi_website.rst:153
msgid "Here are all the objects that you can link to *either one or all the websites*:"
msgstr ""
#: ../../website/publish/multi_website.rst:153
#: ../../website/publish/multi_website.rst:156
msgid "Products"
msgstr ""
#: ../../website/publish/multi_website.rst:155
#: ../../website/publish/multi_website.rst:158
msgid "Product Categories for eCommerce"
msgstr ""
#: ../../website/publish/multi_website.rst:157
#: ../../website/publish/multi_website.rst:160
msgid "Blogs"
msgstr ""
#: ../../website/publish/multi_website.rst:159
#: ../../website/publish/multi_website.rst:162
msgid "Slide Channels"
msgstr ""
#: ../../website/publish/multi_website.rst:161
#: ../../website/publish/multi_website.rst:164
msgid "Forums"
msgstr ""
#: ../../website/publish/multi_website.rst:163
#: ../../website/publish/multi_website.rst:166
msgid "Events"
msgstr ""
#: ../../website/publish/multi_website.rst:165
#: ../../website/publish/multi_website.rst:168
msgid "Job Positions"
msgstr ""
#: ../../website/publish/multi_website.rst:168
#: ../../website/publish/multi_website.rst:171
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 ""
#: ../../website/publish/multi_website.rst:172
#: ../../website/publish/multi_website.rst:175
msgid "Publish a page in all websites"
msgstr ""
#: ../../website/publish/multi_website.rst:174
#: ../../website/publish/multi_website.rst:177
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 ""
#: ../../website/publish/multi_website.rst:178
#: ../../website/publish/multi_website.rst:181
msgid "If you want to duplicate it in just one other website, duplicate the page and set the new website."
msgstr ""
#: ../../website/publish/multi_website.rst:184
#: ../../website/publish/multi_website.rst:187
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 ""
#: ../../website/publish/multi_website.rst:189
#: ../../website/publish/multi_website.rst:192
msgid "By grouping pages by URL in the page manager, you quickly find the original page behind each edited page."
msgstr ""
#: ../../website/publish/multi_website.rst:196
#: ../../website/publish/multi_website.rst:199
msgid "Multi-companies"
msgstr ""
#: ../../website/publish/multi_website.rst:198
#: ../../website/publish/multi_website.rst:201
msgid "Each website can be linked to a specific company of your system, in a multi-companies environment."
msgstr ""
#: ../../website/publish/multi_website.rst:204
#: ../../website/publish/multi_website.rst:207
msgid "With such a configuration, only company-related data appear on the website (products, jobs, events, etc.)."
msgstr ""
#: ../../website/publish/multi_website.rst:207
#: ../../website/publish/multi_website.rst:210
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 ""
#: ../../website/publish/multi_website.rst:213
#: ../../website/publish/multi_website.rst:216
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 ""
#: ../../website/publish/multi_website.rst:219
#: ../../website/publish/multi_website.rst:222
msgid "Configure your eCommerce website"
msgstr ""
#: ../../website/publish/multi_website.rst:221
#: ../../website/publish/multi_website.rst:224
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 ""
#: ../../website/publish/multi_website.rst:226
#: ../../website/publish/multi_website.rst:229
msgid "Products only available on one website"
msgstr ""
#: ../../website/publish/multi_website.rst:228
#: ../../website/publish/multi_website.rst:231
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 ""
#: ../../website/publish/multi_website.rst:236
#: ../../website/publish/multi_website.rst:239
msgid "Products available on *some* websites"
msgstr ""
#: ../../website/publish/multi_website.rst:238
#: ../../website/publish/multi_website.rst:241
msgid "To make a product available on some websites, but not all of them, you should duplicate the product for each website."
msgstr ""
#: ../../website/publish/multi_website.rst:241
#: ../../website/publish/multi_website.rst:244
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 ""
#: ../../website/publish/multi_website.rst:248
#: ../../website/publish/multi_website.rst:251
msgid "Pricelists"
msgstr ""
#: ../../website/publish/multi_website.rst:250
#: ../../website/publish/multi_website.rst:253
msgid "To manage specific prices by websites, you can activate *Multiple Sales Prices per Product* in Website settings."
msgstr ""
#: ../../website/publish/multi_website.rst:253
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. Read `Pricelists Documentation <https://www.odoo.com/documentation/user/online/ecommerce/maximizing_revenue/pricing.html>`__,"
#: ../../website/publish/multi_website.rst:256
msgid "Then, go to :menuselection:`Website --> Products --> Pricelists` to create additional pricelists. See :doc:`../../ecommerce/maximizing_revenue/pricing`."
msgstr ""
#: ../../website/publish/multi_website.rst:256
#: ../../website/publish/multi_website.rst:259
msgid "If you need help. Select a website to make a pricelist only available on this website."
msgstr ""
#: ../../website/publish/multi_website.rst:262
#: ../../website/publish/multi_website.rst:265
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 ""
#: ../../website/publish/multi_website.rst:267
#: ../../website/publish/multi_website.rst:270
msgid "Payment Acquirers and Delivery Methods"
msgstr ""
#: ../../website/publish/multi_website.rst:269
#: ../../website/publish/multi_website.rst:272
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 ""
#: ../../website/publish/multi_website.rst:275
#: ../../website/publish/multi_website.rst:278
msgid "Customer accounts"
msgstr ""
#: ../../website/publish/multi_website.rst:277
#: ../../website/publish/multi_website.rst:280
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 ""
#: ../../website/publish/multi_website.rst:287
#: ../../website/publish/multi_website.rst:290
msgid "Technical hints for customization"
msgstr ""
#: ../../website/publish/multi_website.rst:289
#: ../../website/publish/multi_website.rst:292
msgid "If you want to publish custom objects on the website, here are a few tips to make it work with multi websites:"
msgstr ""
#: ../../website/publish/multi_website.rst:293
#: ../../website/publish/multi_website.rst:296
msgid "Sitemap: don’t forget the domain in the route to only publish"
msgstr ""
#: ../../website/publish/multi_website.rst:293
#: ../../website/publish/multi_website.rst:296
msgid "available records in each website’s sitemap."
msgstr ""
#: ../../website/publish/multi_website.rst:297
#: ../../website/publish/multi_website.rst:300
msgid "Access: you should call the method"
msgstr ""
#: ../../website/publish/multi_website.rst:296
#: ../../website/publish/multi_website.rst:299
msgid "*can_access_from_current_website* in the controller to make sure the visitor can see a record in the current website."
msgstr ""
#: ../../website/publish/multi_website.rst:301
#: ../../website/publish/multi_website.rst:304
msgid "Search: when a list of records is displayed, don’t forget to specify"
msgstr ""
#: ../../website/publish/multi_website.rst:300
#: ../../website/publish/multi_website.rst:303
msgid "the domain to only display records available for the current website."
msgstr ""
@ -1333,7 +1337,7 @@ msgid "To translate the content of the website, click on **Translate** (here **T
msgstr ""
#: ../../website/publish/translate.rst:45
msgid "There, if you have installed the Gengo Translator, You will see that next to the **Translate** button you also have a button **Translate automatically**. Once you click on that button, you will be asked some information on your account. If you don't have an account yet, go to `*https://gengo.com/auth/form/login/* <https://gengo.com/auth/form/login/>`__ in order to create one. You need to ask for a public key and a private key."
msgid "There, if you have installed the Gengo Translator, You will see that next to the **Translate** button you also have a button **Translate automatically**. Once you click on that button, you will be asked some information on your account. If you don't have an account yet, follow `this link <https://gengo.com/auth/form/login/>`_ in order to create one. You need to ask for a public key and a private key."
msgstr ""
#: ../../website/publish/translate.rst:53