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

[I18N] Update translation terms from Transifex

Browse Source
This commit is contained in:
Odoo Translation Bot
2019-11-20 10:27:13 +01:00
parent 3ae6a2b39b
commit 66fc093cc4
84 changed files with 41067 additions and 33874 deletions
Download Patch File Download Diff File Expand all files Collapse all files
locale/ar/LC_MESSAGES/accounting.po
+516 -545
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/crm.po
+158 -11
View File
@@ -3,13 +3,18 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Mustafa Rawi <mustafa@cubexco.com>, 2019
# hoxhe Aits <hoxhe0@gmail.com>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: hoxhe Aits <hoxhe0@gmail.com>, 2019\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -33,42 +38,48 @@ msgstr ""
msgid ""
"The system can generate leads instead of opportunities, in order to add a "
"qualification step before converting a *Lead* into an *Opportunity* and "
"assigning to the right sales people. You can activate this mode from the CRM"
" Settings. It applies to all your sales channels by default. But you can "
"make it specific for specific channels from their configuration form."
"assigning to the right sales people."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:13
#: ../../crm/acquire_leads/convert.rst:9
msgid ""
"You can activate this mode from the CRM Settings. It applies to all your "
"sales channels by default. But you can make it specific for specific "
"channels from their configuration form."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:14
#: ../../crm/acquire_leads/generate_from_website.rst:41
#: ../../crm/optimize/onsip.rst:13 ../../crm/track_leads/lead_scoring.rst:12
#: ../../crm/acquire_leads/lead_mining.rst:8 ../../crm/optimize/onsip.rst:13
#: ../../crm/track_leads/lead_scoring.rst:12
#: ../../crm/track_leads/prospect_visits.rst:12
msgid "Configuration"
msgstr ""
#: ../../crm/acquire_leads/convert.rst:15
#: ../../crm/acquire_leads/convert.rst:16
msgid ""
"For this feature to work, go to :menuselection:`CRM --> Configuration --> "
"Settings` and activate the *Leads* feature."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:21
#: ../../crm/acquire_leads/convert.rst:22
msgid ""
"You will now have a new submenu *Leads* under *Leads* where they will "
"aggregate."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:28
#: ../../crm/acquire_leads/convert.rst:29
msgid "Convert a lead into an opportunity"
msgstr ""
#: ../../crm/acquire_leads/convert.rst:30
#: ../../crm/acquire_leads/convert.rst:31
msgid ""
"When you click on a *Lead* you will have the option to convert it to an "
"opportunity and decide if it should still be assigned to the same "
"channel/person and if you need to create a new customer."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:37
#: ../../crm/acquire_leads/convert.rst:38
msgid ""
"If you already have an opportunity with that customer Odoo will "
"automatically offer you to merge with that opportunity. In the same manner, "
@@ -76,6 +87,44 @@ msgid ""
"customer already exists."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:44
msgid "Merge opportunities"
msgstr "دمج الفرص"
#: ../../crm/acquire_leads/convert.rst:46
msgid ""
"Odoo will also automatically propose to merge opportunities if they have the"
" same email address. When merging opportunities, Odoo merges the information"
" into the opportunity which was created first, giving priority to the "
"information present on the first opportunity."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:51
msgid ""
"No information is lost: data from the other opportunity is logged in the "
"chatter and the information fields for easy access."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:57
msgid ""
"Would you find a duplicate yourself, ...you can also merge opportunities or "
"leads even if the system doesn't propose it."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:60
msgid ""
"Here’s how, from the list view. Select the opportunities or leads you want "
"to merge and the action button will appear. Then, you can select merge."
msgstr ""
#: ../../crm/acquire_leads/convert.rst:66
msgid "..note::"
msgstr ""
#: ../../crm/acquire_leads/convert.rst:67
msgid "It is also possible to merge more than 2 opportunities or leads."
msgstr ""
#: ../../crm/acquire_leads/generate_from_email.rst:3
msgid "Generate leads/opportunities from emails"
msgstr ""
@@ -185,6 +234,104 @@ msgid ""
"CRM settings and refer to :doc:`convert`."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:3
msgid "Lead mining"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:4
msgid ""
"In any business, getting quality leads is essential to keep the business "
"growing. Lead mining allows you to generate leads from scratch directly from"
" your database. Target your leads based on a set of criteria such as the "
"country, the size of the company, the industry your leads are coming from to"
" make them relevant to your business."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:10
msgid ""
"For this feature to work, go to :menuselection:`CRM → Configuration → "
"Settings` and activate the **Lead Mining** feature."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:17
msgid "Start generating leads"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:18
msgid ""
"You will now have a new button **Generate Leads** available in your "
"pipeline. You are also able to create lead mining requests from the "
"**Configuration → Lead Mining Requests** and trough **Leads → Leads** where "
"you have the **Generate Leads** button"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:25
msgid ""
"From there, click on the **Generate Leads** button, a window where you will "
"be able to pick your criteria will pop up."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:32
msgid ""
"When choosing to target Companied and their contacts you can choose the "
"contacts you are getting based on Role or Seniority. When getting contact "
"information make sure to be aware of the latest EU regulation, get more "
"information about General Data Protection Regulation on `Odoo GDPR "
"<http://odoo.com/gdpr>`__,"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:37
msgid ""
"You can decide to filter the leads you are getting depending on the size "
"(number of employees) of the companies. You can pick the countries your "
"leads are coming from. It is possible to pick multiple countries. You can "
"pick the industries your leads are coming from. It is possible to pick "
"multiple countries."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:41
msgid ""
"You can choose the salesperson and the Salesteam the lead will be assigned "
"to. You can also add tags to track your generated leads."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:45
msgid "The generated leads will have the name of the company."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:48
msgid "Pricing"
msgstr "التسعير"
#: ../../crm/acquire_leads/lead_mining.rst:49
msgid ""
"This is an In-App Purchase feature, each generated lead will cost you one "
"credit. If you choose to get contact information each contact will also cost"
" us one additional credit. Here is the pricing for this `feature "
"<https://iap.odoo.com/iap/in-app-services/167?>`__, To buy credits you can "
"either go to CRM > Configuration > Settings > Buy Credits; or go to Settings"
" > In-App Purchases>View my Services"
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:62
msgid ""
"The blue box will automatically tell you how many credits are going to be "
"consumed."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:65
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
#: ../../crm/acquire_leads/lead_mining.rst:67
msgid ""
"More information about `In-App Purchases "
"<https://www.odoo.com/documentation/user/13.0/general/in_app_purchase/in_app_purchase.html?highlight=iap>`__,"
" (IAP)."
msgstr ""
#: ../../crm/acquire_leads/send_quotes.rst:3
msgid "Send quotations"
msgstr ""
locale/ar/LC_MESSAGES/db_management.po
+24 -26
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
@@ -660,76 +660,74 @@ msgstr ""
#: ../../db_management/documentation.rst:39
msgid ""
"In your Odoo instance, click on **Settings**. You will have a section "
"showing you the active users on your database. Click on **Manage access "
"rights.**"
"showing you the active users on your database. Click on **Manage Users.**"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:43
#: ../../db_management/documentation.rst:80
msgid "|settings|"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:43
msgid "|browse_users|"
msgstr ""
#: ../../db_management/documentation.rst:47
#: ../../db_management/documentation.rst:46
msgid "You'll then see the list of your users."
msgstr ""
#: ../../db_management/documentation.rst:52
#: ../../db_management/documentation.rst:51
msgid ""
"The pre-selected filter *Internal Users* shows your paying users (different "
"from the *Portal Users* which are free). If you remove this filter, you'll "
"get all your users (the ones you pay for and the portal ones)"
msgstr ""
#: ../../db_management/documentation.rst:57
#: ../../db_management/documentation.rst:56
msgid ""
"In your list of users, click on the user you want to deactivate. As soon as "
"you are on the userform, go with your mouse cursor on the status **Active** "
"(top right). Click on Active and you will notice that the status will change"
" to **Inactive** immediately."
"you are on the userform, click on the Action drop down menu, and then click "
"on Archive."
msgstr ""
#: ../../db_management/documentation.rst:66
#: ../../db_management/documentation.rst:64
msgid "The user is now deactivated."
msgstr ""
#: ../../db_management/documentation.rst:68
#: ../../db_management/documentation.rst:66
msgid "**Never** deactivate the main user (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:71
#: ../../db_management/documentation.rst:69
msgid "Uninstalling Apps"
msgstr ""
#: ../../db_management/documentation.rst:73
#: ../../db_management/documentation.rst:71
msgid ""
"Make sure you first test what you are about to do on a :ref:`duplicate "
"<duplicate_online>` of your database before making any changes (*especially*"
" installing/uninstalling apps)."
msgstr ""
#: ../../db_management/documentation.rst:77
#: ../../db_management/documentation.rst:75
msgid ""
"In your Odoo instance click on **Settings**; in this app, you will be able "
"to see how many applications you have installed. Click on **Browse Apps** to"
" access the list of your installed applications."
msgstr ""
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:80
msgid "|browse_apps|"
msgstr ""
#: ../../db_management/documentation.rst:85
#: ../../db_management/documentation.rst:83
msgid ""
"In your applications' dashboard, you will see all the icons of your "
"applications. Click on the application you want to uninstall. Then, on the "
"form of the application, click on **Uninstall**."
msgstr ""
#: ../../db_management/documentation.rst:92
#: ../../db_management/documentation.rst:90
msgid ""
"Some applications have dependencies, like Invoicing, eCommerce, etc. "
"Therefore, the system will give you a warning message to advise you of what "
@@ -739,20 +737,20 @@ msgid ""
" click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:99
#: ../../db_management/documentation.rst:97
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:104
#: ../../db_management/documentation.rst:102
msgid "You have finished uninstalling your application."
msgstr ""
#: ../../db_management/documentation.rst:107
#: ../../db_management/documentation.rst:105
msgid "Good to know"
msgstr ""
#: ../../db_management/documentation.rst:109
#: ../../db_management/documentation.rst:107
msgid ""
"**Uninstalling apps, managing users, etc. is up to you**: no one else can "
"know if your business flow is broken better than you. If we were to "
@@ -762,7 +760,7 @@ msgid ""
"operations."
msgstr ""
#: ../../db_management/documentation.rst:115
#: ../../db_management/documentation.rst:113
msgid ""
"**Odoo Apps have dependencies**: this means that you may need to install "
"modules that you do not actively use to access some features of Odoo you "
@@ -772,7 +770,7 @@ msgid ""
"to work properly."
msgstr ""
#: ../../db_management/documentation.rst:122
#: ../../db_management/documentation.rst:120
msgid ""
"**Always test app installation/removal on a duplicate** (or on a free trial "
"database): that way you can know what other apps may be required, etc. This "
locale/ar/LC_MESSAGES/general.po
+105 -9
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
@@ -752,6 +752,110 @@ msgid ""
"company). You must first import the companies and then the persons."
msgstr ""
#: ../../general/in_app_purchase.rst:3
msgid "In-App Purchase"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:3
msgid "General guide about In-App Purchase (IAP) Services"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:4
msgid ""
"In-App Purchases (IAP) gives access to additional services through Odoo. For"
" instance, it allows me to send SMS Text Messages or to send Invoices by "
"post directly from my database."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:7
msgid "Buying Credits"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:8
msgid ""
"Each IAP Service relies on prepaid credits to work and has its own pricing. "
"To consult my current balance or to recharge my account, go to *Settings> "
"Odoo IAP > View my Services*."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:13
msgid ""
"If I am on Odoo Online (SAAS) and have the Enterprise version, I benefit "
"from free credits to test our IAP features."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:16
msgid "IAP accounts"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:17
msgid ""
"Credits to use IAP services are stored on IAP accounts, which are specific "
"to each service and database. By default, IAP accounts are common to all "
"companies, but can be restricted to specific ones by going to *Settings app "
"> Activate the Developer Mode > Technical Settings > IAP Accoun*."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:23
msgid "IAP Portal"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:24
msgid ""
"The IAP Portal is a platform regrouping my IAP Services. It is accessible "
"from *Settings app > Odoo IAP > View my Services*. From there, I can view my"
" current balance, recharge my credits, review my consumption and set a "
"reminder to when credits are low."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:30
msgid "Get notified when credits are low"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:31
msgid ""
"To be notified when it’s time to recharge my credits, I’ll go to my IAP "
"Portal through *Settings app> Odoo IAP > View my Services*, unfold a service"
" and mark the Receive threshold warning option. Then, I’ll provide a minimum"
" amount of credits and email addresses. Now, every time that the limit is "
"reached, an automatic reminder will be sent to by email!"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:38
msgid "IAP services available"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:39
msgid ""
"Different services are available depending on the hosting type of your "
"Database:"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:41
msgid ""
"*Odoo Online (SAAS)*: only the IAP services provided by Odoo can be used "
"(i.e. the SMS, Snailmail, Reveal and Partner Autocomplete features);"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:43
msgid ""
"*Odoo.sh and Odoo Enterprise (on-premise)*: both the services provided by "
"Odoo and by third-party apps can be used."
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:46
msgid "Offering my own services"
msgstr ""
#: ../../general/in_app_purchase/in_app_purchase.rst:47
msgid ""
"I am more than welcome to offer my own IAP services through Odoo Apps! It is"
" the perfect opportunity to get recurring revenue for an ongoing service use"
" rather than — and possibly instead of — a sole initial purchase. Please, "
"find more information at: `In-App Purchase "
"<https://www.odoo.com/documentation/master/webservices/iap.html>`_"
msgstr ""
#: ../../general/odoo_basics.rst:3
msgid "Basics"
msgstr ""
@@ -813,14 +917,6 @@ msgid ""
"users>`_"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:47
msgid "Todo"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:47
msgid "Add link to How to add companies"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:3
msgid "Manage Odoo in your own language"
msgstr ""
locale/ar/LC_MESSAGES/helpdesk.po
+89 -1
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
@@ -21,6 +21,94 @@ msgstr ""
msgid "Helpdesk"
msgstr ""
#: ../../helpdesk/after_sales.rst:3
msgid ""
"After sales features: refund, coupon, return, repair, onsite interventions"
msgstr ""
#: ../../helpdesk/after_sales.rst:4
msgid ""
"As my business grows, having the tools to allow my helpdesk team to record, "
"track and manage issues raised easy and efficiently, is key. Odoo’s Helpdesk"
" app allows me to generate credit notes, return products, grant coupons, do "
"repairs and plan onsite interventions from a ticket’s page."
msgstr ""
#: ../../helpdesk/after_sales.rst:7
msgid "Set up the After Sales services"
msgstr ""
#: ../../helpdesk/after_sales.rst:8
msgid ""
"Go to *Configuration > Helpdesk Teams* and enable the After Sales options: "
"*Refunds, Returns, Coupons, Repairs and Onsite Interventions*."
msgstr ""
#: ../../helpdesk/after_sales.rst:14
msgid "Generate credit notes from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:15
msgid ""
"I can use a credit note to refund a customer or adjust the amount due. For "
"that, I’ll simply go to my ticket page, click on *Refund* and select the "
"corresponding *Invoice*. Clicking on *Reverse* the credit note will be "
"generated, and I can *Post* it while still being in the *Helpdesk* app."
msgstr ""
#: ../../helpdesk/after_sales.rst:22
msgid "Allow product returns from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:23
msgid ""
"The process of a product return from my customer back to my warehouse will "
"be taken into action when, at the ticket page, I choose the option *Return*."
msgstr ""
#: ../../helpdesk/after_sales.rst:29
msgid "Grant coupons from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:30
msgid ""
"First, be sure to have your *Coupon Program* planned at the *Sales or "
"Website* app. At the *Helpdesk* app, I will open my ticket and click on "
"*Coupon*, choose the *Coupon Program > Generate*."
msgstr ""
#: ../../helpdesk/after_sales.rst:37
msgid "Repairs from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:38
msgid ""
"Clicking on *Repair* option, on my ticket page, a new repair order form will"
" be shown. Fill up the rest of the fields as needed and choose the next "
"step."
msgstr ""
#: ../../helpdesk/after_sales.rst:44
msgid "Plan onsite interventions from tickets"
msgstr ""
#: ../../helpdesk/after_sales.rst:45
msgid ""
"At the ticket page, I can now configure my onsite interventions exactly the "
"same way I would do being on the *Field Service* app, clicking on *Plan "
"Intervention*."
msgstr ""
#: ../../helpdesk/after_sales.rst:52
msgid ""
"`Coupons <https://www.odoo.com/slides/slide/coupon-"
"programs-640?fullscreen=1>`_"
msgstr ""
#: ../../helpdesk/after_sales.rst:53
msgid ":doc:`../manufacturing/repair/repair`"
msgstr ""
#: ../../helpdesk/getting_started.rst:3
msgid "Get started with Odoo Helpdesk"
msgstr ""
locale/ar/LC_MESSAGES/inventory.po
+2308 -3595
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/iot.po
+458 -79
View File
@@ -3,13 +3,17 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Mustafa Rawi <mustafa@cubexco.com>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Mustafa Rawi <mustafa@cubexco.com>, 2019\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -21,66 +25,70 @@ msgstr ""
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../iot/connect.rst:3
#: ../../iot/config.rst:3
msgid "Configuration"
msgstr "إعداد"
#: ../../iot/config/connect.rst:3
msgid "Connect an IoT Box to your database"
msgstr ""
#: ../../iot/connect.rst:5
#: ../../iot/config/connect.rst:5
msgid "Install the Internet of Things (IoT) App on your Odoo Database."
msgstr ""
#: ../../iot/connect.rst:10
#: ../../iot/config/connect.rst:10
msgid "Go in the IoT App and click on Connect on the IoT Boxes page."
msgstr ""
#: ../../iot/connect.rst:15
#: ../../iot/config/connect.rst:15
msgid "Follow the steps to connect your IoT Box."
msgstr ""
#: ../../iot/connect.rst:21
#: ../../iot/config/connect.rst:21
msgid "Ethernet Connection"
msgstr ""
#: ../../iot/connect.rst:23
#: ../../iot/config/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
#: ../../iot/config/connect.rst:26
msgid "Power on the IoT Box."
msgstr ""
#: ../../iot/connect.rst:28
#: ../../iot/config/connect.rst:28
msgid "Then click on the Scan button."
msgstr ""
#: ../../iot/connect.rst:34
#: ../../iot/config/connect.rst:34
msgid "WiFi Connection"
msgstr ""
#: ../../iot/connect.rst:36
#: ../../iot/config/connect.rst:36
msgid "Power on the IoT Box"
msgstr ""
#: ../../iot/connect.rst:38
#: ../../iot/config/connect.rst:38
msgid "Copy the token"
msgstr ""
#: ../../iot/connect.rst:43
#: ../../iot/config/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
#: ../../iot/config/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
#: ../../iot/config/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-"
@@ -88,43 +96,43 @@ msgid ""
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
#: ../../iot/connect.rst:63
#: ../../iot/config/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
#: ../../iot/config/connect.rst:70
msgid "You should now see the IoT Box."
msgstr ""
#: ../../iot/connect.rst:76
#: ../../iot/config/connect.rst:76
msgid "IoT Box Schema"
msgstr ""
#: ../../iot/flash_sdcard.rst:3
#: ../../iot/config/flash_sdcard.rst:3
msgid "Flashing your SD Card"
msgstr ""
#: ../../iot/flash_sdcard.rst:5
#: ../../iot/config/flash_sdcard.rst:5
msgid ""
"In some case, you may need to reflash your IoT Box’s SD Card to benefit from"
" our latest updates."
msgstr ""
#: ../../iot/flash_sdcard.rst:9
#: ../../iot/config/flash_sdcard.rst:9
msgid "Updating your SD Card with Etcher"
msgstr ""
#: ../../iot/flash_sdcard.rst:11
#: ../../iot/config/flash_sdcard.rst:11
msgid ""
"Go to Balena’s website and download `Etcher <http://wwww.balena.org>`__, "
"It’s a free and open-source utility used for burning image files. Install "
"and launch it."
msgstr ""
#: ../../iot/flash_sdcard.rst:15
#: ../../iot/config/flash_sdcard.rst:15
msgid ""
"Now, download the latest image `here "
"<http://nightly.odoo.com/master/posbox/iotbox/>`__, and extract it from the "
@@ -132,137 +140,137 @@ msgid ""
"flash (where your SD Card is) and click on *Flash*!."
msgstr ""
#: ../../iot/flash_sdcard.rst:19
#: ../../iot/config/flash_sdcard.rst:19
msgid ""
"Now, your image will be automatically updated. You just have to wait 5 "
"minutes for it to finish."
msgstr ""
#: ../../iot/iot_notfound.rst:3
#: ../../iot/config/iot_notfound.rst:3
msgid "IoT Box not found"
msgstr ""
#: ../../iot/iot_notfound.rst:5
#: ../../iot/config/iot_notfound.rst:5
msgid ""
"When using your IoT Box, a common issue you might encounter is that your box"
" is not found on your database. Fortunately, there are a few easy steps you "
"can follow to find your IoT box."
msgstr ""
#: ../../iot/iot_notfound.rst:10
#: ../../iot/config/iot_notfound.rst:10
msgid "HTTPS Issues"
msgstr ""
#: ../../iot/iot_notfound.rst:12
#: ../../iot/config/iot_notfound.rst:12
msgid "Your IoT Box is not found? You probably have https issues!"
msgstr ""
#: ../../iot/iot_notfound.rst:14
#: ../../iot/config/iot_notfound.rst:14
msgid ""
"To check it, go to your database and verify if your database address starts "
"with an https (like https://www.odoo.com). If this is the case, then you may"
" have problems with your IoT Box image. It should be version 18.12 or later."
msgstr ""
#: ../../iot/iot_notfound.rst:19
#: ../../iot/config/iot_notfound.rst:19
msgid ""
"If your IoT Box image is from an earlier version, then you will have to "
"reflash the SD card of your IoT Box to update the image (the latest image "
"can be found `here <http://nightly/odoo.com>`__)."
msgstr ""
#: ../../iot/iot_notfound.rst:23
#: ../../iot/config/iot_notfound.rst:23
msgid ""
"You can find the documentation about SD card flashing here (`here "
"<https://docs.google.com/document/d/1bqKsZhWqMqI4mhv4ltF61M_QPiBCHygYjjvkhsCTdaY/edit>`__)."
msgstr ""
#: ../../iot/pos.rst:3
#: ../../iot/config/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr ""
#: ../../iot/pos.rst:9
#: ../../iot/config/pos.rst:9
msgid "Prerequisites"
msgstr ""
#: ../../iot/pos.rst:11
#: ../../iot/config/pos.rst:11
msgid "Before starting, make sure you have the following:"
msgstr ""
#: ../../iot/pos.rst:13
#: ../../iot/config/pos.rst:13
msgid "An IoT Box"
msgstr ""
#: ../../iot/pos.rst:15
#: ../../iot/config/pos.rst:15
msgid "A 2A Power adapter with pi 3 b+ 2.5 A"
msgstr ""
#: ../../iot/pos.rst:17
#: ../../iot/config/pos.rst:17
msgid "A computer or tablet with an up-to-date web browser"
msgstr ""
#: ../../iot/pos.rst:19
#: ../../iot/config/pos.rst:19
msgid ""
"A running SaaS or Odoo instance with the Point of Sale and IoT apps "
"installed"
msgstr ""
#: ../../iot/pos.rst:22
#: ../../iot/config/pos.rst:22
msgid "A local network setup with DHCP (this is the default setting)"
msgstr ""
#: ../../iot/pos.rst:24
#: ../../iot/config/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
#: ../../iot/config/pos.rst:28
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
#: ../../iot/pos.rst:30
#: ../../iot/config/pos.rst:30
msgid "An Epson compatible cash drawer"
msgstr ""
#: ../../iot/pos.rst:32
#: ../../iot/config/pos.rst:32
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr ""
#: ../../iot/pos.rst:35
#: ../../iot/config/pos.rst:35
msgid "Set Up"
msgstr ""
#: ../../iot/pos.rst:37
#: ../../iot/config/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
#: ../../iot/config/pos.rst:44
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr ""
#: ../../iot/pos.rst:46
#: ../../iot/config/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
#: ../../iot/config/pos.rst:50
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
#: ../../iot/pos.rst:53
#: ../../iot/config/pos.rst:53
msgid ""
"**Cash drawer**: The cash drawer should be connected to the printer with an "
"RJ25 cable."
msgstr ""
#: ../../iot/pos.rst:56
#: ../../iot/config/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 "
@@ -271,18 +279,18 @@ msgid ""
"your barcode scanner."
msgstr ""
#: ../../iot/pos.rst:62
#: ../../iot/config/pos.rst:62
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
#: ../../iot/pos.rst:64
#: ../../iot/config/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
#: ../../iot/config/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 "
@@ -290,26 +298,26 @@ msgid ""
"on boot."
msgstr ""
#: ../../iot/pos.rst:73
#: ../../iot/config/pos.rst:73
msgid ""
"Once it's done, you can connect the IoT Box to your PoS. For this, go in "
"Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the"
" IoT Box you want to connect with. Save the changes."
msgstr ""
#: ../../iot/pos.rst:77
#: ../../iot/config/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
#: ../../iot/pos.rst:80
#: ../../iot/config/pos.rst:80
msgid "Troubleshoot"
msgstr ""
#: ../../iot/pos.rst:83
#: ../../iot/config/pos.rst:83
msgid "The PoS cannot connect to the IoT Box"
msgstr ""
#: ../../iot/pos.rst:85
#: ../../iot/config/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"
@@ -317,90 +325,90 @@ msgid ""
"receipt is printed, check the following steps:"
msgstr ""
#: ../../iot/pos.rst:91
#: ../../iot/config/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
#: ../../iot/config/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
#: ../../iot/config/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
#: ../../iot/config/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
#: ../../iot/config/pos.rst:106
msgid "Make sure that the POS is not loaded over HTTPS."
msgstr ""
#: ../../iot/pos.rst:108
#: ../../iot/config/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
#: ../../iot/config/pos.rst:113
msgid "The Barcode Scanner is not working"
msgstr ""
#: ../../iot/pos.rst:115
#: ../../iot/config/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
#: ../../iot/config/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
#: ../../iot/config/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
#: ../../iot/config/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
#: ../../iot/config/pos.rst:134
msgid "The Barcode Scanner is not working reliably"
msgstr ""
#: ../../iot/pos.rst:136
#: ../../iot/config/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
#: ../../iot/config/pos.rst:140
msgid "Printing the receipt takes too much time"
msgstr ""
#: ../../iot/pos.rst:142
#: ../../iot/config/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 "
@@ -408,33 +416,404 @@ msgid ""
"and the IoT Box."
msgstr ""
#: ../../iot/pos.rst:148
#: ../../iot/config/pos.rst:148
msgid "Some characters are not correctly printed on the receipt"
msgstr ""
#: ../../iot/pos.rst:150
#: ../../iot/config/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
#: ../../iot/config/pos.rst:155
msgid "The printer is offline"
msgstr ""
#: ../../iot/pos.rst:157
#: ../../iot/config/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
#: ../../iot/config/pos.rst:162
msgid "The cashdrawer does not open"
msgstr ""
#: ../../iot/pos.rst:164
#: ../../iot/config/pos.rst:164
msgid ""
"The cashdrawer should be connected to the printer and should be activated in"
" the POS configuration."
msgstr ""
#: ../../iot/devices.rst:3
msgid "Devices"
msgstr "الأجهزة"
#: ../../iot/devices/camera.rst:3
msgid "Connect a Camera"
msgstr ""
#: ../../iot/devices/camera.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a camera. As it can"
" be done in a few steps, this device is really easy to configure. Then, you "
"can use it in your manufacturing process and link it to a control point. "
"Doing so will allow you to take pictures when you reach the chosen quality "
"control point."
msgstr ""
#: ../../iot/devices/camera.rst:12 ../../iot/devices/footswitch.rst:13
#: ../../iot/devices/printer.rst:11
msgid "Connection"
msgstr "الاتصال"
#: ../../iot/devices/camera.rst:14
msgid ""
"To connect the camera to the *IoT Box*, simply combine the two by cable."
msgstr ""
#: ../../iot/devices/camera.rst:18
msgid "In some cases, a serial to USB adapter could be needed."
msgstr ""
#: ../../iot/devices/camera.rst:20
msgid ""
"If your camera is a `*supported one* <https://www.odoo.com/page/iot-"
"hardware>`__, there is no need to set up anything as it will be detected as "
"soon as it is connected."
msgstr ""
#: ../../iot/devices/camera.rst:27
msgid ""
"In some cases, you could need to restart the box and download your camera’s "
"drivers from the box. To do so, go to your *IoT Box Home Page* and click on "
"*drivers list*. Then, click on load drivers."
msgstr ""
#: ../../iot/devices/camera.rst:35
msgid "Link a Camera to a Quality Control Point"
msgstr ""
#: ../../iot/devices/camera.rst:38 ../../iot/devices/measurement_tool.rst:42
msgid "With the Manufacturing app"
msgstr ""
#: ../../iot/devices/camera.rst:40
msgid ""
"In your *Quality app*, you can setup the device on a *Quality Control "
"Point*. Go to the *Control Points* menu, under *Quality Control* and open "
"the control point you want to link with the camera."
msgstr ""
#: ../../iot/devices/camera.rst:44
msgid ""
"Now, you can edit the control point and select the device from the dropdown "
"list. Now, hit save."
msgstr ""
#: ../../iot/devices/camera.rst:50
msgid ""
"Then, your camera can be used with the picked *Control Point*. During the "
"manufacturing process, reaching the *Quality Control Point* you chose before"
" will allow you to take a picture."
msgstr ""
#: ../../iot/devices/footswitch.rst:3
msgid "Connect a Footswitch"
msgstr ""
#: ../../iot/devices/footswitch.rst:5
msgid ""
"When working, it is always better to have your two hands available. Using "
"Odoo’s *IoT Box* and a footswitch will allow it."
msgstr ""
#: ../../iot/devices/footswitch.rst:8
msgid ""
"In fact, you will be able to go from one screen to another by using your "
"foot and the footswitch. Really convenient, it can be configured in a few "
"steps."
msgstr ""
#: ../../iot/devices/footswitch.rst:15
msgid ""
"Connecting the footswitch to the *IoT Box* is easy, you just have to combine"
" the two by cable."
msgstr ""
#: ../../iot/devices/footswitch.rst:19
msgid "In some cases, a serial to USB adapter may be needed."
msgstr ""
#: ../../iot/devices/footswitch.rst:21
msgid ""
"If your footswitch is a `supported one <https://www.odoo.com/page/iot-"
"hardware>`__, there is no need to set up anything since it will be "
"automatically detected when connected."
msgstr ""
#: ../../iot/devices/footswitch.rst:28
msgid ""
"If it is not a supported one, you may need to restart the box and download "
"your footswitch’s drivers from the box. To do so, go to the *IoT Box Home "
"Page* and click on *drivers list*. Then, click on load drivers."
msgstr ""
#: ../../iot/devices/footswitch.rst:37
msgid "Link a Footswitch to a Workcenter"
msgstr ""
#: ../../iot/devices/footswitch.rst:39
msgid ""
"To link the footswitch to an action, it needs to be configured on a "
"workcenter. Go to the workcenter you want to use the footswitch in and add "
"the device in the *IoT Triggers* tab. Then, you can link it to an action and"
" also add a key to trigger it."
msgstr ""
#: ../../iot/devices/footswitch.rst:47
msgid ""
"Note that the one that is first in the list will be chosen. So, the order "
"matters! In the picture above, using the footswitch will, for example, "
"automatically skip the current part of the process you work on."
msgstr ""
#: ../../iot/devices/footswitch.rst:52
msgid ""
"When you are on the work order screen, a status button indicates if you are "
"correctly connected to the footswitch."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:3
msgid "Connect a Measurement Tool"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:5
msgid ""
"With Odoo’s *IoT Box*, it is possible to connect measurement tools to your "
"database. Find the list of supported devices here: `Supported devices "
"<https://www.odoo.com/page/iot-hardware>`__,."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:10
msgid "Connect in USB"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:12
msgid ""
"To add a device connected by USB, just plug the USB cable in the *IoT Box*, "
"restart the Box and the device should appear in your Odoo database."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:19
msgid ""
"If the device is not found, make sure the drivers have well been loaded on "
"your IoT Box. For this, connect to the *IoT Box Homepage* and click on load "
"drivers."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:27
msgid "Connect in Bluetooth"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:29
msgid ""
"Activate the Bluetooth on your device (see your device manual for further "
"explanation) and the IoT Box will automatically try to connect to the "
"device."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:33
msgid "Here is an example of what it should look like:"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:39
msgid "Link a measurement tool to a quality control point"
msgstr ""
#: ../../iot/devices/measurement_tool.rst:44
msgid ""
"In your *Quality app*, you can setup a device on your *Quality Control "
"Points*. To do so, go to the *Control Points* menu, under *Quality Control* "
"and open the control point to which you want to assign a measurement tool."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:49
msgid ""
"Now, you can edit the control point and choose the device from the dropdown "
"list. Then, hit save."
msgstr ""
#: ../../iot/devices/measurement_tool.rst:55
msgid ""
"Now, your measurement tool is linked to the chosen *Control Point*. The "
"value, which needs to be changed manually, will be automatically updated "
"while the tool is being used."
msgstr ""
#: ../../iot/devices/printer.rst:3
msgid "Connect a Printer"
msgstr ""
#: ../../iot/devices/printer.rst:5
msgid ""
"When using your *IoT Box* in Odoo, you could need to use a printer. Doing so"
" is easy and convenient as it can be done in a few steps. Then, you can use "
"it to print receipts, orders or even reports in different Odoo apps."
msgstr ""
#: ../../iot/devices/printer.rst:13
msgid ""
"To connect the printer to the *IoT Box*, you just have to combine the two by"
" cable."
msgstr ""
#: ../../iot/devices/printer.rst:17
msgid "Sometimes, a serial to USB adapter may be needed."
msgstr ""
#: ../../iot/devices/printer.rst:19
msgid ""
"If your printer is a `supported one <https://www.odoo.com/page/iot-"
"hardware>`__, there is no need to set up anything because it will be "
"automatically detected as soon as it is connected."
msgstr ""
#: ../../iot/devices/printer.rst:24
msgid "The printer can take up to two minutes to appear in your devices list."
msgstr ""
#: ../../iot/devices/printer.rst:29
msgid ""
"In some cases, you may need to restart the box and download your printer’s "
"drivers from the box. To do so, go to the *IoT Box Home Page* and click on "
"*drivers list*. Then, click on load drivers."
msgstr ""
#: ../../iot/devices/printer.rst:37
msgid "Link the Printer"
msgstr ""
#: ../../iot/devices/printer.rst:40
msgid "To Work Orders"
msgstr ""
#: ../../iot/devices/printer.rst:42
msgid ""
"You can link *Work Orders* to printers via a *Quality Control Point* to "
"print labels for manufactured products."
msgstr ""
#: ../../iot/devices/printer.rst:45
msgid ""
"To do so, you need to create a *Quality Control Point* from the *Quality* "
"app. Then, you can select the correct manufacturing operation and the work "
"order operation. In type, choose *Print Label* and hit save."
msgstr ""
#: ../../iot/devices/printer.rst:53
msgid ""
"Now, each time you reach the quality control point for the chosen product, a"
" *Print Label* button will appear."
msgstr ""
#: ../../iot/devices/printer.rst:60
msgid "To Reports"
msgstr ""
#: ../../iot/devices/printer.rst:62
msgid ""
"You can also link a type of report to a certain printer. In the *IoT* app, "
"go to the *Devices* menu and select the printer you want to set up."
msgstr ""
#: ../../iot/devices/printer.rst:69
msgid "Now, go to the *Printer Reports* tab."
msgstr ""
#: ../../iot/devices/printer.rst:74
msgid ""
"Hit edit and then, click on *Add a line*. In the window that shows up, check"
" all the types of reports that should be linked to this printer. Click on "
"select and save."
msgstr ""
#: ../../iot/devices/printer.rst:81
msgid ""
"Now, each time you click on *Print* in the control panel, instead of "
"downloading a PDF, it will send it to the selected printer and automatically"
" print it."
msgstr ""
#: ../../iot/devices/printer.rst:86
msgid "Print Receipts from the PoS"
msgstr ""
#: ../../iot/devices/printer.rst:88
msgid ""
"You can link a printer to your *Point of Sale* app so you can print receipts"
" directly from your *PoS*."
msgstr ""
#: ../../iot/devices/printer.rst:91
msgid ""
"Doing so is really easy. Go to your *Point of Sale* app and open your *PoS* "
"settings, under *Configuration*. There, click on *Edit* and check the *IoT "
"Box* feature. Then, enable the *Receipt Printer*."
msgstr ""
#: ../../iot/devices/printer.rst:98
msgid ""
"Now, on your *PoS* view, you will be able to print different kinds of "
"tickets: **receipts**, **sale details** and **bills**."
msgstr ""
#: ../../iot/devices/printer.rst:101
msgid ""
"For the receipt, it will be printed once the order is validated. The process"
" is automated when you enable the feature in your *PoS*."
msgstr ""
#: ../../iot/devices/printer.rst:104
msgid ""
"Sales details can be printed by clicking on the printer icon on the navbar "
"at the top of the *PoS*. It will print the details of the sales of the "
"current day."
msgstr ""
#: ../../iot/devices/printer.rst:111
msgid ""
"As for the bill, it is only available in restaurant mode. In your restaurant"
" settings, activate bills and a *Bill* button will appear in the left panel."
" Click on it and it will print the bill."
msgstr ""
#: ../../iot/devices/printer.rst:119
msgid "Print Orders in the kitchen"
msgstr ""
#: ../../iot/devices/printer.rst:121
msgid "In restaurant mode, you can send order tickets to the kitchen."
msgstr ""
#: ../../iot/devices/printer.rst:123
msgid ""
"To do so, go to the *PoS* app and open your *PoS* settings. Then, tick "
"*Order Printer*."
msgstr ""
#: ../../iot/devices/printer.rst:129
msgid ""
"Now, go to the *Printers* menu. Hit create and select the *IoT Box* with all"
" the categories of product that should be printed in the *Printer Product "
"Categories* field."
msgstr ""
#: ../../iot/devices/printer.rst:136
msgid ""
"In the *PoS*, when you add or remove a product from one of the selected "
"categories, the button *Order* will be green. If you click on it, a ticket "
"will be printed."
msgstr ""
locale/ar/LC_MESSAGES/manufacturing.po
+57 -79
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
@@ -757,60 +757,47 @@ msgstr ""
#: ../../manufacturing/management/subcontracting.rst:17
msgid ""
"You can now define subcontractors contacts. When you purchase or receive "
"products from a contact of type subcontractor, the correct stock moves are "
"created to represent the subcontracting of the production."
"You can now define subcontracted *Bill of Materials*. Therefore, you need to"
" go to *Manufacturing > Master Data > Bill of Materials* and hit *Create*. "
"In this *BoM*, list the components which will be used by the subcontractor "
"to manufacture the subcontracted finished product. Specify that the *BoM* "
"type is *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:25
msgid ""
"You can set the subcontractor as a vendor in case you plan to buy him the "
"subcontracted products via purchase orders."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:28
msgid ""
"The next step is to create a *Bill of Material* of type *subcontracted*. In "
"this *BoM*, list the components you need to supply to the subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:35
#: ../../manufacturing/management/subcontracting.rst:22
msgid "You can also define subcontractors on the BoM."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:37
#: ../../manufacturing/management/subcontracting.rst:24
msgid "If no subcontractor is set, the BoM can be used by any subcontractor"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:39
#: ../../manufacturing/management/subcontracting.rst:26
msgid "If some are set, the BoM can only be used for those subcontractors"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:45
#: ../../manufacturing/management/subcontracting.rst:32
msgid "Receive or buy a subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:47
#: ../../manufacturing/management/subcontracting.rst:34
msgid "You have two options to trigger the subcontracting of a product:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:50
msgid "**Option A**: You can buy the subcontracted product from your"
#: ../../manufacturing/management/subcontracting.rst:36
msgid ""
"**Option A**: You can buy the subcontracted product from your subcontractor"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:50
msgid "subcontractor"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:52
#: ../../manufacturing/management/subcontracting.rst:38
msgid "**Option B**: You can directly receive the subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:54
#: ../../manufacturing/management/subcontracting.rst:40
msgid "Let’s start with option A (option B is just a simpler version of it)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:56
#: ../../manufacturing/management/subcontracting.rst:42
msgid ""
"Create a new purchase order. The vendor must be a subcontractor. The unit "
"price should be the cost you are paying to the subcontractor for the "
@@ -818,34 +805,34 @@ msgid ""
"subcontracted product)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:64
#: ../../manufacturing/management/subcontracting.rst:50
msgid ""
"The validation of the purchase order automatically creates the receipt. "
"Whenever you receive the product, you can validate the receipt. The "
"following stock moves are created:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:68
#: ../../manufacturing/management/subcontracting.rst:54
msgid "For the components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:70
#: ../../manufacturing/management/subcontracting.rst:56
msgid "From Subcontracting To Production"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:72
#: ../../manufacturing/management/subcontracting.rst:58
msgid "For the subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:74
#: ../../manufacturing/management/subcontracting.rst:60
msgid "From Production to Subcontracting"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:76
#: ../../manufacturing/management/subcontracting.rst:62
msgid "From Subcontracting to Stock"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:78
#: ../../manufacturing/management/subcontracting.rst:64
msgid ""
"The *Subcontracting Location* represents the place where the products are at"
" your subcontractor’s warehouse. It is configured as an internal location, "
@@ -853,35 +840,35 @@ msgid ""
"stock."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:83
#: ../../manufacturing/management/subcontracting.rst:69
msgid ""
"For option B, you can simply create the receipt manually with a partner of "
"type subcontractor defined on it."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:87
#: ../../manufacturing/management/subcontracting.rst:73
msgid "Resupply the subcontractor with the components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:89
#: ../../manufacturing/management/subcontracting.rst:75
msgid ""
"There are 3 ways to manage the resupply of your subcontractor with the "
"components:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:94
#: ../../manufacturing/management/subcontracting.rst:80
msgid "**Manually**: You create a delivery order in which you set the"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:93
#: ../../manufacturing/management/subcontracting.rst:79
msgid "subcontractor as a partner and you choose the components to deliver."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:103
#: ../../manufacturing/management/subcontracting.rst:89
msgid "**With reordering rules**: You can define a *reordering rule*"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:100
#: ../../manufacturing/management/subcontracting.rst:86
msgid ""
"on the *Subcontracting location* to ensure that they are always enough "
"components sent to your subcontractors. When the reordering rule is "
@@ -889,11 +876,11 @@ msgid ""
"created."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:111
#: ../../manufacturing/management/subcontracting.rst:97
msgid "**On order**: You can also deliver the components to your"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:109
#: ../../manufacturing/management/subcontracting.rst:95
msgid ""
"subcontractors each time you order a subcontracted product. For this, you "
"need to tick the route *Resupply Subcontractor on Order* on the wanted "
@@ -1052,73 +1039,64 @@ msgid ""
"colors depending on the situation:"
msgstr ""
#: ../../manufacturing/management/use_mps.rst:90
msgid "**Green**: quantity of products which should be replenished to"
msgstr ""
#: ../../manufacturing/management/use_mps.rst:89
#: ../../manufacturing/management/use_mps.rst:88
msgid ""
"reach the expected safety stock considering the demand forecast and the "
"indirect demand forecast."
"**Green**: quantity of products which should be replenished to reach the "
"expected safety stock considering the demand forecast and the indirect "
"demand forecast."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:93
msgid "**Grey**: replenishment order has already been generated, and its"
#: ../../manufacturing/management/use_mps.rst:90
msgid ""
"**Grey**: replenishment order has already been generated, and its quantity "
"still matches current data."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:93
msgid "quantity still matches current data."
#: ../../manufacturing/management/use_mps.rst:92
msgid ""
"**Red**: replenishment order has already been generated, and its quantity "
"was too high considering current data."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:94
msgid ""
"**Orange**: replenishment order has already been generated, and its quantity"
" was too low considering current data."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:96
msgid "**Red**: replenishment order has already been generated, and its"
msgstr ""
#: ../../manufacturing/management/use_mps.rst:96
msgid "quantity was too high considering current data."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:99
msgid "**Orange**: replenishment order has already been generated, and"
msgstr ""
#: ../../manufacturing/management/use_mps.rst:99
msgid "its quantity was too low considering current data."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:101
msgid ""
"The *Forecasted stock* line can also contain red cells, which means the "
"stock will be negative during the period in question."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:105
#: ../../manufacturing/management/use_mps.rst:100
msgid "What if I have underestimated the demand?"
msgstr ""
#: ../../manufacturing/management/use_mps.rst:107
#: ../../manufacturing/management/use_mps.rst:102
msgid ""
"You can still increase the demand forecast. It will impact the quantity to "
"replenish. The cell will become orange, and you’ll be able to launch a new "
"replenishment."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:112
#: ../../manufacturing/management/use_mps.rst:107
msgid "What if I have overestimated the demand?"
msgstr ""
#: ../../manufacturing/management/use_mps.rst:114
#: ../../manufacturing/management/use_mps.rst:109
msgid ""
"You can decrease the demand forecast. The cell will become red to inform you"
" that you’ve ordered more than planned. If you’re still able to do it, you "
"can cancel some RFQ or MO manually."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:119
#: ../../manufacturing/management/use_mps.rst:114
msgid "What if I wrongly added a product to the MPS?"
msgstr ""
#: ../../manufacturing/management/use_mps.rst:121
#: ../../manufacturing/management/use_mps.rst:116
msgid ""
"You can easily remove a product from the MPS by clicking the small bin on "
"the right of its name."
locale/ar/LC_MESSAGES/point_of_sale.po
+273 -2
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
@@ -41,6 +41,9 @@ msgstr ""
#: ../../point_of_sale/advanced_pricing_features/loyalty.rst:9
#: ../../point_of_sale/advanced_pricing_features/seasonal_discount.rst:10
#: ../../point_of_sale/overview/start.rst:22
#: ../../point_of_sale/payment/ingenico.rst:12
#: ../../point_of_sale/payment/six.rst:12
#: ../../point_of_sale/payment/vantiv.rst:13
#: ../../point_of_sale/restaurant/setup.rst:9
#: ../../point_of_sale/restaurant/split.rst:10
msgid "Configuration"
@@ -877,7 +880,275 @@ 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`"
":doc:`../../../iot/config/connect` and :doc:`../../../iot/config/pos`"
msgstr ""
#: ../../point_of_sale/payment.rst:3
msgid "Payment Terminals"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:3
msgid "Connect an Ingenico Payment Terminal to your PoS"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:5
msgid ""
"Connecting a payment terminal allows you to offer a fluid payment flow to "
"your customers and ease the work of your cashiers."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:8
msgid ""
"Please note that Ingenico is currently only available for customers in the "
"Benelux."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:15
#: ../../point_of_sale/payment/six.rst:15
msgid "Connect a Payment Terminal"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:17
msgid ""
"Connecting an Ingenico Payment Terminal to Odoo is a feature that requires "
"an IoT Box. For more information on how to connect an IoT Box to your "
"database, please refer to `this documentation "
"<https://www.odoo.com/documentation/user/12.0/iot.html>`__."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:22
msgid ""
"Once the IoT Box is up and running, you’ll need to link your payment "
"terminal to your PoS. Open the Point of Sale app and go to *Configuration > "
"Point of Sale*. Select a PoS, tick the IoT Box Device option and select your"
" payment terminal."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:31
msgid "Configure the Lane/5000 for Ingenico BENELUX"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:33
msgid ""
"Click on the F button of the terminal, then go in the *PoS Menu* > settings "
"menu and enter the settings password."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:36
msgid ""
"Now, click on connexion change and TCP/IP. Type the IP of your *IoT Box* "
"(you can find it on the form view of your IoT Box). Then, enter 9000 as "
"port. The terminal will restart. Once it is done, go on your *IoT Box* form "
"in Odoo and verify that the terminal has been found."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:45
msgid "Configure the payment method"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:47
msgid ""
"First, go in the general settings of the POS app, and activate the Ingenico "
"setting."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:53
msgid ""
"Go back in *Point of Sale > Configuration > Point of Sale*, go in the "
"payments section and access your payment methods. Create a new payment "
"method for Ingenico, select the payment terminal option Ingenico, and select"
" your payment terminal device."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:62
msgid "Pay with a payment terminal"
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:64
msgid ""
"In your *PoS interface*, when processing a payment, select a *Payment "
"Method* using a payment terminal. Check that the amount in the tendered "
"column is the one that has to be sent to the payment terminal and click on "
"*Send*. When the payment is successful, the status will change to *Payment "
"Successful*."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:73
msgid ""
"If you want to cancel the payment request, click on cancel. You can still "
"retry to send the payment request."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:76
msgid ""
"If there is any issue with the payment terminal, you can still force the "
"payment using the *Force Done*. This will allow you to validate the order in"
" Odoo even if the connexion between the terminal and Odoo has issues."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:82
msgid ""
"This option will only be available if you received an error message telling "
"you the connexion failed."
msgstr ""
#: ../../point_of_sale/payment/ingenico.rst:85
#: ../../point_of_sale/payment/six.rst:103
msgid ""
"Once your payment is processed, on the payment record, you’ll find the type "
"of card that has been used and the transaction ID."
msgstr ""
#: ../../point_of_sale/payment/six.rst:3
msgid "Connect SIX/Worldline to your PoS"
msgstr ""
#: ../../point_of_sale/payment/six.rst:5
msgid ""
"Connecting a SIX/Worldline payment terminal allows you to offer a fluid "
"payment flow to your customers and ease the work of your cashiers."
msgstr ""
#: ../../point_of_sale/payment/six.rst:9
msgid "Please note SIX/Worldine is currently only available for UE customers."
msgstr ""
#: ../../point_of_sale/payment/six.rst:17
msgid ""
"Connecting a SIX/Worldline Payment Terminal to Odoo is a feature that "
"requires an IoT Box. For more information on how to connect an IoT Box to "
"your database, please refer to `this documentation "
"<https://www.odoo.com/documentation/user/12.0/iot.html>`__."
msgstr ""
#: ../../point_of_sale/payment/six.rst:22
msgid ""
"Once the *IoT Box* is up and running, you’ll need to link it to your PoS. "
"Open the Point of Sale app and go to *Configuration > Point of Sale*. Select"
" a PoS, tick the IoT Box Device option and select your payment terminal."
msgstr ""
#: ../../point_of_sale/payment/six.rst:30
msgid ""
"Then go to your *IoT Box homepage* (accessible from the IoT Box form view in"
" Odoo) and enter the ID of your Six payment terminal."
msgstr ""
#: ../../point_of_sale/payment/six.rst:36
msgid ""
"You should now see that the terminal is connected to your IoT Box (it takes "
"+/- 1 min)."
msgstr ""
#: ../../point_of_sale/payment/six.rst:43
msgid ""
"The terminal should only be connected to the network with the Ethernet. Do "
"not connect it to the IoT Box with a USB Cable."
msgstr ""
#: ../../point_of_sale/payment/six.rst:47
#: ../../point_of_sale/payment/vantiv.rst:16
msgid "Configure the Payment Method"
msgstr ""
#: ../../point_of_sale/payment/six.rst:49
msgid ""
"First, go in the general settings of the POS app, and activate the SIX "
"setting."
msgstr ""
#: ../../point_of_sale/payment/six.rst:55
msgid ""
"Back in *Point of Sale > Configuration > Point of Sale*, go in the payments "
"section and access your payment methods. Create a new payment method for "
"SIX, select the payment terminal option SIX, and select your payment "
"terminal device."
msgstr ""
#: ../../point_of_sale/payment/six.rst:64
#: ../../point_of_sale/payment/vantiv.rst:40
msgid "Pay with a Payment Terminal"
msgstr ""
#: ../../point_of_sale/payment/six.rst:66
msgid ""
"In your PoS interface, at the moment of the payment, select a payment method"
" using a payment terminal. Verify that the amount in the tendered column is "
"the one that has to be sent to the payment terminal and click on *Send*. If "
"you want to cancel the payment request, click on cancel."
msgstr ""
#: ../../point_of_sale/payment/six.rst:74
msgid ""
"When the payment is done, the status will change to *Payment Successful*. "
"You can always reverse the last transaction by clicking on *Reverse*."
msgstr ""
#: ../../point_of_sale/payment/six.rst:81
msgid ""
"If there is any issue with the payment terminal, you can still force the "
"payment using the *Force Done*. This will allow you to validate the order in"
" Odoo even if the connexion between the terminal and Odoo encounters issues."
msgstr ""
#: ../../point_of_sale/payment/six.rst:87
msgid "Close your Session"
msgstr ""
#: ../../point_of_sale/payment/six.rst:89
msgid ""
"At the end of the day, before closing your session, you need to send the "
"balance of the payments to SIX. To do that, click on this button."
msgstr ""
#: ../../point_of_sale/payment/six.rst:95
msgid ""
"Once the balance has been sent, the SIX shift is closed, meaning you cannot "
"do additional operations with the SIX payment terminal (except if you reopen"
" a shift by clicking on the user name and selecting a cashier)."
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:3
msgid "Connect a Vantiv Payment Terminal to your PoS"
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:5
msgid ""
"Connecting a Vantiv payment terminal allows you to offer a fluid payment "
"flow to your customers and ease the work of your cashiers."
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:9
msgid ""
"Please note MercuryPay only operates with US and Canadian banks, making this"
" procedure only suitable for North American businesses."
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:18
msgid ""
"First, go in the general settings of the POS app, and activate the Vantiv "
"setting."
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:24
msgid ""
"Back in *Point of Sale > Configuration > Point of Sale*, go in the payments "
"section and access your payment methods. Create a new payment method for "
"Vantiv, select the payment terminal option Vantiv, and create new Vantiv "
"credentials."
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:32
msgid ""
"To create new Vantiv credentials, fill in your merchant ID and password, "
"then save. Make sure the credentials you just created are selected, then "
"save the payment method."
msgstr ""
#: ../../point_of_sale/payment/vantiv.rst:42
msgid ""
"In your PoS interface, at the moment of the payment, select your Vantiv "
"payment method and… that’s all."
msgstr ""
#: ../../point_of_sale/restaurant.rst:3
locale/ar/LC_MESSAGES/purchase.po
+2 -2
View File
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:47+0000\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
@@ -1623,7 +1623,7 @@ msgid ""
msgstr ""
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:33
msgid "See also: :doc:`../../../inventory/management/misc/schedulers`"
msgid "See also: :doc:`../../../inventory/management/planning/schedulers`"
msgstr ""
#: ../../purchase/replenishment/flows/setup_stock_rule.rst:35
locale/ar/LC_MESSAGES/quality.po
+417
View File
@@ -0,0 +1,417 @@
# 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.
#
# Translators:
# Mustafa Rawi <mustafa@cubexco.com>, 2019
# Ali zuaby <ali@zuaby.net>, 2019
# Osoul <baruni@osoul.ly>, 2019
# zahi chemaly <zahi@sercotex.net>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-11-20 09:24+0000\n"
"Last-Translator: zahi chemaly <zahi@sercotex.net>, 2019\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ar\n"
"Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
#: ../../quality.rst:5
msgid "Quality"
msgstr "جودة"
#: ../../quality/alert.rst:3
msgid "Alert"
msgstr "تنبيه"
#: ../../quality/alert/alert_mo.rst:3
msgid "Generate a Quality Alert from a Manufacturing Order"
msgstr ""
#: ../../quality/alert/alert_mo.rst:5
msgid ""
"Speaking of manufacturing orders, you have two different situations to "
"consider in Odoo. Those two will result in two different processes:"
msgstr ""
#: ../../quality/alert/alert_mo.rst:8
msgid "You work with a simple manufacturing flow;"
msgstr ""
#: ../../quality/alert/alert_mo.rst:10
msgid "You work with a complex manufacturing flow that includes routings."
msgstr ""
#: ../../quality/alert/alert_mo.rst:13
msgid "Simple manufacturing flow"
msgstr ""
#: ../../quality/alert/alert_mo.rst:15
msgid ""
"If you work with simple manufacturing orders, the *Quality Alerts* will be "
"launched from the manufacturing order itself. When manufacturing a product "
"for which you need to process quality controls, a button *Quality Alert* "
"will appear on the top of your manufacturing order."
msgstr ""
#: ../../quality/alert/alert_mo.rst:23
msgid ""
"By clicking on the button, you can specify the quality problem that arose "
"during the process."
msgstr ""
#: ../../quality/alert/alert_mo.rst:29
msgid ""
"If one of the quality checks failed, the button will be highlighted on the "
"document. If not, the button won’t be highlighted."
msgstr ""
#: ../../quality/alert/alert_mo.rst:36 ../../quality/checks/quality_mo.rst:50
msgid "Manufacturing Flow with Routings"
msgstr ""
#: ../../quality/alert/alert_mo.rst:38
msgid ""
"If you work with routings defined on your manufacturing orders, the quality "
"alerts will be launched directly from the work orders on which the quality "
"checks took place."
msgstr ""
#: ../../quality/alert/alert_mo.rst:48
msgid ""
"Then, a button *Quality Alert* will be available from the work order view. "
"When you click on the button, you can specify the quality problem that "
"appeared during the process."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:3
msgid "Generate a Quality Alert from a Transfer"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:6
msgid "Use the Quality Alert"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:8
msgid ""
"Every time you perform some *Quality Checks* on a transfer, a *Quality "
"Alert* button appears. You can always use it. The button is automatically "
"highlighted once you have a failed quality check for the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:16
msgid ""
"If you click on that *Quality Alert* button, you can specify what was the "
"problem with the product."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:22
msgid ""
"The *Quality Alert* that is created from the transfer can be found via the "
"button appearing on the top right corner of the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:28
msgid ""
"You can also access all your *Quality Alerts* via the menu, accessible under"
" *Control*."
msgstr ""
#: ../../quality/checks.rst:3
msgid "Checks"
msgstr "شيكات"
#: ../../quality/checks/quality_mo.rst:3
msgid "Perform Quality Checks on Manufacturing Orders"
msgstr ""
#: ../../quality/checks/quality_mo.rst:5
msgid ""
"There are two different situations to consider and that will differ in Odoo "
"processes:"
msgstr ""
#: ../../quality/checks/quality_mo.rst:8
msgid "You work with simple manufacturing flows;"
msgstr ""
#: ../../quality/checks/quality_mo.rst:10
msgid ""
"You work with complex manufacturing flows that are represented by the use of"
" routings in Odoo."
msgstr ""
#: ../../quality/checks/quality_mo.rst:13
msgid "Simple Manufacturing Flow"
msgstr ""
#: ../../quality/checks/quality_mo.rst:16
#: ../../quality/checks/quality_mo.rst:53
#: ../../quality/checks/quality_transfers.rst:6
msgid "Create the Quality Control Point"
msgstr ""
#: ../../quality/checks/quality_mo.rst:18
msgid ""
"To create a quality control point, open the quality app and go to *Control >"
" Control Points*. There, hit create. Make sure to select *Manufacturing* as "
"operation and choose the type of quality check you want to perform."
msgstr ""
#: ../../quality/checks/quality_mo.rst:27
#: ../../quality/checks/quality_mo.rst:69
#: ../../quality/checks/quality_transfers.rst:17
msgid "Process the Quality Check"
msgstr ""
#: ../../quality/checks/quality_mo.rst:29
msgid ""
"Once your *Quality Control Point* has been created, you can create a "
"manufacturing order for your product. Now, and before marking the "
"manufacturing as done, you can register the *Quality Checks*."
msgstr ""
#: ../../quality/checks/quality_mo.rst:39
msgid ""
"Once you have performed your quality checks, you can find them via the "
"*Quality Checks* button available on the manufacturing order form."
msgstr ""
#: ../../quality/checks/quality_mo.rst:46
msgid ""
"If you want to access all your quality checks, you can do this by opening "
"the quality checks menu, under quality control."
msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid ""
"If you want to create a *Quality Control Point*, open the *Quality* app and "
"go to *Control > Control Points*. Then, click on create. Make sure to select"
" *Manufacturing* as operation and select the work order operation on which "
"the quality check should be performed."
msgstr ""
#: ../../quality/checks/quality_mo.rst:64
msgid ""
"Choosing the work order operation is necessary if you want the quality "
"checks to be performed in the work orders. After that, you can choose the "
"type of quality check."
msgstr ""
#: ../../quality/checks/quality_mo.rst:71
msgid ""
"Once your *Quality Control Point* has been configured, create a "
"manufacturing order for your product. You have to plan it if you want to "
"generate the necessary work orders."
msgstr ""
#: ../../quality/checks/quality_mo.rst:78
msgid ""
"Now, process the work order and your quality check will appear. In this "
"example, the quality check requests to enter the serial number of the Table "
"Top component."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:3
msgid "Perform Quality Checks on Transfers"
msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid ""
"To create a *Quality Control Point*, open the *Quality* application. Then, "
"go to *Quality Control > Control Points > Create*. Now, you can define the "
"quality control point you want to apply to a specific product. Don’t forget "
"to select a transfer operation type."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:19
msgid ""
"Let’s say that we will receive a laptop. First, create a planned receipt for"
" the product. Then, on the receipt, you will see a *Quality Checks* button "
"that appears to proceed to the quality check you configured before."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:27
msgid ""
"By clicking on it, the instruction set on the quality control point will be "
"displayed and will require the check value."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:33
msgid ""
"Once the quality check is done, you can find it linked to the corresponding "
"transfer and access it by clicking on the button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:39
msgid ""
"But, if the quality check failed, the stat button will appear in red "
"(instead of green) and Odoo will suggest you to create a *Quality Alert* by "
"highlighting the corresponding button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:46
msgid ""
"The quality checks can also be found in the *Quality* application by opening"
" the *Quality Checks* menu, under *Quality Control*."
msgstr ""
#: ../../quality/control.rst:3
msgid "Control"
msgstr "التتبع"
#: ../../quality/control/control_points.rst:3
msgid "Define Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:6
msgid "Quality Control Points"
msgstr "نقاط مراقبة الجودة"
#: ../../quality/control/control_points.rst:8
msgid ""
"If it is the first *Quality Control Point* that you create, know that you "
"need to open the *Quality* app. Then, go to *Quality Control > Control "
"Points*. Once there, you have to define the product on which the quality "
"control will take place, as well as the operation at which it should take "
"place."
msgstr ""
#: ../../quality/control/control_points.rst:14
msgid ""
"The *Quality Control Points* can take place during transfers or during the "
"manufacturing process of the products. If you work with routings on your "
"*Bill of Materials*, you have to precise at which step of the manufacturing "
"process the quality control point should be applied."
msgstr ""
#: ../../quality/control/control_points.rst:19
msgid ""
"The control type defines at which frequency the quality checks should take "
"place:"
msgstr ""
#: ../../quality/control/control_points.rst:22
msgid ""
"All Operations: all the operations will generate quality checks to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:24
msgid ""
"Randomly: the quality checks will only be performed on x% of the operation. "
"You must define the percentage yourself, on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:26
msgid ""
"Periodically: the quality checks will be performed periodically. The "
"periodicity is based on the period you define (once a day, once a week)."
msgstr ""
#: ../../quality/control/control_points.rst:32
msgid "Quality Control Point Types"
msgstr ""
#: ../../quality/control/control_points.rst:34
msgid ""
"Now that the rest is configured, you need to define the type of quality "
"check."
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid ""
"Some of the types are only available with the manufacturing application."
msgstr ""
#: ../../quality/control/control_points.rst:41
msgid "Text"
msgstr "النص"
#: ../../quality/control/control_points.rst:43
msgid ""
"This control point type allows you to give instructions to your workers "
"during the transfer, or the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:56
msgid "Take a Picture"
msgstr "التقاط صورة"
#: ../../quality/control/control_points.rst:58
msgid ""
"This control point type asks you to take a picture of the product in a "
"transfer, or when manufacturing it."
msgstr ""
#: ../../quality/control/control_points.rst:71
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:73
msgid ""
"This type of control point requires that you specify if the products pass or"
" fail a specific text. It can be applied for both transfers or manufacturing"
" orders."
msgstr ""
#: ../../quality/control/control_points.rst:80
msgid ""
"For this kind of control point type, you have the possibility to define a "
"failure message that will give instructions to follow in case of quality "
"check failure."
msgstr ""
#: ../../quality/control/control_points.rst:94
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:96
msgid ""
"This control point type requires you to enter the product’s measurements "
"during a transfer, or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid ""
"For this kind of control point type, you also have the possibility to define"
" a failure message that will give instructions to the worker."
msgstr ""
#: ../../quality/control/control_points.rst:115
msgid "Register Consumed Materials"
msgstr ""
#: ../../quality/control/control_points.rst:117
msgid ""
"This control point type requires you register the component serial/lot "
"numbers during the manufacturing process. It is only available if you work "
"with routings."
msgstr ""
#: ../../quality/control/control_points.rst:128
msgid "Register By-Products"
msgstr ""
#: ../../quality/control/control_points.rst:130
msgid ""
"With this control point type, you must register the serial/lot number of the"
" by-products that are manufactured. It is also only available with routings."
msgstr ""
#: ../../quality/control/control_points.rst:141
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:143
msgid ""
"This control point type allows you to print labels to add to the product "
"during the manufacturing process."
msgstr ""
locale/ar/LC_MESSAGES/sales.po
+331 -5
View File
@@ -3,13 +3,17 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Mustafa Rawi <mustafa@cubexco.com>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:47+0000\n"
"Last-Translator: Mustafa Rawi <mustafa@cubexco.com>, 2019\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -1013,6 +1017,332 @@ msgid ""
"Attributes / Attribute / ID)."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:3
msgid "Using product variants"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:5
msgid ""
"Product variants are used to manage products having different variations, "
"like size, color, etc. It allows managing the product at the template level "
"(for all variations) and at the variant level (specific attributes)."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:10
msgid ""
"As an example, a company selling t-shirts may have the following product:"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:13
msgid "B&C T-shirt"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:15
msgid "Sizes: S, M, L, XL, XXL"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:16
msgid "Colors: Blue, Red, White, Black"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:18
msgid ""
"In this example, **B&C T-Shirt** is called the product template and **B&C "
"T-Shirt, S, Blue** is a variant. Sizes and color are **attributes**."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:22
msgid ""
"The above example has a total of 20 different products (5 sizes x 4 colors)."
" Each one of these products has its own inventory, sales, etc."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:26
msgid "Impact of variants"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:28
msgid ""
"**Barcode**: the code and barcode is associated to a variant, not the "
"template. Every variant may have its own barcode / SKU."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:31
msgid ""
"**Price**: every product variant has its own public price that is computed "
"based on the template price ($20) with an optional extra for every variant "
"(+$3 for color red). However, you can define pricelist rules that apply on "
"the template or the variant."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:36
msgid ""
"**Inventory**: the inventory is managed by product variant. You don't own "
"t-shirts, you only own \"T-shirts, S, Red\", or \"T-Shirts, M, Blue\". For "
"information purpose, on the product template form, you get the inventory "
"that is the sum of every variant. (but the actual inventory is computed by "
"variant)"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:42
msgid ""
"**Picture**: the picture is related to the variant, every variation of a "
"product may have its own primary picture."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:45
msgid ""
"**Other fields**: most of the other fields belongs to the product template. "
"If you update them, it updates automatically all the variants. (example: "
"Income Account, Taxes)"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:50
msgid "Should you use variants?"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:53
msgid "When should you use variants?"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:55
msgid "Using variants has the following impacts:"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:57
msgid ""
"**eCommerce**: in your online shop, the customer will only see product "
"templates in the catalog page. Once the visitor click on such a product, he "
"will have options to choose amongst the variants (colors, sizes, …)"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:62
msgid ""
"**Manufacturing**: Using variants allows to define only one bill of material"
" for a product template and slight variations for some of the variants. "
"Example: instead of creating a Bill of Material for \"T-shirt, Red, S\", you"
" create a bill of material for \"T-shirt\" and add some lines that are "
"specific to the dimension S, and other lines specific to the color Red."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:69
msgid ""
"**Pricing**: The default price of a product is computed using the price of "
"the product template and add the optional extra price on each dimension of "
"the variant. This way, variant prices are easier to maintain since you don't"
" have to set the price for every variant. However, it's possible to create "
"pricelist rules to fix price per variants too."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:77
msgid "When should you avoid using variants?"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:79
msgid ""
"Using variants may add a level of complexity on the way you use Odoo. You "
"should consider using variants only if you need it to reduce the complexity "
"of managing lots of products that are similars."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:83
msgid ""
"As an example, importing your initial product catalog is more complex if you"
" use variants. You can't just import a list of products, you must import "
"product templates and all their related variations."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:87
msgid ""
"In addition to that, you should also carefully select the dimensions that "
"you manage as separate product templates and those as variants. As an "
"example, a company having these products:"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:91
msgid "Quality: T-Shirts, Polos, Shirts"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:93
#: ../../sales/products_prices/products/variants.rst:105
#: ../../sales/products_prices/products/variants.rst:110
msgid "Color: Red, Blue"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:95
#: ../../sales/products_prices/products/variants.rst:106
#: ../../sales/products_prices/products/variants.rst:111
msgid "Size: S, M, L, XL"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:97
msgid ""
"In such a use case, you could create 1 template with three dimensions of "
"variants (Layout, T-Shirts, Polos). But, it's recommended to create two "
"different product templates as T-shirts may highly differ from polos or "
"shirts and customer expect to see these as two different products in the "
"e-Commerce:"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:103
msgid "Product Template: T-shirt"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:108
msgid "Product Template: Polos"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:114
#: ../../sales/send_quotations/quote_template.rst:10
msgid "Configuration"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:117
msgid "Activate the variant feature"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:119
msgid ""
"Before you can use product variants, you must first activate the product "
"variants in the settings. To do so, you must go to the Sales app. In the "
"menu :menuselection:`Configuration --> Settings`, locate the **Products "
"Variants** line, and tick the option **Products can have several "
"attributes**, then click on **Apply**."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:129
msgid "Creating products with variants"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:131
msgid ""
"Once you have activated the variant option, you can add variants to your "
"products. To do so, go to the Sales module, :menuselection:`Sales --> "
"Products`. It is also accessible from the Purchase and inventory modules."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:135
msgid "Now, click on the product you wish to add variants to."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:137
msgid ""
"In the product page, a new tab called Variants has appeared. The number in "
"purple written on top is the number of variants this product currently has. "
"To add new variants, click on the tile. In the new window, click on "
"**Create**."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:142
msgid ""
"In **Attributes**, click on the rolldown menu and select the type of "
"variance you wish to add. If the variant does not yet exist, you can create "
"it on the fly by clicking on Create and edit…"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:149
msgid ""
"In the Attributes window, the **Value** field is the description of the "
"attribute such as Green, Plastic or 32GB. The **Attribute** field is the "
"type of variant such as Color, Material or Memory."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:156
msgid ""
"You can add a cost for the variant on the fly by adding it in the "
"**Attribute Price Extra** field, or choose to modify it later. Click on "
"**Save**."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:160
msgid ""
"You can also add a different barcode and internal reference to the variant."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:163
msgid ""
"When you have entered all the specifications of the variant, click on "
"**Save**."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:167
msgid "Managing Product Variants"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:170
msgid "Introduction"
msgstr "المقدمة"
#: ../../sales/products_prices/products/variants.rst:172
msgid ""
"The examples below are all based on this product template that has two "
"variant attributes :"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:175
msgid "T-Shirt B&C"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:177
msgid "Color: Red, Blue, White"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:179
msgid "Size: S, M, L, XL, XXL"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:182
msgid "Managing combination possibilities"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:184
msgid ""
"By default, with the above product template, you get 15 different products "
"(3 colors, 5 sizes). If the XXL size only exists for red and blue t-shirts, "
"you can deactivate the white product variant."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:188
msgid ""
"To do this, click on the **Variants** button, select the XXL, White T-shirt."
" From the product form, uncheck the **Active** box of the T-shirt White, "
"XXL."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:197
msgid ""
"That deactivating a product is different than having an inventory of 0."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:200
msgid "Setting a price per variant"
msgstr ""
#: ../../sales/products_prices/products/variants.rst:202
msgid ""
"You can add a cost over the main price for some of the variants of a "
"product."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:205
msgid ""
"Once you have activated the variant option, you can add variants to your "
"products. To do so, go to the Sales module, open :menuselection:`Sales --> "
"Products` and click on the product you want to modify. Click on the "
"**Variant Prices** button to access the list of variant values."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:213
msgid ""
"Click on the variant name you wish to add a value to, to make the 3 fields "
"editable. In the **Attribute Price Extra** field, add the cost of the "
"variant that will be added to the original price."
msgstr ""
#: ../../sales/products_prices/products/variants.rst:220
msgid "When you have entered all the extra values, click on **Save**."
msgstr ""
#: ../../sales/products_prices/taxes.rst:3
msgid "Set taxes"
msgstr ""
@@ -1579,10 +1909,6 @@ msgid ""
"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 --> "
locale/ar/LC_MESSAGES/sms_marketing.po
+515
View File
@@ -0,0 +1,515 @@
# 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.
#
# Translators:
# Mustafa Rawi <mustafa@cubexco.com>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-11-20 09:24+0000\n"
"Last-Translator: Mustafa Rawi <mustafa@cubexco.com>, 2019\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ar\n"
"Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
#: ../../sms_marketing.rst:5
msgid "SMS Marketing"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:3
msgid "Build, send and get reports from a SMS mailing"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:5
msgid ""
"Why to use SMS? Using SMS Marketing as part of my communication strategies "
"can empower me to expand my markets, considering that in some countries "
"emails are not very used or used at all. It also helps to boost my "
"conversion rate, as this strategy has a high open-rate percentage among "
"people who use smartphones - people usually don’t keep unread SMSs!"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:8
msgid ""
"With Odoo’s SMS Marketing app you can plan, organize, schedule and keep "
"track of your mailings with its easy to use interface."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:12
msgid "Install the app"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:14
msgid "Go to *Apps*, search for *SMS Marketing* and click on *Install*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:17
msgid "Build an SMS mailing"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:19
msgid "Go to *SMS Marketing > Create*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:24
msgid ""
"First, I’ll be able to specify a *subject* name that will help me to "
"remember what the mailing is about. Under *recipients*, I’ll choose to whom "
"I’d like the SMS to be sent. If I choose *Contact*, all my Odoo contacts "
"(vendor, customers, etc.) will receive my SMS. From there, I can refine my "
"recipient list with the *add filter* option. In the example below, I choose "
"to send it to my contacts living in Belgium."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:31
msgid ""
"The *Mailing list* option, on the other hand, allows me to choose mailing "
"lists I’ve created with specific contacts or people who have subscribed to "
"my Newsletters, or both! I’m allowed to select more than one *Mailing list*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:36
msgid ""
"Under the *SMS Content* tab, links can be included and Odoo will "
"automatically generate *link trackers*. Thank to those, I’ll be able to get "
"data about those links."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:38
msgid ""
"On *Settings* I have the option *include opt-out link* available. If "
"activated, the contact will be able to unsubscribe from the mailing list "
"he’s not interested in anymore."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:43
msgid ""
"in the *Link Tracker* menu under *Configuration*, I can see the history of "
"my sent links, access them and look at statistics."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:48
msgid "Double-check that you have the phone number of your contacts saved!"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:52
msgid "Sending my mailing"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:56
msgid ""
"Once I have my mailing created, I must choose when I would like it to be "
"delivered:"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:58
msgid ""
"**Put in queue**: the mailing will be triggered with the next automatic run."
" Interesting option if I don’t mind when the triggering will happen."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:59
msgid ""
"**Send now**: sends the message immediately. Advised to use this option if "
"there are not that many recipients."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:60
msgid ""
"**Schedule**: allows me to choose a day and time. Best option for mailings "
"that I would like to send during a specific event, to promote an offer while"
" it is active or to simply plan my content strategy in advance."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:61
msgid ""
"**Test**: allows me to send an SMS to one or multiple numbers for test "
"purposes. Check, for example, if the link provided lands on the right page "
"while making sure they are responsive. If sending it to multiple numbers, I "
"must remember to use a comma between them."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:65
msgid "Visualize reports"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:66
msgid ""
"On the *Reporting* menu, with just a few clicks, I am capable of applying "
"filters, measures and adopt different layouts to do an analysis of the "
"performance of my SMS mailings."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:71
msgid ""
"I can also check the price to send an SMS on your country when clicking on "
"the *information* icon when creating a new SMS."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:76
msgid ""
"**Buy Credits!** In order to take advantage of the app and its features, "
"make sure you’ve purchased credits. For more information on that access: "
":doc:`../sms_marketing/fqapricing`"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:3
msgid "Contact lists and Blacklist"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:6
msgid "Contact lists"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:7
msgid ""
"Creating my own list of contacts, or importing it, is useful when I want to "
"create specific groups of people, such as the subscribers of my newsletter. "
"It is also the best way to get started if I am coming from another system "
"and already have built an audience. It makes the SMS distribution a lot "
"easier."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:9
msgid ""
"Go to *Contacts lists > Contacts lists > Create*. I’ll choose a name for my "
"*Mailing list*, and activate the option *Public* if I would like to make the"
" mailing list accessible to my recipients in the unsubscription page to "
"allow them to update their subscription preferences."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:12
msgid ""
"Once inside the list, I can again *Create* or *Import* contacts for that "
"specific list."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:18
msgid "History with the Log Notes"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:19
msgid ""
"A record of the mailings sent is kept in the chatter of the recipient "
"(whether it is a contact or an opportunity, for example)."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:24
msgid ""
"This is important as I and my team can easily keep track and see a history "
"of interactions with my contacts or prospects, granting me the ability to "
"better understand them. Example: my sales representative can easily find out"
" which SMS mailing promotions a customer has received or not."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:29
msgid "Blacklist"
msgstr "القائمة السوداء"
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:30
msgid ""
"If I’m coming from another software and have a list of clients who have "
"already asked to be blacklisted from my news, I can import those entries in "
"my database. For that, I’ll go to *Configuration > Phone Blacklist > "
"Import*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:3
msgid "Integrations and Templates"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:4
msgid ""
"Using SMS to reach people can be a strategy not just used for advertisement "
"purposes but also as a reminder of events or issued invoices to your "
"costumers, for example. As you know, one of the biggest benefits of using "
"Odoo is the capability of the apps to be integrated. With the SMS Marketing "
"app isn’t different!"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:9
msgid "Organize Email Marketing and SMS campaigns"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:10
msgid ""
"First, make sure to have the necessary feature activated. Go to the *Email "
"Marketing app > Configuration > Settings> activate the option Mailing "
"Campaigns*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:15
msgid ""
"Now, I’ll also have the menu *Campaigns* included in my *SMS Marketing* "
"page, allowing me to have an overview of my SMS mailings and my email "
"marketing ones."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:20
msgid ""
"This feature is especially useful if I have aggregated campaigns, as I have "
"a global reporting view. In addition to that, I can create stages in my "
"kanban view to better organize the work being done."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:26
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:27
msgid ""
"Sending SMSs through the contact’s form is available by default in Odoo. It "
"makes my work easier if I need to send an SMS to a specific contact, for "
"example. For that, I’ll go to the *Contacts* app, select the contact and "
"click on the *SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:33
msgid ""
"If I’d like to send a message in a batch here, I could go to *List View > "
"select all the contacts > Action > Send SMS*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:39
msgid "Set up SMS Templates"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:40
msgid ""
"To set up *SMS Templates*, I’ll go to the *Settings* app and activate the "
"*developer mode*. Now, back to *Settings* app, I’ll go to *Technical > "
"Phone/SMS section > SMS Templates* and create the content I need."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:48
msgid ""
"Use *Dynamic Placeholders* to adapt automatically the content of the SMS to "
"the context."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:52
msgid ""
"SMS Text Messaging is available throughout Odoo! Here are some of our extra "
"notable integrations:"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:54
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:55
msgid "*Subscription*: alert customers about their subscription."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:56
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:57
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:58
msgid ""
"*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:59
msgid ""
"*Sign*: receive a validation code to verify your identity before signing a "
"document online."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:60
msgid ""
"*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:61
msgid ""
"*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:63
msgid ""
"For more information about SMS integrations in Odoo and a list of frequently"
" asked questions, go to `Pricing and FQA <fqapricing.html>`__."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:3
msgid "SMS Pricing and FAQ"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:6
msgid "Pricing"
msgstr "التسعير"
#: ../../sms_marketing/fqapricing.rst:7
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service which requires "
"prepaid credits to work. The price of an SMS depends on the destination and "
"the length of the message. With 1 credit, I can send up to 92 SMSs."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:9
msgid ""
"**For more information, please consult our FAQ page**: `Odoo SMS - FAQ "
"<https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:11
msgid ""
"To buy credits I will go to *Settings > Buy Credits* (under *Send SMS*); or"
" go to *Settings > View my Services* (under *Odoo IAP*)."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:18
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:21
msgid "FAQ"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:22
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:24
msgid "No, your credits won’t expire."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:26
msgid ""
"**Can I send an SMS to a phone number (which is not a mobile phone) because "
"I see the icon in front of the field “phone”?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:28
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:30
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:32
msgid "Yes."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:34
msgid "**Can the recipient answer to me?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:36
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:38
msgid ""
"**What happens if I send multiple SMS but I do not have enough credits to "
"send them all?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:40
msgid ""
"The whole transaction is counted as a single one, so no SMS will be sent "
"until you have enough credits to send them all."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:42
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:44
msgid ""
"Yes, the SMS is logged as a note under the chatter of the corresponding "
"record, and a complete history of SMS sent is available under Settings> "
"Activate the developer mode > Technical > SMS."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:46
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:48
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:50
msgid ""
"**If I have a number that does not exist in the list of recipients, will I "
"lose credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:52
msgid ""
"Not if the phone number is in the wrong format (e.g. too many digits). "
"Otherwise, if the SMS is sent to the wrong person or to a fake number, the "
"credit will be lost."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:54
msgid ""
"**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
" ticket for a festival)?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:56
msgid ""
"The SMS will not be delivered to that kind of number, so you won’t be "
"charged."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:58
msgid ""
"**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:60
msgid "Only the ones that have an invalid format."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:62
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:64
msgid ""
"Please find our Privacy Policy here: `Odoo IPA Purchase Privacy Policy "
"<https://iap.odoo.com/privacy#sms>`__"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:66
msgid "**How many types of SMS exist and how many characters make 1 SMS?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:68
msgid "There are 2 types of SMS message:"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:70
msgid ""
"*Standard* (GSM-7): contains only characters from the GSM-7 set, which can "
"be seen in the following picture."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:75
msgid ""
"*Unicode*: contains at least one character that is not in the previous "
"table. For Standard SMS the size limit is 160 characters, and for Unicode is"
" 70. Above these limits, the content is divided into a multi-part message. "
"The system will inform you in real-time about the number of SMS your message"
" represents."
msgstr ""
locale/ar/LC_MESSAGES/social_marketing.po
+168
View File
@@ -0,0 +1,168 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-11-20 09:24+0000\n"
"Language-Team: Arabic (https://www.transifex.com/odoo/teams/41243/ar/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ar\n"
"Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 && n%100<=99 ? 4 : 5;\n"
#: ../../social_marketing.rst:5
#: ../../social_marketing/social_marketing/social_marketing.rst:2
msgid "Social Marketing"
msgstr ""
#: ../../social_marketing/social_marketing.rst:3
msgid "Advanced Topics"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:4
msgid ""
"One of the biggest challenges of a company is to engage efficiently with "
"their community. Odoo Social helps you to meet your audience with the help "
"of several supports: social media, push notifications, or live chat request."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:10
msgid "Add your social media and create your feed"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:12
msgid ""
"You first need to add your social media accounts. To do that, add a Stream "
"and choose your social media account. You’ll need to grant permissions to "
"Odoo Social Marketing application."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:19
msgid ""
"Once it’s done, you’ll be redirected to your Feed and a column will be "
"automatically added with the publications of your freshly added account. You"
" can then add new streams to your Feed and customize your Kanban view as you"
" like."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:28
msgid ""
"Adding social media accounts to your Feed will also add some KPIs on it:"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:30
msgid "Audience: Number of followers of your channel"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:32
msgid "Engagement: Number of times people have engaged with your posts"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:35
msgid "Stories: Number of times people who have engaged with your channel"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:35
msgid ""
"have created stories on their friend’s or follower’s feed (Shares, "
"Retweet,..)"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:37
msgid ""
"You can access more information by clicking on the “Insights” link: this "
"will lead you to statistics of the selected social medium."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:41
msgid "Publish content"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:43
msgid ""
"To publish content on your social media accounts or send a push notification"
" to your subscribed users, either go to your Feed and click on New Post, or "
"use the “Posts” menu and create it from there. Select all the accounts where"
" you want to post your content, write your post and get an instant preview "
"of how it will look when published."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:49
msgid ""
"If you select the push notifications, you’ll get some additional fields on "
"the form that will allow you to complete the push notifications "
"configuration and choose your segment between all your subscribed users. You"
" can also send push notifications via the Visitors menu, as explained in the"
" previous paragraph."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:56
msgid "Enable push notifications on your website"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:58
msgid ""
"The push notifications system uses a Firebase account, configured by "
"default. This feature allows you to send push notifications to your "
"website’s visitors after they subscribed to it. To enable push notifications"
" on your website, go to the Website application Settings, and configure the "
"notifications permission request."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:67
msgid ""
"Once it’s done, a popup will appear to your website’s visitors, asking them "
"to allow push notifications. As soon as they subscribe to it, you can start "
"sending them push notifications through the Visitors menu. You can either "
"send it individually or target a bigger segment by selecting multiple "
"visitors in the list view (e.g. all the visitors that visited your "
"Homepage)."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:75
msgid "Interact with your online visitors"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:77
msgid ""
"You can monitor your online visits via the Visitors menu. You’ll see every "
"visitors that landed on one of your tracked pages (you can configure your "
"tracked pages in the Website application), online or offline. Your online "
"visitors will be authenticated if they’re linked to a lead or an existing "
"partner. You will be able to contact them with an email, a message sms, a "
"push notification (if they have subscribed to it), or even send them a live "
"chat request that they will receive on their next move on one of your "
"tracked pages (if you installed the Live Chat application)."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:91
msgid "Configure your own Facebook and Twitter developer accounts"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:93
msgid ""
"By default, the Social application is already configured with a Facebook and"
" Twitter developer accounts but you can use your own if necessary. Activate "
"the developer mode, go to Configuration > Settings and enter your own API "
"keys."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:102
msgid "Configure your own Firebase API"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:104
msgid ""
"By default, a Firebase project is running on your database so there’s no "
"need to configure it. If you have multiple websites, every website will be "
"linked to a different Firebase project. If you need to configure your own "
"Firebase project, please go to :menuselection:`Website --> Configuration -->"
" Settings` Web Push Notifications section."
msgstr ""