[I18N] export 12.0 source terms

This commit is contained in:
Martin Trigaux 2018-11-07 15:39:32 +01:00
parent d895527c64
commit 556c13bb3f
6 changed files with 428 additions and 420 deletions

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: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -26,6 +26,7 @@ msgid "Bank & Cash"
msgstr ""
#: ../../accounting/bank/feeds.rst:3
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Bank Feeds"
msgstr ""
@ -978,7 +979,6 @@ msgstr ""
#: ../../accounting/bank/setup/create_bank_account.rst:0
#: ../../accounting/bank/setup/manage_cash_register.rst:0
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Type"
msgstr ""
@ -1263,7 +1263,27 @@ msgid "The currency used to enter statement"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Debit Methods"
msgid "Defines how the bank statements will be registered"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Creation of Bank Statements"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Defines when a new bank statement"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "will be created when fetching new transactions"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "from your bank account."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "For Incoming Payments"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
@ -1281,7 +1301,7 @@ msgid "Batch Deposit: Encase several customer checks at once by generating a bat
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Payment Methods"
msgid "For Outgoing Payments"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
@ -1296,14 +1316,6 @@ msgstr ""
msgid "SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit to your bank. Enable this option from the settings."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Group Invoice Lines"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "If this box is checked, the system will try to group the accounting lines when generating them from invoices."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Profit Account"
msgstr ""
@ -1321,11 +1333,27 @@ msgid "Used to register a loss when the ending balance of a cash register differ
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Show journal on dashboard"
msgid "Group Invoice Lines"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Whether this journal should be displayed on the dashboard or not"
msgid "If this box is checked, the system will try to group the accounting lines when generating them from invoices."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Post At Bank Reconciliation"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Whether or not the payments made in this journal should be generated in draft state, so that the related journal entries are only posted when performing bank reconciliation."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Alias Name for Vendor Bills"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "It creates draft vendor bill by sending an email."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
@ -1362,22 +1390,6 @@ msgstr ""
msgid "Sequence number of the next printed check."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Creation of bank statement"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "This field is used for the online synchronization:"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "depending on the option selected, newly fetched transactions"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "will be put inside previous statement or in a new one"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Amount Authorized Difference"
msgstr ""
@ -2003,7 +2015,7 @@ msgid "First, make sure that your company is configured with the correct data. G
msgstr ""
#: ../../accounting/localizations/mexico.rst:77
msgid "If you want use the Mexican localization on test mode, you can put any known address inside Mexico with all fields for the company address and set the vat to **ACO560518KW7**."
msgid "If you want use the Mexican localization on test mode, you can put any known address inside Mexico with all fields for the company address and set the vat to **TCM970625MB1**."
msgstr ""
#: ../../accounting/localizations/mexico.rst:85
@ -2995,6 +3007,134 @@ msgstr ""
msgid "Explanation of the fields:"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Status"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "When an asset is created, the status is 'Draft'."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "If the asset is confirmed, the status goes in 'Running' and the depreciation lines can be posted in the accounting."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "You can manually close an asset when the depreciation is over. If the last line of depreciation is posted, the asset automatically goes in that status."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Asset Category"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Category of asset"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Date"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Date of asset"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Depreciation Dates"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "The way to compute the date of the first depreciation."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Based on last day of purchase period: The depreciation dates will be based on the last day of the purchase month or the purchase year (depending on the periodicity of the depreciations)."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Based on purchase date: The depreciation dates will be based on the purchase date."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "First Depreciation Date"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Note that this date does not alter the computation of the first journal entry in case of prorata temporis assets. It simply changes its accounting date"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Gross Value"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Gross value of asset"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Salvage Value"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "It is the amount you plan to have that you cannot depreciate."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Computation Method"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Choose the method to use to compute the amount of depreciation lines."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Linear: Calculated on basis of: Gross Value / Number of Depreciations"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Degressive: Calculated on basis of: Residual Value * Degressive Factor"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Time Method Based On"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Choose the method to use to compute the dates and number of entries."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Number of Entries: Fix the number of entries and the time between 2 depreciations."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Ending Date: Choose the time between 2 depreciations and the date the depreciations won't go beyond."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Prorata Temporis"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Indicates that the first depreciation entry for this asset have to be done from the asset date (purchase date) instead of the first January / Start date of fiscal year"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Number of Depreciations"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "The number of depreciations needed to depreciate your asset"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Number of Months in a Period"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "The amount of time between two depreciations, in months"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:88
msgid "Try creating an *Asset* in our online demonstration"
msgstr ""
@ -4132,42 +4272,6 @@ msgstr ""
msgid "To create a new accounts, go to the Accounting application. Open the menu :menuselection:`Adviser --> Chart of Accounts`, the click on the **Create** button."
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Account Type is used for information purpose, to generate country-specific legal reports, and set the rules to close a fiscal year and generate opening entries."
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Tags"
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Optional tags you may want to assign for custom reporting"
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Account Currency"
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Forces all moves for this account to have this account currency."
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Internal Type"
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "The 'Internal Type' is used for features available on different types of accounts: liquidity type is for cash or bank accounts, payable/receivable is for vendor/customer accounts."
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Allow Reconciliation"
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:0
msgid "Check this box if this account allows invoices & payments matching of journal items."
msgstr ""
#: ../../accounting/others/configuration/account_type.rst:86
msgid "View *Create Account* in our Online Demonstration"
msgstr ""
@ -7273,13 +7377,21 @@ msgid "Check: Pay bill by check and print it from Odoo."
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "Batch Deposit: Encase several customer checks at once by generating a batch deposit to submit to your bank. When encoding the bank statement in Odoo, you are suggested to reconcile the transaction with the batch deposit.To enable batch deposit,module account_batch_deposit must be installed."
msgid "Batch Deposit: Encase several customer checks at once by generating a batch deposit to submit to your bank. When encoding the bank statement in Odoo, you are suggested to reconcile the transaction with the batch deposit.To enable batch deposit, module account_batch_payment must be installed."
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "SEPA Credit Transfer: Pay bill from a SEPA Credit Transfer file you submit to your bank. To enable sepa credit transfer, module account_sepa must be installed"
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "Show Partner Bank Account"
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "Technical field used to know whether the field `partner_bank_account_id` needs to be displayed or not in the payments form views"
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "Code"
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: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -561,3 +561,51 @@ msgstr ""
msgid ":doc:`../../website/publish/translate`"
msgstr ""
#: ../../general/unsplash.rst:3
msgid "Unsplash"
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:3
msgid "How to generate an Unsplash access key"
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:5
msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:7
msgid "Go to your `applications dashboard <https://unsplash.com/oauth/applications>`_ and click on **New Application**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:12
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**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:22
msgid "You should be redirected to your application details page. Scroll down a bit to find your **access key**."
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>`_."
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:7
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."
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-26 12:01+0200\n"
"POT-Creation-Date: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -17,486 +17,266 @@ msgstr ""
"Content-Transfer-Encoding: 8bit\n"
#: ../../getting_started/documentation.rst:5
msgid "Odoo Online Implementation"
msgid "Basics of the QuickStart Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:7
msgid "This document summarizes **Odoo Online's services**, our Success Pack **implementation methodology**, and best practices to get started with our product."
msgid "This document summarizes Odoo Online's services, our Success Pack implementation methodology, and best practices to get started with our product."
msgstr ""
#: ../../getting_started/documentation.rst:11
msgid "*We recommend that new Odoo Online customers read this document before the kick-off call with our project manager. This way, we save time and don't have to use your hours from the success pack discussing the basics.*"
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:16
msgid "*If you have not read this document, our project manager will review this with you at the time of the kick-off call.*"
#: ../../getting_started/documentation.rst:14
msgid "Within the context of your project, it is highly recommended to designate and maintain on both sides (your side and ours) **one and only single person of contact** who will take charge and assume responsibilities regarding the project. He also has to have **the authority** in terms of decision making."
msgstr ""
#: ../../getting_started/documentation.rst:20
msgid "Getting Started"
msgid "**The Odoo Consultant ensures the project implementation from A to Z**: From the beginning to the end of the project, he ensures the overall consistency of the implementation in Odoo and shares his expertise in terms of good practices."
msgstr ""
#: ../../getting_started/documentation.rst:22
msgid "Do not wait for the kick-off meeting to begin playing with the software. The more exposure you have with Odoo, the more time you will save later during the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:26
msgid "Once you purchase an Odoo Online subscription, you will receive instructions by email on how to activate or create your database. From this email, you can activate your existing Odoo database or create a new one from scratch."
#: ../../getting_started/documentation.rst:25
msgid "**One and only decision maker on the client side (SPoC)**: He is responsible for the business knowledge transmission (coordinate key users intervention if necessary) and the consistency of the implementation from a business point of view (decision making, change management, etc.)"
msgstr ""
#: ../../getting_started/documentation.rst:31
msgid "If you did not receive this email, e.g. because the payment was made by someone else in your company, contact our support team using our `online support form <https://www.odoo.com/help>`__."
msgid "**Meetings optimization**: The Odoo consultant is not involved in the process of decision making from a business point of view nor to precise processes and company's internal procedures (unless a specific request or an exception). Project meetings, who will take place once or twice a week, are meant to align on the business needs (SPoC) and to define the way those needs will be implemented in Odoo (Consultant)."
msgstr ""
#: ../../getting_started/documentation.rst:38
msgid "Fill in the sign-in or sign-up screens and you will get your first Odoo database ready to be used."
msgstr ""
#: ../../getting_started/documentation.rst:41
msgid "In order to familiarize yourself with the user interface, take a few minutes to create records: *products, customers, opportunities* or *projects/tasks*. Follow the blinking dots, they give you tips about the user interface as shown in the picture below."
#: ../../getting_started/documentation.rst:39
msgid "**Train the Trainer approach**: The Odoo consultant provides functional training to the SPoC so that he can pass on this knowledge to his collaborators. In order for this approach to be successful, it is necessary that the SPoC is also involved in its own rise in skills through self-learning via the `Odoo documentation <http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "|left_pic|"
msgid "2. Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "|right_pic|"
#: ../../getting_started/documentation.rst:49
msgid "To make sure all the stakeholders involved are always aligned, it is necessary to define and to make the project scope evolve as long as the project implementation is pursuing."
msgstr ""
#: ../../getting_started/documentation.rst:50
msgid "Once you get used to the user interface, have a look at the implementation planners. These are accessible from the Settings app, or from the top progress bar on the right hand side of the main applications."
#: ../../getting_started/documentation.rst:53
msgid "**A clear definition of the initial project scope**: A clear definition of the initial needs is crucial to ensure the project is running smoothly. Indeed, when all the stakeholders share the same vision, the evolution of the needs and the resulting decision-making process are more simple and more clear."
msgstr ""
#: ../../getting_started/documentation.rst:58
msgid "These implementation planners will:"
msgstr ""
#: ../../getting_started/documentation.rst:60
msgid "help you define your goals and KPIs for each application,"
msgstr ""
#: ../../getting_started/documentation.rst:62
msgid "guide you through the different configuration steps,"
msgstr ""
#: ../../getting_started/documentation.rst:64
msgid "and provide you with tips and tricks to getting the most out of Odoo."
#: ../../getting_started/documentation.rst:59
msgid "**Phasing the project**: Favoring an implementation in several coherent phases allowing regular production releases and an evolving takeover of Odoo by the end users have demonstrated its effectiveness over time. This approach also helps to identify gaps and apply corrective actions early in the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
msgid "Fill in the first steps of the implementation planner (goals, expectations and KPIs). Our project manager will review them with you during the implementation process."
msgid "**Adopting standard features as a priority**: Odoo offers a great environment to implement slight improvements (customizations) or more important ones (developments). Nevertheless, adoption of the standard solution will be preferred as often as possible in order to optimize project delivery times and provide the user with a long-term stability and fluid scalability of his new tool. Ideally, if an improvement of the software should still be realized, its implementation will be carried out after an experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:73
msgid "If you have questions or need support, our project manager will guide you through all the steps. But you can also:"
msgstr ""
#: ../../getting_started/documentation.rst:76
msgid "Read the documentation on our website: `https://www.odoo.com/documentation/user <https://www.odoo.com/documentation/user>`__"
msgstr ""
#: ../../getting_started/documentation.rst:79
msgid "Watch the videos on our eLearning platform (free with your first Success Pack): `https://odoo.thinkific.com/courses/odoo-functional <https://odoo.thinkific.com/courses/odoo-functional>`__"
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
msgid "Watch the webinars on our `Youtube channel <https://www.youtube.com/user/OpenERPonline>`__"
msgid "The gap between the reality of an implementation and the expectations of future users is a crucial factor. Three important aspects must be taken into account from the beginning of the project:"
msgstr ""
#: ../../getting_started/documentation.rst:85
msgid "Or send your questions to our online support team through our `online support form <https://www.odoo.com/help>`__."
#: ../../getting_started/documentation.rst:86
msgid "**Align with the project approach**: Both a clear division of roles and responsibilities and a clear description of the operating modes (validation, problem-solving, etc.) are crucial to the success of an Odoo implementation. It is therefore strongly advised to take the necessary time at the beginning of the project to align with these topics and regularly check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:89
msgid "What do we expect from you?"
#: ../../getting_started/documentation.rst:94
msgid "**Focus on the project success, not on the ideal solution**: The main goal of the SPoC and the Consultant is to carry out the project entrusted to them in order to provide the most effective solution to meet the needs expressed. This goal can sometimes conflict with the end user's vision of an ideal solution. In that case, the SPoC and the consultant will apply the 80-20 rule: focus on 80% of the expressed needs and take out the remaining 20% of the most disadvantageous objectives in terms of cost/benefit ratio (those proportions can of course change over time). Therefore, it will be considered acceptable to integrate a more time-consuming manipulation if a global relief is noted. Changes in business processes may also be proposed to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:91
msgid "We are used to deploying fully featured projects within 25 to 250 hours of services, which is much faster than any other ERP vendor on the market. Most projects are completed between 1 to 9 calendar months."
#: ../../getting_started/documentation.rst:108
msgid "**Specifications are always EXPLICIT**: Gaps between what is expected and what is delivered are often a source of conflict in a project. In order to avoid being in this delicate situation, we recommend using several types of tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:95
msgid "But what really **differentiates between a successful implementation and a slow one, is you, the customer!** From our experience, when our customer is engaged and proactive the implementation is smooth."
#: ../../getting_started/documentation.rst:113
msgid "**The GAP Analysis**: The comparison of the request with the standard features proposed by Odoo will make it possible to identify the gap to be filled by developments/customizations or changes in business processes."
msgstr ""
#: ../../getting_started/documentation.rst:100
msgid "Your internal implementation manager"
#: ../../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."
msgstr ""
#: ../../getting_started/documentation.rst:102
msgid "We ask that you maintain a single point of contact within your company to work with our project manager on your Odoo implementation. This is to ensure efficiency and a single knowledge base in your company. Additionally, this person must:"
msgstr ""
#: ../../getting_started/documentation.rst:107
msgid "**Be available at least 2 full days a week** for the project, otherwise you risk slowing down your implementation. More is better with the fastest implementations having a full time project manager."
msgstr ""
#: ../../getting_started/documentation.rst:111
msgid "**Have authority to take decisions** on their own. Odoo usually transforms all departments within a company for the better. There can be many small details that need quick turnarounds for answers and if there is too much back and forth between several internal decision makers within your company it could potentially seriously slow everything down."
msgstr ""
#: ../../getting_started/documentation.rst:117
msgid "**Have the leadership** to train and enforce policies internally with full support from all departments and top management, or be part of top management."
msgstr ""
#: ../../getting_started/documentation.rst:121
msgid "Integrate 90% of your business, not 100%"
msgstr ""
#: ../../getting_started/documentation.rst:123
msgid "You probably chose Odoo because no other software allows for such a high level of automation, feature coverage, and integration. But **don't be an extremist.**"
msgstr ""
#: ../../getting_started/documentation.rst:127
msgid "Customizations cost you time, money, are more complex to maintain, add risks to the implementation, and can cause issues with upgrades."
#: ../../getting_started/documentation.rst:126
msgid "`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A simplified version, a prototype of what is expected to agree on the main lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
msgid "Standard Odoo can probably cover 90% of your business processes and requirements. Be flexible on the remaining 10%, otherwise that 10% will cost you twice the original project price. One always underestimates the hidden costs of customization."
msgid "**The Mockup**: In the same idea as the Proof of Concept, it will align with the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:134
msgid "**Do it the Odoo way, not yours.** Be flexible, use Odoo the way it was designed. Learn how it works and don't try to replicate the way your old system(s) work."
#: ../../getting_started/documentation.rst:133
msgid "To these tools will be added complete transparency on the possibilities and limitations of the software and/or its environment so that all project stakeholders have a clear idea of what can be expected/achieved in the project. We will, therefore, avoid basing our work on hypotheses without verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:138
msgid "**The project first, customizations second.** If you really want to customize Odoo, phase it towards the end of the project, ideally after having been in production for several months. Once a customer starts using Odoo, they usually drop about 60% of their customization requests as they learn to perform their workflows out of the box, or the Odoo way. It is more important to have all your business processes working than customizing a screen to add a few fields here and there or automating a few emails."
#: ../../getting_started/documentation.rst:139
msgid "*This list can, of course, be completed by other tools that would more adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:147
msgid "Our project managers are trained to help you make the right decisions and measure the tradeoffs involved but it is much easier if you are aligned with them on the objectives. Some processes may take more time than your previous system(s), however you need to weigh that increase in time with other decreases in time for other processes. If the net time spent is decreased with your move to Odoo than you are already ahead."
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:155
msgid "Invest time in learning Odoo"
#: ../../getting_started/documentation.rst:145
msgid "The purpose of the QuickStart methodology is to ensure quick ownership of the tool for end users. Effective communication is therefore crucial to the success of this approach. Its optimization will, therefore, lead us to follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:157
msgid "Start your free trial and play with the system. The more comfortable you are navigating Odoo, the better your decisions will be and the quicker and easier your training phases will be."
#: ../../getting_started/documentation.rst:150
msgid "**Sharing the project management documentation**: The best way to ensure that all stakeholders in a project have the same level of knowledge is to provide direct access to the project's tracking document (Project Organizer). This document will contain at least a list of tasks to be performed as part of the implementation for which the priority level and the manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:161
msgid "Nothing replaces playing with the software, but here are some extra resources:"
#: ../../getting_started/documentation.rst:158
msgid "The Project Organizer is a shared project tracking tool that allows both detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
#: ../../getting_started/documentation.rst:164
msgid "Documentation: `https://www.odoo.com/documentation/user <https://www.odoo.com/documentation/user>`__"
#: ../../getting_started/documentation.rst:162
msgid "**Report essential information**: In order to minimize the documentation time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:167
msgid "Introduction Videos: `https://www.odoo.com/r/videos <https://www.odoo.com/r/videos>`__"
#: ../../getting_started/documentation.rst:166
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:170
msgid "Customer Reviews: `https://www.odoo.com/blog/customer-reviews-6 <https://www.odoo.com/blog/customer-reviews-6>`__"
#: ../../getting_started/documentation.rst:168
msgid "Project statuses will only be established when an important milestone is reached;"
msgstr ""
#: ../../getting_started/documentation.rst:174
msgid "Get things done"
#: ../../getting_started/documentation.rst:171
msgid "Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:176
msgid "Want an easy way to start using Odoo? Install Odoo Notes to manage your to-do list for the implementation: `https://www.odoo.com/page/notes <https://www.odoo.com/page/notes>`__. From your Odoo home, go to Apps and install the Notes application."
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:184
msgid "This module allows you to:"
#: ../../getting_started/documentation.rst:177
msgid "Odoo is a software known for its flexibility and its important evolution capacity. However, a significant amount of development contradicts a fast and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""
#: ../../getting_started/documentation.rst:186
msgid "Manage to-do lists for better interactions with your consultant;"
#: ../../getting_started/documentation.rst:182
msgid "**Develop only for a good reason**: The decision to develop must always be taken when the cost-benefit ratio is positive (saving time on a daily basis, etc.). For example, it will be preferable to realize a significant development in order to reduce the time of a daily operation, rather than an operation to be performed only once a quarter. It is generally accepted that the closer the solution is to the standard, the lighter and more fluid the migration process, and the lower the maintenance costs for both parties. In addition, experience has shown us that 60% of initial development requests are dropped after a few weeks of using standard Odoo (see \"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:188
msgid "Share Odoo knowledge & good practices with your employees;"
msgstr ""
#: ../../getting_started/documentation.rst:190
msgid "Get acquainted with all the generic tools of Odoo: Messaging, Discussion Groups, Kanban Dashboard, etc."
msgstr ""
#: ../../getting_started/documentation.rst:197
msgid "This application is even compatible with the Etherpad platform (http://etherpad.org). To use these collaborative pads rather than standard Odoo Notes, install the following add-on: Memos Pad."
#: ../../getting_started/documentation.rst:194
msgid "**Replace, without replicate**: There is a good reason for the decision to change the management software has been made. In this context, the moment of implementation is THE right moment to accept and even be a change initiator both in terms of how the software will be used and at the level of the business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "What should you expect from us?"
msgid "6. Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:205
msgid "Subscription Services"
#: ../../getting_started/documentation.rst:204
msgid "Whether developments are made or not in the implementation, it is crucial to test and validate the correspondence of the solution with the operational needs of the company."
msgstr ""
#: ../../getting_started/documentation.rst:208
msgid "Cloud Hosting"
msgstr ""
#: ../../getting_started/documentation.rst:210
msgid "Odoo provides a top notch cloud infrastructure including backups in three different data centers, database replication, the ability to duplicate your instance in 10 minutes, and more!"
msgid "**Role distribution**: In this context, the Consultant will be responsible for delivering a solution corresponding to the defined specifications; the SPoC will have to test and validate that the solution delivered meets the requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
msgid "Odoo Online SLA: `https://www.odoo.com/page/odoo-online-sla <https://www.odoo.com/page/odoo-online-sla>`__\\"
msgid "**Change management**: When a change needs to be made to the solution, the noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:217
msgid "Odoo Online Security: `https://www.odoo.com/page/security <https://www.odoo.com/fr_FR/page/security>`__"
#: ../../getting_started/documentation.rst:218
msgid "A difference between the specification and the delivered solution - This is a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
msgid "Privacy Policies: `https://www.odoo.com/page/odoo-privacy-policy <https://www.odoo.com/page/odoo-privacy-policy>`__"
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:224
msgid "Support"
#: ../../getting_started/documentation.rst:222
msgid "A difference between the specification and the imperatives of operational reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
msgid "Importing the history of transactional data is an important issue and must be answered appropriately to allow the project running smoothly. Indeed, this task can be time-consuming and, if its priority is not well defined, prevent production from happening in time. To do this as soon as possible, it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:234
msgid "**Not to import anything**: It often happens that after reflection, importing data history is not considered necessary, these data being, moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
#: ../../getting_started/documentation.rst:239
msgid "**To import a limited amount of data before going into production**: When the data history relates to information being processed (purchase orders, invoices, open projects, for example), the need to have this information available from the first day of use in production is real. In this case, the import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:246
msgid "**To import after production launch**: When the data history needs to be integrated with Odoo mainly for reporting purposes, it is clear that these can be integrated into the software retrospectively. In this case, the production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
msgid "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!"
msgstr ""
#: ../../getting_started/documentation.rst:231
#: ../../getting_started/documentation.rst:260
msgid "What kind of support is included?"
msgstr ""
#: ../../getting_started/documentation.rst:233
#: ../../getting_started/documentation.rst:262
msgid "Providing you with relevant material (guidelines, product documentation, etc...)"
msgstr ""
#: ../../getting_started/documentation.rst:235
#: ../../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:237
#: ../../getting_started/documentation.rst:266
msgid "Questions related to your account, subscription, or billing"
msgstr ""
#: ../../getting_started/documentation.rst:238
#: ../../getting_started/documentation.rst:267
msgid "Bug resolution (blocking issues or unexpected behaviour not due to misconfiguration or customization)"
msgstr ""
#: ../../getting_started/documentation.rst:240
#: ../../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:242
#: ../../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:245
#: ../../getting_started/documentation.rst:274
msgid "What kind of support is not included?"
msgstr ""
#: ../../getting_started/documentation.rst:247
#: ../../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:249
#: ../../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:250
#: ../../getting_started/documentation.rst:279
msgid "Importation of documents into your database"
msgstr ""
#: ../../getting_started/documentation.rst:251
#: ../../getting_started/documentation.rst:280
msgid "Guidance on which configurations to apply inside of an application or the database"
msgstr ""
#: ../../getting_started/documentation.rst:252
#: ../../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:254
#: ../../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:258
#: ../../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:263
#: ../../getting_started/documentation.rst:292
msgid "Our support team can be contacted through our `online support form <https://www.odoo.com/help>`__."
msgstr ""
#: ../../getting_started/documentation.rst:268
msgid "Upgrades"
msgstr ""
#: ../../getting_started/documentation.rst:270
msgid "Once every two months, Odoo releases a new version. You will get an upgrade button within the **Manage Your Databases** screen. Upgrading your database is at your own discretion, but allows you to benefit from new features."
msgstr ""
#: ../../getting_started/documentation.rst:275
msgid "We provide the option to upgrade in a test environment so that you can evaluate a new version or train your team before the rollout. Simply fill our `online support form <https://www.odoo.com/help>`__ to make this request."
msgstr ""
#: ../../getting_started/documentation.rst:280
msgid "Success Pack Services"
msgstr ""
#: ../../getting_started/documentation.rst:282
msgid "The Success Pack is a package of premium hour-based services performed by a dedicated project manager and business analyst. The initial allotted hours you purchased are purely an estimate and we do not guarantee completion of your project within the first pack. We always strive to complete projects within the initial allotment however any number of factors can contribute to us not being able to do so; for example, a scope expansion (or \"Scope Creep\") in the middle of your implementation, new detail discoveries, or an increase in complexity that was not apparent from the beginning."
msgstr ""
#: ../../getting_started/documentation.rst:291
msgid "The list of services according to your Success Pack is detailed online: `https://www.odoo.com/pricing-packs <https://www.odoo.com/pricing-packs>`__"
msgstr ""
#: ../../getting_started/documentation.rst:294
msgid "The goal of the project manager is to help you get to production within the defined time frame and budget, i.e. the initial number of hours defined in your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:298
msgid "His/her role includes:"
msgstr ""
#: ../../getting_started/documentation.rst:300
msgid "**Project Management:** Review of your objectives & expectations, phasing of the implementation (roadmap), mapping your business needs to Odoo features."
msgstr ""
#: ../../getting_started/documentation.rst:304
msgid "**Customized Support:** By phone, email or webinar."
msgstr ""
#: ../../getting_started/documentation.rst:306
msgid "**Training, Coaching, and Onsite Consulting:** Remote trainings via screen sharing or training on premises. For on-premise training sessions, you will be expected to pay extra for travel expenses and accommodations for your consultant."
msgstr ""
#: ../../getting_started/documentation.rst:311
msgid "**Configuration:** Decisions about how to implement specific needs in Odoo and advanced configuration (e.g. logistic routes, advanced pricing structures, etc.)"
msgstr ""
#: ../../getting_started/documentation.rst:315
msgid "**Data Import**: We can do it or assist you on how to do it with a template prepared by the project manager."
msgstr ""
#: ../../getting_started/documentation.rst:318
msgid "If you have subscribed to **Studio**, you benefit from the following extra services:"
msgstr ""
#: ../../getting_started/documentation.rst:321
msgid "**Customization of screens:** Studio takes the Drag and Drop approach to customize most screens in any way you see fit."
msgstr ""
#: ../../getting_started/documentation.rst:324
msgid "**Customization of reports (PDF):** Studio will not allow you to customize the reports yourself, however our project managers have access to developers for advanced customizations."
msgstr ""
#: ../../getting_started/documentation.rst:328
msgid "**Website design:** Standard themes are provided to get started at no extra cost. However, our project manager can coach you on how to utilize the building blocks of the website designer. The time spent will consume hours of your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:333
msgid "**Workflow automations:** Some examples include setting values in fields based on triggers, sending reminders by emails, automating actions, etc. For very advanced automations, our project managers have access to Odoo developers."
msgstr ""
#: ../../getting_started/documentation.rst:338
msgid "If any customization is needed, Odoo Studio App will be required. Customizations made through Odoo Studio App will be maintained and upgraded at each Odoo upgrade, at no extra cost."
msgstr ""
#: ../../getting_started/documentation.rst:342
msgid "All time spent to perform these customizations by our Business Analysts will be deducted from your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:345
msgid "In case of customizations that cannot be done via Studio and would require a developers intervention, this will require Odoo.sh, please speak to your Account Manager for more information. Additionally, any work performed by a developer will add a recurring maintenance fee to your subscription to cover maintenance and upgrade services. This cost will be based on hours spent by the developer: 4€ or $5/month, per hour of development will be added to the subscription fee."
msgstr ""
#: ../../getting_started/documentation.rst:353
msgid "**Example:** A customization that took 2 hours of development will cost: 2 hours deducted from the Success Pack for the customization development 2 * $5 = $10/month as a recurring fee for the maintenance of this customization"
msgstr ""
#: ../../getting_started/documentation.rst:358
msgid "Implementation Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:360
msgid "We follow a **lean and hands-on methodology** that is used to put customers in production in a short period of time and at a low cost."
msgstr ""
#: ../../getting_started/documentation.rst:363
msgid "After the kick-off meeting, we define a phasing plan to deploy Odoo progressively, by groups of apps."
msgstr ""
#: ../../getting_started/documentation.rst:369
msgid "The goal of the **Kick-off call** is for our project manager to come to an understanding of your business in order to propose an implementation plan (phasing). Each phase is the deployment of a set of applications that you will fully use in production at the end of the phase."
msgstr ""
#: ../../getting_started/documentation.rst:375
msgid "For every phase, the steps are the following:"
msgstr ""
#: ../../getting_started/documentation.rst:377
msgid "**Onboarding:** Odoo's project manager will review Odoo's business flows with you, according to your business. The goal is to train you, validate the business process and configure according to your specific needs."
msgstr ""
#: ../../getting_started/documentation.rst:382
msgid "**Data:** Created manually or imported from your existing system. You are responsible for exporting the data from your existing system and Odoo's project manager will import them in Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:386
msgid "**Training:** Once your applications are set up, your data imported, and the system is working smoothly, you will train your users. There will be some back and forth with your Odoo project manager to answer questions and process your feedback."
msgstr ""
#: ../../getting_started/documentation.rst:391
msgid "**Production**: Once everyone is trained, your users start using Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:394
msgid "Once you are comfortable using Odoo, we will fine-tune the process and **automate** some tasks and do the remaining customizations (**extra screens and reports**)."
msgstr ""
#: ../../getting_started/documentation.rst:398
msgid "Once all applications are deployed and users are comfortable with Odoo, our project manager will not work on your project anymore (unless you have new needs) and you will use the support service if you have further questions."
msgstr ""
#: ../../getting_started/documentation.rst:404
msgid "Managing your databases"
msgstr ""
#: ../../getting_started/documentation.rst:406
msgid "To access your databases, go to Odoo.com, sign in and click **My Databases** in the drop-down menu at the top right corner."
msgstr ""
#: ../../getting_started/documentation.rst:412
msgid "Odoo gives you the opportunity to test the system before going live or before upgrading to a newer version. Do not mess up your working environment with test data!"
msgstr ""
#: ../../getting_started/documentation.rst:416
msgid "For those purposes, you can create as many free trials as you want (each available for 15 days). Those instances can be instant copies of your working environment. To do so, go to the Odoo.com account in **My Organizations** page and click **Duplicate**."
msgstr ""
#: ../../getting_started/documentation.rst:427
msgid "You can find more information on how to manage your databases :ref:`here <db_management/documentation>`."
msgstr ""
#: ../../getting_started/documentation.rst:431
msgid "Customer Success"
msgstr ""
#: ../../getting_started/documentation.rst:433
msgid "Odoo is passionate about delighting our customers and ensuring that they have all the resources needed to complete their project."
msgstr ""
#: ../../getting_started/documentation.rst:436
msgid "During the implementation phase, your point of contact is the project manager and eventually the support team."
msgstr ""
#: ../../getting_started/documentation.rst:439
msgid "Once you are in production, you will probably have less interaction with your project manager. At that time, we will assign a member of our Client Success Team to you. They are specialized in the long-term relationship with our customers. They will contact you to showcase new versions, improve the way you work with Odoo, assess your new needs, etc..."
msgstr ""
#: ../../getting_started/documentation.rst:446
msgid "Our internal goal is to keep customers for at least 10 years and offer them a solution that grows with their needs!"
msgstr ""
#: ../../getting_started/documentation.rst:449
msgid "Welcome aboard and enjoy your Odoo experience!"
msgstr ""
#: ../../getting_started/documentation.rst:452
msgid ":doc:`../../db_management/documentation`"
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: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -541,7 +541,7 @@ msgid "Product Unit of Measure"
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
msgid "Default Unit of Measure used for all stock operation."
msgid "Default unit of measure used for all stock operations."
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
@ -549,7 +549,7 @@ msgid "Procurement Group"
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
msgid "Moves created through this orderpoint will be put in this procurement group. If none is given, the moves generated by procurement rules will be grouped into one big picking."
msgid "Moves created through this orderpoint will be put in this procurement group. If none is given, the moves generated by stock rules will be grouped into one big picking."
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0

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: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -224,11 +224,7 @@ msgid ":doc:`../configuration/setup`"
msgstr ""
#: ../../project/advanced/so_to_task.rst:114
msgid ":doc:`../../sales/invoicing/services/reinvoice`"
msgstr ""
#: ../../project/advanced/so_to_task.rst:115
msgid ":doc:`../../sales/invoicing/services/support`"
msgid ":doc:`../../sales/invoicing/subscriptions`"
msgstr ""
#: ../../project/application.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: 2018-11-07 15:38+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -705,6 +705,78 @@ msgstr ""
msgid "Select your supplier in the **Vendor** menu, or create it on-the-fly by clicking on **Create and Edit**. In the **Order Date** field, select the date to which you wish to proceed to the actual order."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Receipt"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoming Shipments"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "You can find a vendor by its Name, TIN, Email or Internal Reference."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor Reference"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Reference of the sales order or bid sent by the vendor. It's used to do the matching when you receive the products as this reference is usually written on the delivery order sent by your vendor."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Order Date"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Depicts the date where the Quotation should be validated and converted into a purchase order."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Source Document"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Reference of the document that generated this purchase order request (e.g. a sales order)"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Deliver To"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "This will determine operation type of incoming shipment"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Drop Ship Address"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Put an address if you want to deliver directly from the vendor to the customer. Otherwise, keep empty to deliver to your own company."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Destination Location Type"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Technical field used to display the Drop Ship Address"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoterm"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "International Commercial Terms are a series of predefined commercial terms used in international transactions."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:32
msgid "View *Request for Quotation* in our Online Demonstration"
msgstr ""