[I18N] *: export 12.0 source terms

This commit is contained in:
Martin Trigaux 2019-09-16 15:50:50 +02:00
parent be47d7c8bd
commit 812d290c07
16 changed files with 2659 additions and 1774 deletions

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-07-03 08:44+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -97,7 +97,7 @@ msgid "|image0|\\ |image1|"
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:16
msgid "With the CRM app installed, you benefit from ready-to-use contact form on your Odoo website that will generate leads/opportunities automatically."
msgid "With the CRM app installed, you benefit from a ready-to-use contact form on your Odoo website that will generate leads/opportunities automatically."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:23
@ -110,23 +110,23 @@ msgid "Create a custom contact form"
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:34
msgid "You may want to know more from your visitor when they use the contact form to contact you. You will then need to build a custom contact form on your website. Those contact forms can generate multiple types of records in the system (emails, leads/opportunities, project tasks, helpdesk tickets, etc...)"
msgid "You may want to know more from your visitor when they use the contact form to you will need to build a custom contact form on your website. These contact forms can generate multiple types of records in the system (emails, leads/opportunities, project tasks, helpdesk tickets, etc.)"
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:43
msgid "You will need to install the free *Form Builder* module. Only available in Odoo Enterprise."
msgid "You will need to install the free *Form Builder* module, only available in Odoo Enterprise."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:52
msgid "From any page you want your contact form to be in, in edit mode, drag the form builder in the page and you will be able to add all the fields you wish."
msgid "First, go to the page where you want to put your contact form. In edit mode, drag the form builder onto the page, and you will be able to add all the fields you wish."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:59
msgid "By default any new contact form will send an email, you can switch to lead/opportunity generation in *Change Form Parameters*."
msgid "By default, any new contact form will send an email. You can switch to lead/opportunity generation in *Change Form Parameters*."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:63
msgid "If the same visitor uses the contact form twice, the second information will be added to the first lead/opportunity in the chatter."
msgid "If the same visitor uses the contact form twice, the second entry will be added to the first lead/opportunity in the chatter."
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:67
@ -134,7 +134,7 @@ msgid "Generate leads instead of opportunities"
msgstr ""
#: ../../crm/acquire_leads/generate_from_website.rst:69
msgid "When using a contact form, it is advised to use a qualification step before assigning to the right sales people. To do so, activate *Leads* in CRM settings and refer to :doc:`convert`."
msgid "When using a contact form, you should use a qualification step before assigning the form to the right sales people. To do so, activate *Leads* in CRM settings and refer to :doc:`convert`."
msgstr ""
#: ../../crm/acquire_leads/send_quotes.rst:3

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-27 11:08+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -93,123 +93,167 @@ msgid "Upgrade"
msgstr ""
#: ../../db_management/db_online.rst:53
msgid "Make sure to be connected to the database you want to upgrade and access the database management page. On the line of the database you want to upgrade, click on the \"Upgrade\" button."
msgid "Upgrading your database to a newer version of Odoo is a complex operation that require time and caution. It is extremely important that you fully test the process before upgrading your production database."
msgstr ""
#: ../../db_management/db_online.rst:57
msgid "Odoo releases new versions regularly (at least once a year), and upgrading your database to enjoy new Odoo features is part of the Odoo Online experience."
msgstr ""
#: ../../db_management/db_online.rst:60
msgid "You have the possibility to choose the target version of the upgrade. By default, we select the highest available version available for your database; if you were already in the process of testing a migration, we will automatically select the version you were already testing (even if we released a more recent version during your tests)."
msgid "The upgrade process can take some time, especially if you use multiple apps or apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In general, the 'smaller' the database, the quickest the upgrade. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase and Manufacturing."
msgstr ""
#: ../../db_management/db_online.rst:66
msgid "By clicking on the \"Test upgrade\" button an upgrade request will be generated. If our automated system does not encounter any problem, you will receive a \"Test\" version of your upgraded database."
msgid "Unfortunately, it is impossible to give time estimates for every upgrade request, since Odoo.com will test manually every database upgrade at least once and will need to correct/adapt changes made to the standard Odoo Apps (e.g. through Studio or through a Success Pack) on a case-by-case basis. This can make the process slower, since requests are treated in the order they arrive. This is especially true in the months following the release of a new major version, which can lengthen the upgrade delay significantly."
msgstr ""
#: ../../db_management/db_online.rst:73
msgid "If our automatic system detect an issue during the creation of your test database, our dedicated team will have to work on it. You will be notified by email and the process will take up to 4 weeks."
#: ../../db_management/db_online.rst:74
msgid "The upgrade process is quite simple from your point of view:"
msgstr ""
#: ../../db_management/db_online.rst:76
msgid "You request a test upgrade"
msgstr ""
#: ../../db_management/db_online.rst:77
msgid "You will have the possibility to test it for 1 month. Inspect your data (e.g. accounting reports, stock valuation, etc.), check that all your usual flows work correctly (CRM flow, Sales flow, etc.)."
msgid "Once all tests have been validated **by you**, you upgrade your actual database"
msgstr ""
#: ../../db_management/db_online.rst:79
msgid "The process to request a test or a production (*actual*) upgrade is the same."
msgstr ""
#: ../../db_management/db_online.rst:81
msgid "Once you are ready and that everything is correct in your test migration, 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."
msgid "First, make sure to be connected to the database you want to upgrade and access the `database management page <https://www.odoo.com/my/databases>`__."
msgstr ""
#: ../../db_management/db_online.rst:89
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."
#: ../../db_management/db_online.rst:84
msgid "You have to have an active session with access to the Settings app in the database you want to upgrade for the button to be visible."
msgstr ""
#: ../../db_management/db_online.rst:96
msgid "Duplicating a database"
#: ../../db_management/db_online.rst:87
msgid "On the line of the database you want to upgrade, click on the \"Cog\" menu. If an newer version of Odoo is available, you will see an 'Upgrade' button."
msgstr ""
#: ../../db_management/db_online.rst:98
msgid "Database duplication, renaming, custom DNS, etc. is not available for trial databases on our Online platform. Paid Databases and \"One App Free\" database can duplicate without problem."
#: ../../db_management/db_online.rst:94
msgid "You have the possibility to choose the target version of the upgrade. By default, we select the highest available version available for your database; if you were already in the process of testing an upgrade, we will automatically select the version you were already testing (even if we released a more recent version during your tests)."
msgstr ""
#: ../../db_management/db_online.rst:103
msgid "In the line of the database you want to duplicate, you will have a few buttons. To duplicate your database, just click **Duplicate**. You will have to give a name to your duplicate, then click **Duplicate Database**."
msgid "By clicking on the \"Test upgrade\" button, an upgrade request will be generated. Only one request can be made at time for each database; if a request has already been made, you will see an 'Upgrade Queued' note instead and asking another request will not be possible."
msgstr ""
#: ../../db_management/db_online.rst:110
msgid "If you do not check the \"For testing purposes\" checkbox when duplicating a database, all external communication will remain active:"
#: ../../db_management/db_online.rst:108
msgid "A test upgrade will create a copy of your database, upgrade it and make it available to you automatically once successful. If this is the first test you request for this particular database, a manual testing phase will be done by Odoo.com - this could take time (up to several weeks). Subsequent requests will not go through that manual testing step and will usually be made available in a few hours. Once the test database is available, you should receive an e-mail with the URL of the test database."
msgstr ""
#: ../../db_management/db_online.rst:113
msgid "Emails are sent"
#: ../../db_management/db_online.rst:116
msgid "**Testing your database is the most important step of the upgrade process!** Even though we test all upgrades manually, we do not know your work processes. A change in standard worfklows of Odoo in new versions might require you to change internal processes, or some of the customizations you made through Odoo Studio might now work properly. *It is up to you to make sure that everything works as it should!* You can report issues with your test database through our `Support page <https://www.odoo.com/help>`__."
msgstr ""
#: ../../db_management/db_online.rst:115
msgid "Payments are processed (in the e-commerce or Subscriptions apps, for example)"
msgstr ""
#: ../../db_management/db_online.rst:118
msgid "Delivery orders (shipping providers) are sent"
msgstr ""
#: ../../db_management/db_online.rst:120
msgid "Etc."
msgstr ""
#: ../../db_management/db_online.rst:122
msgid "Make sure to check the checkbox \"For testing purposes\" if you want these behaviours to be disabled."
msgstr ""
#: ../../db_management/db_online.rst:125
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."
#: ../../db_management/db_online.rst:124
msgid "Make sure to do one last test of your upgrade right before the final upgrade (e.g. the day before) to ensure everything will run smoothly. Downgrading is not possible and post-poning an upgrade is always easier than being prevented to work by an upgrade issue after the fact!"
msgstr ""
#: ../../db_management/db_online.rst:129
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../db_management/db_online.rst:137
msgid "Rename a Database"
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
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**."
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 ""
#: ../../db_management/db_online.rst:150
msgid "Deleting a Database"
#: ../../db_management/db_online.rst:146
msgid "Duplicating a database"
msgstr ""
#: ../../db_management/db_online.rst:152
msgid "You can only delete databases of which you are the administrator."
#: ../../db_management/db_online.rst:148
msgid "Database duplication, renaming, custom DNS, etc. is not available for trial databases on our Online platform. Paid Databases and \"One App Free\" database can duplicate without problem."
msgstr ""
#: ../../db_management/db_online.rst:154
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."
#: ../../db_management/db_online.rst:153
msgid "In the line of the database you want to duplicate, you will have a few buttons. To duplicate your database, just click **Duplicate**. You will have to give a name to your duplicate, then click **Duplicate Database**."
msgstr ""
#: ../../db_management/db_online.rst:160
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."
msgid "If you do not check the \"For testing purposes\" checkbox when duplicating a database, all external communication will remain active:"
msgstr ""
#: ../../db_management/db_online.rst:167
msgid "Read carefully the warning message that will appear and proceed only if you fully understand the implications of deleting a database:"
#: ../../db_management/db_online.rst:163
msgid "Emails are sent"
msgstr ""
#: ../../db_management/db_online.rst:173
msgid "After a few seconds, the database will be deleted and the page will reload automatically."
#: ../../db_management/db_online.rst:165
msgid "Payments are processed (in the e-commerce or Subscriptions apps, for example)"
msgstr ""
#: ../../db_management/db_online.rst:177
msgid "If you need to re-use this database name, it will be immediately available."
#: ../../db_management/db_online.rst:168
msgid "Delivery orders (shipping providers) are sent"
msgstr ""
#: ../../db_management/db_online.rst:170
msgid "Etc."
msgstr ""
#: ../../db_management/db_online.rst:172
msgid "Make sure to check the checkbox \"For testing purposes\" if you want these behaviours to be disabled."
msgstr ""
#: ../../db_management/db_online.rst:175
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
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../db_management/db_online.rst:187
msgid "Rename a Database"
msgstr ""
#: ../../db_management/db_online.rst:189
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
msgid "Deleting a Database"
msgstr ""
#: ../../db_management/db_online.rst:202
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../db_management/db_online.rst:204
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
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
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
msgid "After a few seconds, the database will be deleted and the page will reload automatically."
msgstr ""
#: ../../db_management/db_online.rst:227
msgid "If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../db_management/db_online.rst:229
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:183
#: ../../db_management/db_online.rst:233
msgid "If you want to delete your Account, please contact `Odoo Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:7
msgid "On-premise Database management"
msgid "On-premises Database management"
msgstr ""
#: ../../db_management/db_premise.rst:10
@ -229,8 +273,8 @@ msgid "If you are unable to register your database, you will likely encounter th
msgstr ""
#: ../../db_management/db_premise.rst:31
#: ../../db_management/db_premise.rst:97
#: ../../db_management/db_premise.rst:130
#: ../../db_management/db_premise.rst:110
#: ../../db_management/db_premise.rst:143
msgid "Solutions"
msgstr ""
@ -263,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:190
#: ../../db_management/db_premise.rst:176
msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required."
msgstr ""
@ -279,107 +323,95 @@ msgstr ""
msgid "For your information, we identify database with UUID. Therefore, each database should have a distinct UUID to ensure that registration and invoicing proceed effortlessly for your and for us."
msgstr ""
#: ../../db_management/db_premise.rst:80
msgid "Check your network and firewall settings"
msgstr ""
#: ../../db_management/db_premise.rst:82
msgid "The Update notification must be able to reach Odoo's subscription validation servers. In other words, make sure that the Odoo server is able to open outgoing connections towards:"
msgstr ""
#: ../../db_management/db_premise.rst:86
msgid "services.odoo.com on port 443 (or 80)"
msgstr ""
#: ../../db_management/db_premise.rst:87
msgid "services.openerp.com on port 443 (or 80) for older deployments"
msgstr ""
#: ../../db_management/db_premise.rst:89
msgid "Once you activated your database, you must keep these ports open, as the Update notification runs once a week."
msgstr ""
#: ../../db_management/db_premise.rst:95
msgid "Error message due to too many users"
msgstr ""
#: ../../db_management/db_premise.rst:84
#: ../../db_management/db_premise.rst:97
msgid "If you have more users in your local database than provisionned in your Odoo Enterprise subscription, you may encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:93
#: ../../db_management/db_premise.rst:106
msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday."
msgstr ""
#: ../../db_management/db_premise.rst:99
#: ../../db_management/db_premise.rst:112
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:102
#: ../../db_management/db_premise.rst:115
msgid "or"
msgstr ""
#: ../../db_management/db_premise.rst:104
#: ../../db_management/db_premise.rst:117
msgid "**Deactivate users** as explained in this `Documentation <https://www.odoo.com /documentation/user/11.0/db_management/documentation.html#deactivating-users>`__ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:109
#: ../../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:116
#: ../../db_management/db_premise.rst:129
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:118
#: ../../db_management/db_premise.rst:131
msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:126
#: ../../db_management/db_premise.rst:139
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:134
#: ../../db_management/db_premise.rst:147
msgid "Renew your subscription: follow the link and renew your subscription - note that"
msgstr ""
#: ../../db_management/db_premise.rst:133
#: ../../db_management/db_premise.rst:146
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:136
#: ../../db_management/db_premise.rst:149
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:138
#: ../../db_management/db_premise.rst:151
msgid "None of those solutions worked for you? Please contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:145
msgid "Force an Update Notification"
msgstr ""
#: ../../db_management/db_premise.rst:147
msgid "Update Notifications happen once every 7 days and keep your database up-to-date with your Odoo Enterprise subscription. If you modify your subscription (i.e. add more users, renew it for a year, etc.), your local database will only be made aware of the change once every 7 days - this can cause discrepancies between the state of your subscription and some notifications in your App Switcher. When doing such an operation on your subscription, you can force an Update using the following procedure:"
msgstr ""
#: ../../db_management/db_premise.rst:154
msgid "Connect to the database with the **Administrator** account"
msgstr ""
#: ../../db_management/db_premise.rst:155
msgid "Switch to the Developer mode by using the **About** option in the top-right menu (in V9) / in **Settings** (in V10): click on **Activate the developer mode**"
msgstr ""
#: ../../db_management/db_premise.rst:158
msgid "Navigate to the \"Settings\" menu, then \"Technical\" > \"Automation\" > \"Scheduled Actions\""
msgstr ""
#: ../../db_management/db_premise.rst:160
msgid "Find \"Update Notification\" in the list, click on it, and finally click on the button \"**RUN MANUALLY**\""
msgstr ""
#: ../../db_management/db_premise.rst:162
msgid "Refresh the page, the \"Expiration\" notification should be gone"
msgstr ""
#: ../../db_management/db_premise.rst:165
msgid "You may have kept the same UUID on different databases and we receive information from those databases too. So please read :ref:`this documentation <duplicate_premise>` to know how to change the UUID. After the change you can force a ping to speed up the verification, your production database will then be correctly identified."
msgstr ""
#: ../../db_management/db_premise.rst:174
msgid "Duplicate a database"
msgstr ""
#: ../../db_management/db_premise.rst:176
#: ../../db_management/db_premise.rst:162
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:184
#: ../../db_management/db_premise.rst:170
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:193
#: ../../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."
msgstr ""

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -73,114 +73,114 @@ msgid "How to use a G Suite server"
msgstr ""
#: ../../discuss/email_servers.rst:48
msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to enable a SMTP relay and to allow *Any addresses* in the *Allowed senders* section. The configuration steps are explained in `Google documentation <https://support.google.com/a/answer/2956491?hl=en>`__."
msgid "You can use an G Suite server for any Odoo hosting type. To do so you need to setup the SMTP relay service. The configuration steps are explained in `Google documentation <https://support.google.com/a/answer/2956491?hl=en>`__."
msgstr ""
#: ../../discuss/email_servers.rst:56
#: ../../discuss/email_servers.rst:55
msgid "Be SPF-compliant"
msgstr ""
#: ../../discuss/email_servers.rst:57
#: ../../discuss/email_servers.rst:56
msgid "In case you use SPF (Sender Policy Framework) to increase the deliverability of your outgoing emails, don't forget to authorize Odoo as a sending host in your domain name settings. Here is the configuration for Odoo Online:"
msgstr ""
#: ../../discuss/email_servers.rst:61
#: ../../discuss/email_servers.rst:60
msgid "If no TXT record is set for SPF, create one with following definition: v=spf1 include:_spf.odoo.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:63
#: ../../discuss/email_servers.rst:62
msgid "In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g. for a domain name that sends emails via Odoo Online and via G Suite it could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:67
#: ../../discuss/email_servers.rst:66
msgid "Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to create or modify TXT records in your own domain registrar."
msgstr ""
#: ../../discuss/email_servers.rst:70
#: ../../discuss/email_servers.rst:69
msgid "Your new SPF record can take up to 48 hours to go into effect, but this usually happens more quickly."
msgstr ""
#: ../../discuss/email_servers.rst:73
#: ../../discuss/email_servers.rst:72
msgid "Adding more than one SPF record for a domain can cause problems with mail delivery and spam classification. Instead, we recommend using only one SPF record by modifying it to authorize Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:78
#: ../../discuss/email_servers.rst:77
msgid "Allow DKIM"
msgstr ""
#: ../../discuss/email_servers.rst:79
#: ../../discuss/email_servers.rst:78
msgid "You should do the same thing if DKIM (Domain Keys Identified Mail) is enabled on your email server. In the case of Odoo Online & Odoo.sh, you should add a DNS \"odoo._domainkey\" CNAME record to \"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have a record \"odoo._domainkey.foo.com\" that is a CNAME with the value \"odoo._domainkey.odoo.com\"."
msgstr ""
#: ../../discuss/email_servers.rst:87
#: ../../discuss/email_servers.rst:86
msgid "How to manage inbound messages"
msgstr ""
#: ../../discuss/email_servers.rst:89
#: ../../discuss/email_servers.rst:88
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr ""
#: ../../discuss/email_servers.rst:91
#: ../../discuss/email_servers.rst:90
msgid "**Reply messages** of messages sent from Odoo are routed to their original discussion thread (and to the inbox of all its followers) by the catchall alias (**catchall@**)."
msgstr ""
#: ../../discuss/email_servers.rst:95
#: ../../discuss/email_servers.rst:94
msgid "**Bounced messages** are routed to **bounce@** in order to track them in Odoo. This is especially used in `Odoo Email Marketing <https://www.odoo.com/page/email-marketing>`__ to opt-out invalid recipients."
msgstr ""
#: ../../discuss/email_servers.rst:99
#: ../../discuss/email_servers.rst:98
msgid "**Original messages**: Several business objects have their own alias to create new records in Odoo from incoming emails:"
msgstr ""
#: ../../discuss/email_servers.rst:102
#: ../../discuss/email_servers.rst:101
msgid "Sales Channel (to create Leads or Opportunities in `Odoo CRM <https://www.odoo.com/page/crm>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:104
#: ../../discuss/email_servers.rst:103
msgid "Support Channel (to create Tickets in `Odoo Helpdesk <https://www.odoo.com/page/helpdesk>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:106
#: ../../discuss/email_servers.rst:105
msgid "Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page/project-management>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:108
#: ../../discuss/email_servers.rst:107
msgid "Job Positions (to create Applicants in `Odoo Recruitment <https://www.odoo.com/page/recruitment>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:110
#: ../../discuss/email_servers.rst:109
msgid "etc."
msgstr ""
#: ../../discuss/email_servers.rst:112
#: ../../discuss/email_servers.rst:111
msgid "Depending on your mail server, there might be several methods to fetch emails. The easiest and most recommended method is to manage one email address per Odoo alias in your mail server."
msgstr ""
#: ../../discuss/email_servers.rst:116
#: ../../discuss/email_servers.rst:115
msgid "Create the corresponding email addresses in your mail server (catchall@, bounce@, sales@, etc.)."
msgstr ""
#: ../../discuss/email_servers.rst:118
#: ../../discuss/email_servers.rst:117
msgid "Set your domain name in the General Settings."
msgstr ""
#: ../../discuss/email_servers.rst:123
#: ../../discuss/email_servers.rst:122
msgid "If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for each alias. You can do it from the General Settings as well. Fill out the form according to your email providers settings. Leave the *Actions to Perform on Incoming Mails* blank. Once all the information has been filled out, click on *TEST & CONFIRM*."
msgstr ""
#: ../../discuss/email_servers.rst:132
#: ../../discuss/email_servers.rst:131
msgid "If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming messages to Odoo's domain name rather than exclusively use your own email server. That way you will receive incoming messages without delay. Indeed, Odoo Online is fetching incoming messages of external servers once per hour only. You should set redirections for all the email addresses to Odoo's domain name in your email server (e.g. *catchall@mydomain.ext* to *catchall@mycompany.odoo.com*)."
msgstr ""
#: ../../discuss/email_servers.rst:139
#: ../../discuss/email_servers.rst:138
msgid "All the aliases are customizable in Odoo. Object aliases can be edited from their respective configuration view. To edit catchall and bounce aliases, you first need to activate the developer mode from the Settings Dashboard."
msgstr ""
#: ../../discuss/email_servers.rst:147
#: ../../discuss/email_servers.rst:146
msgid "Then refresh your screen and go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` to customize the aliases (*mail.catchall.alias* & * mail.bounce.alias*)."
msgstr ""
#: ../../discuss/email_servers.rst:154
#: ../../discuss/email_servers.rst:153
msgid "By default inbound messages are fetched every 5 minutes in Odoo on-premise. You can change this value in developer mode. Go to :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions` and look for *Mail: Fetchmail Service*."
msgstr ""

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -462,7 +462,7 @@ msgid "You can access the web page from the detail form by clicking the *Publish
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:3
msgid "How to sell pricier product alternatives (upselling)"
msgid "How to sell pricier alternative products (upselling)"
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:5
@ -570,7 +570,6 @@ msgid "Once ready, switch to **Production** mode."
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:30
#: ../../ecommerce/shopper_experience/paypal.rst:74
msgid "Set up Odoo"
msgstr ""
@ -587,7 +586,6 @@ msgid "To get those credentials in Authorize.Net, you can rely on *API Login ID
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:47
#: ../../ecommerce/shopper_experience/paypal.rst:102
msgid "Go live"
msgstr ""
@ -620,13 +618,11 @@ msgid "To perform ficticious transactions you can use fake card numbers provided
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:76
#: ../../ecommerce/shopper_experience/paypal.rst:154
msgid ":doc:`payment`"
msgstr ""
#: ../../ecommerce/shopper_experience/authorize.rst:77
#: ../../ecommerce/shopper_experience/payment.rst:111
#: ../../ecommerce/shopper_experience/paypal.rst:155
msgid ":doc:`payment_acquirer`"
msgstr ""
@ -844,137 +840,201 @@ msgid "With other payment acquirers, you can manage the capture in their own int
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:3
msgid "How to get paid with Paypal"
msgid "Configure your Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:5
msgid "Paypal is the easiest online payment acquirer to configure. It is also the only one without any subscription fee. We definitely advise it to any starter."
msgid "Paypal is available and popular worldwide. It doesnt charge any subscription fee and creating an account is very easy. Thats why we definitely recommend it for starters in Odoo. It works as a seamless flow where the customer is routed to Paypal website to register the payment."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:11
msgid "Set up your Paypal account"
#: ../../ecommerce/shopper_experience/paypal.rst:12
msgid "Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:13
msgid "Create a `Paypal Business Account <https://www.paypal.com>`__ or upgrade your account to *Business account* if you have a basic account."
#: ../../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:16
msgid "Log in to `Paypal <https://www.paypal.com>`__ and open the settings of your **Profile**."
#: ../../ecommerce/shopper_experience/paypal.rst:18
msgid "Settings in Paypal"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:22
msgid "Now enter the menu **My selling tools**."
#: ../../ecommerce/shopper_experience/paypal.rst:21
msgid "First, lets see how to set up your Paypal account in order to build a seamless customer experience with Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:27
msgid "Let's start with the **Website Preferences**."
#: ../../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*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:29
msgid "Turn on **Auto Return** and enter the **Return URL**: <odoo_instance_url>/shop/confirmation. Verify that this address uses the correct protocol (HTTP/HTTPS)."
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)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:36
msgid "Turn on **Payment Data Transfer**. When saving, an **Identity Token** is generated. You will be later requested to enter it in Odoo."
msgid "This URL is requested in Paypal but not used in practice as Odoo transmits it at each transaction. Dont worry if you manage several sales channels or Odoo databases."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:43
msgid "Then, get back to your profile to activate the **Instant Payment Notification (IPN)** in *My selling tools*."
#: ../../ecommerce/shopper_experience/paypal.rst:44
msgid "Payment Data Transfer (PDT)"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:46
msgid "Enter the **Notification URL**: <odoo_instance_url>/payment/paypal/ipn"
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:51
msgid "Now you must change the encoding format of the payment request sent by Odoo to Paypal. To do so, get back to *My selling tools* and click **PayPal button language encoding** in *More Selling Tools* section."
#: ../../ecommerce/shopper_experience/paypal.rst:54
msgid "Paypal Account Optional"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:58
msgid "Then, click *More Options* and set the two default encoding formats as **UTF-8**."
#: ../../ecommerce/shopper_experience/paypal.rst:56
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:66
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:63
msgid "Instant Payment Notification (IPN)"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:65
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. Thats 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
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 "Open Paypal setup form in :menuselection:`Website or Sales or Accounting --> Settings --> Payment Acquirers+`. Enter both your **Email ID** and your **Merchant ID** and check **Use IPN**."
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:82
msgid "They are both provided in your Paypal profile, under :menuselection:`My business info`."
#: ../../ecommerce/shopper_experience/paypal.rst:81
msgid "Payment Messages Format"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:85
msgid "Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so, open the *Settings* and activate the **Developer Mode**."
#: ../../ecommerce/shopper_experience/paypal.rst:83
msgid "Finally make sure the encoding format of payment messages is correctly set. Go to *PayPal button language encoding*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:91
msgid "Then, go to :menuselection:`Settings --> Technical --> Parameters --> System Parameters` and create a parameter with following values:"
#: ../../ecommerce/shopper_experience/paypal.rst:89
msgid "Click *More Options* and set the two default encoding formats as *UTF-8*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:94
msgid "Key: payment_paypal.pdt_token"
#: ../../ecommerce/shopper_experience/paypal.rst:98
msgid "Your Paypal account is ready!"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:95
msgid "Value: your Paypal *Identity Token*"
#: ../../ecommerce/shopper_experience/paypal.rst:101
msgid "Settings in Odoo"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:103
msgid "Your configuration is now ready! You can make Paypal visible on your merchant interface and activate the **Production mode**."
#: ../../ecommerce/shopper_experience/paypal.rst:104
msgid "Activation"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:106
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:110
msgid "Credentials"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:112
msgid "Transaction fees"
msgid "Odoo requires three Paypal credentials:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:114
msgid "You can charge an extra to the customer to cover the transaction fees Paypal charges you. Once redirected to Paypal, your customer sees an extra applied to the order amount."
msgid "*Email ID* is your login email address in Paypal."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:117
msgid "To activate this, go to the *Configuration* tab of Paypal config form in Odoo and check *Add Extra Fees*. Default fees for US can be seen here below."
#: ../../ecommerce/shopper_experience/paypal.rst:116
msgid "*Merchant ID* can be found in the settings of your Paypal account, in *Profile > About the business*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:123
msgid "To apply the right fees for your country, please refer to `Paypal Fees <https://www.paypal.com/webapps/mpp/paypal-fees>`__."
#: ../../ecommerce/shopper_experience/paypal.rst:118
msgid "*Paypal PDT Token* is given in *Website payments* configuration as explained here above."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:128
msgid "Test the payment flow"
#: ../../ecommerce/shopper_experience/paypal.rst:124
msgid "Transaction fees"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:130
msgid "You can test the entire payment flow thanks to Paypal Sandbox accounts."
#: ../../ecommerce/shopper_experience/paypal.rst:126
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:132
msgid "Log in to `Paypal Developer Site <https://developer.paypal.com>`__ with your Paypal credentials. This will create two sandbox accounts:"
#: ../../ecommerce/shopper_experience/paypal.rst:129
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:136
msgid "A business account (to use as merchant, e.g. pp.merch01-facilitator@example.com)."
#: ../../ecommerce/shopper_experience/paypal.rst:135
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:137
msgid "A default personal account (to use as shopper, e.g. pp.merch01-buyer@example.com)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:139
msgid "Log in to `Paypal Sandbox <https://www.sandbox.paypal.com>`__ with the merchant account and follow the same configuration instructions."
#: ../../ecommerce/shopper_experience/paypal.rst:138
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."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:142
msgid "Enter your sandbox credentials in Odoo and make sure Paypal is still set on *Test* mode. Also, make sure the confirmation mode of Paypal is not *Authorize & capture the amount, confirm the SO and auto-validate the invoice on acquirer confirmation*. Otherwise a confirmed invoice will be automatically generated when the transaction is completed."
msgid "Go live!"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:150
#: ../../ecommerce/shopper_experience/paypal.rst:144
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:153
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:162
msgid "Test environment"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:164
msgid "You can test the entire payment flow in Odoo thanks to Paypal Sandbox accounts."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:166
msgid "Log in to `Paypal Developer Site <https://developer.paypal.com/>`__ with your Paypal credentials."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:168
msgid "This will create two sandbox accounts:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:170
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:172
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:174
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:180
msgid "Run a test transaction from Odoo using the sandbox personal account."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:182
msgid "See also"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:184
msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/12.0/ecommerce/shopper_experience/payment.html>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:186
msgid "`How to manage orders paid with payment acquirers <https://www.odoo.com/documentation/user/12.0/ecommerce/shopper_experience/payment_acquirer.html>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their customer account"
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -24,6 +24,14 @@ msgstr ""
msgid "Authentication"
msgstr ""
#: ../../general/auth/azure.rst:3
msgid "OAuth"
msgstr ""
#: ../../general/auth/azure.rst:5
msgid "Due to specific requirements in Azure's OAuth implementation, Microsoft Azure OAuth identification is NOT compatible with Odoo at the moment."
msgstr ""
#: ../../general/auth/google.rst:3
msgid "How to allow users to sign in with their Google account"
msgstr ""
@ -64,6 +72,50 @@ msgstr ""
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 ""
#: ../../general/auth/ldap.rst:3
msgid "How to allow users to sign in with LDAP"
msgstr ""
#: ../../general/auth/ldap.rst:5
msgid "Install the LDAP module in General Settings."
msgstr ""
#: ../../general/auth/ldap.rst:7
msgid "Click on **Create** in Setup your LDAP Server."
msgstr ""
#: ../../general/auth/ldap.rst:15
msgid "Choose the company about to use the LDAP."
msgstr ""
#: ../../general/auth/ldap.rst:20
msgid "In **Server Information**, enter the IP address of your server and the port it listens to."
msgstr ""
#: ../../general/auth/ldap.rst:22
msgid "Tick **User TLS** if your server is compatible."
msgstr ""
#: ../../general/auth/ldap.rst:27
msgid "In **Login Information**, enter ID and password of the account used to query the server. If left empty, the server will be queried anonymously."
msgstr ""
#: ../../general/auth/ldap.rst:32
msgid "In **Process Parameter**, enter the domain name of your LDAP server in LDAP nomenclature (e.g. ``dc=example,dc=com``)."
msgstr ""
#: ../../general/auth/ldap.rst:34
msgid "In **LDAP filter**, enter ``uid=%s``"
msgstr ""
#: ../../general/auth/ldap.rst:39
msgid "In **User Information**, tick *Create User* if you want Odoo to create a User profile the first time someone log in with LDAP."
msgstr ""
#: ../../general/auth/ldap.rst:41
msgid "In **Template User**, indicate a template for the new profiles created. If left blanked, the admin profile will be used as template."
msgstr ""
#: ../../general/base_import.rst:3
msgid "Data Import"
msgstr ""
@ -505,6 +557,14 @@ msgstr ""
msgid "`Deactivating Users <../../db_management/documentation.html#deactivating-users>`_"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:47
msgid "Todo"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:47
msgid "Add link to How to add companies"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:3
msgid "Manage Odoo in your own language"
msgstr ""
@ -569,43 +629,56 @@ msgstr ""
msgid "How to generate an Unsplash access key"
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:5
#: ../../general/unsplash/unsplash_access_key.rst:6
msgid "**As a SaaS user**, Unsplash is ready to use. You won't need to follow this guide to set up Unsplash informations as you will use our own Odoo Unsplash key in a transparent way."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:9
msgid "Generate an Unsplash access key for **non-Saas** users"
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:11
msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:7
#: ../../general/unsplash/unsplash_access_key.rst:13
msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on **New Application**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:12
#: ../../general/unsplash/unsplash_access_key.rst:18
msgid "Accept the conditions and click on **Accept terms**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:17
msgid "You will be prompted to insert an **Application name** and a **Description**. Once done, click on **Create application**."
#: ../../general/unsplash/unsplash_access_key.rst:23
msgid "You will be prompted to insert an **Application name** and a **Description**. Please prefix your application name by \"**Odoo:** \" so it can be recognized as an Odoo instance by Unsplash. Once done, click on **Create application**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:22
#: ../../general/unsplash/unsplash_access_key.rst:28
msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:34
#: ../../general/unsplash/unsplash_application_id.rst:19
msgid "**As a non-SaaS user**, you won't be able to register for a production Unsplash key and will be limited to your test key that has a 50 Unsplash requests per hour restriction."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:37
msgid ":doc:`unsplash_application_id`"
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:3
msgid "How to generate an Unsplash application ID"
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:5
msgid "You should first create and set up your Unsplash application with this tutorial: `How to generate an Unsplash access key <https://www.odoo.com/documentation/user/unsplash_access_key.html>`_."
#: ../../general/unsplash/unsplash_application_id.rst:6
msgid "You should first create and set up your Unsplash application with this tutorial: :doc:`unsplash_access_key`."
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:7
#: ../../general/unsplash/unsplash_application_id.rst:8
msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on your newly created Unsplash application under **Your applications**."
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:12
msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/application_id``"
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:17
msgid "Note that if you `apply for a production account <https://unsplash.com/documentation#registering-your-application>`_ and it got approved, your will also find your application ID in the UI. It will be listed next to your **Access Key** on your application details page."
#: ../../general/unsplash/unsplash_application_id.rst:13
msgid "You will be redirected to your application details page. The **application ID** will be visible in your browser's URL. The URL should be something like ``https://unsplash.com/oauth/applications/<application_id>``"
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -93,7 +93,7 @@ msgid "**The GAP Analysis**: The comparison of the request with the standard fea
msgstr ""
#: ../../getting_started/documentation.rst:118
msgid "`The User Story <https://help.rallydev.com/writing-great-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."
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
@ -213,70 +213,10 @@ msgid "8. Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
msgid "Your Odoo Online subscription includes **unlimited 24hr support at no extra cost, Monday to Friday**. Our teams are located around the world to ensure you have support, no matter your location. Your support representative could be communicating to you from San Francisco, Belgium, or India!"
msgid "When your project is put in production, our support teams take care of your questions or technical issues."
msgstr ""
#: ../../getting_started/documentation.rst:260
msgid "What kind of support is included?"
msgstr ""
#: ../../getting_started/documentation.rst:262
msgid "Providing you with relevant material (guidelines, product documentation, etc...)"
msgstr ""
#: ../../getting_started/documentation.rst:264
msgid "Answers to issues that you may encounter in your standard Odoo database (eg. “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
#: ../../getting_started/documentation.rst:266
msgid "Questions related to your account, subscription, or billing"
msgstr ""
#: ../../getting_started/documentation.rst:267
msgid "Bug resolution (blocking issues or unexpected behaviour not due to misconfiguration or customization)"
msgstr ""
#: ../../getting_started/documentation.rst:269
msgid "Issues that might occur in a test database after upgrading to a newer version"
msgstr ""
#: ../../getting_started/documentation.rst:271
msgid "*Odoo Support does not make changes to your production database, but gives you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../getting_started/documentation.rst:274
msgid "What kind of support is not included?"
msgstr ""
#: ../../getting_started/documentation.rst:276
msgid "Questions that require us to understand your business processes in order to help you implement your database"
msgstr ""
#: ../../getting_started/documentation.rst:278
msgid "Training on how to use our software (we will direct you to our many resources)"
msgstr ""
#: ../../getting_started/documentation.rst:279
msgid "Importation of documents into your database"
msgstr ""
#: ../../getting_started/documentation.rst:280
msgid "Guidance on which configurations to apply inside of an application or the database"
msgstr ""
#: ../../getting_started/documentation.rst:281
msgid "How to set up configuration models (Examples include: Inventory Routes, Payment Terms, Warehouses, etc)"
msgstr ""
#: ../../getting_started/documentation.rst:283
msgid "Questions or issues related to specific developments or customizations done either by Odoo or a third party (this is specific only to your database or involving code)"
msgstr ""
#: ../../getting_started/documentation.rst:287
msgid "You can get this type of support with a `Success Pack <https://www.odoo.com/pricing-packs>`__. With a pack, one of our consultants will analyze the way your business runs and tell you how you can get the most out of your Odoo Database. We will handle all configurations and coach you on how to use Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:292
msgid "Our support team can be contacted through our `online support form <https://www.odoo.com/help>`__."
#: ../../getting_started/documentation.rst:258
msgid "See :ref:`support-expectations`."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -304,47 +304,39 @@ msgstr ""
msgid "The barcode scanning features can save you a lot of the time usually lost switching between the keyboard, the mouse and the scanner. Properly attributing barcodes to products, pickings locations, etc. allows you to work more efficiently by controlling the software almost exclusively with the barcode scanner."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:17
msgid "Print this document to be able to use your barcode scanner to perform more actions."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:19
msgid "Document: |download_barcode|"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:23
#: ../../inventory/barcode/setup/software.rst:12
msgid "Set products barcodes"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:28
#: ../../inventory/barcode/setup/software.rst:17
msgid "In order to fill a picking or to perform an inventory, you need to make sure that your products are encoded in Odoo along with their barcodes. If this is not already done, you can fill in the products barcodes through a handy interface. Go to :menuselection:`Inventory --> Configuration --> Settings` and click :menuselection:`Operations --> Barcode Scanner`. Click Save, and go back into the previous screen to click Configure Product Barcodes. This interface can also be accessed via the planner."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:39
#: ../../inventory/barcode/setup/software.rst:28
msgid "Product variants: be careful to add barcodes directly on the variant, and not the template product (otherwise you won't be able to differentiate them)."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:44
#: ../../inventory/barcode/setup/software.rst:33
msgid "Set locations barcodes"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:49
#: ../../inventory/barcode/setup/software.rst:38
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 --> Warehouse Management --> Locations`. There is button in the **Print** menu that you can use to print the locations names and barcodes. There are 4 barcodes per page, arranged in a way that is convenient to print on sticker paper."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:58
#: ../../inventory/barcode/setup/software.rst:47
msgid "Example of location naming: **warehouse short name** - **location short name** - (**Corridor X** - **Shelf Y** - **Height Z**) Example: A032-025-133"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:65
#: ../../inventory/barcode/setup/software.rst:54
msgid "Barcode formats"
msgstr ""
#: ../../inventory/barcode/setup/software.rst:67
#: ../../inventory/barcode/setup/software.rst:56
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 (that's why no two products in a store will ever have the same EAN code)."
msgstr ""
#: ../../inventory/barcode/setup/software.rst:72
#: ../../inventory/barcode/setup/software.rst:61
msgid "Still, as Odoo supports any string as a barcode, so you can always define your own barcode format for internal use."
msgstr ""
@ -503,7 +495,7 @@ msgstr ""
#: ../../inventory/routes/concepts/procurement_rule.rst:25
#: ../../inventory/routes/concepts/push_rule.rst:29
#: ../../inventory/routes/concepts/use_routes.rst:22
#: ../../inventory/routes/costing/landed_costs.rst:18
#: ../../inventory/routes/costing/landed_costs.rst:17
#: ../../inventory/routes/strategies/putaway.rst:23
#: ../../inventory/routes/strategies/removal.rst:18
#: ../../inventory/settings/products/strategies.rst:30
@ -610,6 +602,42 @@ msgstr ""
msgid "The choice between the two options is thus dependent of your inventory strategy. If you prefer to have a buffer and always have at least a minimum amount, the minimum stock rule should be used. If you want to reorder your stocks only if your sale is confirmed it is better to use the Make to Order."
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:3
msgid "TaKing stock from different warehouses"
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:5
msgid "When you plan to deliver a customer, you dont know in advance if the products will come from Warehouse A or Warehouse B. You may, in some cases, need to take stock from different warehouses. With *Odoo*, you can configure this by using the concept of virtual warehouses. Let us show you how to set those virtual warehouses."
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:12
msgid "Set up virtual warehouses"
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:14
msgid "Lets say you have two warehouses: Warehouse A and Warehouse B. Create a new warehouse, that will be a virtual one. It will allow you to take the stock from A or B. To do so, go to your inventory app settings and enable the multi-warehouses feature. Then, go to the warehouses menu and click on create."
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:24
msgid "The *Storage Location* feature will be automatically enabled. Good news, because you will need it later in the process."
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:27
msgid "Now, you have to make sure that the main stock locations of warehouse A and warehouse B are children locations of the main stock location of warehouse A + B. Go to the locations menu, and edit the main location of your two warehouses. Then, change their parent location to main location of warehouse A+B."
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:37
msgid "Sell a product from the virtual warehouse"
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:39
msgid "Lets say you have two products, one stored in warehouse A and one stored in warehouse B. Now, you can create a new quotation for one of each product. Go to other information and choose Warehouse A+B in the shipping information."
msgstr ""
#: ../../inventory/management/adjustment/virtual_warehouses.rst:47
msgid "Once you have done it, you can convert it to a sales order. Then, a delivery order will be automatically generated, with a product reserved in warehouse A and one in warehouse B."
msgstr ""
#: ../../inventory/management/delivery.rst:3
msgid "Delivery Orders"
msgstr ""
@ -767,7 +795,7 @@ msgid "Now, open the menu :menuselection:`Sales --> Sales --> Products`. Add a s
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:74
msgid "How to send products from the customers directly to the suppliers"
msgid "How to send products from the suppliers directly to the customers"
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:76
@ -790,6 +818,21 @@ msgstr ""
msgid ":doc:`inventory_flow`"
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:105
#: ../../inventory/management/delivery/one_step.rst:63
#: ../../inventory/management/delivery/three_steps.rst:159
#: ../../inventory/management/delivery/two_steps.rst:129
#: ../../inventory/management/incoming/handle_receipts.rst:70
#: ../../inventory/overview/concepts/double-entry.rst:179
#: ../../inventory/settings/products/uom.rst:124
#: ../../inventory/settings/products/variants.rst:222
msgid "Todo"
msgstr ""
#: ../../inventory/management/delivery/dropshipping.rst:106
msgid "Add link to this section when available * How to analyse the performance of my vendors?"
msgstr ""
#: ../../inventory/management/delivery/inventory_flow.rst:3
msgid "How to choose the right inventory flow to handle delivery orders?"
msgstr ""
@ -954,6 +997,16 @@ msgstr ""
msgid "This has completed the **Shipping Step** and the WH/OUT should now show **Done** in the status column at the top of the page, which means the product has been shipped to the customer."
msgstr ""
#: ../../inventory/management/delivery/one_step.rst:64
msgid "Ajouter un lien vers ces pages quand elles existeront - Process Overview: From sales orders to delivery orders"
msgstr ""
#: ../../inventory/management/delivery/one_step.rst:67
#: ../../inventory/management/delivery/three_steps.rst:163
#: ../../inventory/management/delivery/two_steps.rst:133
msgid "Process Overview: From purchase orders to receptions"
msgstr ""
#: ../../inventory/management/delivery/packaging_type.rst:3
msgid "How can you change the packaging type for your sale order?"
msgstr ""
@ -1298,6 +1351,10 @@ msgstr ""
msgid "This has completed the shipping step and the **WH/OUT** should now show **Done** in the status column at the top of the page. The product has been shipped to the customer."
msgstr ""
#: ../../inventory/management/delivery/three_steps.rst:160
msgid "Link to these sections when available - Process Overview: From sales orders to delivery orders"
msgstr ""
#: ../../inventory/management/delivery/two_steps.rst:3
msgid "How to process delivery orders in two steps (pick + ship)?"
msgstr ""
@ -1378,6 +1435,10 @@ msgstr ""
msgid "This has completed the shipping step and the **WH/OUT** move should now show **Done** in the status column at the top of the page. The product has been shipped to the customer."
msgstr ""
#: ../../inventory/management/delivery/two_steps.rst:130
msgid "link to these sections when they will be available - Process Overview: From sales orders to delivery orders"
msgstr ""
#: ../../inventory/management/incoming.rst:3
msgid "Incoming Shipments"
msgstr ""
@ -1440,6 +1501,10 @@ msgstr ""
msgid ":doc:`../delivery/inventory_flow`"
msgstr ""
#: ../../inventory/management/incoming/handle_receipts.rst:71
msgid "Add section when available - How to analyse the performance of my vendors?"
msgstr ""
#: ../../inventory/management/incoming/three_steps.rst:3
msgid "How to add a quality control step in goods receipt? (3 steps)"
msgstr ""
@ -3245,6 +3310,10 @@ msgstr ""
msgid "whether the procurement is :abbr:`MTO (Made To Order)` or :abbr:`MTS (Made To Stock)`"
msgstr ""
#: ../../inventory/overview/concepts/double-entry.rst:179
msgid "needs schema thing from FP"
msgstr ""
#: ../../inventory/overview/concepts/double-entry.rst:182
msgid "Routes"
msgstr ""
@ -4249,67 +4318,31 @@ msgid "Product Costing"
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:3
msgid "How to integrate landed costs in the cost of the product?"
msgid "How to integrate additional costs in the cost of the product? (landed costs)"
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:8
msgid "Landed costs include all charges associated to a good transfer."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:10
msgid "Landed cost includes = Cost of product + Shipping + Customs + Risk"
msgid "The landed cost feature in Odoo allows to include additional costs (shipment, insurance, customs duties, etc.) into the cost of the product."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:12
msgid "All of these components might not be applicable in every shipment, but relevant components must be considered as a part of the landed cost. We have to identify landed cost to decide sale price of product because it will impact on company profits."
msgid "Landed costs can only be applied to products with a FIFO costing method and an automated inventory valuation (which requires the accounting application to be installed)."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:21
msgid "Applications configuration"
#: ../../inventory/routes/costing/landed_costs.rst:20
msgid "First, you need to activate the landed costs feature in :menuselection:`Inventory --> Configuration --> Settings`."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:23
msgid "First, you need to activate the use of the landed costs. Go to :menuselection:`Inventory application --> Configuration --> Setting`. Check accounting option **Include landed costs in product costing computation** & **Perpetual inventory valuation**, then click on **Apply** to save changes."
#: ../../inventory/routes/costing/landed_costs.rst:27
msgid "Add costs to products"
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:32
msgid "Then go to the :menuselection:`Purchase application --> Configuration --> Setting`. Choose costing method **Use a 'Fixed', 'Real' or 'Average' price costing method**, then click on **Apply** to save changes."
#: ../../inventory/routes/costing/landed_costs.rst:29
msgid "Go in :menuselection:`Inventory --> Operations --> Landed Costs` and click on the **Create** button. You then have to select the transfers on which you want to attribute additional costs and the costs lines you want to add up. Once it's done, click on the **Compute** button to see how the costs lines will be split accross your transfers lines."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:40
msgid "Landed Cost Types"
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:42
msgid "Start by creating specific products to indicate your various **Landed Costs**, such as freight, insurance or custom duties. Go to :menuselection:`Inventory --> Configuration --> Landed Cost types`."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:50
msgid "Landed costs are only possible for products configured in real time valuation with real price costing method. The costing method is configured on the product category."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:55
msgid "Link landed costs to a transfer"
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:57
msgid "To calculate landed costs, go to :menuselection:`Inventory --> Inventory Control --> Landed Costs`."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:60
msgid "Click on the **Create** button and select the picking(s) you want to attribute landed costs."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:66
msgid "Select the account journal in which to post the landed costs. We recommend you to create a specific journal for landed costs. Therefore it will be easier to keep track of your postings."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:73
msgid "Click the **Compute** button to see how the landed costs will be split across the picking lines."
msgstr ""
#: ../../inventory/routes/costing/landed_costs.rst:79
msgid "To confirm the landed costs attribution, click on the **Validate** button."
#: ../../inventory/routes/costing/landed_costs.rst:38
msgid "To confirm, click on the **Validate** button."
msgstr ""
#: ../../inventory/routes/strategies.rst:3
@ -4755,6 +4788,10 @@ msgstr ""
msgid "But the transfer is done in the product unit of measure. Everything is converted automatically :"
msgstr ""
#: ../../inventory/settings/products/uom.rst:125
msgid "Create a link when the document is available - When should you use packages, units of measure or kits?"
msgstr ""
#: ../../inventory/settings/products/usage.rst:3
msgid "When should you use packages, units of measure or kits?"
msgstr ""
@ -5063,6 +5100,14 @@ msgstr ""
msgid "When you have entered all the extra values, click on **Save**."
msgstr ""
#: ../../inventory/settings/products/variants.rst:226
msgid "Accounting Memento: Details of Journal Entries"
msgstr ""
#: ../../inventory/settings/products/variants.rst:227
msgid "Process Overview: From Billing to Payment Orders"
msgstr ""
#: ../../inventory/settings/warehouses/difference_warehouse_location.rst:3
msgid "What is the difference between warehouses and locations?"
msgstr ""

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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,6 +88,58 @@ msgstr ""
msgid "IoT Box Schema"
msgstr ""
#: ../../iot/flash_sdcard.rst:3
msgid "Flashing your SD Card"
msgstr ""
#: ../../iot/flash_sdcard.rst:5
msgid "In some case, you may need to reflash your IoT Boxs SD Card to benefit from our latest updates."
msgstr ""
#: ../../iot/flash_sdcard.rst:9
msgid "Updating your SD Card with Etcher"
msgstr ""
#: ../../iot/flash_sdcard.rst:11
msgid "Go to Balenas website and download `Etcher <http://wwww.balena.org>`__, Its a free and open-source utility used for burning image files. Install and launch it."
msgstr ""
#: ../../iot/flash_sdcard.rst:15
msgid "Now, download the latest image `here <http://nightly.odoo.com/master/posbox/iotbox/>`__, and extract it from the zip file. Then, open *Etcher* and select the image. Select the drive to flash (where your SD Card is) and click on *Flash*!."
msgstr ""
#: ../../iot/flash_sdcard.rst:19
msgid "Now, your image will be automatically updated. You just have to wait 5 minutes for it to finish."
msgstr ""
#: ../../iot/iot_notfound.rst:3
msgid "IoT Box not found"
msgstr ""
#: ../../iot/iot_notfound.rst:5
msgid "When using your IoT Box, a common issue you might encounter is that your box is not found on your database. Fortunately, there are a few easy steps you can follow to find your IoT box."
msgstr ""
#: ../../iot/iot_notfound.rst:10
msgid "HTTPS Issues"
msgstr ""
#: ../../iot/iot_notfound.rst:12
msgid "Your IoT Box is not found? You probably have https issues!"
msgstr ""
#: ../../iot/iot_notfound.rst:14
msgid "To check it, go to your database and verify if your database address starts with an https (like https://www.odoo.com). If this is the case, then you may have problems with your IoT Box image. It should be version 18.12 or later."
msgstr ""
#: ../../iot/iot_notfound.rst:19
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/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>`__)."
msgstr ""
#: ../../iot/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr ""

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-23 12:10+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -21,7 +21,7 @@ msgid "Live Chat"
msgstr ""
#: ../../livechat/livechat.rst:8
msgid "Chat in live with website visitors"
msgid "Chat in real time with website visitors"
msgstr ""
#: ../../livechat/livechat.rst:10
@ -85,11 +85,11 @@ msgid "If no operator is available and/or if the channel is unpublished on the w
msgstr ""
#: ../../livechat/livechat.rst:92
msgid "In practice, the conversations initiated by the visitors will appear in the Discuss module and will also pop up as a direct message. Therefore, inquiries can be answered wherever you are in Odoo."
msgid "Conversations initiated by visitors also appear in the Discuss module in addition to popping up as a direct message. Therefore, inquiries can be answered wherever you are in Odoo."
msgstr ""
#: ../../livechat/livechat.rst:96
msgid "If there several operators in charge of a channel, the system will dispatch sessions randomly between them."
msgid "If there are several operators who have all joined a channel, the system will dispatch visitor sessions randomly between them."
msgstr ""
#: ../../livechat/livechat.rst:100

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -21,78 +21,14 @@ msgid "Mobile"
msgstr ""
#: ../../mobile/firebase.rst:8
msgid "Setup your Firebase Cloud Messaging"
msgid "Push Notifications"
msgstr ""
#: ../../mobile/firebase.rst:10
msgid "In order to have mobile notifications in our Android app, you need an API key."
msgid "As of Odoo 12.0, there is no more complex configuration to enable push notifications in the mobile app."
msgstr ""
#: ../../mobile/firebase.rst:13
msgid "If it is not automatically configured (for instance for On-premise or Odoo.sh) please follow these steps below to get an API key for the android app."
msgstr ""
#: ../../mobile/firebase.rst:18
msgid "The iOS app doesn't support mobile notifications for Odoo versions < 12."
msgstr ""
#: ../../mobile/firebase.rst:22
msgid "Firebase Settings"
msgstr ""
#: ../../mobile/firebase.rst:25
msgid "Create a new project"
msgstr ""
#: ../../mobile/firebase.rst:27
msgid "First, make sure you to sign in to your Google Account. Then, go to `https://console.firebase.google.com <https://console.firebase.google.com/>`__ and create a new project."
msgstr ""
#: ../../mobile/firebase.rst:34
msgid "Choose a project name, click on **Continue**, then click on **Create project**."
msgstr ""
#: ../../mobile/firebase.rst:37
msgid "When you project is ready, click on **Continue**."
msgstr ""
#: ../../mobile/firebase.rst:39
msgid "You will be redirected to the overview project page (see next screenshot)."
msgstr ""
#: ../../mobile/firebase.rst:43
msgid "Add an app"
msgstr ""
#: ../../mobile/firebase.rst:45
msgid "In the overview page, click on the Android icon."
msgstr ""
#: ../../mobile/firebase.rst:50
msgid "You must use \"com.odoo.com\" as Android package name. Otherwise, it will not work."
msgstr ""
#: ../../mobile/firebase.rst:56
msgid "No need to download the config file, you can click on **Next** twice and skip the fourth step."
msgstr ""
#: ../../mobile/firebase.rst:60
msgid "Get generated API key"
msgstr ""
#: ../../mobile/firebase.rst:62
msgid "On the overview page, go to Project settings:"
msgstr ""
#: ../../mobile/firebase.rst:67
msgid "In **Cloud Messaging**, you will see the **API key** and the **Sender ID** that you need to set in Odoo General Settings."
msgstr ""
#: ../../mobile/firebase.rst:74
msgid "Settings in Odoo"
msgstr ""
#: ../../mobile/firebase.rst:76
msgid "Simply paste the API key and the Sender ID from Cloud Messaging."
msgid "Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification (OCN)* and make sure that **Push Notifications** is checked."
msgstr ""

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -33,13 +33,13 @@ msgid "Using a barcode scanner to process point of sale orders improves your eff
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:9
#: ../../point_of_sale/advanced/loyalty.rst:9
#: ../../point_of_sale/advanced/mercury.rst:25
#: ../../point_of_sale/advanced/reprint.rst:8
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:9
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:10
#: ../../point_of_sale/overview/start.rst:22
#: ../../point_of_sale/restaurant/setup.rst:9
#: ../../point_of_sale/restaurant/split.rst:10
#: ../../point_of_sale/shop/seasonal_discount.rst:10
msgid "Configuration"
msgstr ""
@ -52,159 +52,25 @@ msgid "Under the IoT Box / Hardware category, you will find *Barcode Scanner* se
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:21
msgid "You can find more about Barcode Nomenclature here (ADD HYPERLINK)"
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:25
msgid "Add barcodes to product"
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:27
#: ../../point_of_sale/advanced/barcode.rst:23
msgid "Go to :menuselection:`Point of Sale --> Catalog --> Products` and select a product."
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:30
#: ../../point_of_sale/advanced/barcode.rst:26
msgid "Under the general information tab, you can find a barcode field where you can input any barcode."
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:37
#: ../../point_of_sale/advanced/barcode.rst:33
msgid "Scanning products"
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:39
#: ../../point_of_sale/advanced/barcode.rst:35
msgid "From your PoS interface, scan any barcode with your barcode scanner. The product will be added, you can scan the same product to add it multiple times or change the quantity manually on the screen."
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:3
msgid "Using discount tags with a barcode scanner"
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:5
msgid "If you want to sell your products with a discount, for a product getting close to its expiration date for example, you can use discount tags. They allow you to scan discount barcodes."
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:10
msgid "To use discount tags you will need to use a barcode scanner, you can see the documentation about it `here <https://docs.google.com/document/d/1tg7yarr2hPKTddZ4iGbp9IJO-cp7u15eHNVnFoL40Q8/edit>`__"
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:15
msgid "Barcode Nomenclature"
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:17
msgid "To use discounts tags, we need to learn about barcode nomenclature."
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:19
msgid "Let's say you want to have a discount for the product with the following barcode:"
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:25
msgid "You can find the *Default Nomenclature* under the settings of your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:34
msgid "Let's say you want 50% discount on a product you have to start your barcode with 22 (for the discount barcode nomenclature) and then 50 (for the %) before adding the product barcode. In our example, the barcode would be:"
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:43
msgid "Scan the products & tags"
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:45
msgid "You first have to scan the desired product (in our case, a lemon)."
msgstr ""
#: ../../point_of_sale/advanced/discount_tags.rst:50
msgid "And then scan the discount tag. The discount will be applied and you can finish the transaction."
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:3
msgid "Manage a loyalty program"
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:5
msgid "Encourage your customers to continue to shop at your point of sale with a *Loyalty Program*."
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:11
msgid "To activate the *Loyalty Program* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface. Under the Pricing features, select *Loyalty Program*"
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:19
msgid "From there you can create and edit your loyalty programs."
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:24
msgid "You can decide what type of program you wish to use, if the reward is a discount or a gift, make it specific to some products or cover your whole range. Apply rules so that it is only valid in specific situation and everything in between."
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:30
msgid "Use the loyalty program in your PoS interface"
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:32
msgid "When a customer is set, you will now see the points they will get for the transaction and they will accumulate until they are spent. They are spent using the button *Rewards* when they have enough points according to the rules defined in the loyalty program."
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:40
#: ../../point_of_sale/shop/seasonal_discount.rst:45
msgid "You can see the price is instantly updated to reflect the pricelist. You can finalize the order in your usual way."
msgstr ""
#: ../../point_of_sale/advanced/loyalty.rst:44
#: ../../point_of_sale/shop/seasonal_discount.rst:49
msgid "If you select a customer with a default pricelist, it will be applied. You can of course change it."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:3
msgid "Apply manual discounts"
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:5
msgid "If you seldom use discounts, applying manual discounts might be the easiest solution for your Point of Sale."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:8
msgid "You can either apply a discount on the whole order or on specific products."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:12
msgid "Apply a discount on a product"
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:14
msgid "From your session interface, use *Disc* button."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:19
msgid "You can then input a discount (in percentage) over the product that is currently selected and the discount will be applied."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:23
msgid "Apply a global discount"
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:25
msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:28
msgid "Under the *Pricing* category, you will find *Global Discounts* select it."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:34
msgid "You now have a new *Discount* button in your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:39
msgid "Once clicked you can then enter your desired discount (in percentages)."
msgstr ""
#: ../../point_of_sale/advanced/manual_discount.rst:44
msgid "On this example, you can see a global discount of 50% as well as a specific product discount also at 50%."
msgstr ""
#: ../../point_of_sale/advanced/mercury.rst:3
msgid "Accept credit card payment using Mercury"
msgstr ""
@ -326,25 +192,199 @@ msgid "Use the *Reprint receipt* feature if you have the need to reprint a ticke
msgstr ""
#: ../../point_of_sale/advanced/reprint.rst:10
msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface."
msgid "To activate *Reprint Receipt*, go to :menuselection:`Point of Sale --> Configuration --> Point of sale`. and select your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced/reprint.rst:13
msgid "Under the Bills & Receipts category, you will find *Reprint Receipt* option."
msgstr ""
#: ../../point_of_sale/advanced/reprint.rst:20
#: ../../point_of_sale/advanced/reprint.rst:17
msgid "In order to allow the option reprint receipt, you need to activate the receipt printer."
msgstr ""
#: ../../point_of_sale/advanced/reprint.rst:23
msgid "Reprint a receipt"
msgstr ""
#: ../../point_of_sale/advanced/reprint.rst:22
#: ../../point_of_sale/advanced/reprint.rst:25
msgid "On your PoS interface, you now have a *Reprint receipt* button."
msgstr ""
#: ../../point_of_sale/advanced/reprint.rst:27
#: ../../point_of_sale/advanced/reprint.rst:30
msgid "When you use it, you can then reprint your last receipt."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features.rst:3
msgid "Advanced Pricing Features"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:3
msgid "Using discount tags with a barcode scanner"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:5
msgid "If you want to sell your products with a discount, for a product getting close to its expiration date for example, you can use discount tags. They allow you to scan discount barcodes."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:10
msgid "To use discount tags you will need to use a barcode scanner."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:13
msgid "Barcode Nomenclature"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:15
msgid "To use discounts tags, we need to learn about barcode nomenclature."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:17
msgid "Let's say you want to have a discount for the product with the following barcode:"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:23
msgid "You can find the *Default Nomenclature* under the settings of your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:32
msgid "Let's say you want 50% discount on a product you have to start your barcode with 22 (for the discount barcode nomenclature) and then 50 (for the %) before adding the product barcode. In our example, the barcode would be:"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:41
msgid "Scan the products & tags"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:43
msgid "You first have to scan the desired product (in our case, a lemon)."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/discount_tags.rst:48
msgid "And then scan the discount tag. The discount will be applied and you can finish the transaction."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:3
msgid "Manage a loyalty program"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:5
msgid "Encourage your customers to continue to shop at your point of sale with a *Loyalty Program*."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:11
msgid "To activate the *Loyalty Program* feature, go to :menuselection:`Point of Sale --> Configuration --> Point of sale` and select your PoS interface. Under the Pricing features, select *Loyalty Program*"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:19
msgid "From there you can create and edit your loyalty programs."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:24
msgid "You can decide what type of program you wish to use, if the reward is a discount or a gift, make it specific to some products or cover your whole range. Apply rules so that it is only valid in specific situation and everything in between."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:30
msgid "Use the loyalty program in your PoS interface"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:32
msgid "When a customer is set, you will now see the points they will get for the transaction and they will accumulate until they are spent. They are spent using the button *Rewards* when they have enough points according to the rules defined in the loyalty program."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:40
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:45
msgid "You can see the price is instantly updated to reflect the pricelist. You can finalize the order in your usual way."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:44
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:49
msgid "If you select a customer with a default pricelist, it will be applied. You can of course change it."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:3
msgid "Apply manual discounts"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:5
msgid "If you seldom use discounts, applying manual discounts might be the easiest solution for your Point of Sale."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:8
msgid "You can either apply a discount on the whole order or on specific products."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:12
msgid "Apply a discount on a product"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:14
msgid "From your session interface, use *Disc* button."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:19
msgid "You can then input a discount (in percentage) over the product that is currently selected and the discount will be applied."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:23
msgid "Apply a global discount"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:25
msgid "To apply a discount on the whole order, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:28
msgid "Under the *Pricing* category, you will find *Global Discounts* select it."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:34
msgid "You now have a new *Discount* button in your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:39
msgid "Once clicked you can then enter your desired discount (in percentages)."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/manual_discount.rst:44
msgid "On this example, you can see a global discount of 50% as well as a specific product discount also at 50%."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:3
msgid "Apply time-limited discounts"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:5
msgid "Entice your customers and increase your revenue by offering time-limited or seasonal discounts. Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:12
msgid "To activate the *Pricelists* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:18
msgid "Choose the pricelists you want to make available in this Point of Sale and define the default pricelist. You can access all your pricelists by clicking on *Pricelists*."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:23
msgid "Create a pricelist"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:25
msgid "By default, you have a *Public Pricelist* to create more, go to :menuselection:`Point of Sale --> Catalog --> Pricelists`"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:31
msgid "You can set several criterias to use a specific price: periods, min. quantity (meet a minimum ordered quantity and get a price break), etc. You can also chose to only apply that pricelist on specific products or on the whole range."
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:37
msgid "Using a pricelist in the PoS interface"
msgstr ""
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:39
msgid "You now have a new button above the *Customer* one, use it to instantly select the right pricelist."
msgstr ""
#: ../../point_of_sale/analyze.rst:3
msgid "Analyze sales"
msgstr ""
@ -679,34 +719,34 @@ msgid "To activate the *Order printing* feature, go to :menuselection:`Point of
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:16
msgid "Under the IoT Box / Hardware Proxy category, you will find *Order Printers*."
msgid "Under the IoT Box / Hardware Proxy category, you will find *Order Printers*. Note that you need an IoT Box to connect your Printer to the PoS."
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:19
#: ../../point_of_sale/restaurant/kitchen_printing.rst:20
msgid "Add a printer"
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:21
#: ../../point_of_sale/restaurant/kitchen_printing.rst:22
msgid "In your configuration menu you will now have a *Order Printers* option where you can add the printer."
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:28
#: ../../point_of_sale/restaurant/kitchen_printing.rst:29
msgid "Print a kitchen/bar order"
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:33
#: ../../point_of_sale/restaurant/kitchen_printing.rst:34
msgid "Select or create a printer."
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:36
#: ../../point_of_sale/restaurant/kitchen_printing.rst:37
msgid "Print the order in the kitchen/bar"
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:38
#: ../../point_of_sale/restaurant/kitchen_printing.rst:39
msgid "On your PoS interface, you now have a *Order* button."
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:43
#: ../../point_of_sale/restaurant/kitchen_printing.rst:44
msgid "When you press it, it will print the order on your kitchen/bar printer."
msgstr ""
@ -858,7 +898,7 @@ msgstr ""
msgid "Once on the payment interface, you now have a new *Tip* button"
msgstr ""
#: ../../point_of_sale/restaurant/tips.rst:31
#: ../../point_of_sale/restaurant/tips.rst:28
msgid "Add the tip your customer wants to leave and process to the payment."
msgstr ""
@ -1014,39 +1054,3 @@ msgstr ""
msgid "As you can see, the total is in negative, to end the refund you simply have to process the payment."
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:3
msgid "Apply time-limited discounts"
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:5
msgid "Entice your customers and increase your revenue by offering time-limited or seasonal discounts. Odoo has a powerful pricelist feature to support a pricing strategy tailored to your business."
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:12
msgid "To activate the *Pricelists* feature, go to :menuselection:`Point of Sales --> Configuration --> Point of sale` and select your PoS interface."
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:18
msgid "Choose the pricelists you want to make available in this Point of Sale and define the default pricelist. You can access all your pricelists by clicking on *Pricelists*."
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:23
msgid "Create a pricelist"
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:25
msgid "By default, you have a *Public Pricelist* to create more, go to :menuselection:`Point of Sale --> Catalog --> Pricelists`"
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:31
msgid "You can set several criterias to use a specific price: periods, min. quantity (meet a minimum ordered quantity and get a price break), etc. You can also chose to only apply that pricelist on specific products or on the whole range."
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:37
msgid "Using a pricelist in the PoS interface"
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:39
msgid "You now have a new button above the *Customer* one, use it to instantly select the right pricelist."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -151,7 +151,11 @@ msgid "In order to be able to generate a task from a sale order you will need to
msgstr ""
#: ../../project/advanced/so_to_task.rst:39
msgid "Moreover if you wish to be able to invoice your customers based on time spent on the task, it is also necessary to install the **Timesheet** module. Simply go into the application module and install the following:"
msgid "And finally, the **Timesheet** app, Timesheet will not only let you create a task from a Sales order, but also invoice your customer based on the time spent on that task."
msgstr ""
#: ../../project/advanced/so_to_task.rst:41
msgid "Simply go into the application module and install the following:"
msgstr ""
#: ../../project/advanced/so_to_task.rst:47

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -41,7 +41,7 @@ msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:18
#: ../../purchase/purchases/rfq/analyze.rst:24
#: ../../purchase/purchases/rfq/approvals.rst:9
#: ../../purchase/purchases/rfq/bills.rst:31
#: ../../purchase/purchases/rfq/bills.rst:10
#: ../../purchase/purchases/rfq/create.rst:13
#: ../../purchase/purchases/rfq/lock_orders.rst:9
#: ../../purchase/purchases/rfq/reception.rst:14
@ -385,215 +385,39 @@ msgid "Once approved, the purchase order follows the normal process."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:3
msgid "Control supplier bills"
msgid "Bill Control"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:5
msgid "The **Purchase** application allows you to manage your purchase orders, incoming products, and vendor bills all seamlessly in one place."
msgid "With Odoo, you can define a setting to help the control of your bills. *Bill Control* lets you choose if the supplier sends you the bill before or after you receive the goods."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:8
msgid "If you want to set up a vendor bill control process, the first thing you need to do is to have purchase data in Odoo. Knowing what has been purchased and received is the first step towards understanding your purchase management processes."
#: ../../purchase/purchases/rfq/bills.rst:12
msgid "For this feature to work, go to :menuselection:`Purchases --> Configuration --> Settings` and select which way you want to control your bills."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:13
msgid "Here is the standard work flow in Odoo:"
#: ../../purchase/purchases/rfq/bills.rst:20
msgid "Change the control policy"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:15
msgid "You begin with a **Request for Quotation (RFQ)** to send out to your vendor(s)."
#: ../../purchase/purchases/rfq/bills.rst:22
msgid "While the setting above will be your default method of bill control, you can always select which way you want to invoice your product on each product page under the *Purchase* tab."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:18
msgid "Once the vendor has accepted the RFQ, confirm the RFQ into a **Purchase Order (PO)**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:21
msgid "Confirming the PO generates an **Incoming Shipment** if you purchased any stockable products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:24
msgid "Upon receiving a **Vendor Bill** from your Vendor, validate the bill with products received in the previous step to ensure accuracy."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:27
msgid "This process may be done by three different people within the company, or only one."
#: ../../purchase/purchases/rfq/bills.rst:26
msgid "You might want to use different settings for different types of products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:34
msgid "Installing the Purchase and Inventory applications"
msgid "Verify your Vendor Bill"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:36
msgid "From the **Apps** application, search for the **Purchase** module and install it. Due to certain dependencies, installing purchase will automatically install the **Inventory** and **Accounting** applications."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:41
msgid "Creating products"
msgid "If you didnt receive any of your product yet on *Purchase Order* under the *Shipment* tab,"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:43
msgid "Creating products in Odoo is essential for quick and efficient purchasing within Odoo. Simply navigate to the **Products** submenu under **Purchase**, and click **Create**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:50
msgid "When creating the product, Pay attention to the **Product Type** field, as it is important:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:53
msgid "Products that are set as **Stockable** or **Consumable** will allow you to keep track of their inventory levels. These options imply stock management and will allow for receiving these kinds of products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:58
msgid "Conversely, products that are set as a **Service** or **Digital Product** will not imply stock management, simply due to the fact that there is no inventory to manage. You will not be able to receive products under either of these designations."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:64
msgid "It is recommended that you create a **Miscellaneous** product for all purchases that occur infrequently and do not require inventory valuation or management. If you create such a product, it is recommend to set the product type to **Service**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:70
msgid "Managing your Vendor Bills"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:73
msgid "Purchasing products or services"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:75
msgid "From the purchase application, you can create a purchase order with as many products as you need. If the vendor sends you a confirmation or quotation for an order, you may record the order reference number in the **Vendor Reference** field. This will enable you to easily match the PO with the the vendor bill later (as the vendor bill will probably include the Vendor Reference)"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:85
msgid "Validate the purchase order and receive the products from the **Inventory** application."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:89
msgid "Receiving Products"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:91
msgid "If you purchased any stockable products that you manage the inventory of, you will need to receive the products from the **Inventory** application after you confirm a purchase order. From the **Inventory** dashboard, you should see a button linking you directly to the transfer of products. This button is outlined in red below:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:100
msgid "Navigating this route will take you to a list of all orders awaiting to be received."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:106
msgid "If you have a lot of awaiting orders, apply a filter using the search bar in the upper right. With this search bar, you may filter based on the **Vendor** (or **Partner**), the product, or the source document, also known as the reference of your purchase order. You also have the capability to group the orders by different criteria under **Group By**. Selecting an item from this list will open the following screen where you then will receive the products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:117
msgid "Purchasing **Service** products does not trigger a delivery order."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:120
msgid "Managing Vendor Bills"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:122
msgid "When you receive a **Vendor Bill** for a previous purchase, be sure to record it in the **Purchases** application under the **Control Menu**. You need to create a new vendor bill even if you already registered a purchase order."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:130
msgid "The first thing you will need to do upon creating a **Vendor Bill** is to select the appropriate **Vendor** as this will also pull up any associated accounting or pricelist information. From there, you can choose to specify any one or multiple purchase orders to populate the vendor bill with. When you select a purchase order from the list, Odoo will pull any uninvoiced products associated to that purchase order and automatically populate that information below. If you are having a hard time finding the appropriate vendor bill, you may search through the list by inputting the vendor reference number or your internal purchase order number."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:144
msgid "While the invoice is in draft state, you can make any modifications you need (i.e. remove or add product lines, modify quantities, and change prices)."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:149
msgid "Your vendor may send you several bills for the same purchase order if:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:151
msgid "Your vendor is in back-order and is sending you invoices as they ship the products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:154
msgid "Your vendor is sending you a partial bill or asking for a deposit."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:156
msgid "Every time you record a new vendor bill, Odoo will automatically populate the product quantities based on what has been received from the vendor. If this value is showing a zero, this means that you have not yet received this product and simply serves as a reminder that the product is not in hand and you may need to inquire further into this. At any point in time, before you validate the vendor bill, you may override this zero quantity."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:165
msgid "Vendor Bill Matching"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:168
msgid "What to do if your vendor bill does not match what you received"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:170
msgid "If the bill you receive from the vendor has different quantities than what Odoo automatically populates as quantities, this could be due to several reasons:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:174
msgid "The vendor is incorrectly charging you for products and/or services that you have not ordered."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:177
msgid "The vendor is billing you for products that you might not have received yet, as the invoicing control may be based on ordered or received quantities."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:181
msgid "Or the vendor did not bill you for previously purchased products."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:183
msgid "In these instances it is recommended that you verify that the bill, and any associated purchase order to the vendor, are accurate and that you understand what you have ordered and what you have already received."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:187
msgid "If you are unable to find a purchase order related to a vendor bill, this could be due to one of a few reasons:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:190
msgid "The vendor has already invoiced you for this purchase order, therefore it is not going to appear anywhere in the selection."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:193
msgid "Someone in the company forgot to record a purchase order for this vendor."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:196
msgid "Or the vendor is charging you for something you did not order."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:199
msgid "How product quantities are managed"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:201
msgid "By default, services are managed based on ordered quantities, while stockables and consumables are managed based on received quantities."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:204
msgid "If you need to manage products based on ordered quantities over received quantities, you will need to enable **Debug Mode** from the **About Odoo** information. Once debug mode is activated, select the product(s) you wish to modify, and you should see a new field appear, labeled **Control Purchase Bills**."
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:213
msgid "You can then change the default management method for the selected product to be based on either:"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:216
msgid "Ordered quantities"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:218
msgid "Received quantities"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:221
msgid "Batch Billing"
msgstr ""
#: ../../purchase/purchases/rfq/bills.rst:223
msgid "When creating a vendor bill and selecting the appropriate purchase order, you may continue to select additional purchase orders and Odoo will add the additional line items from that purchase order. If you have not deleted the previous line items from the first purchase order the bill will be linked to all the appropriate purchase orders."
msgid "Depending on the billing policy defined above. If you're supposed to be billed based on ordered quantity, Odoo will suggest a bill for the number of units ordered. If you're supposed to be billed based on the received quantities, Odoo will suggest a bill for 0 as shown above."
msgstr ""
#: ../../purchase/purchases/rfq/cancel.rst:3

View File

@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 12.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"POT-Creation-Date: 2019-09-16 15:50+0200\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"
@ -750,7 +750,7 @@ msgid "Stimulate customers with quotations deadline"
msgstr ""
#: ../../sales/send_quotations/deadline.rst:5
msgid "As you send quotations, it is important to set a quotation deadline; Both to entice your customer into action with the fear of missing out on an offer and to protect yourself. You don't want to have to fulfill an order at a price that is no longer cost effective for you."
msgid "As you send quotations, it is important to set a quotation deadline, both to entice your customer into action with the fear of missing out on an offer and to protect yourself. You don't want to have to fulfill an order at a price that is no longer cost effective for you."
msgstr ""
#: ../../sales/send_quotations/deadline.rst:11
@ -770,7 +770,7 @@ msgid "You can also set a default deadline in a *Quotation Template*. Each time
msgstr ""
#: ../../sales/send_quotations/deadline.rst:29
msgid "On your customer side, they will see this."
msgid "On your customer side, they will see this:"
msgstr ""
#: ../../sales/send_quotations/different_addresses.rst:3

File diff suppressed because it is too large Load Diff