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

[I18N] export v12 documentation source terms

Browse Source
This commit is contained in:
Martin Trigaux 2018-10-19 10:16:23 +02:00
parent 6ae5e29df7
commit 9866567755
19 changed files with 1679 additions and 3089 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

51
.tx/config
View File

@ -2,117 +2,122 @@
host = https://www.transifex.com
type = PO
[odoo-11-doc.accounting]
[odoo-12-doc.accounting]
file_filter = locale/<lang>/LC_MESSAGES/accounting.po
source_file = locale/sources/accounting.pot
source_lang = en
[odoo-11-doc.applications]
[odoo-12-doc.applications]
file_filter = locale/<lang>/LC_MESSAGES/applications.po
source_file = locale/sources/applications.pot
source_lang = en
[odoo-11-doc.crm]
[odoo-12-doc.crm]
file_filter = locale/<lang>/LC_MESSAGES/crm.po
source_file = locale/sources/crm.pot
source_lang = en
[odoo-11-doc.db_management]
[odoo-12-doc.db_management]
file_filter = locale/<lang>/LC_MESSAGES/db_management.po
source_file = locale/sources/db_management.pot
source_lang = en
[odoo-11-doc.discuss]
[odoo-12-doc.discuss]
file_filter = locale/<lang>/LC_MESSAGES/discuss.po
source_file = locale/sources/discuss.pot
source_lang = en
[odoo-11-doc.ecommerce]
[odoo-12-doc.ecommerce]
file_filter = locale/<lang>/LC_MESSAGES/ecommerce.po
source_file = locale/sources/ecommerce.pot
source_lang = en
[odoo-11-doc.expenses]
[odoo-12-doc.expenses]
file_filter = locale/<lang>/LC_MESSAGES/expenses.po
source_file = locale/sources/expenses.pot
source_lang = en
[odoo-11-doc.general]
[odoo-12-doc.general]
file_filter = locale/<lang>/LC_MESSAGES/general.po
source_file = locale/sources/general.pot
source_lang = en
[odoo-11-doc.getting_started]
[odoo-12-doc.getting_started]
file_filter = locale/<lang>/LC_MESSAGES/getting_started.po
source_file = locale/sources/getting_started.pot
source_lang = en
[odoo-11-doc.helpdesk]
[odoo-12-doc.helpdesk]
file_filter = locale/<lang>/LC_MESSAGES/helpdesk.po
source_file = locale/sources/helpdesk.pot
source_lang = en
[odoo-11-doc.index]
[odoo-12-doc.index]
file_filter = locale/<lang>/LC_MESSAGES/index.po
source_file = locale/sources/index.pot
source_lang = en
[odoo-11-doc.inventory]
[odoo-12-doc.inventory]
file_filter = locale/<lang>/LC_MESSAGES/inventory.po
source_file = locale/sources/inventory.pot
source_lang = en
[odoo-11-doc.iot]
[odoo-12-doc.iot]
file_filter = locale/<lang>/LC_MESSAGES/iot.po
source_file = locale/sources/iot.pot
source_lang = en
[odoo-11-doc.livechat]
[odoo-12-doc.livechat]
file_filter = locale/<lang>/LC_MESSAGES/livechat.po
source_file = locale/sources/livechat.pot
source_lang = en
[odoo-11-doc.manufacturing]
[odoo-12-doc.mobile]
file_filter = locale/<lang>/LC_MESSAGES/mobile.po
source_file = locale/sources/mobile.pot
source_lang = en
[odoo-12-doc.manufacturing]
file_filter = locale/<lang>/LC_MESSAGES/manufacturing.po
source_file = locale/sources/manufacturing.pot
source_lang = en
[odoo-11-doc.point_of_sale]
[odoo-12-doc.point_of_sale]
file_filter = locale/<lang>/LC_MESSAGES/point_of_sale.po
source_file = locale/sources/point_of_sale.pot
source_lang = en
[odoo-11-doc.portal]
[odoo-12-doc.portal]
file_filter = locale/<lang>/LC_MESSAGES/portal.po
source_file = locale/sources/portal.pot
source_lang = en
[odoo-11-doc.practical]
[odoo-12-doc.practical]
file_filter = locale/<lang>/LC_MESSAGES/practical.po
source_file = locale/sources/practical.pot
source_lang = en
[odoo-11-doc.project]
[odoo-12-doc.project]
file_filter = locale/<lang>/LC_MESSAGES/project.po
source_file = locale/sources/project.pot
source_lang = en
[odoo-11-doc.purchase]
[odoo-12-doc.purchase]
file_filter = locale/<lang>/LC_MESSAGES/purchase.po
source_file = locale/sources/purchase.pot
source_lang = en
[odoo-11-doc.recruitment]
[odoo-12-doc.recruitment]
file_filter = locale/<lang>/LC_MESSAGES/recruitment.po
source_file = locale/sources/recruitment.pot
source_lang = en
[odoo-11-doc.sales]
[odoo-12-doc.sales]
file_filter = locale/<lang>/LC_MESSAGES/sales.po
source_file = locale/sources/sales.pot
source_lang = en
[odoo-11-doc.website]
[odoo-12-doc.website]
file_filter = locale/<lang>/LC_MESSAGES/website.po
source_file = locale/sources/website.pot
source_lang = en

1230
locale/sources/accounting.pot
View File

File diff suppressed because it is too large Load Diff

6
locale/sources/applications.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

6
locale/sources/business.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-10 09:08+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

28
locale/sources/discuss.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-27 11:08+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -25,15 +25,19 @@ msgid "How to use my mail server to send and receive emails in Odoo"
msgstr ""
#: ../../discuss/email_servers.rst:5
msgid "This document is mainly dedicated to Odoo on-premise users who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike in `Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh <https://www.odoo.sh>`__."
msgid "This document is mainly dedicated to Odoo on-premise users who don't benefit from an out-of-the-box solution to send and receive emails in Odoo, unlike `Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh <https://www.odoo.sh>`__."
msgstr ""
#: ../../discuss/email_servers.rst:9
msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for such convenient Odoo hosting solutions. Indeed their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself."
msgid "If no one in your company is used to manage email servers, we strongly recommend that you opt for those Odoo hosting solutions. Their email system works instantly and is monitored by professionals. Nevertheless you can still use your own email servers if you want to manage your email server's reputation yourself."
msgstr ""
#: ../../discuss/email_servers.rst:15
msgid "You will find here below some useful information to do so by integrating your own email solution with Odoo. .. note::"
msgid "You will find here below some useful information on how to integrate your own email solution with Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:18
msgid "Office 365 email servers don't allow easiliy to send external emails from hosts like Odoo. Refer to the `Microsoft's documentation <https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
msgstr ""
#: ../../discuss/email_servers.rst:24
@ -308,6 +312,22 @@ msgstr ""
msgid "If you need to use other activity types with a calendar planning, make sure their *Category* is set as *Meeting*."
msgstr ""
#: ../../discuss/plan_activities.rst:40
msgid "Schedule a chain of activities to follow"
msgstr ""
#: ../../discuss/plan_activities.rst:42
msgid "Odoo helps you easily plan your usual flow of activities. Go to :menuselection:`Configuration --> Activity Types` and set the common following steps as *Recommended next activities*."
msgstr ""
#: ../../discuss/plan_activities.rst:49
msgid "Now, when an activity is completed, you can select *Done & schedule next*. The next steps will automatically be suggested to you."
msgstr ""
#: ../../discuss/plan_activities.rst:55
msgid "Have fun getting better organized by planning activities !"
msgstr ""
#: ../../discuss/team_communication.rst:3
msgid "How to efficiently communicate in team using channels"
msgstr ""

6
locale/sources/ecommerce.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-10 09:08+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

7
locale/sources/expense.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-20 11:50+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -16,7 +16,6 @@ msgstr ""
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../expense.rst:5
#: ../../expense/expense.rst:5
msgid "Expenses"
msgstr ""

10
locale/sources/general.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-10-10 09:08+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -505,10 +505,6 @@ msgstr ""
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 ""

6
locale/sources/helpdesk.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-03-08 14:28+0100\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

6
locale/sources/index.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

10
locale/sources/inventory.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-01-08 17:10+0100\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -4839,10 +4839,6 @@ msgstr ""
msgid ":doc:`uom`"
msgstr ""
#: ../../inventory/settings/products/usage.rst:72
msgid ":doc:`packages`"
msgstr ""
#: ../../inventory/settings/products/variants.rst:3
msgid "Using product variants"
msgstr ""

282
locale/sources/iot.pot Normal file
View File

@ -0,0 +1,282 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../iot.rst:5
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../iot/connect.rst:3
msgid "Connect an IoT Box to your database"
msgstr ""
#: ../../iot/connect.rst:5
msgid "Install the Internet of Things (IoT) App on your Odoo Database."
msgstr ""
#: ../../iot/connect.rst:10
msgid "Go in the IoT App and click on Connect on the IoT Boxes page."
msgstr ""
#: ../../iot/connect.rst:15
msgid "Follow the steps to connect your IoT Box."
msgstr ""
#: ../../iot/connect.rst:21
msgid "Ethernet Connection"
msgstr ""
#: ../../iot/connect.rst:23
msgid "Connect to the IoT Box all the devices that have to be connected with cables (ethernet, usb devices, etc.)."
msgstr ""
#: ../../iot/connect.rst:26
msgid "Power on the IoT Box."
msgstr ""
#: ../../iot/connect.rst:28
msgid "Then click on the Scan button."
msgstr ""
#: ../../iot/connect.rst:34
msgid "WiFi Connection"
msgstr ""
#: ../../iot/connect.rst:36
msgid "Power on the IoT Box"
msgstr ""
#: ../../iot/connect.rst:38
msgid "Copy the token"
msgstr ""
#: ../../iot/connect.rst:43
msgid "Connect to the IoT Box WiFi Network (make sure there is no ethernet cable plugged in your computer)."
msgstr ""
#: ../../iot/connect.rst:49
msgid "You will be redirected to the IoT Box Homepage (if it doesn't work, connect to the IP address of the box). Give a name to your IoT Box (not required) and paste the token, then click on next."
msgstr ""
#: ../../iot/connect.rst:57
msgid "If you are on Runbot, do not forget to add the -all or -base in the token (e.g. this token **http://375228-saas-11-5-iot-f3f920.runbot16.odoo.com\\|4957098401** should become **http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
#: ../../iot/connect.rst:63
msgid "Choose the WiFi network you want to connect with (enter the password if there is one) and click on Submit. Wait a few seconds before being redirected to your database."
msgstr ""
#: ../../iot/connect.rst:70
msgid "You should now see the IoT Box."
msgstr ""
#: ../../iot/connect.rst:76
msgid "IoT Box Schema"
msgstr ""
#: ../../iot/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr ""
#: ../../iot/pos.rst:9
msgid "Prerequisites"
msgstr ""
#: ../../iot/pos.rst:11
msgid "Before starting, make sure you have the following:"
msgstr ""
#: ../../iot/pos.rst:13
msgid "An IoT Box"
msgstr ""
#: ../../iot/pos.rst:15
msgid "A 2A Power adapter with pi 3 b+ 2.5 A"
msgstr ""
#: ../../iot/pos.rst:17
msgid "A computer or tablet with an up-to-date web browser"
msgstr ""
#: ../../iot/pos.rst:19
msgid "A running SaaS or Odoo instance with the Point of Sale and IoT apps installed"
msgstr ""
#: ../../iot/pos.rst:22
msgid "A local network setup with DHCP (this is the default setting)"
msgstr ""
#: ../../iot/pos.rst:24
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 ""
#: ../../iot/pos.rst:28
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
#: ../../iot/pos.rst:30
msgid "An Epson compatible cash drawer"
msgstr ""
#: ../../iot/pos.rst:32
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr ""
#: ../../iot/pos.rst:35
msgid "Set Up"
msgstr ""
#: ../../iot/pos.rst:37
msgid "To connect hardware to the PoS, the first step is to connect an IoT Box to your database. For this, follow this `documentation <https://docs.google.com/document/d/1vhWrSSlSdJcRYe4tjPpXKYVMTD47lVK3ysyYc7tJDlA/edit#>`__."
msgstr ""
#: ../../iot/pos.rst:44
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr ""
#: ../../iot/pos.rst:46
msgid "Officially supported hardware is listed on `the POS Hardware page <https://www.odoo.com/page/pos-ipad-android-hardware>`__, but other hardware might work as well."
msgstr ""
#: ../../iot/pos.rst:50
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
#: ../../iot/pos.rst:53
msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable."
msgstr ""
#: ../../iot/pos.rst:56
msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must behave as a keyboard and must be configured in **US QWERTY**. It also must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner."
msgstr ""
#: ../../iot/pos.rst:62
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
#: ../../iot/pos.rst:64
msgid "**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. Make sure this will connect the IoT Box to the same network as your POS device."
msgstr ""
#: ../../iot/pos.rst:68
msgid "**Wi-Fi**: The current version of the IoT Box has Wi-Fi built in. Make sure not to plug in an Ethernet cable when booting, because all Wi-Fi functionality will be bypassed when a wired network connection is available on boot."
msgstr ""
#: ../../iot/pos.rst:73
msgid "Once it's done, you can connect the IoT Box to your PoS. For this, go in Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the IoT Box you want to connect with. Save the changes."
msgstr ""
#: ../../iot/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
#: ../../iot/pos.rst:80
msgid "Troubleshoot"
msgstr ""
#: ../../iot/pos.rst:83
msgid "The PoS cannot connect to the IoT Box"
msgstr ""
#: ../../iot/pos.rst:85
msgid "The easiest way to make sure the IoT Box is properly set-up is to turn it on with the printer plugged in as it will print a receipt indicating any error if encountered or the IoT Box's IP address in case of success. If no receipt is printed, check the following steps:"
msgstr ""
#: ../../iot/pos.rst:91
msgid "Make sure the IoT Box is powered on, indicated by a brightly lit red status LED."
msgstr ""
#: ../../iot/pos.rst:94
msgid "Make sure the IoT Box is ready, this is indicated by a brightly lit green status LED just next to the red power status LED. The IoT Box should be ready ~2 minutes after it is started."
msgstr ""
#: ../../iot/pos.rst:98
msgid "Make sure the IoT Box is connected to the same network as your POS device. Both the device and the IoT Box should be visible in the list of connected devices on your network router."
msgstr ""
#: ../../iot/pos.rst:102
msgid "If you specified the IoT Box's IP address in the configuration, make sure it corresponds to the ip address printed on the IoT Box's status receipt."
msgstr ""
#: ../../iot/pos.rst:106
msgid "Make sure that the POS is not loaded over HTTPS."
msgstr ""
#: ../../iot/pos.rst:108
msgid "A bug in Firefox's HTTP implementation might prevent the autodiscovery from working reliably. You could also manually set up the IoT Box's IP address in the POS configuration."
msgstr ""
#: ../../iot/pos.rst:113
msgid "The Barcode Scanner is not working"
msgstr ""
#: ../../iot/pos.rst:115
msgid "The barcode scanner must be configured in US QWERTY and emit an Enter after each barcode. This is the default configuration of most barcode readers. Refer to the barcode reader documentation for more information."
msgstr ""
#: ../../iot/pos.rst:120
msgid "The IoT Box needs a 2A power supply to work with some barcode scanners. If you are not using the provided power supply, make sure the one you use has enough power."
msgstr ""
#: ../../iot/pos.rst:124
msgid "Some barcode scanners will need more than 2A and will not work, or will work unreliably, even with the provided power supply. In those case you can plug the barcode scanner in a self-powered USB hub."
msgstr ""
#: ../../iot/pos.rst:129
msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a usb keyboard instead, and will not be recognized by the IoT Box."
msgstr ""
#: ../../iot/pos.rst:134
msgid "The Barcode Scanner is not working reliably"
msgstr ""
#: ../../iot/pos.rst:136
msgid "Make sure that no more than one device with 'Scan via Proxy'/'Barcode Scanner' enabled are connected to the IoT Box at the same time."
msgstr ""
#: ../../iot/pos.rst:140
msgid "Printing the receipt takes too much time"
msgstr ""
#: ../../iot/pos.rst:142
msgid "A small delay before the first print is expected, as the IoT Box will do some preprocessing to speed up the next printings. If you suffer delays afterwards it is most likely due to poor network connection between the POS and the IoT Box."
msgstr ""
#: ../../iot/pos.rst:148
msgid "Some characters are not correctly printed on the receipt"
msgstr ""
#: ../../iot/pos.rst:150
msgid "The IoT Box does not support all languages and characters. It currently supports Latin and Cyrillic based scripts, with basic Japanese support."
msgstr ""
#: ../../iot/pos.rst:155
msgid "The printer is offline"
msgstr ""
#: ../../iot/pos.rst:157
msgid "Make sure the printer is connected, powered, has enough paper and has its lid closed, and is not reporting an error. If the error persists, please contact support."
msgstr ""
#: ../../iot/pos.rst:162
msgid "The cashdrawer does not open"
msgstr ""
#: ../../iot/pos.rst:164
msgid "The cashdrawer should be connected to the printer and should be activated in the POS configuration."
msgstr ""

128
locale/sources/manufacturing.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-12-22 15:27+0100\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -41,102 +41,102 @@ msgid "Setting up a Basic BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:16
msgid "If you 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."
msgid "If you choose to manage your manufacturing operations using manufacturing orders only, you will define basic bills of materials without routings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:22
#: ../../manufacturing/management/bill_configuration.rst:19
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/management/bill_configuration.rst:32
#: ../../manufacturing/management/bill_configuration.rst:29
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/management/bill_configuration.rst:38
#: ../../manufacturing/management/bill_configuration.rst:35
msgid "Adding a Routing to a BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:40
#: ../../manufacturing/management/bill_configuration.rst:37
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/management/bill_configuration.rst:46
#: ../../manufacturing/management/bill_configuration.rst:43
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/management/bill_configuration.rst:50
#: ../../manufacturing/management/bill_configuration.rst:47
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/management/bill_configuration.rst:61
#: ../../manufacturing/management/bill_configuration.rst:58
msgid "Adding Byproducts to a BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:63
#: ../../manufacturing/management/bill_configuration.rst:60
msgid "In Odoo, a byproduct is any product produced by a BoM in addition to the primary product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:66
#: ../../manufacturing/management/bill_configuration.rst:63
msgid "To add byproducts to a BoM, you will first need to enable them from :menuselection:`Configuration --> Settings`."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:72
#: ../../manufacturing/management/bill_configuration.rst:69
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/management/bill_configuration.rst:81
#: ../../manufacturing/management/bill_configuration.rst:78
msgid "Setting up a BoM for a Product With Sub-Assemblies"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:83
#: ../../manufacturing/management/bill_configuration.rst:80
#: ../../manufacturing/management/sub_assemblies.rst:5
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/management/bill_configuration.rst:90
#: ../../manufacturing/management/bill_configuration.rst:87
#: ../../manufacturing/management/sub_assemblies.rst:12
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/management/bill_configuration.rst:97
#: ../../manufacturing/management/bill_configuration.rst:94
msgid "Configure the Top-Level Product BoM"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:99
#: ../../manufacturing/management/bill_configuration.rst:96
#: ../../manufacturing/management/sub_assemblies.rst:21
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/management/bill_configuration.rst:107
#: ../../manufacturing/management/bill_configuration.rst:104
#: ../../manufacturing/management/sub_assemblies.rst:29
msgid "Configure the Subassembly Product Data"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:109
#: ../../manufacturing/management/bill_configuration.rst:106
#: ../../manufacturing/management/sub_assemblies.rst:31
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/management/bill_configuration.rst:117
#: ../../manufacturing/management/bill_configuration.rst:114
#: ../../manufacturing/management/sub_assemblies.rst:39
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/management/bill_configuration.rst:123
#: ../../manufacturing/management/bill_configuration.rst:120
msgid "Using a Single BoM to Describe Several Variants of a Single Product"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:125
#: ../../manufacturing/management/bill_configuration.rst:122
#: ../../manufacturing/management/product_variants.rst:5
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/management/bill_configuration.rst:132
#: ../../manufacturing/management/bill_configuration.rst:129
#: ../../manufacturing/management/product_variants.rst:12
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/management/bill_configuration.rst:137
#: ../../manufacturing/management/bill_configuration.rst:134
#: ../../manufacturing/management/product_variants.rst:17
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 ""
@ -271,7 +271,83 @@ msgstr ""
msgid "Configure the Top -Level Product BoM"
msgstr ""
#: ../../manufacturing/management/unbuild.rst:3
msgid "Unbuild a product"
msgstr ""
#: ../../manufacturing/management/unbuild.rst:5
msgid "In Odoo Manufacturing App, you can *Unbuild* products. Two use cases can be managed: (1) you can unbuild products you have built yourself or (2) you can unbuild products you have received."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:9
msgid "Let's take the first case, you are manufacturing products yourself. If one of your product presents some defect, you might want to unbuild it instead of scrapping it completely, allowing you to reuse some components of the product."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:14
msgid "In the second case, you are buying products for the sole purpose of unbuilding them and recycling them."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:18
msgid "Unbuild Order"
msgstr ""
#: ../../manufacturing/management/unbuild.rst:20
msgid "While in the Manufacturing App, under the *Operations* tab you will find the menu *Unbuild Orders*."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:26
msgid "When creating a new one, you can either select a MO if you are unbuilding something you manufactured or only select a product if you are unbuilding something you received."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:33
msgid "When you are done, just click unbuild and the process will be over."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:35
msgid "If you unbuild a product that you manufactured before, you will get the components from the MO back in stock."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:38
msgid "If you unbuild a product you bought, you will get the components from the BoM back in stock."
msgstr ""
#: ../../manufacturing/overview.rst:5
msgid "Overview"
msgstr ""
#: ../../manufacturing/repair.rst:5
msgid "Repair Management"
msgstr ""
#: ../../manufacturing/repair/repair.rst:3
msgid "Repair products"
msgstr ""
#: ../../manufacturing/repair/repair.rst:5
msgid "The Odoo *Repair* app allows you to manage a complete after sales process but also to simply repair products you have manufactured, if they present a defect."
msgstr ""
#: ../../manufacturing/repair/repair.rst:10
msgid "Create a Repair Order"
msgstr ""
#: ../../manufacturing/repair/repair.rst:12
msgid "Once in the app, you can access your existing *Repair Orders* and create a new one."
msgstr ""
#: ../../manufacturing/repair/repair.rst:19
msgid "Manage a repair"
msgstr ""
#: ../../manufacturing/repair/repair.rst:21
msgid "When a customer sends you a product for repair, create a new *Repair Order*. Fill it in with all the information you may need such as the product, the customer, if it has to be invoiced after or before the repair, the parts you might need, etc."
msgstr ""
#: ../../manufacturing/repair/repair.rst:29
msgid "Once everything is done, you can then send the repair quotation to your customer. If it is approved, you can confirm the repair. You will then be able to start & end the repair when it is completed."
msgstr ""
#: ../../manufacturing/repair/repair.rst:36
msgid "You can now invoice the repair."
msgstr ""

98
locale/sources/mobile.pot Normal file
View File

@ -0,0 +1,98 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../mobile/firebase.rst:5
msgid "Mobile"
msgstr ""
#: ../../mobile/firebase.rst:8
msgid "Setup your Firebase Cloud Messaging"
msgstr ""
#: ../../mobile/firebase.rst:10
msgid "In order to have mobile notifications in our Android app, you need an API key."
msgstr ""
#: ../../mobile/firebase.rst:13
msgid "If it is not automatically configured (for instance for On-premise or Odoo.sh) please follow these steps below to get an API key for the android app."
msgstr ""
#: ../../mobile/firebase.rst:18
msgid "The iOS app doesn't support mobile notifications for Odoo versions < 12."
msgstr ""
#: ../../mobile/firebase.rst:22
msgid "Firebase Settings"
msgstr ""
#: ../../mobile/firebase.rst:25
msgid "Create a new project"
msgstr ""
#: ../../mobile/firebase.rst:27
msgid "First, make sure you to sign in to your Google Account. Then, go to `https://console.firebase.google.com <https://console.firebase.google.com/>`__ and create a new project."
msgstr ""
#: ../../mobile/firebase.rst:34
msgid "Choose a project name, click on **Continue**, then click on **Create project**."
msgstr ""
#: ../../mobile/firebase.rst:37
msgid "When you project is ready, click on **Continue**."
msgstr ""
#: ../../mobile/firebase.rst:39
msgid "You will be redirected to the overview project page (see next screenshot)."
msgstr ""
#: ../../mobile/firebase.rst:43
msgid "Add an app"
msgstr ""
#: ../../mobile/firebase.rst:45
msgid "In the overview page, click on the Android icon."
msgstr ""
#: ../../mobile/firebase.rst:50
msgid "You must use \"com.odoo.com\" as Android package name. Otherwise, it will not work."
msgstr ""
#: ../../mobile/firebase.rst:56
msgid "No need to download the config file, you can click on **Next** twice and skip the fourth step."
msgstr ""
#: ../../mobile/firebase.rst:60
msgid "Get generated API key"
msgstr ""
#: ../../mobile/firebase.rst:62
msgid "On the overview page, go to Project settings:"
msgstr ""
#: ../../mobile/firebase.rst:67
msgid "In **Cloud Messaging**, you will see the **API key** and the **Sender ID** that you need to set in Odoo General Settings."
msgstr ""
#: ../../mobile/firebase.rst:74
msgid "Settings in Odoo"
msgstr ""
#: ../../mobile/firebase.rst:76
msgid "Simply paste the API key and the Sender ID from Cloud Messaging."
msgstr ""

632
locale/sources/point_of_sale.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-26 12:01+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -48,7 +48,7 @@ msgid "To use a barcode scanner, go to :menuselection:`Point of Sale --> Configu
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:14
msgid "Under the PosBox / Hardware category, you will find *Barcode Scanner* select it."
msgid "Under the IoT Box / Hardware category, you will find *Barcode Scanner* select it."
msgstr ""
#: ../../point_of_sale/advanced/barcode.rst:21
@ -406,7 +406,7 @@ msgid "Serial-to-USB adapter per FDM (`example <http://trendnet.com/products/pro
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:32
msgid "A registered POSBox per POS configuration"
msgid "A registered IoT Box per POS configuration"
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:35
@ -414,11 +414,11 @@ msgid "Setup"
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:38
msgid "POSBox"
msgid "IoT Box"
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:40
msgid "In order to use a Fiscal Data Module, you will need a registered POSBox. These POSBoxes are similar to the regular POSBoxes we sell, but they are registered with the Belgian government. This is required by law. Attempting to use a Fiscal Data Module on a non-registered POSBox will not work. You can verify that the Fiscal Data Module is recognized by the POSBox by going to the *Hardware status page* via the POSBox homepage."
msgid "In order to use a Fiscal Data Module, you will need a registered IoT Box. These IoT Boxes are similar to the regular IoT Boxes we sell, but they are registered with the Belgian government. This is required by law. Attempting to use a Fiscal Data Module on a non-registered IoT Box will not work. You can verify that the Fiscal Data Module is recognized by the IoT Box by going to the *Hardware status page* via the IoT Box homepage."
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:52
@ -426,7 +426,7 @@ msgid "Odoo"
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:54
msgid "An Odoo POS app can be given certified POS capabilities by installing the **Belgian Registered Cash Register** app (technical name: ``pos_blackbox_be``). Because of government restrictions imposed on us, this installation cannot be undone. After this, you will have to ensure that each POS configuration has a unique registered POSBox associated with it (:menuselection:`Point of Sale --> Configuration --> Point of Sale` and ensure Hardware Proxy / POSBox and the serial number of your POSBox is set). The first time you open the Point of Sale and attempt to do a transaction, you will be asked to input the PIN that you received with your VAT signing card."
msgid "An Odoo POS app can be given certified POS capabilities by installing the **Belgian Registered Cash Register** app (technical name: ``pos_blackbox_be``). Because of government restrictions imposed on us, this installation cannot be undone. After this, you will have to ensure that each POS configuration has a unique registered IoT Box associated with it (:menuselection:`Point of Sale --> Configuration --> Point of Sale` and ensure Hardware Proxy / IoT Box and the serial number of your IoT Box is set). The first time you open the Point of Sale and attempt to do a transaction, you will be asked to input the PIN that you received with your VAT signing card."
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:69
@ -462,11 +462,11 @@ msgid "Selling products without a valid tax"
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:90
msgid "Multiple Odoo POS configurations per POSBox are not allowed"
msgid "Multiple Odoo POS configurations per IoT Box are not allowed"
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:91
msgid "Using the POS without a connection to the POSBox (and thus FDM)"
msgid "Using the POS without a connection to the IoT Box (and thus FDM)"
msgstr ""
#: ../../point_of_sale/belgian_fdm/setup.rst:92
@ -506,614 +506,6 @@ msgstr ""
msgid "Use the save button when you are done. You can then select that customer in any future transactions."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:3
msgid "Point of Sale Hardware Setup"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:6
msgid "POSBox Setup Guide"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:11
#: ../../point_of_sale/overview/setup.rst:205
msgid "Prerequisites"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:13
msgid "Before you start setting up your POSBox make sure you have everything. You will need :"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:16
msgid "The POSBox"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:17
msgid "A 2A Power adapter"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:18
msgid "A computer or tablet with an up-to-date web browser"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:19
msgid "A running SaaS or Odoo database with the Point of Sale installed"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:20
msgid "A local network set up with DHCP (this is the default setting)"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:21
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:24
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:25
msgid "An Epson compatible cash drawer"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:26
msgid "An RJ45 Ethernet Cable (optional, Wi-Fi is built in)"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:29
#: ../../point_of_sale/overview/setup.rst:213
msgid "Step By Step Setup Guide"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:32
msgid "Current version of the POSBox (since 2015)"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:36
msgid "Connect peripheral devices"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:38
msgid "Officially supported hardware is listed on `the POS Hardware page <https://www.odoo.com/page/pos-ipad-android-hardware>`_, but other hardware might work as well."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:42
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:45
msgid "**Cash drawer**: The cash drawer should be connected to the printer with an RJ25 cable."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:48
msgid "**Barcode scanner**: Connect your barcode scanner. In order for your barcode scanner to be compatible it must behave as a keyboard and must be configured in **US QWERTY**. It also must end barcodes with an Enter character (keycode 28). This is most likely the default configuration of your barcode scanner."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:54
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:56
msgid "**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. Make sure this will connect the POSBox to the same network as your POS device."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:60
msgid "**Wi-Fi**: The current version of the POSBox has Wi-Fi built in. Make sure not to plug in an Ethernet cable, because all Wi-Fi functionality will be bypassed when a wired network connection is available."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:66
msgid "Power the POSBox"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:68
msgid "Plug the power adapter into the POSBox, a bright red status led should light up."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:72
msgid "Make sure the POSBox is ready"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:74
msgid "Once powered, The POSBox needs a while to boot. Once the POSBox is ready, it should print a status receipt with its IP address. Also the status LED, just next to the red power LED, should be permanently lit green."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:80
#: ../../point_of_sale/overview/setup.rst:292
msgid "Setup the Point of Sale"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:82
msgid "To setup the POSBox in the Point of Sale go to :menuselection:`Point of Sale --> Configuration --> Point of Sale` and select your Point of Sale. Scroll down to the ``PoSBox / Hardware Proxy`` section and activate the options for the hardware you want to use through the POSBox. Specifying the IP of the POSBox is recommended (it is printed on the receipt that gets printed after booting up the POSBox). When the IP is not specified the Point of Sale will attempt to find it on the local network."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:91
msgid "If you are running multiple Point of Sale on the same POSBox, make sure that only one of them has Remote Scanning/Barcode Scanner activated."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:94
msgid "It might be a good idea to make sure the POSBox IP never changes in your network. Refer to your router documentation on how to achieve this."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:99
msgid "Launch the Point of Sale"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:101
msgid "If you didn't specify the POSBox's IP address in the configuration, the POS will need some time to perform a network scan to find the POSBox. This is only done once."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:105
msgid "The Point of Sale is now connected to the POSBox and your hardware should be ready to use."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:109
msgid "Wi-Fi configuration"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:111
msgid "The most recent version of the POSBox has Wi-Fi built in. If you're using an older version you'll need a Linux compatible USB Wi-Fi adapter. Most commercially available Wi-Fi adapters are Linux compatible. Officially supported are Wi-Fi adapters with a Ralink 5370 chipset."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:117
msgid "Make sure not to plug in an Ethernet cable, as all Wi-Fi related functionality will be disabled when a wired network connection is available."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:121
msgid "When the POSBox boots with a Wi-Fi adapter it will start its own Wi-Fi Access Point called \"Posbox\" you can connect to. The receipt that gets printed when the POSBox starts will reflect this. In order to make the POSBox connect to an already existing Wi-Fi network, go to the homepage of the POSBox (indicated on the receipt) and go to the Wi-Fi configuration page. On there you can choose a network to connect to. Note that we only support open and WPA(2)-PSK networks. When connecting to a WPA-secured network, fill in the password field. The POSBox will attempt to connect to the specified network and will print a new POSBox status receipt after it has connected."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:132
msgid "If you plan on permanently setting up the POSBox with Wi-Fi, you can use the \"persistent\" checkbox on the Wi-Fi configuration page when connecting to a network. This will make the network choice persist across reboots. This means that instead of starting up its own \"Posbox\" network it will always attempt to connect to the specified network after it boots."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:139
msgid "When the POSBox fails to connect to a network it will fall back to starting it's own \"Posbox\" Access Point. If connection is lost with a Wi-Fi network after connecting to it, the POSBox will attempt to re-establish connection automatically."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:145
msgid "Multi-POS Configuration"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:147
msgid "The advised way to setup a multi Point of Sale shop is to have one POSBox per Point of Sale. In this case it is mandatory to manually specify the IP address of each POSBox in each Point of Sale. You must also configure your network to make sure the POSBox's IP addresses don't change. Please refer to your router documentation."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:154
msgid "POSBoxless Guide (advanced)"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:158
msgid "If you are running your Point of Sale on a Debian-based Linux distribution, you do not need the POSBox as you can run its software locally. However the installation process is not foolproof. You'll need at least to know how to install and run Odoo. You may also run into issues specific to your distribution or to your particular setup and hardware configuration."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:165
msgid "Drivers for the various types of supported hardware are provided as Odoo modules. In fact, the POSBox runs an instance of Odoo that the Point of Sale communicates with. The instance of Odoo running on the POSBox is very different from a 'real' Odoo instance however. It does not handle *any* business data (eg. POS orders), but only serves as a gateway between the Point of Sale and the hardware."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:172
msgid "The goal of this section will be to set up a local Odoo instance that behaves like the Odoo instance running on the POSBox."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:176
msgid "Image building process"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:178
msgid "We generate the official POSBox images using the scripts in https://github.com/odoo/odoo/tree/11.0/addons/point_of_sale/tools/posbox. More specifically, we run `posbox_create_image.sh <https://github.com/odoo/odoo/blob/11.0/addons/point_of_sale/tools/posbox/posbox_create_image.sh>`_. This builds an image called ``posbox.img``, which we zip and upload to `nightly.odoo.com <https://nightly.odoo.com>`_ for users to download."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:186
msgid "The scripts in this directory might be useful as a reference if you get stuck or want more detail about something."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:190
msgid "Summary of the image creation process"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:192
msgid "The image creation process starts by downloading the latest `Raspbian <https://www.raspbian.org/>`_ image. It then locally mounts this Raspbian image and copies over some files and scripts that will make the Raspbian image turn itself into a POSBox when it boots. These scripts will update Raspbian, remove non-essential packages and install required packages. In order to boot Raspbian we use qemu, which is capable of providing ARM emulation. After this, the emulated Raspbian OS will shut itself down. We then once again locally mount the image, remove the scripts that were used to initialize the image at boot and we copy over some extra configuration files. The resulting image is then ready to be tested and used."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:207
msgid "A Debian-based Linux distribution (Debian, Ubuntu, Mint, etc.)"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:208
msgid "A running Odoo instance you connect to load the Point of Sale"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:209
msgid "You must uninstall any ESC/POS printer driver as it will conflict with Odoo's built-in driver"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:216
msgid "Extra dependencies"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:218
msgid "Because Odoo runs on Python 2, you need to check which version of pip you need to use."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:221
msgid "``# pip --version``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:223
#: ../../point_of_sale/overview/setup.rst:229
msgid "If it returns something like::"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:227
msgid "You need to try pip2 instead."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:233
msgid "You can use pip."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:235
msgid "The driver modules requires the installation of new python modules:"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:237
msgid "``# pip install pyserial``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:239
msgid "``# pip install pyusb==1.0.0b1``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:241
msgid "``# pip install qrcode``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:244
msgid "Access Rights"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:246
msgid "The drivers need raw access to the printer and barcode scanner devices. Doing so requires a bit system administration. First we are going to create a group that has access to USB devices"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:250
msgid "``# groupadd usbusers``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:252
msgid "Then we add the user who will run the OpenERP server to ``usbusers``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:254
msgid "``# usermod -a -G usbusers USERNAME``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:256
msgid "Then we need to create a udev rule that will automatically allow members of ``usbusers`` to access raw USB devices. To do so create a file called ``99-usbusers.rules`` in the ``/etc/udev/rules.d/`` directory with the following content::"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:264
msgid "Then you need to reboot your machine."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:267
msgid "Start the local Odoo instance"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:269
msgid "We must launch the Odoo server with the correct settings"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:271
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:274
msgid "Test the instance"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:276
msgid "Plug all your hardware to your machine's USB ports, and go to ``http://localhost:8069/hw_proxy/status`` refresh the page a few times and see if all your devices are indicated as *Connected*. Possible source of errors are: The paths on the distribution differ from the paths expected by the drivers, another process has grabbed exclusive access to the devices, the udev rules do not apply or a superseded by others."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:284
msgid "Automatically start Odoo"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:286
msgid "You must now make sure that this Odoo install is automatically started after boot. There are various ways to do so, and how to do it depends on your particular setup. Using the init system provided by your distribution is probably the easiest way to accomplish this."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:294
msgid "The IP address field in the POS configuration must be either ``127.0.0.1`` or ``localhost`` if you're running the created Odoo server on the machine that you'll use as the Point of Sale device. You can also leave it empty."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:300
msgid "POSBox Technical Documentation"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:303
msgid "Technical Overview"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:306
msgid "The POSBox Hardware"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:308
msgid "The POSBox's Hardware is based on a `Raspberry Pi 2 <https://www.raspberrypi.org/products/raspberry-pi-2-model-b/>`_, a popular single-board computer. The Raspberry Pi 2 is powered with a 2A micro-usb power adapter. 2A is needed to give enough power to the barcode scanners. The Software is installed on a 8Gb Class 10 or Higher SD Card. All this hardware is easily available worldwide from independent vendors."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:317
msgid "Compatible Peripherals"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:319
msgid "Officially supported hardware is listed on the `POS Hardware page <https://www.odoo.com/page/pos-ipad-android-hardware>`_."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:323
msgid "The POSBox Software"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:325
msgid "The POSBox runs a heavily modified Raspbian Linux installation, a Debian derivative for the Raspberry Pi. It also runs a barebones installation of Odoo which provides the webserver and the drivers. The hardware drivers are implemented as Odoo modules. Those modules are all prefixed with ``hw_*`` and they are the only modules that are running on the POSBox. Odoo is only used for the framework it provides. No business data is processed or stored on the POSBox. The Odoo instance is a shallow git clone of the ``8.0`` branch."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:334
msgid "The root partition on the POSBox is mounted read-only, ensuring that we don't wear out the SD card by writing to it too much. It also ensures that the filesystem cannot be corrupted by cutting the power to the POSBox. Linux applications expect to be able to write to certain directories though. So we provide a ramdisk for /etc and /var (Raspbian automatically provides one for /tmp). These ramdisks are setup by ``setup_ramdisks.sh``, which we run before all other init scripts by running it in ``/etc/init.d/rcS``. The ramdisks are named /etc_ram and /var_ram respectively. Most data from /etc and /var is copied to these tmpfs ramdisks. In order to restrict the size of the ramdisks, we do not copy over certain things to them (eg. apt related data). We then bind mount them over the original directories. So when an application writes to /etc/foo/bar it's actually writing to /etc_ram/foo/bar. We also bind mount / to /root_bypass_ramdisks to be able to get to the real /etc and /var during development."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:350
msgid "Logs of the running Odoo server can be found at:"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:352
msgid "``/var/log/odoo/odoo.log``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:354
msgid "Various POSBox related scripts (eg. wifi-related scripts) running on the POSBox will log to /var/log/syslog and those messages are tagged with ``posbox_*``."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:359
msgid "Accessing the POSBox"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:362
msgid "Local Access"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:364
msgid "If you plug a QWERTY USB keyboard into one of the POSBox's USB ports, and if you connect a computer monitor to the *HDMI* port of the POSBox, you can use it as a small GNU/Linux computer and perform various administration tasks, like viewing some logs."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:369
msgid "The POSBox will automatically log in as root on the default tty."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:372
msgid "Remote Access"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:374
msgid "If you have the POSBox's IP address and an SSH client you can access the POSBox's system remotely. The login credentials are ``pi``/``raspberry``."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:379
msgid "Updating The POSBox Software"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:381
msgid "Only upgrade the POSBox if you experience problems or want to use newly implemented features."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:384
msgid "The best way to update the POSBox software is to download a new version of the image and flash the SD-Card with it. This operation is described in detail in `this tutorial <http://elinux.org/RPi_Easy_SD_Card_Setup>`_, just replace the standard Raspberry Pi image with the latest one found at `the official POSBox image page <http://nightly.odoo.com/master/posbox/>`_. This method of upgrading will ensure that you're running the latest version of the POSBox software."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:393
msgid "The second way of upgrading is through the built in upgrade interface that can be reached through the POSBox homepage. The nice thing about upgrading like this is that you don't have to flash a new image. This upgrade method is limited to what it can do however. It can not eg. update installed configuration files (like eg. /etc/hostapd.conf). It can only upgrade:"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:400
msgid "The internal Odoo application"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:401
msgid "Scripts in the folder ``odoo/addons/point_of_sale/tools/posbox/configuration/``"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:403
msgid "When in doubt, always use the first method of upgrading."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:406
msgid "Troubleshoot"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:409
msgid "The POS cannot connect to the POSBox"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:411
msgid "The easiest way to make sure the POSBox is properly set-up is to turn it on with the printer plugged in as it will print a receipt indicating any error if encountered or the POSBox's IP address in case of success. If no receipt is printed, check the following steps:"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:415
msgid "Make sure the POSBox is powered on, indicated by a brightly lit red status LED."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:417
msgid "Make sure the POSBox is ready, this is indicated by a brightly lit green status LED just next to the red power status LED. The POSBox should be ready ~2 minutes after it is started."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:420
msgid "Make sure the POSBox is connected to the same network as your POS device. Both the device and the POSBox should be visible in the list of connected devices on your network router."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:423
msgid "Make sure that your LAN is set up with DHCP, and gives IP addresses in the range 192.168.0.X, 192.168.1.X, 10.0.0.X. If you cannot setup your LAN that way, you must manually set up your POSBox's IP address."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:427
msgid "If you have specified the POSBox's IP address in the configuration, make sure it correspond to the printed on the POSBox's status receipt."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:430
msgid "Make sure that the POS is not loaded over HTTPS."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:431
msgid "A bug in Firefox's HTTP implementation prevents the autodiscovery from working reliably. When using Firefox you should manually set up the POSBox's IP address in the POS configuration."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:436
msgid "The Barcode Scanner is not working"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:438
msgid "The barcode scanner must be configured in US QWERTY and emit an Enter after each barcode. This is the default configuration of most barcode readers. Refer to the barcode reader documentation for more information."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:442
msgid "The POSBox needs a 2A power supply to work with some barcode scanners. If you are not using the provided power supply, make sure the one you use has enough power."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:445
msgid "Some barcode scanners will need more than 2A and will not work, or will work unreliably, even with the provided power supply. In those case you can plug the barcode scanner in a self-powered USB hub."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:448
msgid "Some poorly built barcode scanners do not advertise themselves as barcode scanners but as a usb keyboard instead, and will not be recognized by the POSBox."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:453
msgid "The Barcode Scanner is not working reliably"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:455
msgid "Make sure that no more than one device with 'Scan via Proxy'/'Barcode Scanner' enabled are connected to the POSBox at the same time."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:460
msgid "Printing the receipt takes too much time"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:462
msgid "A small delay before the first print is expected, as the POSBox will do some preprocessing to speed up the next printings. If you suffer delays afterwards it is most likely due to poor network connection between the POS and the POSBox."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:468
msgid "Some characters are not correctly printed on the receipt"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:470
msgid "The POSBox does not support all languages and characters. It currently supports Latin and Cyrillic based scripts, with basic Japanese support."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:475
msgid "The printer is offline"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:477
msgid "Make sure the printer is connected, powered, has enough paper and has its lid closed, and is not reporting an error. If the error persists, please contact support."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:482
msgid "The cashdrawer does not open"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:484
msgid "The cashdrawer should be connected to the printer and should be activated in the POS configuration."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:488
msgid "Credits"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:489
msgid "The POSBox project was developed by Frédéric van der Essen with the kind help of Gary Malherbe, Fabien Meghazi, Nicolas Wisniewsky, Dimitri Del Marmol, Joren Van Onder and Antony Lesuisse."
msgstr ""
#: ../../point_of_sale/overview/setup.rst:493
msgid "This development would not have been possible without the Indiegogo campaign and those who contributed to it. Special thanks goes to the partners who backed the campaign with founding partner bundles:"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:497
msgid "Camptocamp"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:498
msgid "BHC"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:499
msgid "openBig"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:500
msgid "Eeezee-IT"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:501
msgid "Solarsis LDA"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:502
msgid "ACSONE"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:503
msgid "Vauxoo"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:504
msgid "Ekomurz"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:505
msgid "Datalp"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:506
msgid "Dao Systems"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:507
msgid "Eggs Solutions"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:508
msgid "OpusVL"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:510
msgid "And also the partners who've backed the development with the Founding POSBox Bundle:"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:513
msgid "Willow IT"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:514
msgid "E\\. Akhalwaya & Sons"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:515
msgid "Multibase"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:516
msgid "Mindesa"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:517
msgid "bpso.biz"
msgstr ""
#: ../../point_of_sale/overview/setup.rst:518
msgid "Shine IT."
msgstr ""
#: ../../point_of_sale/overview/start.rst:3
msgid "Getting started with Odoo Point of Sale"
msgstr ""
@ -1230,6 +622,10 @@ msgstr ""
msgid "It's done, you have now closed your first PoS session."
msgstr ""
#: ../../point_of_sale/overview/start.rst:133
msgid "To connect the PoS to hardware with an Odoo IoT Box, please see the section :doc:`../../../iot/connect` and :doc:`../../../iot/pos`"
msgstr ""
#: ../../point_of_sale/restaurant.rst:3
msgid "Advanced Restaurant Features"
msgstr ""
@ -1283,7 +679,7 @@ msgid "To activate the *Order printing* feature, go to :menuselection:`Point of
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:16
msgid "Under the PosBox / Hardware Proxy category, you will find *Order Printers*."
msgid "Under the IoT Box / Hardware Proxy category, you will find *Order Printers*."
msgstr ""
#: ../../point_of_sale/restaurant/kitchen_printing.rst:19
@ -1515,7 +911,7 @@ msgid "In this example, you can see I want to have 275$ in various denomination
msgstr ""
#: ../../point_of_sale/shop/cash_control.rst:24
msgid "When clicking on *->Opening/Closing Values* you will be able to create those values."
msgid "When clicking on **Opening/Closing Values** you will be able to create those values."
msgstr ""
#: ../../point_of_sale/shop/cash_control.rst:31

6
locale/sources/practical.pot
View File

@ -1,14 +1,14 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

6
locale/sources/project.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-26 12:01+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -120,10 +120,6 @@ msgstr ""
msgid "Then, you will be able to publish your result on your website by clicking on the website button in the upper right corner and confirming it in the front end of the website."
msgstr ""
#: ../../project/advanced/feedback.rst:111
msgid ":doc:`claim_issue`"
msgstr ""
#: ../../project/advanced/so_to_task.rst:3
msgid "How to create tasks from sales orders?"
msgstr ""

1716
locale/sources/purchase.pot
View File

File diff suppressed because it is too large Load Diff

534
locale/sources/sales.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-07-23 12:10+0200\n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -160,441 +160,321 @@ msgstr ""
msgid "Invoicing Method"
msgstr ""
#: ../../sales/invoicing/services.rst:3
msgid "Services"
#: ../../sales/invoicing/down_payment.rst:3
msgid "Request a down payment"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:3
msgid "How to invoice milestones of a project?"
#: ../../sales/invoicing/down_payment.rst:5
msgid "A down payment is an initial, partial payment, with the agreement that the rest will be paid later. For expensive orders or projects, it is a way to protect yourself and make sure your customer is serious."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:5
msgid "There are different kind of service sales: prepaid volume of hours/days (e.g. support contract), billing based on time and material (e.g. billing consulting hours) or a fixed price contract (e.g. a project)."
#: ../../sales/invoicing/down_payment.rst:10
msgid "First time you request a down payment"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:9
msgid "In this section, we will have a look at how to invoice milestones of a project."
#: ../../sales/invoicing/down_payment.rst:12
msgid "When you confirm a sale, you can create an invoice and select a down payment option. It can either be a fixed amount or a percentage of the total amount."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:12
msgid "Milestone invoicing can be used for expensive or large scale projects, with each milestone representing a clear sequence of work that will incrementally build up to the completion of the contract. For example, a marketing agency hired for a new product launch could break down a project into the following milestones, each of them considered as one service with a fixed price on the sale order :"
#: ../../sales/invoicing/down_payment.rst:16
msgid "The first time you request a down payment you can select an income account and a tax setting that will be reused for next down payments."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:19
msgid "Milestone 1 : Marketing strategy audit - 5 000 euros"
#: ../../sales/invoicing/down_payment.rst:22
msgid "You will then see the invoice for the down payment."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:21
msgid "Milestone 2 : Brand Identity - 10 000 euros"
#: ../../sales/invoicing/down_payment.rst:27
msgid "On the subsequent or final invoice, any prepayment made will be automatically deducted."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:23
msgid "Milestone 3 : Campaign launch & PR - 8 500 euros"
#: ../../sales/invoicing/down_payment.rst:34
msgid "Modify the income account and customer taxes"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:25
msgid "In this case, an invoice will be sent to the customer each time a milestone will be successfully reached. That invoicing method is comfortable both for the company which is ensured to get a steady cash flow throughout the project lifetime and for the client who can monitor the project's progress and pay in several times."
#: ../../sales/invoicing/down_payment.rst:36
msgid "From the products list, search for *Down Payment*."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:32
msgid "You can also use milestones to invoice percentages of the entire project. For example, for a million euros project, your company might require a 15% upfront payment, 30% at the midpoint and the balance at the contract conclusion. In that case, each payment will be considered as one milestone."
#: ../../sales/invoicing/down_payment.rst:41
msgid "You can then edit it, under the invoicing tab you will be able to change the income account & customer taxes."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:39
#: ../../sales/invoicing/services/reinvoice.rst:26
#: ../../sales/invoicing/services/reinvoice.rst:95
#: ../../sales/invoicing/services/support.rst:17
#: ../../sales/send_quotations/quote_template.rst:10
msgid "Configuration"
#: ../../sales/invoicing/expense.rst:3
msgid "Re-invoice expenses to customers"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:42
msgid "Install the Sales application"
#: ../../sales/invoicing/expense.rst:5
msgid "It often happens that your employees have to spend their personal money while working on a project for your client. Let's take the example of an consultant paying an hotel to work on the site of your client. As a company, you would like to be able to invoice that expense to your client."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:44
#: ../../sales/invoicing/services/reinvoice.rst:28
msgid "In order to sell services and to send invoices, you need to install the **Sales** application, from the **Apps** icon."
#: ../../sales/invoicing/expense.rst:12
#: ../../sales/invoicing/time_materials.rst:64
msgid "Expenses configuration"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:51
msgid "Create products"
#: ../../sales/invoicing/expense.rst:14
#: ../../sales/invoicing/time_materials.rst:66
msgid "To track & invoice expenses, you will need the expenses app. Go to :menuselection:`Apps --> Expenses` to install it."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:53
msgid "In Odoo, each milestone of your project is considered as a product. From the **Sales** application, use the menu :menuselection:`Sales --> Products`, create a new product with the following setup:"
#: ../../sales/invoicing/expense.rst:17
#: ../../sales/invoicing/time_materials.rst:69
msgid "You should also activate the analytic accounts feature to link expenses to the sales order, to do so, go to :menuselection:`Invoicing --> Configuration --> Settings` and activate *Analytic Accounting*."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:57
msgid "**Name**: Strategy audit"
#: ../../sales/invoicing/expense.rst:22
#: ../../sales/invoicing/time_materials.rst:74
msgid "Add expenses to your sales order"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:59
#: ../../sales/invoicing/services/support.rst:50
msgid "**Product Type**: Service"
#: ../../sales/invoicing/expense.rst:24
#: ../../sales/invoicing/time_materials.rst:76
msgid "From the expense app, you or your consultant can create a new one, e.g. the hotel for the first week on the site of your customer."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:61
msgid "**Invoicing Policy**: Delivered Quantities, since you will invoice your milestone after it has been delivered"
#: ../../sales/invoicing/expense.rst:27
#: ../../sales/invoicing/time_materials.rst:79
msgid "You can then enter a relevant description and select an existing product or create a new one from right there."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:64
msgid "**Track Service**: Manually set quantities on order, as you complete each milestone, you will manually update their quantity from the **Delivered** tab on your sale order"
#: ../../sales/invoicing/expense.rst:33
#: ../../sales/invoicing/time_materials.rst:85
msgid "Here, we are creating a *Hotel* product:"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:72
msgid "Apply the same configuration for the others milestones."
#: ../../sales/invoicing/expense.rst:38
msgid "Under the invoicing tab, select *Delivered quantities* and either *At cost* or *Sales price* as well depending if you want to invoice the cost of your expense or a previously agreed on sales price."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:75
msgid "Managing your project"
#: ../../sales/invoicing/expense.rst:45
#: ../../sales/invoicing/time_materials.rst:97
msgid "To modify or create more products go to :menuselection:`Expenses --> Configuration --> Expense products`."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:78
msgid "Quotations and sale orders"
#: ../../sales/invoicing/expense.rst:48
#: ../../sales/invoicing/time_materials.rst:100
msgid "Back on the expense, add the original sale order in the expense to submit."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:80
msgid "Now that your milestones (or products) are created, you can create a quotation or a sale order with each line corresponding to one milestone. For each line, set the **Ordered Quantity** to ``1`` as each milestone is completed once. Once the quotation is confirmed and transformed into a sale order, you will be able to change the delivered quantities when the corresponding milestone has been achieved."
#: ../../sales/invoicing/expense.rst:54
#: ../../sales/invoicing/time_materials.rst:106
msgid "It can then be submitted to the manager, approved and finally posted."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:91
#: ../../sales/invoicing/expense.rst:65
#: ../../sales/invoicing/time_materials.rst:117
msgid "It will then be in the sales order and ready to be invoiced."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:3
msgid "Invoice based on delivered or ordered quantities"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:5
msgid "Depending on your business and what you sell, you have two options for invoicing:"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:8
msgid "Invoice on ordered quantity: invoice the full order as soon as the sales order is confirmed."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:10
msgid "Invoice on delivered quantity: invoice on what you delivered even if it's a partial delivery."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:13
msgid "Invoice on ordered quantity is the default mode."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:15
msgid "The benefits of using *Invoice on delivered quantity* depends on your type of business, when you sell material, liquids or food in large quantities the quantity might diverge a little bit and it is therefore better to invoice the actual delivered quantity."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:21
msgid "You also have the ability to invoice manually, letting you control every options: invoice ready to invoice lines, invoice a percentage (advance), invoice a fixed advance."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:26
msgid "Decide the policy on a product page"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:28
msgid "From any products page, under the invoicing tab you will find the invoicing policy and select the one you want."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:35
msgid "Send the invoice"
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:37
msgid "Once you confirm the sale, you can see your delivered and invoiced quantities."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:43
msgid "If you set it in ordered quantities, you can invoice as soon as the sale is confirmed. If however you selected delivered quantities, you will first have to validate the delivery."
msgstr ""
#: ../../sales/invoicing/invoicing_policy.rst:47
msgid "Once the products are delivered, you can invoice your customer. Odoo will automatically add the quantities to invoiced based on how many you delivered if you did a partial delivery."
msgstr ""
#: ../../sales/invoicing/milestone.rst:3
msgid "Invoice project milestones"
msgstr ""
#: ../../sales/invoicing/milestone.rst:5
msgid "Milestone invoicing can be used for expensive or large-scale projects, with each milestone representing a clear sequence of work that will incrementally build up to the completion of the contract. This invoicing method is comfortable both for the company which is ensured to get a steady cash flow throughout the project lifetime and for the client who can monitor the project's progress and pay in several installments."
msgstr ""
#: ../../sales/invoicing/milestone.rst:13
msgid "Create milestone products"
msgstr ""
#: ../../sales/invoicing/milestone.rst:15
msgid "In Odoo, each milestone of your project is considered as a product. To configure products to work this way, go to any product form."
msgstr ""
#: ../../sales/invoicing/milestone.rst:18
msgid "You have to set the product type as *Service* under general information and select *Milestones* in the sales tab."
msgstr ""
#: ../../sales/invoicing/milestone.rst:25
msgid "Invoice milestones"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:93
msgid "Let's assume that your first milestone (the strategy audit) has been successfully delivered and you want to invoice it to your customer. On the sale order, click on **Edit** and set the **Delivered Quantity** of the related product to ``1``."
#: ../../sales/invoicing/milestone.rst:27
msgid "From the sales order, you can manually edit the quantity delivered as you complete a milestone."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:99
msgid "As soon as the above modification has been saved, you will notice that the color of the line has changed to blue, meaning that the service can now be invoiced. In the same time, the invoice status of the SO has changed from **Nothing To Invoice** to **To Invoice**"
#: ../../sales/invoicing/milestone.rst:33
msgid "You can then invoice that first milestone."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:104
msgid "Click on **Create invoice** and, in the new window that pops up, select **Invoiceable lines** and validate. It will create a new invoice (in draft status) with only the **strategy audit** product as invoiceable."
#: ../../sales/invoicing/proforma.rst:3
#: ../../sales/invoicing/proforma.rst:22
msgid "Send a pro-forma invoice"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:112
msgid "In order to be able to invoice a product, you need to set up the **Accounting** application and to configure an accounting journal and a chart of account. Click on the following link to learn more: :doc:`../../../accounting/overview/getting_started/setup`"
#: ../../sales/invoicing/proforma.rst:5
msgid "A pro-forma invoice is an abridged or estimated invoice in advance of a delivery of goods. It notes the kind and quantity of goods, their value, and other important information such as weight and transportation charges. Pro-forma invoices are commonly used as preliminary invoices with a quotation, or for customs purposes in importation. They differ from a normal invoice in not being a demand or request for payment."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:117
msgid "Back on your sale order, you will notice that the **Invoiced** column of your order line has been updated accordingly and that the **Invoice Status** is back to **Nothing to Invoice**."
#: ../../sales/invoicing/proforma.rst:13
#: ../../sales/send_quotations/different_addresses.rst:10
msgid "Activate the feature"
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:121
msgid "Follow the same workflow to invoice your remaining milestones."
#: ../../sales/invoicing/proforma.rst:15
msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Pro-Forma Invoice* feature."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:124
msgid ":doc:`reinvoice`"
#: ../../sales/invoicing/proforma.rst:24
msgid "From any quotation or sales order, you know have an option to send a pro-forma invoice."
msgstr ""
#: ../../sales/invoicing/services/milestones.rst:125
#: ../../sales/invoicing/services/reinvoice.rst:185
msgid ":doc:`support`"
#: ../../sales/invoicing/proforma.rst:30
msgid "When you click on send, Odoo will send an email with the pro-forma invoice in attachment."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:3
msgid "How to re-invoice expenses to your customers?"
#: ../../sales/invoicing/subscriptions.rst:3
msgid "Sell subscriptions"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:5
msgid "It often happens that your employees have to spend their personal money while working on a project for your client. Let's take the example of an employee paying a parking spot for a meeting with your client. As a company, you would like to be able to invoice that expense to your client."
#: ../../sales/invoicing/subscriptions.rst:5
msgid "Selling subscription products will give you predictable revenue, making planning ahead much easier."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:11
msgid "In this documentation we will see two use cases. The first, very basic, consists of invoicing a simple expense to your client like you would do for a product. The second, more advanced, will consist of invoicing expenses entered in your expense system by your employees directly to your customer."
#: ../../sales/invoicing/subscriptions.rst:9
msgid "Make a subscription from a sales order"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:18
msgid "Use case 1: Simple expense invoicing"
#: ../../sales/invoicing/subscriptions.rst:11
msgid "From the sales app, create a quotation to the desired customer, and select the subscription product your previously created."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:20
msgid "Let's take the following example. You are working on a promotion campaign for one of your customers (``Agrolait``) and you have to print a lot of copies. Those copies are an expense for your company and you would like to invoice them."
#: ../../sales/invoicing/subscriptions.rst:14
msgid "When you confirm the sale the subscription will be created automatically. You will see a direct link from the sales order to the Subscription in the upper right corner."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:35
msgid "Create product to be expensed"
#: ../../sales/invoicing/time_materials.rst:3
msgid "Invoice based on time and materials"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:37
msgid "You will need now to create a product called ``Copies``."
#: ../../sales/invoicing/time_materials.rst:5
msgid "Time and Materials is generally used in projects in which it is not possible to accurately estimate the size of the project, or when it is expected that the project requirements would most likely change."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:39
#: ../../sales/invoicing/services/reinvoice.rst:112
msgid "From your **Sales** module, go to :menuselection:`Sales --> Products` and create a product as follows:"
#: ../../sales/invoicing/time_materials.rst:9
msgid "This is opposed to a fixed-price contract in which the owner agrees to pay the contractor a lump sum for the fulfillment of the contract no matter what the contractors pay their employees, sub-contractors, and suppliers."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:42
msgid "**Product type**: consumable"
#: ../../sales/invoicing/time_materials.rst:14
msgid "For this documentation I will use the example of a consultant, you will need to invoice their time, their various expenses (transport, lodging, ...) and purchases."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:44
msgid "**Invoicing policy**: on delivered quantities (you will manually set the quantities to invoice on the sale order)"
#: ../../sales/invoicing/time_materials.rst:19
msgid "Invoice time configuration"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:51
msgid "Create a sale order"
#: ../../sales/invoicing/time_materials.rst:21
msgid "To keep track of progress in the project, you will need the *Project* app. Go to :menuselection:`Apps --> Project` to install it."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:53
msgid "Now that your product is correctly set up, you can create a sale order for that product (from the menu :menuselection:`Sales --> Sales Orders`) with the ordered quantities set to 0. Click on **Confirm the Sale** to create the sale order. You will be able then to manually change the delivered quantities on the sale order to reinvoice the copies to your customer."
#: ../../sales/invoicing/time_materials.rst:24
msgid "In *Project* you will use timesheets, to do so go to :menuselection:`Project --> Configuration --> Settings` and activate the *Timesheets* feature."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:64
#: ../../sales/invoicing/services/reinvoice.rst:177
msgid "Invoice expense to your client"
#: ../../sales/invoicing/time_materials.rst:32
msgid "Invoice your time spent"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:66
msgid "At the end of the month, you have printed ``1000`` copies on behalf of your client and you want to re-invoice them. From the related sale order, click on **Delivered Quantities**, manually enter the correct amount of copies and click on **Save**. Your order line will turn blue, meaning that it is ready to be invoiced. Click on **Create invoice**."
#: ../../sales/invoicing/time_materials.rst:34
msgid "From a product page set as a service, you will find two options under the invoicing tab, select both *Timesheets on tasks* and *Create a task in a new project*."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:73
msgid "The total amount on your sale order will be of 0 as it is computed on the ordered quantities. It is your invoice which will compute the correct amount due by your customer."
#: ../../sales/invoicing/time_materials.rst:41
msgid "You could also add the task to an existing project."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:77
msgid "The invoice generated is in draft, so you can always control the quantities and change the amount if needed. You will notice that the amount to be invoiced is based here on the delivered quantities."
#: ../../sales/invoicing/time_materials.rst:43
msgid "Once confirming a sales order, you will now see two new buttons, one for the project overview and one for the current task."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:84
msgid "Click on validate to issue the payment to your customer."
#: ../../sales/invoicing/time_materials.rst:49
msgid "You will directly be in the task if you click on it, you can also access it from the *Project* app."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:87
msgid "Use case 2: Invoice expenses via the expense module"
#: ../../sales/invoicing/time_materials.rst:52
msgid "Under timesheets, you can assign who works on it. You can or they can add how many hours they worked on the project so far."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:89
msgid "To illustrate this case, let's imagine that your company sells some consultancy service to your customer ``Agrolait`` and both parties agreed that the distance covered by your consultant will be re-invoiced at cost."
#: ../../sales/invoicing/time_materials.rst:58
msgid "From the sales order, you can then invoice those hours."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:97
msgid "Here, you will need to install two more modules:"
#: ../../sales/invoicing/time_materials.rst:90
msgid "under the invoicing tab, select *Delivered quantities* and either *At cost* or *Sales price* as well depending if you want to invoice the cost of your expense or a previously agreed on sales price."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:99
msgid "Expense Tracker"
#: ../../sales/invoicing/time_materials.rst:120
msgid "Invoice purchases"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:101
msgid "Accounting, where you will need to activate the analytic accounting from the settings"
#: ../../sales/invoicing/time_materials.rst:122
msgid "The last thing you might need to add to the sale order is purchases made for it."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:108
msgid "Create a product to be expensed"
#: ../../sales/invoicing/time_materials.rst:125
msgid "You will need the *Purchase Analytics* feature, to activate it, go to :menuselection:`Invoicing --> Configuration --> Settings` and select *Purchase Analytics*."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:110
msgid "You will now need to create a product called ``Kilometers``."
#: ../../sales/invoicing/time_materials.rst:129
msgid "While making the purchase order don't forget to add the right analytic account."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:115
msgid "Product can be expensed"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:117
msgid "Product type: Service"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:119
msgid "Invoicing policy: invoice based on time and material"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:121
msgid "Expense invoicing policy: At cost"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:123
msgid "Track service: manually set quantities on order"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:129
msgid "Create a sales order"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:131
msgid "Still from the Sales module, go to :menuselection:`Sales --> Sales Orders` and add your product **Consultancy** on the order line."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:135
msgid "If your product doesn't exist yet, you can configure it on the fly from the SO. Just type the name on the **product** field and click on **Create and edit** to configure it."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:139
msgid "Depending on your product configuration, an **Analytic Account** may have been generated automatically. If not, you can easily create one in order to link your expenses to the sale order. Do not forget to confirm the sale order."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:148
msgid "Refer to the documentation :doc:`../../../accounting/others/analytic/usage` to learn more about that concept."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:152
msgid "Create expense and link it to SO"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:154
msgid "Let's assume that your consultant covered ``1.000km`` in October as part of his consultancy project. We will create a expense for it and link it to the related sales order thanks to the analytic account."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:158
msgid "Go to the **Expenses** module and click on **Create**. Record your expense as follows:"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:161
msgid "**Expense description**: Kilometers October 2015"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:163
msgid "**Product**: Kilometers"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:165
msgid "**Quantity**: 1.000"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:167
msgid "**Analytic account**: SO0019 - Agrolait"
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:172
msgid "Click on **Submit to manager**. As soon as the expense has been validated and posted to the journal entries, a new line corresponding to the expense will automatically be generated on the sale order."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:179
msgid "You can now invoice the invoiceable lines to your customer."
msgstr ""
#: ../../sales/invoicing/services/reinvoice.rst:186
msgid ":doc:`milestones`"
msgstr ""
#: ../../sales/invoicing/services/support.rst:3
msgid "How to invoice a support contract (prepaid hours)?"
msgstr ""
#: ../../sales/invoicing/services/support.rst:5
msgid "There are different kinds of service sales: prepaid volume of hours/days (e.g. support contract), billing based on time and material (e.g. billing consulting hours) and a fixed price contract (e.g. a project)."
msgstr ""
#: ../../sales/invoicing/services/support.rst:9
msgid "In this section, we will have a look at how to sell and keep track of a pre-paid support contract."
msgstr ""
#: ../../sales/invoicing/services/support.rst:12
msgid "As an example, you may sell a pack of ``50 Hours`` of support at ``$25,000``. The price is fixed and charged initially. But you want to keep track of the support service you did for the customer."
msgstr ""
#: ../../sales/invoicing/services/support.rst:20
msgid "Install the Sales and Timesheet applications"
msgstr ""
#: ../../sales/invoicing/services/support.rst:22
msgid "In order to sell services, you need to install the **Sales** application, from the **Apps** icon. Install also the **Timesheets** application if you want to track support services you worked on every contract."
msgstr ""
#: ../../sales/invoicing/services/support.rst:33
msgid "Create Products"
msgstr ""
#: ../../sales/invoicing/services/support.rst:35
msgid "By default, products are sold by number of units. In order to sell services ``per hour``, you must allow using multiple unit of measures. From the **Sales** application, go to the menu :menuselection:`Configuration --> Settings`. From this screen, activate the multiple **Unit of Measures** option."
msgstr ""
#: ../../sales/invoicing/services/support.rst:44
msgid "In order to sell a support contract, you must create a product for every support contract you sell. From the **Sales** application, use the menu :menuselection:`Sales --> Products`, create a new product with the following setup:"
msgstr ""
#: ../../sales/invoicing/services/support.rst:48
msgid "**Name**: Technical Support"
msgstr ""
#: ../../sales/invoicing/services/support.rst:52
msgid "**Unit of Measure**: Hours"
msgstr ""
#: ../../sales/invoicing/services/support.rst:54
msgid "**Invoicing Policy**: Ordered Quantities, since the service is prepaid, we will invoice the service based on what has been ordered, not based on delivered quantities."
msgstr ""
#: ../../sales/invoicing/services/support.rst:58
msgid "**Track Service**: Timesheet on contracts. An analytic account will automatically be created for every order containing this service so that you can track hours in the related account."
msgstr ""
#: ../../sales/invoicing/services/support.rst:66
msgid "There are different ways to track the service related to a sales order or product sold. With the above configuration, you can only sell one support contract per order. If your customer orders several service contracts on timesheet, you will have to split the quotation into several orders."
msgstr ""
#: ../../sales/invoicing/services/support.rst:72
msgid "Note that you can sell in different unit of measure than hours, example: days, pack of 40h, etc. To do that, just create a new unit of measure in the **Unit of Measure** category and set a conversion ratio compared to **Hours** (example: ``1 day = 8 hours``)."
msgstr ""
#: ../../sales/invoicing/services/support.rst:78
msgid "Managing support contract"
msgstr ""
#: ../../sales/invoicing/services/support.rst:81
msgid "Quotations and Sales Orders"
msgstr ""
#: ../../sales/invoicing/services/support.rst:83
msgid "Once the product is created, you can create a quotation or a sales order with the related product. Once the quotation is confirmed and transformed into a sales order, your users will be able to record services related to this support contract using the timesheet application."
msgstr ""
#: ../../sales/invoicing/services/support.rst:93
msgid "Timesheets"
msgstr ""
#: ../../sales/invoicing/services/support.rst:95
msgid "To track the service you do on a specific contract, you should use the timesheet application. An analytic account related to the sale order has been automatically created (``SO009 - Agrolait`` on the screenshot here above), so you can start tracking services as soon as it has been sold."
msgstr ""
#: ../../sales/invoicing/services/support.rst:104
msgid "Control delivered support on the sales order"
msgstr ""
#: ../../sales/invoicing/services/support.rst:106
msgid "From the **Sales** application, use the menu :menuselection:`Sales --> Sales Orders` to control the progress of every order. On the sales order line related to the support contract, you should see the **Delivered Quantities** that are updated automatically, based on the number of hours in the timesheet."
msgstr ""
#: ../../sales/invoicing/services/support.rst:116
msgid "Upselling and renewal"
msgstr ""
#: ../../sales/invoicing/services/support.rst:118
msgid "If the number of hours you performed on the support contract is bigger or equal to the number of hours the customer purchased, you are suggested to sell an extra contract to the customer since they used all their quota of service. Periodically (ideally once every two weeks), you should check the sales order that are in such a case. To do so, go to :menuselection:`Sales --> Invoicing --> Orders to Upsell`."
msgstr ""
#: ../../sales/invoicing/services/support.rst:127
msgid "If you use Odoo CRM, a good practice is to create an opportunity for every sale order in upselling invoice status so that you easily track your upselling effort."
msgstr ""
#: ../../sales/invoicing/services/support.rst:131
msgid "If you sell an extra support contract, you can either add a new line on the existing sales order (thus, you continue to timesheet on the same order) or create a new order (thus, people will timesheet their hours on the new contract). To unmark the sales order as **Upselling**, you can set the sales order as done and it will disappear from your upselling list."
msgstr ""
#: ../../sales/invoicing/services/support.rst:138
msgid "Special Configuration"
msgstr ""
#: ../../sales/invoicing/services/support.rst:140
msgid "When creating the product form, you may set a different approach to track the service:"
msgstr ""
#: ../../sales/invoicing/services/support.rst:143
msgid "**Create task and track hours**: in this mode, a task is created for every sales order line. Then when you do the timesheet, you don't record hours on a sales order/contract, but you record hours on a task (that represents the contract). The advantage of this solution is that it allows to sell several service contracts within the same sales order."
msgstr ""
#: ../../sales/invoicing/services/support.rst:150
msgid "**Manually**: you can use this mode if you don't record timesheets in Odoo. The number of hours you worked on a specific contract can be recorded manually on the sales order line directly, in the delivered quantity field."
msgstr ""
#: ../../sales/invoicing/services/support.rst:156
msgid ":doc:`../../../inventory/settings/products/uom`"
#: ../../sales/invoicing/time_materials.rst:135
msgid "Once the PO is confirmed and received, you can create the vendor bill, this will automatically add it to the SO where you can invoice it."
msgstr ""
#: ../../sales/products_prices.rst:3
@ -901,10 +781,6 @@ msgstr ""
msgid "In Odoo you can configure different addresses for delivery and invoicing. This is key, not everyone will have the same delivery location as their invoice location."
msgstr ""
#: ../../sales/send_quotations/different_addresses.rst:10
msgid "Activate the feature"
msgstr ""
#: ../../sales/send_quotations/different_addresses.rst:12
msgid "Go to :menuselection:`SALES --> Configuration --> Settings` and activate the *Customer Addresses* feature."
msgstr ""
@ -1054,6 +930,10 @@ msgstr ""
msgid "If you often sell the same products or services, you can save a lot of time by creating custom quotation templates. By using a template you can send a complete quotation in no time."
msgstr ""
#: ../../sales/send_quotations/quote_template.rst:10
msgid "Configuration"
msgstr ""
#: ../../sales/send_quotations/quote_template.rst:12
msgid "For this feature to work, go to :menuselection:`Sales --> Configuration --> Settings` and activate *Quotations Templates*."
msgstr ""