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

[IMP] translations: Update source terms

Browse Source
This commit is contained in:
Yannick Tivisse 2016-11-22 13:16:49 +01:00
parent ff4e424702
commit 8b8e6c5916
20 changed files with 2165 additions and 397 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

191
locale/sources/accounting.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-31 16:02+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"
@ -1066,95 +1066,6 @@ msgstr ""
msgid "In the tab Journal Entries, the Default Debit and Credit Account can be configured as well as the currency of the journal"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Select 'Sale' for customer invoices journals. Select 'Purchase' for vendor bills journals. Select 'Cash' or 'Bank' for journals that are used in customer or vendor payments. Select 'General' for miscellaneous operations journals. Select 'Opening/Closing Situation' for entries generated for new fiscal years."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Company related to this journal"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "The journal entries of this journal will be named using this prefix."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Check this box if you don't want to share the same sequence for invoices and refunds made from this journal"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "This field contains the information related to the numbering of the journal entries of this journal."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "This field contains the information related to the numbering of the refund entries of this journal."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "It acts as a default account for debit amount"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "It acts as a default account for credit amount"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "The currency used to enter statement"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Means of payment for collecting money. Odoo modules offer various payments handling facilities, but you can always use the 'Manual' payment method in order to manage payments outside of the software."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Means of payment for sending money. Odoo modules offer various payments handling facilities, but you can always use the 'Manual' payment method in order to manage payments outside of the software."
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 "Used to register a profit when the ending balance of a cash register differs from what the system computes"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Used to register a loss when the ending balance of a cash register differs from what the system computes"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Whether this journal should be displayed on the dashboard or not"
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Technical feature used to know whether check printing was enabled as payment method."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Checks numbering sequence."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
#: ../../accounting/payables/pay/check.rst:0
msgid "Check this option if your pre-printed checks are not numbered."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Sequence number of the next printed check."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Display this bank account on the footer of printed documents like invoices and sales orders."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "Check this box if this journal define a payment method that can be used in a point of sale."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:0
msgid "This field depicts the maximum difference allowed between the ending balance and the theoretical cash when closing a session, for non-POS managers. If this maximum is reached, the user will have an error message at the closing of his session saying that he needs to contact his manager."
msgstr ""
#: ../../accounting/bank/setup/manage_cash_register.rst:25
msgid "Usage"
msgstr ""
@ -1292,70 +1203,6 @@ msgstr ""
msgid "Explanation of the fields:"
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 "Category of asset"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Date of asset"
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "Gross value of asset"
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 "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 "Choose the method to use to compute the dates and number of depreciation lines."
msgstr ""
#: ../../accounting/others/adviser/assets.rst:0
msgid "* Number of Depreciations: Fix the number of depreciation lines 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 "Indicates that the first depreciation entry for this asset have to be done from the purchase date instead of the first January / Start date of fiscal year"
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 "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 ""
@ -2484,26 +2331,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 "Optional tags you may want to assign for custom reporting"
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 "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 "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 ""
@ -5361,22 +5188,6 @@ msgstr ""
msgid "Explanation of the fields of the payment screen:"
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "Technical field used for usability purposes"
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "Technical field used to hide the payment method if the selected journal has only one available which is 'manual'"
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "Technical field used to adapt the interface to the payment type selected."
msgstr ""
#: ../../accounting/payables/pay/check.rst:0
msgid "The selected journal is configured to print check numbers. If your pre-printed check paper already has numbers or if the current numbering is wrong, you can change it in the journal configuration page."
msgstr ""
#: ../../accounting/payables/pay/check.rst:80
msgid "Try paying a supplier bill with a check"
msgstr ""

2
locale/sources/applications.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

4
locale/sources/crm.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"
@ -178,7 +178,7 @@ msgid "Odoo CRM allows you to manually add contacts into your pipeline. It can b
msgstr ""
#: ../../crm/leads/generate/manual.rst:11
msgid "By default, the lead stage is not activated in Odoo CRM. To activate it, go to :menuselection:`Configuration --> Settings`, select the option \"\"use leads if…** as shown below and click on **Apply**."
msgid "By default, the lead stage is not activated in Odoo CRM. To activate it, go to :menuselection:`Sales --> Configuration --> Settings`, select the option \"\"use leads if…** as shown below and click on **Apply**."
msgstr ""
#: ../../crm/leads/generate/manual.rst:18

2
locale/sources/db_management.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

2
locale/sources/discuss.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

879
locale/sources/ecommerce.pot Normal file
View File

@ -0,0 +1,879 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:08+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../ecommerce.rst:5
msgid "eCommerce"
msgstr ""
#: ../../ecommerce/getting_started.rst:3
msgid "Get started"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:3
msgid "How to customize my catalog page"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:6
msgid "Product Catalog"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:8
msgid "All your published items show up in your catalog page (or *Shop* page)."
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:13
msgid "Most options are available in the *Customize* menu: display attributes, website categories, etc."
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:20
msgid "Highlight a product"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:22
msgid "Boost the visibility of your star/promoted products: push them to top, make them bigger, add a ribbon that you can edit (Sale, New, etc.). Open the Shop page, switch to Edit mode and click any item to start customizing the grid."
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:26
msgid "See how to do it: https://www.odoo.com/openerp_website/static/src/video/e-commerce/editing.mp4"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:29
msgid "Quick add to cart"
msgstr ""
#: ../../ecommerce/getting_started/catalog.rst:31
msgid "If your customers buy a lot of items at once, make their process shorter by enabling purchases from the catalog page. To do so, add product description and add to cart button. Turn on the following options in *Customize* menu: Product Description, Add to Cart, List View (to display product description better)."
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:3
msgid "How to build a product page"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:5
msgid "On the website click *New Page* in the top-right corner."
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:7
msgid "Then click *New Product* and follow the blinking tips."
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:12
msgid "Here are the main elements of the Product page:"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:17
msgid "Many elements can be made visible from the *Customize* menu."
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:22
msgid "See how to configure your products from links here below."
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:26
msgid ":doc:`../managing_products/variants`"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:27
msgid ":doc:`../../sales/products_prices/taxes`"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:28
msgid ":doc:`../managing_products/stock`"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:29
msgid ":doc:`../maximizing_revenue/cross_selling`"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:30
msgid ":doc:`../maximizing_revenue/reviews`"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:31
msgid ":doc:`../maximizing_revenue/pricing`"
msgstr ""
#: ../../ecommerce/getting_started/product_page.rst:32
msgid ":doc:`../../website/optimize/seo`"
msgstr ""
#: ../../ecommerce/managing_products.rst:3
msgid "Manage my products"
msgstr ""
#: ../../ecommerce/managing_products/multi_images.rst:3
msgid "How to display several images per product"
msgstr ""
#: ../../ecommerce/managing_products/multi_images.rst:5
msgid "By default your product web page displays the main image of your product only. If you like to show your products under several angles, you can turn the image into a carrousel."
msgstr ""
#: ../../ecommerce/managing_products/multi_images.rst:11
msgid "Check *Several images per product* in :menuselection:`Website Admin --> Configuration --> Settings`."
msgstr ""
#: ../../ecommerce/managing_products/multi_images.rst:13
msgid "Open a product detail form and upload images from *Images* tab. Hit *Create* in Edit mode to get the upload wizard."
msgstr ""
#: ../../ecommerce/managing_products/multi_images.rst:19
msgid "Such extra image are common to all the product variants (if any)."
msgstr ""
#: ../../ecommerce/managing_products/stock.rst:3
msgid "How to show product availability"
msgstr ""
#: ../../ecommerce/managing_products/stock.rst:5
msgid "The availability of your products can be shown on the website to reassure your customers."
msgstr ""
#: ../../ecommerce/managing_products/stock.rst:10
msgid "To display this, open the *Sales* tab in the product detail form and select an option in *Availability*."
msgstr ""
#: ../../ecommerce/managing_products/stock.rst:16
msgid "A custom warning message can be anything related to a stock out, delivery delay, etc."
msgstr ""
#: ../../ecommerce/managing_products/stock.rst:22
msgid "This tool does not require the Inventory app to be installed."
msgstr ""
#: ../../ecommerce/managing_products/stock.rst:25
msgid "If one item is no longer sellable, unpublish it from your website. If it comes to one particular product variant, deactivate the variant in the backend (see :doc:`../maximizing_revenue/pricing`)."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:3
msgid "How to manage product variants"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:5
msgid "Product variants are used to offer variations of the same product to your customers on the products page. For example, the customer chooses a T-shirt and then selects its size and color."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:13
msgid "How to create attributes & variants"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:15
msgid "Turn on *Products can have several attributes, defining variants (Example: size, color,...)* in :menuselection:`Sales --> Settings`."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:18
msgid "Select a product from the Products list, go to the *Variants* tab."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:20
msgid "Add as many attributes as you need from 3 different types: radio buttons, drop-down menu or color buttons. You get several variants as soon as there are 2 values for 1 attribute."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:28
msgid "How to edit variants"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:30
msgid "See all the variants from the product template detail form."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:38
msgid "You can edit following data:"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:40
msgid "Picture (will update in real time on the website),"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:41
msgid "Barcode,"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:42
msgid "Internal Reference (SKU #),"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:43
msgid "Volume,"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:44
msgid "Weight,"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:45
msgid "Active (available in quotes & website)."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:48
msgid "Both the Barcode and the Internal Reference are variant-specific. You need to populate them once the variants generated."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:52
msgid "See and edit all the variants from :menuselection:`Sales --> Sales --> Product Variants` as well. This might be quicker if you manage lots of variants."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:56
msgid "How to set specific prices per variant"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:58
msgid "You can also set a specific public price per variant by clicking *Variant Prices* in the product detail form (action in top-left corner)."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:64
msgid "The Price Extra is added to the product price whenever the corresponding attribute value is selected."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:74
msgid "Pricelist formulas let you set advanced price computation methods for product variants. See :doc:`../maximizing_revenue/pricing`."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:78
msgid "How to disable/archive variants"
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:80
msgid "You can disable/archive specific variants so that they are no longer available in quotes & website (not existing in your stock, deprecated, etc.). Simply uncheck *Active* in their detail form."
msgstr ""
#: ../../ecommerce/managing_products/variants.rst:86
msgid "To retrieve such archived items, hit *Archived* on searching the variants list. You can reactivate them the same way."
msgstr ""
#: ../../ecommerce/maximizing_revenue.rst:3
msgid "Maximize my revenue"
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:3
msgid "How to sell accessories and optional products (cross-selling)"
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:5
msgid "You sell computers. Why not stimulating your customers to buy a top-notch screen or an extra-warranty? That's the goal of cross-selling functionalities:"
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:8
msgid "Accessory products on checkout page,"
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:9
msgid "Optional products on a new *Add to Cart* screen (not installed by default)."
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:12
msgid "Accessory products when checking out"
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:14
msgid "Accessories (e.g. for computers: mouse, keyboard) show up when the customer reviews the cart before paying."
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:20
msgid "Select accessories in the *Sales* tab of the product detail page."
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:26
msgid "There is an algorithm to figure out the best accessories to display in case several items are added to cart. If any item is the accessory of several products added to cart, it is most likely that it will be atop the list of suggested accessories."
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:31
msgid "Optional products when adding to cart"
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:33
msgid "Optional products are directly related to the item added to cart (e.g. for computers: warranty, OS software, extra components). Whenever the main product is added to cart, such a new screen pops up as an extra step."
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:40
msgid "To publish optional products:"
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:42
msgid "Install *eCommerce Optional Products* addon in *Apps* menu. Remove the default filter to search on addons as well, otherwise only main apps show up."
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:48
msgid "Select optional items from the *Sales* tab of the product detail form."
msgstr ""
#: ../../ecommerce/maximizing_revenue/cross_selling.rst:54
msgid "The quantity of optional items added to cart is the same than the main item."
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:3
msgid "How to adapt the prices to my website visitors"
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:5
msgid "This section sheds some light on pricing features of eCommerce app:"
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:7
msgid "force a price by geo-localization,"
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:9
msgid "let the customer choose the currency."
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:11
msgid "As a pre-requisite, check out how to managing produt pricing: :doc:`../../sales/products_prices/prices/pricing`)."
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:15
msgid "Geo-IP to automatically apply the right price"
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:17
msgid "Assign country groups to your pricelists. That way, your visitors not yet logged in will get their own currency when landing on your website."
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:20
msgid "Once logged in, they get the pricelist matching their country."
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:23
msgid "Currency selector"
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:25
msgid "In case you sell in several currencies, you can let your customers choose their own currency. Check *Selectable* to add the pricelist to the website drop-down menu."
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:34
msgid ":doc:`../../sales/products_prices/prices/pricing`"
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:35
msgid ":doc:`../../sales/products_prices/prices/currencies`"
msgstr ""
#: ../../ecommerce/maximizing_revenue/pricing.rst:36
msgid ":doc:`promo_code`"
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:3
msgid "How to create & share promotional codes"
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:5
msgid "Want to boost your sales for Xmas? Share promocodes through your marketing campaigns and apply any kind of discounts."
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:9
#: ../../ecommerce/maximizing_revenue/reviews.rst:13
msgid "Setup"
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:11
msgid "Go to :menuselection:`Sales --> Settings` and choose *Advanced pricing based on formula* for *Sale Price*."
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:14
msgid "Go to :menuselection:`Website Admin --> Catalog --> Pricelists` and create a new pricelist with the discount rule (see :doc:`pricing`). Then enter a code."
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:21
msgid "Make the promocode field available on your *Shopping Cart* page (option in *Customize* menu). Add a product to cart to reach it."
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:27
msgid "Once turned on you see a new section on the right side. On clicking *Apply* prices get automatically updated in the cart."
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:33
msgid "The promocode used by the customer is stored in the system so you can analyze the performance of your marketing campaigns."
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:39
msgid "Show sales per pricelists..."
msgstr ""
#: ../../ecommerce/maximizing_revenue/promo_code.rst:43
msgid ":doc:`pricing`"
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:3
msgid "How to enable comments & rating"
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:5
msgid "Publishing and monitoring customer experience will help you gain the trust of new customers and better engage with your community. In 2 clicks, allow your customer to share their feedback!"
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:15
msgid "Activate comments & rating from the *Customize* menu of the product web page."
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:21
msgid "Visitors must log in to share their comments. Make sure they are able to do so (see Portal documentation)."
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:25
msgid "Review the posts in real time"
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:27
msgid "Whenever a post is published, the product manager and all the product followers get notified in their Inbox (*Discuss* menu)."
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:34
msgid "By default the user who created the product is automatically set as follower."
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:36
msgid "Click the product name to open the detail form and review the comment (in the product discussion thread)."
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:43
msgid "Moderate & unpublish"
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:45
msgid "You can easily moderate by using the chatter, either in the product detail form or on the web page."
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:48
msgid "To unpublish the post, open the product web page and click the *Published* button to turn it red (*Unpublished*)."
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:56
msgid "..tip::"
msgstr ""
#: ../../ecommerce/maximizing_revenue/reviews.rst:55
msgid "You can access the web page from the detail form by clicking the *Published* smart button (and vice versa)."
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:3
msgid "How to sell pricier product alternatives (upselling)"
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:5
msgid "In order to maximize your revenue, suggesting pricier alternative products is strongly advised for basic items. That way, your customer will spend more time browsing your catalog."
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:12
msgid "To do so:"
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:14
msgid "Select such *Alternative Products* in the *Sales* tab of the product detail form. 3 alternatives are fine! Don't publish too many otherwise your customers will be confused."
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:20
msgid "Turn on *Alternative Products* from the *Customize* menu of the product web page."
msgstr ""
#: ../../ecommerce/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:3
msgid "Introduction to Odoo eCommerce"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:10
msgid "The documentation will help you go live with your eCommerce website in no time. The topics follow the buying process:"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:13
msgid "Product Page"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:14
msgid "Shop Page"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:15
msgid "Pricing"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:16
msgid "Taxes"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:17
msgid "Checkout process"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:18
msgid "Upselling & cross-selling"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:19
msgid "Payment"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:20
msgid "Shipping & Tracking"
msgstr ""
#: ../../ecommerce/overview/introduction.rst:24
msgid ":doc:`../../website/publish/domain_name`"
msgstr ""
#: ../../ecommerce/publish.rst:3
msgid "Launch my website"
msgstr ""
#: ../../ecommerce/shopper_experience.rst:3
msgid "Improve shopper experience"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:3
msgid "How to set up payment methods"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:5
msgid "To collect payments, you can either request your customers to process it manually (e.g. wire transfer) or redirect them to payment acquirers. The payment process described hereunder is common to both eCommerce and online quotations."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:10
msgid "Payment methods"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:13
msgid "Wire transfer"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:15
msgid "Wire Transfer is the default payment method available. The aim is providing your customers with your bank details so that they can pay via their bank. This is very easy to start with but slow and inefficient process-wise. Opt for online acquirers as soon as you can!"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:21
msgid "For B2B users: you can create new manually-processed payment methods (check, purchase order, etc.) by renaming 'Wire Transfer' or duplicating it."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:25
msgid "Online payment acquirers"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:27
msgid "Redirect your customers to payment acquirer platforms to collect money effortless. Odoo supports more and more platforms over time: Paypal, Ingenico, Authorize.net, etc. Once the payment accepted, orders are confirmed in Odoo so that the delivery & invoicing processes are triggered automatically."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:33
msgid "Custom (advanced)"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:35
msgid "Can be used to request payments to any payment acquirer not listed in Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:38
msgid "Edit a payment method"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:40
msgid "To make payment methods intuitive for your customers feel free to customize them by editing:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:42
msgid "the name,"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:44
msgid "the picture,"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:46
msgid "the notification messages (thank you & next step, error, cancellation)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:48
msgid "Go to :menuselection:`Website Admin --> Configuration --> Payment Acquirers` to do so."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:51
msgid "Generic setup"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:53
msgid "Review the elements here above."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:55
msgid "Enter your credentials (online acquirers only)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:57
msgid "Choose your order confirmation preference (see below)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:59
msgid "Publish the payment method."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:61
msgid "Test the payment flow in *Test* mode (default mode)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:63
msgid "Switch to *Production* mode."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:65
msgid "Se your default payment acquirer in :menuselection:`Accounting --> Configuration --> Settings`. It will be auto-selected for your customers when they enter the payment screen."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:69
msgid "Rely on the documentation related to your payment acquirer to go through step 2, 5 and 6. Some acquirers provides you with specific credentials for test and production modes (Paypal). Others let you switch mode in their setup interface (Authorize.net)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:74
msgid "With Ingenico and Authorize.net, you can let your customers save and reuse a payment card to accelerate the process on next checkouts. See *Store Card Data* in Configuration tab."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:78
msgid "Payment flow"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:80
msgid "When choosing the payment method, the customer is taken to the payment acquirer interface to process the payment."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:83
msgid "Once done he is taken back to Odoo's confirmation page. The transaction status shows up:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:85
msgid "*Pending*: the order will be confirmed as soon as you authorize the transaction in the acquirer interface."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:87
msgid "*Confirmed*: the payment has been authorized automatically."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:89
msgid "A confirmation email is sent to the customer with a copy of the order in pdf. It shows the payment status."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:91
msgid "Launch the delivery and invoicing from:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:93
msgid "eCommerce: :menuselection:`Website Admin --> Orders --> (Unpaid) Orders`,"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:95
msgid "online quotations: :menuselection:`Sales --> Sales --> Quotations/Sales Orders`."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:97
msgid "For internal tracking purposes, a link to the transaction status is provided in the sales order."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:100
msgid "If the customer cancels the payment while on the payment acquirer form, it is taken back to the store page (or online quotation) in order to reprocess the order. The payment is marked as *Cancelled* in Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:105
msgid "You can edit the confirmation email template from :menuselection:`Website Admin --> Configuration --> Settings`."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:109
msgid "Order confirmation preferences"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:111
msgid "There are 4 different behaviors available for any payment acquirer."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:114
msgid "No automatic confirmation"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:116
msgid "This is the default mode for *Wire Transfer*. It means Odoo does not confirm orders but keep them in an intermediary stage (*Quotation Sent* = *Unpaid Order*). Once you get the payment, you are expected to confirm the order manually to pursue the process (delivery, invoicing)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:121
msgid "Authorize the amount and confirm the SO on acquirer confirmation (capture manually)"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:123
msgid "Odoo confirms the order as soon as the payment success notification comes in. To get the money however, you need to capture it from your payment transaction. In lots of countries you are indeed requested to deliver your goods before capturing the amount."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:128
msgid "Authorize & capture the amount and confirm the SO on acquirer confirmation"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:130
msgid "This is the default mode for payment acquirers. The amount is captured automatically."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:133
msgid "For B2B: if you use a manual payment method like *Wire Transfer* and don't expect any upfront payment to launch the delivery, switch to this mode as well."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:137
msgid "Authorize & capture the amount, confirm the SO and auto-validate the invoice on acquirer confirmation"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:139
msgid "If you invoice upfront and not at the delivery, switch to this last mode to automate everything. You are requested to select a Payment Journal to record such payments (see :doc:`../../accounting/receivables/customer_payments/credit_cards`)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:144
msgid "Custom payment acquirers (advanced)"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:146
msgid "Odoo can submit payment requests and redirect to any payment acquirer. In such a case, you need to confirm the sale manually in Odoo once you get paid because Odoo cannot read any payment status sent by the acquirer."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:150
msgid "To configure this:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:152
msgid "switch to developer mode,"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:154
msgid "edit the *Custom* payment method,"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:156
msgid "set up the payment form (S2S Form Template) as instructed by your payment acquirer. You can start from *default_acquirer_button* that you can duplicate."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:160
msgid "Recurring payments & Installment plans"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:162
msgid "The Ingenico integration allows you to process and manage recurring payments from Odoo Subscriptions app out-of-the-box (more information coming soon)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:165
msgid "With some customization, Odoo can also trigger installment plans if this is permitted by your payment acquirer’s API:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:168
msgid "e.g. Paypal Installment Plans (see https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/installment_buttons)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:170
msgid "Such a service is made on-demand by our technical experts based on your own requirements. Ask our business advisors at info@odoo.com."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:175
msgid ":doc:`paypal`"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:3
msgid "How to collect payments with Paypal"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:5
msgid "Paypal is the easiest payment method to configure. It is also the only one without any subscription free."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:9
msgid "Setup your Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:11
msgid "1. Create a business account at Paypal.com (see: https://www.paypal.com/in/cgi-bin/webscr?cmd=xpt/Marketing/general/how-to-set-up-a-paypal-account-outside) or upgrade your account to Business account (merchant) if you have a basic account."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:15
msgid "2. Log in to your account at Paypal.com and go to :menuselection:`My Account --> Profile --> My Selling Tools`. There click *PayPal button language encoding* under *More Selling Tools* section. Then, click *More Options* and replace the two default encoding formats by *UTF-8*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:20
msgid "Open Paypal setup form in Odoo and enter your *Email ID*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:22
msgid "4. The Paypal Merchant ID is not mandatory (extra verification level). It is provided in Paypal under :menuselection:`My Account --> Overview`."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:25
msgid "5. Configure the IPN feedback (Paypal contacting your Odoo instance without needing the redirection). The setting can be found in :menuselection:`Profile --> My Selling Tools --> Instant payment notification`. Activate it and set it to <odoo_instance_url>/payment/paypal/ipn."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:30
msgid "6. To test the workflow, you can create sandbox accounts by logging in at https://developer.paypal.com/webapps/developer/applications/myapps with the same Paypal credentials. Two default sandbox accounts are automatically generated when you register to Paypal: one is a buyer, the other is a shopper."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:35
msgid "7. Log in with your buyer sandbox account to https://www.sandbox.paypal.com (same password than real account) and apply the same format change."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:39
msgid "To automatically redirect your customers when the payment is completed, go to your Website Preferences and turn *Auto Return* on. Set *Return URL* to <odoo_instance_url>/shop/confirmation. Verify that your *Notify URL* uses the correct protocol (HTTP/HTTPS)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:44
msgid "If you want your customers to pay without creating a Paypal account, *Paypal Account Optional* needs to be turned on."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:48
msgid "Transaction fees"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:50
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."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:53
msgid "To activate this, go to the *Configuration* tab and check *Add Extra Fees*. Default fees are the ones charged by Paypal."
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their portal"
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:5
msgid "It has never been so easy for your customers to access their documents through a portal. Forget endless signup forms, Odoo makes it as easy as ABC. With eCommerce and Online Quotation apps, your customers are requested to create a portal account (name, email, password only) from the very first order confirmation or online quotation email they get from you."
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:12
msgid "Sign up"
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:14
msgid "When clicking the link in the email or when clicking *Sign up* in the checkout process, your customer is directed to the *Sign up* page."
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:21
msgid "Customer account"
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:23
msgid "Once logged in the customer will access his account by clicking *My Account* in the login dropdown menu."
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:29
msgid "From the portal menu all the customer history can be reviewed. The main address (billing) can also be modified."
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:36
msgid "If a portal user is a contact of a company (*Company* field set in customer detail form), this last will see all the documents of the company and all its other contacts through the portal."
msgstr ""
#: ../../ecommerce/taxes.rst:3
msgid "Collect taxes"
msgstr ""

256
locale/sources/expense.pot Normal file
View File

@ -0,0 +1,256 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:08+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../expense.rst:5
#: ../../expense/expense.rst:5
msgid "Expenses"
msgstr ""
#: ../../expense/expense.rst:8
msgid "How to set expense types"
msgstr ""
#: ../../expense/expense.rst:9
msgid "The first step to track expenses is to configure the expense types (managed as products in Odoo) that your company allows, from the *Configuration* menu. When a specific expense is reimbursed at a fixed price, set a cost on the product. Otherwise keep the cost at 0.0 and employees will report the real cost per expense."
msgstr ""
#: ../../expense/expense.rst:17
msgid "Here are some examples to configure:"
msgstr ""
#: ../../expense/expense.rst:19
msgid "Restaurant:"
msgstr ""
#: ../../expense/expense.rst:21
#: ../../expense/expense.rst:27
msgid "Cost: 0.00 (the cost of the ticket will be recorded on every expense)"
msgstr ""
#: ../../expense/expense.rst:22
msgid "Travel with Personal Car:"
msgstr ""
#: ../../expense/expense.rst:24
msgid "Cost: 0.30 (the price per mile reimbursed by the company is fixed)"
msgstr ""
#: ../../expense/expense.rst:25
msgid "Hotel:"
msgstr ""
#: ../../expense/expense.rst:29
msgid "Others:"
msgstr ""
#: ../../expense/expense.rst:31
msgid "Cost: 0.0"
msgstr ""
#: ../../expense/expense.rst:33
msgid "Don’t forget to set an expense tax on each expense type (and an account if you use Odoo Accounting). It’s usually a good practice to use a tax that is configured with *Tax Included in Price* (see: :doc:`../accounting/others/taxes/tax_included`). That way, employees report expenses with prices including taxes, which is usually the expected behaviour."
msgstr ""
#: ../../expense/expense.rst:41
msgid "The *Sales* app allows you to specify unit of measures for your expense types (units, miles, nights, etc.). Go to :menuselection:`Sales --> Configuration --> Settings` and check *Some products may be sold/purchased in different units of measure (advanced)*."
msgstr ""
#: ../../expense/expense.rst:48
msgid "How to record expenses"
msgstr ""
#: ../../expense/expense.rst:51
msgid "Manually"
msgstr ""
#: ../../expense/expense.rst:53
msgid "As an employee (Employee in user access rights), you can record expenses from :menuselection:`My Expenses --> Expenses to Submit`."
msgstr ""
#: ../../expense/expense.rst:59
msgid "Select the related product and enter either the total amount you paid (with Quantity = 1) or the unit price if Quantity is countable (e.g. number of hotel nights)."
msgstr ""
#: ../../expense/expense.rst:62
msgid "Enter the expense date."
msgstr ""
#: ../../expense/expense.rst:63
msgid "Choose if you paid the bill on your own (and expect to be reimbursed) or if the company paid directly (e.g. if you used a company's credit card)."
msgstr ""
#: ../../expense/expense.rst:65
msgid "Set the bill reference, add some notes if requested and attach a photo/scan of the receipt from the discussion thread. That will help the manager and the accountant validate it."
msgstr ""
#: ../../expense/expense.rst:73
msgid "In one click from emails"
msgstr ""
#: ../../expense/expense.rst:74
msgid "Let your employees record their expenses from a simple email. Make a snapshot of the receipt and send it by email, or simply forward a bill!"
msgstr ""
#: ../../expense/expense.rst:77
msgid "The only thing to do is setting up an email alias in :menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* @mycompany.odoo.com). For security purposes, only authenticated employee emails (cfr. *Work Email* in employee detail form) are accepted."
msgstr ""
#: ../../expense/expense.rst:83
msgid "The expense product is set automatically if the mail subject contains the product's internal reference between brackets (e.g. [Food]). Type the expense amount in the mail subject to set it on the expense too."
msgstr ""
#: ../../expense/expense.rst:88
msgid "How to submit expenses to managers"
msgstr ""
#: ../../expense/expense.rst:90
msgid "When you are ready to submit your expenses to your manager (e.g. at the end of a business trip, or once a month), go to the menu :menuselection:`My Expenses --> Expenses to Submit`. Select all expenses from the list view and click on :menuselection:`Action > Submit to Manager`. Save the newly created expense report (i.e. set of expenses), and wait for your manager to approve it."
msgstr ""
#: ../../expense/expense.rst:100
msgid "You can also submit expenses one by one from the *Submit to Manager* button on the form view of an expense."
msgstr ""
#: ../../expense/expense.rst:103
msgid "All your submitted expense reports can be found in :menuselection:`Expenses --> My Expenses --> Expense Reports`."
msgstr ""
#: ../../expense/expense.rst:108
msgid "How to approve expenses"
msgstr ""
#: ../../expense/expense.rst:110
msgid "HR and team managers get an overview of all expense reports to validate from the top menu :menuselection:`To Approve --> Expense Reports to Approve`. Such users must have at least *Officers* access rights for *Expenses*."
msgstr ""
#: ../../expense/expense.rst:117
msgid "They can review expense reports, approve or reject them, as well as providing feedback thanks to the integrated communication tool."
msgstr ""
#: ../../expense/expense.rst:123
msgid "As a team manager you can easily find the expense reports of your team members. You need to be set as manager in the detail form of those employees."
msgstr ""
#: ../../expense/expense.rst:131
msgid "How to post expenses in accounting"
msgstr ""
#: ../../expense/expense.rst:133
msgid "Once expense reports approved by managers, the accounting department goes to :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to check accounts, products and taxes. They can click *Post Journal Entries* to post related journal entries into your books. To do so, the user must have following access rights:"
msgstr ""
#: ../../expense/expense.rst:139
msgid "Accounting: Accountant or Adviser"
msgstr ""
#: ../../expense/expense.rst:140
msgid "Expenses: Manager"
msgstr ""
#: ../../expense/expense.rst:143
msgid "To post an expense, a *Home Address* must be set on the employee. If you get a related blocking message when posting, click the employee, go to *Personal Information* tab and select/create the contact of your employee in the address book. A contact has been automatically created if this person is using Odoo."
msgstr ""
#: ../../expense/expense.rst:150
msgid "How to reimburse employees"
msgstr ""
#: ../../expense/expense.rst:152
msgid "You can now see all the expense reports to reimburse in :menuselection:`Expenses --> Accountant --> Expense Reports To Pay`. To record the payment or pay by check, click *Register a Payment*."
msgstr ""
#: ../../expense/expense.rst:156
msgid "See how you can easily manage the payment process in Odoo:"
msgstr ""
#: ../../expense/expense.rst:158
msgid ":doc:`../accounting/payables/pay/check`"
msgstr ""
#: ../../expense/expense.rst:159
msgid ":doc:`../accounting/payables/pay/sepa`"
msgstr ""
#: ../../expense/expense.rst:163
msgid "How to reinvoice expenses to your customers"
msgstr ""
#: ../../expense/expense.rst:165
msgid "If you track expenses on customer projects, you can charge them back to your customers automatically."
msgstr ""
#: ../../expense/expense.rst:169
msgid "Setup"
msgstr ""
#: ../../expense/expense.rst:171
msgid "Install *Sales* app if not yet done."
msgstr ""
#: ../../expense/expense.rst:172
msgid "Go to :menuselection:`Accounting --> Configuration --> Settings` and install Analytic Accounting* (in Recommended Features)."
msgstr ""
#: ../../expense/expense.rst:175
msgid "Go to :menuselection:`Sales --> Sales --> Products` and set the invoicing method on all your Expense types:"
msgstr ""
#: ../../expense/expense.rst:178
msgid "At cost: will invoice expenses at their real cost."
msgstr ""
#: ../../expense/expense.rst:179
msgid "At sales price: will invoice based on a fixed sales price defined in the product form."
msgstr ""
#: ../../expense/expense.rst:186
msgid "Create an order"
msgstr ""
#: ../../expense/expense.rst:187
msgid "As a salesman, create and confirm a Sales Order for the services delivered to your customer. Don’t put any expense in the order. They will be added automatically once posted by the accountant."
msgstr ""
#: ../../expense/expense.rst:191
msgid "Link this order to an analytic account dedicated to the customer project. You can create it on the fly."
msgstr ""
#: ../../expense/expense.rst:198
msgid "If you track *Timesheets* on customer projects, Odoo can create an analytic account automatically once the order confirmed. It's useful if your employees must record timesheets on customer-specific projects. To do so, open your order product (service item) and make sure *Track Service* is set on *Timesheets on project*."
msgstr ""
#: ../../expense/expense.rst:205
msgid "Submit, validate and post expenses"
msgstr ""
#: ../../expense/expense.rst:206
msgid "As a manager, make sure the analytic account is set on every expense line on approving expenses reports. Click the line to add one if missing. Employees are already able to set one when submitting."
msgstr ""
#: ../../expense/expense.rst:213
msgid "As an accountant, post journal entries."
msgstr ""
#: ../../expense/expense.rst:216
msgid "Invoice expenses"
msgstr ""
#: ../../expense/expense.rst:217
msgid "Now you can invoice the order.It shows up in :menuselection:`Sales --> Invoicing --> Sales to Invoice`. The expenses have been added automatically in the order lines. Such items show up in blue (i.e. to invoice)."
msgstr ""

2
locale/sources/expenses.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

430
locale/sources/general.pot Normal file
View File

@ -0,0 +1,430 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:08+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../general.rst:5
msgid "General"
msgstr ""
#: ../../general/base_import.rst:3
msgid "BASE IMPORT"
msgstr ""
#: ../../general/base_import/import_faq.rst:3
msgid "Import CSV file to Odoo"
msgstr ""
#: ../../general/base_import/import_faq.rst:8
msgid "Frequently Asked Questions"
msgstr ""
#: ../../general/base_import/import_faq.rst:12
msgid "Need to import data from an other application?"
msgstr ""
#: ../../general/base_import/import_faq.rst:14
msgid "In order to re-create relationships between different records, you should use the unique identifier from the original application and map it to the **ID** (External ID) column in Odoo. When you import an other record that links to the first one, use **XXX/ID** (XXX/External ID) to the original unique identifier."
msgstr ""
#: ../../general/base_import/import_faq.rst:16
msgid "The **ID** (External ID) will also be used to update the original import if you need to re-import modified data later, it's thus good practice to specify it whenever possible."
msgstr ""
#: ../../general/base_import/import_faq.rst:21
msgid "I cannot find the field I want to map my column to?"
msgstr ""
#: ../../general/base_import/import_faq.rst:23
msgid "Odoo try to find with some heuristic, based on the first ten lines of the files, the type of field for each columns inside your file. For example if you have a column only containing numbers, only the fields that are of type integer will be displayed for you to choose from. While this behaviour might be good and easy for most cases scenarios, it is also possible that it goes wrong sometimes or that you want to map your column to a field that is not proposed by default."
msgstr ""
#: ../../general/base_import/import_faq.rst:25
msgid "If that happens, you just have to check the **Show all fields for completion (advanced)** option, you will then be able to choose from the complete list of fields for each columns."
msgstr ""
#: ../../general/base_import/import_faq.rst:30
msgid "Where can I change the date import format?"
msgstr ""
#: ../../general/base_import/import_faq.rst:32
msgid "Odoo can automatically detect if a column is a date and it will try to guess the date format from a set of most used date format. While this process can work for a lot of simple date format, some exotic date format will not be recognize and it is also possible to have some confusion (day and month inverted as example) as it is difficult to guess correctly which part is the day and which one is the month in a date like '01-03-2016'."
msgstr ""
#: ../../general/base_import/import_faq.rst:34
msgid "To view which date format Odoo has found from your file you can check the **Date Format** that is shown when clicking on **Options** under the file selector. If this format is incorrect you can change it to your liking using the *ISO 8601* to define the format."
msgstr ""
#: ../../general/base_import/import_faq.rst:37
msgid "If you are importing an excel (.xls, .xlsx) file, you can use date cells to store dates as the display of dates in excel is different from the way it is stored. That way you will be sure that the date format is correct in Odoo whatever your locale date format is."
msgstr ""
#: ../../general/base_import/import_faq.rst:42
msgid "Can I import numbers with currency sign (e.g.: $32.00)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:44
msgid "Yes, we fully support numbers with parenthesis to represent negative sign as well as numbers with currency sign attached to them. Odoo also automatically detect which thousand/decimal separator you use (you can change those under **options**). If you use a currency symbol that is not known to Odoo, it might not be recognized as a number though and it will crash."
msgstr ""
#: ../../general/base_import/import_faq.rst:46
msgid "Examples of supported numbers (using thirty-two thousands as an example):"
msgstr ""
#: ../../general/base_import/import_faq.rst:48
msgid "32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:49
msgid "32000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:50
msgid "32,000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:51
msgid "-32000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:52
msgid "(32000.00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:53
msgid "$ 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:54
msgid "(32000.00 €)"
msgstr ""
#: ../../general/base_import/import_faq.rst:56
msgid "Example that will not work:"
msgstr ""
#: ../../general/base_import/import_faq.rst:58
msgid "ABC 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:59
msgid "$ (32.000,00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:64
msgid "What can I do when the Import preview table isn't displayed correctly?"
msgstr ""
#: ../../general/base_import/import_faq.rst:66
msgid "By default the Import preview is set on commas as field separators and quotation marks as text delimiters. If your csv file does not have these settings, you can modify the File Format Options (displayed under the Browse CSV file bar after you select your file)."
msgstr ""
#: ../../general/base_import/import_faq.rst:68
msgid "Note that if your CSV file has a tabulation as separator, Odoo will not detect the separations. You will need to change the file format options in your spreadsheet application. See the following question."
msgstr ""
#: ../../general/base_import/import_faq.rst:73
msgid "How can I change the CSV file format options when saving in my spreadsheet application?"
msgstr ""
#: ../../general/base_import/import_faq.rst:75
msgid "If you edit and save CSV files in speadsheet applications, your computer's regional settings will be applied for the separator and delimiter. We suggest you use OpenOffice or LibreOffice Calc as they will allow you to modify all three options (in 'Save As' dialog box > Check the box 'Edit filter settings' > Save)."
msgstr ""
#: ../../general/base_import/import_faq.rst:77
msgid "Microsoft Excel will allow you to modify only the encoding when saving (in 'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)."
msgstr ""
#: ../../general/base_import/import_faq.rst:82
msgid "What's the difference between Database ID and External ID?"
msgstr ""
#: ../../general/base_import/import_faq.rst:84
msgid "Some fields define a relationship with another object. For example, the country of a contact is a link to a record of the 'Country' object. When you want to import such fields, Odoo will have to recreate links between the different records. To help you import such fields, Odoo provides 3 mechanisms. You must use one and only one mechanism per field you want to import."
msgstr ""
#: ../../general/base_import/import_faq.rst:86
msgid "For example, to reference the country of a contact, Odoo proposes you 3 different fields to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:88
msgid "Country: the name or code of the country"
msgstr ""
#: ../../general/base_import/import_faq.rst:89
msgid "Country/Database ID: the unique Odoo ID for a record, defined by the ID postgresql column"
msgstr ""
#: ../../general/base_import/import_faq.rst:90
msgid "Country/External ID: the ID of this record referenced in another application (or the .XML file that imported it)"
msgstr ""
#: ../../general/base_import/import_faq.rst:92
msgid "For the country Belgium, you can use one of these 3 ways to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:94
msgid "Country: Belgium"
msgstr ""
#: ../../general/base_import/import_faq.rst:95
msgid "Country/Database ID: 21"
msgstr ""
#: ../../general/base_import/import_faq.rst:96
msgid "Country/External ID: base.be"
msgstr ""
#: ../../general/base_import/import_faq.rst:98
msgid "According to your need, you should use one of these 3 ways to reference records in relations. Here is when you should use one or the other, according to your need:"
msgstr ""
#: ../../general/base_import/import_faq.rst:100
msgid "Use Country: This is the easiest way when your data come from CSV files that have been created manually."
msgstr ""
#: ../../general/base_import/import_faq.rst:101
msgid "Use Country/Database ID: You should rarely use this notation. It's mostly used by developers as it's main advantage is to never have conflicts (you may have several records with the same name, but they always have a unique Database ID)"
msgstr ""
#: ../../general/base_import/import_faq.rst:102
msgid "Use Country/External ID: Use External ID when you import data from a third party application."
msgstr ""
#: ../../general/base_import/import_faq.rst:104
msgid "When you use External IDs, you can import CSV files with the \"External ID\" column to define the External ID of each record you import. Then, you will be able to make a reference to that record with columns like \"Field/External ID\". The following two CSV files give you an example for Products and their Categories."
msgstr ""
#: ../../general/base_import/import_faq.rst:106
msgid "`CSV file for categories <../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:108
msgid "`CSV file for Products <../../_static/example_files/External_id_3rd_party_application_products.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:112
msgid "What can I do if I have multiple matches for a field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:114
msgid "If for example you have two product categories with the child name \"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other Products/Sellable\"), your validation is halted but you may still import your data. However, we recommend you do not import the data because they will all be linked to the first 'Sellable' category found in the Product Category list (\"Misc. Products/Sellable\"). We recommend you modify one of the duplicates' values or your product category hierarchy."
msgstr ""
#: ../../general/base_import/import_faq.rst:116
msgid "However if you do not wish to change your configuration of product categories, we recommend you use make use of the external ID for this field 'Category'."
msgstr ""
#: ../../general/base_import/import_faq.rst:121
msgid "How can I import a many2many relationship field (e.g. a customer that has multiple tags)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:123
msgid "The tags should be separated by a comma without any spacing. For example, if you want your customer to be linked to both tags 'Manufacturer' and 'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column of your CSV file."
msgstr ""
#: ../../general/base_import/import_faq.rst:125
msgid "`CSV file for Manufacturer, Retailer <../../_static/example_files/m2m_customers_tags.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:130
msgid "How can I import a one2many relationship (e.g. several Order Lines of a Sales Order)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:132
msgid "If you want to import sales order having several order lines; for each order line, you need to reserve a specific row in the CSV file. The first order line will be imported on the same row as the information relative to order. Any additional lines will need an addtional row that does not have any information in the fields relative to the order. As an example, here is purchase.order_functional_error_line_cant_adpat.CSV file of some quotations you can import, based on demo data."
msgstr ""
#: ../../general/base_import/import_faq.rst:135
msgid "`File for some Quotations <../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:137
msgid "The following CSV file shows how to import purchase orders with their respective purchase order lines:"
msgstr ""
#: ../../general/base_import/import_faq.rst:139
msgid "`Purchase orders with their respective purchase order lines <../../_static/example_files/o2m_purchase_order_lines.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:141
msgid "The following CSV file shows how to import customers and their respective contacts:"
msgstr ""
#: ../../general/base_import/import_faq.rst:143
msgid "`Customers and their respective contacts <../../_static/example_files/o2m_customers_contacts.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:148
msgid "Can I import several times the same record?"
msgstr ""
#: ../../general/base_import/import_faq.rst:150
msgid "If you import a file that contains one of the column \"External ID\" or \"Database ID\", records that have already been imported will be modified instead of being created. This is very usefull as it allows you to import several times the same CSV file while having made some changes in between two imports. Odoo will take care of creating or modifying each record depending if it's new or not."
msgstr ""
#: ../../general/base_import/import_faq.rst:152
msgid "This feature allows you to use the Import/Export tool of Odoo to modify a batch of records in your favorite spreadsheet application."
msgstr ""
#: ../../general/base_import/import_faq.rst:157
msgid "What happens if I do not provide a value for a specific field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:159
msgid "If you do not set all fields in your CSV file, Odoo will assign the default value for every non defined fields. But if you set fields with empty values in your CSV file, Odoo will set the EMPTY value in the field, instead of assigning the default value."
msgstr ""
#: ../../general/base_import/import_faq.rst:164
msgid "How to export/import different tables from an SQL application to Odoo?"
msgstr ""
#: ../../general/base_import/import_faq.rst:166
msgid "If you need to import data from different tables, you will have to recreate relations between records belonging to different tables. (e.g. if you import companies and persons, you will have to recreate the link between each person and the company they work for)."
msgstr ""
#: ../../general/base_import/import_faq.rst:168
msgid "To manage relations between tables, you can use the \"External ID\" facilities of Odoo. The \"External ID\" of a record is the unique identifier of this record in another application. This \"External ID\" must be unique accoss all the records of all objects, so it's a good practice to prefix this \"External ID\" with the name of the application or table. (like 'company_1', 'person_1' instead of '1')"
msgstr ""
#: ../../general/base_import/import_faq.rst:170
msgid "As an example, suppose you have a SQL database with two tables you want to import: companies and persons. Each person belong to one company, so you will have to recreate the link between a person and the company he work for. (If you want to test this example, here is a <a href=\"/base_import/static/csv/database_import_test.sql\">dump of such a PostgreSQL database</a>)"
msgstr ""
#: ../../general/base_import/import_faq.rst:172
msgid "We will first export all companies and their \"External ID\". In PSQL, write the following command:"
msgstr ""
#: ../../general/base_import/import_faq.rst:178
msgid "This SQL command will create the following CSV file::"
msgstr ""
#: ../../general/base_import/import_faq.rst:185
msgid "To create the CSV file for persons, linked to companies, we will use the following SQL command in PSQL:"
msgstr ""
#: ../../general/base_import/import_faq.rst:191
msgid "It will produce the following CSV file::"
msgstr ""
#: ../../general/base_import/import_faq.rst:199
msgid "As you can see in this file, Fabien and Laurence are working for the Bigees company (company_1) and Eric is working for the Organi company. The relation between persons and companies is done using the External ID of the companies. We had to prefix the \"External ID\" by the name of the table to avoid a conflict of ID between persons and companies (person_1 and company_1 who shared the same ID 1 in the orignial database)."
msgstr ""
#: ../../general/base_import/import_faq.rst:201
msgid "The two files produced are ready to be imported in Odoo without any modifications. After having imported these two CSV files, you will have 4 contacts and 3 companies. (the firsts two contacts are linked to the first company). You must first import the companies and then the persons."
msgstr ""
#: ../../general/odoo_basics.rst:3
msgid "BASICS"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:3
msgid "How to add an user"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:5
msgid "Odoo provides you with the option to add additional users at any given point."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:9
msgid "Add individual users"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:11
msgid "From the Settings module, go to the submenu :menuselection:`Users --> Users` and click on **CREATE.** First add the name of your new user and the professional email address - the one he will use to log into Odoo instance - and a picture."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:19
msgid "Under Access Rights, you can choose which applications your user can access and use. Different levels of rights are available depending on the app."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:23
msgid "When you’re done editing the page and have clicked on **SAVE**, an invitation email will automatically be sent to the user. The user must click on it to accept the invitation to your instance and create a log-in."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:32
msgid "Remember that each additional user will increase your subscription fees. Refer to our `*Pricing page* <https://www.odoo.com/pricing>`__ for more information."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:39
msgid "You can also add a new user on the fly from your dashboard. From the above screenshot, enter the email address of the user you would like to add and click on **INVITE**. The user will receive an email invite containing a link to set his password. You will then be able to define his accesses rights under the :menuselection:`Settings --> Users menu`."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:45
msgid "`Deactivating Users <../../db_management/documentation.html#deactivating-users>`_"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:46
msgid ":doc:`../../crm/salesteam/setup/create_team`"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:3
msgid "Manage Odoo in your own language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:5
msgid "Odoo provides you with the option to manage Odoo in different languages, and each user can use Odoo in his own language ."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:9
msgid "Load your desired language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:11
msgid "The first thing to do is to load your desired language on your Odoo instance."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:14
msgid "From the general dashboard click on the **Settings** app; on the top left of the page select :menuselection:`Translations --> Load a Translation`, select a language to install and click on **LOAD.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:23
msgid "If you check the \"Websites to translate\" checkbox you will have the option to change the navigation language on your website."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:27
msgid "Change your language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:29
msgid "You can change the language to the installed language by going to the drop-down menu at the top right side of the screen, choose **Preferences**."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:36
msgid "Then change the Language setting to your installed language and click **SAVE.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:42
msgid "Open a new menu to view the changes."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:45
msgid "Change another user's language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:47
msgid "Odoo also gives you the possibility for each user to choose his preferred language."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:50
msgid "To change the language for a different user, choose :menuselection:`Users --> Users` from the Settings app. Here you have a list of all users and you can choose the user who you'd like to change the language for. Select the user and click on **Edit** in the top left corner. Under Preferences you can change the Language to any previously installed language and click **SAVE.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:61
msgid ":doc:`../../website/publish/translate`"
msgstr ""

34
locale/sources/getting_started.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-09-07 10:10+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"
@ -354,7 +354,7 @@ msgid "**Data:** created manually or imported from your existing system. You are
msgstr ""
#: ../../getting_started/documentation.rst:321
msgid "**Training:** once the applications are set up and the data imported, you have to train your users on the environment that is perfectly working. There will be some back and forth with Odoo's project manager to answer questions and process your feedback. (\\*)"
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:326
@ -362,62 +362,58 @@ msgid "**Production**: Once everyone is trained, your users start using Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:329
msgid "(\\*) *Before the training, our project manager will have done the customizations that are required to go into production. If you can use the software without these customizations (even if it requires extra manual tasks), we will push these customizations after going into production (see phase below).*"
msgstr ""
#: ../../getting_started/documentation.rst:335
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:339
#: ../../getting_started/documentation.rst:333
msgid "Once all applications are deployed and users are comfortable on 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:345
#: ../../getting_started/documentation.rst:339
msgid "Managing your databases"
msgstr ""
#: ../../getting_started/documentation.rst:347
#: ../../getting_started/documentation.rst:341
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:353
#: ../../getting_started/documentation.rst:347
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:357
#: ../../getting_started/documentation.rst:351
msgid "In that purpose, you can create as many free trials as you want (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:368
#: ../../getting_started/documentation.rst:362
msgid "You can find more information on how to manage your databases :ref:`here <db_management/documentation>`."
msgstr ""
#: ../../getting_started/documentation.rst:372
#: ../../getting_started/documentation.rst:366
msgid "Customer Success"
msgstr ""
#: ../../getting_started/documentation.rst:374
#: ../../getting_started/documentation.rst:368
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:377
#: ../../getting_started/documentation.rst:371
msgid "During the implementation phase, your point of contact is the project manager and eventually the support team."
msgstr ""
#: ../../getting_started/documentation.rst:380
#: ../../getting_started/documentation.rst:374
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:387
#: ../../getting_started/documentation.rst:381
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:390
#: ../../getting_started/documentation.rst:384
msgid "Welcome aboard and enjoy your Odoo experience!"
msgstr ""
#: ../../getting_started/documentation.rst:393
#: ../../getting_started/documentation.rst:387
msgid ":doc:`../../db_management/documentation`"
msgstr ""

2
locale/sources/index.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

84
locale/sources/inventory.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-31 16:00+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"
@ -516,30 +516,6 @@ msgstr ""
msgid "The Minimum Stock Rules configuration is available through the menu :menuselection:`Inventory --> Inventory Control --> Reordering Rule` in the drop down menu. There, click on **Create** to set minimum and maximum stock values for a given product."
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."
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
msgid "When the virtual stock goes below the Min Quantity specified for this field, Odoo generates a procurement to bring the forecasted quantity to the Max Quantity."
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
msgid "When the virtual stock goes below the Min Quantity, Odoo generates a procurement to bring the forecasted quantity to the Quantity specified as Max Quantity."
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
msgid "The procurement quantity will be rounded up to this multiple. If it is 0, the exact quantity will be used."
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
msgid "If the active field is set to False, it will allow you to hide the orderpoint without removing it."
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:0
msgid "Number of days after the orderpoint is triggered to receive the products or to order to the vendor"
msgstr ""
#: ../../inventory/management/adjustment/min_stock_rule_vs_mto.rst:45
msgid "Then, click on your product to access the related product form and, on the **Inventory submenu**, do not forget to select a supplier."
msgstr ""
@ -4232,7 +4208,7 @@ msgid "What is a putaway strategy?"
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:8
msgid "A good warehouse implementation takes care that products automatically move to their appropriate destination location. Putaway is the process of taking products off the receiving shipment and put them into the most appropriate location."
msgid "A good warehouse implementation takes care that products automatically move to their appropriate destination location. Putaway is the process of taking products off the receiving shipment and putting them into the most appropriate location."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:13
@ -4240,7 +4216,7 @@ msgid "If for instance a warehouse contains volatile substances, it is important
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:17
msgid "A putaway strategy follows the same principle as removal strategies but affect on the destination location. Put away strategies are defined at the location level (unlike removal strategies which are defined at the product level)."
msgid "A putaway strategy follows the same principle as removal strategies but affects the destination location. Putaway strategies are defined at the location level (unlike removal strategies which are defined at the product level)."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:25
@ -4276,7 +4252,7 @@ msgid "When you have entered all the necessary information, click on **Save**."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:61
msgid "Now, when you will purchase products from those categories, they will automatically be transferred to the correct location."
msgid "Now, when you purchase products with those categories, they will automatically be transferred to the correct location."
msgstr ""
#: ../../inventory/routes/strategies/putaway.rst:64
@ -5522,6 +5498,58 @@ msgstr ""
msgid ":doc:`../operation/invoicing`"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:3
msgid "How to get DHL credentials for integration with Odoo?"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:5
msgid "In order to use the Odoo DHL API, you will need:"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:7
msgid "A DHL.com SiteID"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:9
msgid "A DHL Password"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:11
msgid "A DHL Account Number"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:15
msgid "Getting SiteID and password for countries other than United States (UK and Rest of the world)"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:17
msgid "You should contact DHL account manager and request integration for XML Express API. The presales should provide you live credentials."
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:20
msgid "Getting SiteID and Password for United States"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:22
msgid "You need to write to xmlrequests@dhl.com along with your full Account details like account number, region, address, etc. to get API Access."
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:24
msgid "In meantime, for testing the solution, you can use the tests credentials as given in the demo data:"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:26
msgid "**SiteID**: CustomerTest"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:28
msgid "**Password**: alkd89nBV"
msgstr ""
#: ../../inventory/shipping/setup/dhl_credentials.rst:30
msgid "**DHL Account Number**: 803921577"
msgstr ""
#: ../../inventory/shipping/setup/third_party_shipper.rst:3
msgid "How to integrate a third party shipper?"
msgstr ""

2
locale/sources/legal.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

512
locale/sources/manufacturing.pot Normal file
View File

@ -0,0 +1,512 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:08+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../manufacturing.rst:5
msgid "Manufacturing"
msgstr ""
#: ../../manufacturing/operations.rst:3
msgid "Manufactufing Operations"
msgstr ""
#: ../../manufacturing/operations/replenishment.rst:3
msgid "Replenishment Strategies"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:3
msgid "How to select the right replenishment strategy"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:5
msgid "Minimum Stock rules and Make to Order have similar consequences but different rules. They should be used depending on your manufacturing and delivery strategies."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:10
msgid "Terminology"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:13
msgid "Minimum stock rule"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:15
msgid "Minimum Stock rules are used to ensure that you always have the minimum amount of a product in stock in order to manufacture your products and/or answer to your customer needs. When the stock level of a product reaches its minimum the system will automatically generate a procurement order with the quantity needed to reach the maximum stock level."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:22
#: ../../manufacturing/operations/replenishment/strategies.rst:58
msgid "Make to Order"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:24
msgid "The Make to Order function will trigger a Purchase Order of the amount of the Sales Order related to the product. The system will **not** check the current stock. This means that a draft purchase order will be generated regardless of the quantity on hand of the product."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:30
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:27
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:62
msgid "Configuration"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:33
msgid "Minimum stock rules"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:35
msgid "The Minimum Stock Rules configuration is available through your Inventory module. In the Inventory Control menu select \"Reordering Rule\" in the drop down menu. There, click on \"Create\" to set minimum and maximum stock values for a given product."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:44
msgid "Show tooltips for \"minimum quantity\", \"maximum quantity\" and \"quantity multiple\" fields"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:47
msgid "Then, click on your product to access the related product form and, on the \"Inventory submenu\", do not forget to select a supplier."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:54
msgid "Don't forget to select the right product type. A consumable can not be stocked and will thus not be accounted for in the stock valuation."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:60
msgid "The Make to Order configuration is available on your product form through your :menuselection:`Inventory --> Inventory control --> Products` (or any other module where products are available)."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:64
msgid "On the product form, under Inventory, click on \"Make To Order\"."
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:70
msgid "Choice between the two options"
msgstr ""
#: ../../manufacturing/operations/replenishment/strategies.rst:72
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 ""
#: ../../manufacturing/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials.rst:3
#: ../../manufacturing/overview/main_concepts/terminologies.rst:6
msgid "Bill of Materials"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:3
msgid "How to Sell a Set of Products as a Kit"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:5
msgid "A *kit* is a set of components that are delivered without first being assembled or mixed. Kits are described in Odoo using *bills of materials*. There are two basic ways to configure kits, depending on how stock of the kit product is to be managed. In either case, both the Inventory and Manufacturing apps must be installed."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:12
msgid "Manage Stock of Component Products"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:14
msgid "If you would like to assemble kits as they are ordered, managing stock of the kit *components* only, you will use a Kit BoM without a manufacturing step."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:18
msgid "A product using a Kit BoM will appear as a single line item on a quotation and sales order, but will generate a delivery order with one line item for each of the components of the kit. In the examples below, the image at left shows a sales order for the kit \"Custom Computer Kit\", while the image at right shows the corresponding delivery order."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:24
msgid "|image0|\\ |image1|"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:29
msgid "From the **Products** menu in either the Inventory or Manufacturing app, create each component product as you would any other product, then create the top-level, or kit product. The kit product should have only the route **Manufacture** set. Because you cannot track the stock of kit products, the Product Type should be set to **Consumable**. Because a kit product cannot be purchased, **Can be Purchased** should be unchecked."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:37
msgid "All other parameters on the kit product may be modified according to your preference. The component products require no special configuration."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:44
msgid "Once the products are configured, create a bill of materials for the kit product. Add each component and its quantity. Select the BoM Type **Ship this product as a set of components**. All other options may be left with their default values."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:53
msgid "Manage Stock of Kit Product and Component Products"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:55
msgid "If you would like to manage stock of the top-level kit product, you will use a standard BoM with a manufacturing step instead of a Kit BoM. When using a standard BoM to assemble kits, a manufacturing order will be created. The manufacturing order must be registered as completed before the kit product will appear in your stock."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:64
msgid "On the kit product, select the route **Manufacture**. You may also select **Make to Order**, which will create a manufacturing order whenever a sales order is confirmed. Select the product type **Stockable Product** to enable stock management."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/kit_shipping.rst:72
msgid "When you create the bill of materials, select the BoM Type **Manufacture this product**. The assembly of the kit will be described by a manufacturing order rather than a packing operation."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:3
msgid "How to manage BoMs for product variants"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:5
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:125
msgid "Odoo allows you to use one bill of materials for multiple variants of the same product. Simply enable variants from :menuselection:`Configuration --> Settings`."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:12
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:132
msgid "You will then be able to specify which component lines are to be used in the manufacture of each product variant. You may specify multiple variants for each line. If no variant is specified, the line will be used for all variants."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/product_variants.rst:17
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:137
msgid "When defining variant BoMs on a line-item-basis, the **Product Variant** field in the main section of the BoM should be left blank. This field is used when creating a BoM for one variant of a product only."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:3
msgid "How to manage semi-finished products"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:5
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:83
msgid "A subassembly is a manufactured product which is intended to be used as a component of another manufactured product. You may wish to employ sub-assemblies to simplify a complex BoM, to more accurately represent your manufacturing flow, or to use the same subassembly in multiple BoMs. A BoM that employs subassemblies is often referred to as a multi-level BoM."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:12
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:90
msgid "Multi-level bills of materials in Odoo are accomplished by creating a top-level BoM and subassembly BoMs. Next, the procurement route of the subassembly product is defined. This ensures that every time a manufacturing order for the top-level product is created, a manufacturing order for each subassembly is created as well."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:19
msgid "Configure the Top -Level Product BoM"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:21
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:99
msgid "To configure a multi-level BoM, create the top-level product and its BoM. Include any subassemblies in the list of components. Create a BoM for each subassembly as you would for any product."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:29
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:107
msgid "Configure the Subassembly Product Data"
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:31
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:109
msgid "On the product form of the subassembly, you must select the routes **Manufacture** and **Make To Order**. The **Manufacture** route takes precedence over the **Buy** route, so selecting the latter will have no effect."
msgstr ""
#: ../../manufacturing/overview/bill_of_materials/sub_assemblies.rst:39
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:117
msgid "If you would like to be able to purchase the subassembly in addition to manufacturing it, select **Can be Purchased**. All other fields on the subassembly product form may be configured according to your preference."
msgstr ""
#: ../../manufacturing/overview/getting_started.rst:3
msgid "Getting Started"
msgstr ""
#: ../../manufacturing/overview/getting_started.rst:5
msgid "How to consume composents to make a finished product"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:3
msgid "How to create a Bill of Materials"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:5
msgid "A bill of materials (BoM) is a document that describes the component products, the quantity of each component, and the process required to manufacture a product, including a routing and individual steps."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:9
msgid "In Odoo, each product may have multiple BoMs associated with it, but a BoM can only be associated with a single product. A single BoM can, however, describe multiple variants of the same product."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:14
msgid "Setting up a Basic BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:16
msgid "If choose to manage your manufacturing operations using manufacturing orders only, you will define basic bills of materials without routings. For more information about which method of management to use, review the **Getting Started** section of the *Manufacturing* chapter of the documentation."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:22
msgid "Before creating your first bill of materials, you will need to create a product and at least one component (components are considered products in Odoo). You can do so from :menuselection:`Master Data --> Products`, or on the fly from the relevant fields on the BoM form. Review the Inventory chapter for more information about configuring products. Once you have created a product and at least one component, select them from the relevant dropdown menus to add them to your bill of materials. A new bill of materials can be created from :menuselection:`Master Data --> Bills of Materials`, or using the button on the top of the product form."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:32
msgid "Under the **Miscellaneous** tab, you can fill additional fields. **Sequence** defines the order in which your BoMs will be selected for production orders, with lower numbers having higher priority. **Version** allows you to track changes to your BoM over time."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:38
msgid "Adding a Routing to a BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:40
msgid "A routing defines a series of operations required to manufacture a product and the work center at which each operation is performed. A routing may be added to multiple BoMs, though a BoM may only have one routing. For more information about configuring routings, review the chapter on routings."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:46
msgid "After enabling routings from :menuselection:`Configuration --> Settings`, you will be able to add a routing to a bill of materials by selecting a routing from the dropdown list or creating one on the fly."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:50
msgid "You may define the work operation or step in which each component is consumed using the field, **Consumed in Operation** under the **Components** tab. Similarly, you can define the operation at which the product will be produced under the **Miscellaneous** tab using the field **Produced at Operation**. If this field is left blank, the products will be consumed/produced at the final operation in the routing."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:61
msgid "Adding Byproducts to a BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:63
msgid "In Odoo, a byproduct is any product produced by a BoM in addition to the primary product."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:66
msgid "To add byproducts to a BoM, you will first need to enable them from :menuselection:`Configuration --> Settings`."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:72
msgid "Once byproducts are enabled, you can add them to your bills of materials under the **Byproducts** tab of the bill of materials. You can add any product or products as byproducts. Byproducts are produced in the same step of the routing as the primary product of the BoM."
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:81
msgid "Setting up a BoM for a Product With Sub-Assemblies"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:97
msgid "Configure the Top-Level Product BoM"
msgstr ""
#: ../../manufacturing/overview/getting_started/bill_configuration.rst:123
msgid "Using a Single BoM to Describe Several Variants of a Single Product"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:3
msgid "How to process a manufacturing order"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:6
msgid "Introduction"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:8
msgid "There are two basic ways to manage manufacturing in Odoo. The first way manages work with one document only. This document is the **manufacturing order**. The second way uses additional documents to give you more precise control over the manufacturing process. In this way, **Manufacturing orders** are divided into one or more steps defined by **work orders**, performed in an order defined by **routings**."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:17
msgid "How to manage manufacturing without routings"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:19
msgid "You will most likely use manufacturing orders without routings if all the work to produce your product is performed in one place, by one person, in one step, and/or you do not need the level of granular control afforded by work orders and routings."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:24
msgid "Managing your operations in this way is the default behavior in Odoo. There are two basic phases from planning to production:"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:27
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:52
msgid "Create manufacturing orders"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:29
msgid "Record Production"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:32
msgid "How to manage manufacturing with routings and work orders"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:34
msgid "To use work orders and routings, you will need to enable the option **Manage production by work orders** From :menuselection:`Configuration --> Settings`. You will then be able to add routings to bills of materials, and configure some additional related fields. You will also be able to create **work centers**, the locations at which work orders are performed."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:41
msgid "When manufacturing with routings and work orders, each work order is scheduled individually. You will also have access to time and capacity planning, and reports on costing and efficiency on a work center level."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:45
msgid "Manufacturing using routings can be broken down into several steps. When configuring your BoM, you will need to add a routing defining the component work orders. After planning the manufacturing order, you will have the added step of scheduling work orders."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:50
msgid "The workflow is thus divided into three basic phases, as follows:"
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:54
msgid "Schedule the associated work orders."
msgstr ""
#: ../../manufacturing/overview/getting_started/manufacturing_order.rst:56
msgid "Perform the scheduled work and record production."
msgstr ""
#: ../../manufacturing/overview/main_concepts.rst:3
msgid "Main Concepts"
msgstr ""
#: ../../manufacturing/overview/main_concepts/intro.rst:3
msgid "Introduction to Odoo Manufacturing"
msgstr ""
#: ../../manufacturing/overview/main_concepts/intro.rst:11
msgid "Transcript"
msgstr ""
#: ../../manufacturing/overview/main_concepts/intro.rst:13
msgid "Work in progress."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:3
msgid "Manufacturing Terminologies"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:9
msgid "A bill of materials (BoM) is a document that describes the materials, the quantity of each material, and the steps required to manufacture a product. Depending on the industry and the nature of the finished product, a different name may be used to describe the same document. For example, in the pharmaceutical industry, the term “recipe” may be used."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:14
msgid "Cycle"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:17
msgid "A production cycle is a frame of time during which an entire manufacturing process can be fulfilled."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:19
msgid "Downtime or Leave"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:22
msgid "Time during which a resource is unavailable. If the resource is a machine, the unavailability is downtime, while if the resource is human, unavailable time is called a Leave."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:25
msgid "Finished products"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:28
msgid "Finished products are the final output of a manufacturing process. They are normally not intended to be used as input into another manufacturing order of the company."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:31
msgid "Kit"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:34
msgid "A kit is a set of components that are described by a bill of materials, but which are delivered separately rather than assembled or mixed."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:36
msgid "Multi-level Bill of Materials"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:39
msgid "A bill of material can quickly grow very complex. To keep it manageable, it can be broken down into several smaller manufactured parts, each having its own BOM. These parts are typically referred to as sub-assembly of intermediate products."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:44
msgid "Defining a BOM in multiple levels reduces the complexity of the top-level document and allows components to be reused in other BoMs."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:46
msgid "Phantom Bill of Material"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:49
msgid "A phantom bill of material is always used in the context of multi-level BOMs. It allows to add a sub-assembly as part of a bigger end-product while avoiding to trigger a separate manufacturing order for the sub-assembly."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:54
msgid "As such, when a manufacturing order for the final product is launched, the components of the sub-assembly are reflected in the parent BOM as if they were direct components of the parent BOM."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:58
msgid "Phantom BOM are thus used for grouping a set of components with the aim of reusing them in many other BOM without the need to launch separate manufacturing orders for the sub-assemblies."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:61
msgid "Raw Materials"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:64
msgid "Raw materials and components constitute the input that are transformed to produce semi-finished or finished goods."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:67
msgid "The transformation here can take many aspects according to the industry. It can be simple assembly, welding, mixing, etc."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:69
msgid "Routing"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:72
msgid "A routing is a document that describes a series of Work Orders and the Work Centers at which they will be carried out"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:74
msgid "Semi-finished products and sub-assemblies"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:77
msgid "These are products which are manufactured with the purpose to be consumed in another manufacturing order."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:79
msgid "Work Order Operations"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:82
msgid "Work Order Operations specify the set of activities necessary to fully process a manufacturing order. Each activity or operation takes some time to be completed and is performed into a determined production unit (also called work center)."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:86
msgid "Work Order"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:89
msgid "A work order is a single manufacturing operation that is scheduled for execution on a given date and a given duration."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:91
msgid "Work Center"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:94
msgid "Work centers identify production units and their resources. They are used to represent the plant capacity as well as costing information. The capacity is a combination of resources and their availability time."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:97
msgid "Resources"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:100
msgid "In manufacturing a resource can be a human being (employee) or machine available in a work center."
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:102
msgid "Working Time"
msgstr ""
#: ../../manufacturing/overview/main_concepts/terminologies.rst:105
msgid "Each resource has its normal working time. For instance, machines can be set up to operate 7 days a week 20 hours out of 24."
msgstr ""

118
locale/sources/point_of_sale.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-09-01 11:43+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"
@ -805,7 +805,7 @@ msgid "An RJ45 Ethernet Cable or a Linux compatible USB Wi-Fi adapter"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:22
msgid "An Epson USB TM-T20 Printer or another compatible printer (officially supported printers are listed at the `POS Hardware page <https://www.odoo.com/page/pos-ipad-android-hardware>`_)"
msgid "An Epson USB TM-T20 Printer or another ESC/POS compatible printer (officially supported printers are listed at the `POS Hardware page <https://www.odoo.com/page/pos-ipad-android-hardware>`_)"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:25
@ -1064,7 +1064,7 @@ msgid "We must launch the Odoo server with the correct settings"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:276
msgid "``$ ./odoo.py --load=web,hw_proxy,hw_posbox_homepage,hw_posbox_upgrade,hw_scale, hw_scanner,hw_escpos``"
msgid "``$ ./odoo.py --load=web,hw_proxy,hw_posbox_homepage,hw_posbox_upgrade,hw_scale,hw_scanner,hw_escpos``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:279
@ -1459,114 +1459,6 @@ msgstr ""
msgid "You can configure each point of sale according to your hardware, location,..."
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "An internal identification of the point of sale"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Accounting journal used to post sales entries."
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Check this if you want to group the Journal Items by Product while closing a Session"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Defines what kind of barcodes are available and how they are assigned to products, customers and cashiers"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "This sequence is automatically created by Odoo but you can change it to customize the reference numbers of your orders."
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Enables an integrated Virtual Keyboard"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Enables invoice generation from the Point of Sale"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The payment input will behave similarily to bank payment input, and will be prefilled with the exact due amount"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The point of sale will display this product category by default. If no category is specified, all available products will be shown"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The product used to encode the customer tip. Leave empty if you do not accept tips."
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The displayed prices will always include all taxes, even if the taxes have been setup differently"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "For imprecise industrial touchscreens"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The receipt will automatically be printed at the end of each order"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The product categories will be displayed with pictures."
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The receipt screen will be skipped if the receipt can be printed automatically."
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Check the amount of the cashbox at opening and closing."
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The hostname or ip address of the hardware proxy, Will be autodetected if left empty"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Bypass browser printing and prints via the hardware proxy"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Enable barcode scanning with a remotely connected barcode scanner"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Enables Electronic Scale integration"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Automatically open the cashdrawer"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "A short text that will be inserted as a header in the printed receipt"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "A short text that will be inserted as a footer in the printed receipt"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Enables Bill Splitting in the Point of Sale"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Allows to print the Bill before payment"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "Allow custom notes on Orderlines"
msgstr ""
#: ../../point_of_sale/overview/start.rst:0
msgid "The restaurant floors served by this point of sale"
msgstr ""
#: ../../point_of_sale/overview/start.rst:100
msgid "Now you are ready to make your first steps with your point of sale."
msgstr ""
@ -2191,10 +2083,6 @@ msgstr ""
msgid "Create a **Pricelist** for your point of sale. Each pricelist can contain several items with different prices and different dates. It can be done on all products or only on specific ones. Click on **Add an item**."
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:0
msgid "If unchecked, it will allow you to hide the pricelist without removing it."
msgstr ""
#: ../../point_of_sale/shop/seasonal_discount.rst:45
msgid "For example, the price of the oranges costs ``3€`` but for two days, we want to give a ``10%`` discount to our PoS customers."
msgstr ""

2
locale/sources/project.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-31 15:56+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

34
locale/sources/purchase.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"
@ -1176,38 +1176,6 @@ 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 "Incoming Shipments"
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 "Depicts the date where the Quotation should be validated and converted into a purchase order."
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Reference of the document that generated this purchase order request (e.g. a sale order or an internal procurement request)"
msgstr ""
#: ../../purchase/purchases/rfq/create.rst:0
msgid "This will determine picking type of incoming shipment"
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 "Technical field used to display the Drop Ship Address"
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:35
msgid "View *Request for Quotation* in our Online Demonstration"
msgstr ""

2
locale/sources/recruitment.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

2
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"

2
locale/sources/website.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-08-18 10:05+0200\n"
"POT-Creation-Date: 2016-11-22 13:16+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"