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

[I18N] *: export pot files

Browse Source 
And fetch matching translations
This commit is contained in:
Martin Trigaux
2021-05-18 07:16:30 +02:00
parent 8ad392222b
commit e9d06b7881
514 changed files with 290877 additions and 436984 deletions
Download Patch File Download Diff File Expand all files Collapse all files
locale/ar/LC_MESSAGES/accounting.po
-13103
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/applications.po
-22
View File
@@ -1,22 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+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"
#: ../../applications.rst:3
msgid "Applications"
msgstr ""
locale/ar/LC_MESSAGES/crm.po
-1299
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/db_management.po
-778
View File
@@ -1,778 +0,0 @@
# 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-10-03 09:46+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"
#: ../../db_management/db_online.rst:8
msgid "Online Database management"
msgstr ""
#: ../../db_management/db_online.rst:10
msgid ""
"To manage your databases, access the `database management page "
"<https://www.odoo.com/my/databases>`__ (you will have to sign in). Then "
"click on the `Manage Your Databases "
"<https://www.odoo.com/my/databases/manage>`__ button."
msgstr ""
#: ../../db_management/db_online.rst:18
msgid ""
"Make sure you are connected as the administrator of the database you want to"
" manage - many operations depends on indentifying you remotely to that "
"database."
msgstr ""
#: ../../db_management/db_online.rst:22
msgid "Several actions are available:"
msgstr ""
#: ../../db_management/db_online.rst:28
msgid ":ref:`Upgrade <upgrade_button>`"
msgstr ""
#: ../../db_management/db_online.rst:28
msgid ""
"Upgrade your database to the latest Odoo version to enjoy cutting-edge "
"features"
msgstr ""
#: ../../db_management/db_online.rst:32
msgid ":ref:`Duplicate <duplicate_online>`"
msgstr ""
#: ../../db_management/db_online.rst:31
msgid ""
"Make an exact copy of your database, if you want to try out new apps or new "
"flows without compromising your daily operations"
msgstr ""
#: ../../db_management/db_online.rst:34
msgid ":ref:`Rename <rename_online_database>`"
msgstr ""
#: ../../db_management/db_online.rst:35
msgid "Rename your database (and its URL)"
msgstr ""
#: ../../db_management/db_online.rst:37
msgid "**Backup**"
msgstr ""
#: ../../db_management/db_online.rst:37
msgid ""
"Download an instant backup of your database; note that we back up databases "
"daily according to our Odoo Cloud SLA"
msgstr ""
#: ../../db_management/db_online.rst:40
msgid ":ref:`Domains <custom_domain>`"
msgstr ""
#: ../../db_management/db_online.rst:40
msgid "Configure custom domains to access your database via another URL"
msgstr ""
#: ../../db_management/db_online.rst:42
msgid ":ref:`Delete <delete_online_database>`"
msgstr ""
#: ../../db_management/db_online.rst:43
msgid "Delete a database instantly"
msgstr ""
#: ../../db_management/db_online.rst:46
msgid "Contact Support"
msgstr ""
#: ../../db_management/db_online.rst:45
msgid ""
"Access our `support page <https://www.odoo.com/help>`__ with the correct "
"database already selected"
msgstr ""
#: ../../db_management/db_online.rst:51
msgid "Upgrade"
msgstr ""
#: ../../db_management/db_online.rst:53
msgid ""
"Upgrading your database to a newer version of Odoo is a complex operation "
"that require time and caution. It is extremely important that you fully test"
" the process before upgrading your production database."
msgstr ""
#: ../../db_management/db_online.rst:57
msgid ""
"Odoo releases new versions regularly (at least once a year), and upgrading "
"your database to enjoy new Odoo features is part of the Odoo Online "
"experience."
msgstr ""
#: ../../db_management/db_online.rst:60
msgid ""
"The upgrade process can take some time, especially if you use multiple apps "
"or apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In "
"general, the 'smaller' the database, the quickest the upgrade. A single-user"
" database that uses only CRM will be processed faster than a multi-company, "
"multi-user database that uses Accounting, Sales, Purchase and Manufacturing."
msgstr ""
#: ../../db_management/db_online.rst:66
msgid ""
"Unfortunately, it is impossible to give time estimates for every upgrade "
"request, since Odoo.com will test manually every database upgrade at least "
"once and will need to correct/adapt changes made to the standard Odoo Apps "
"(e.g. through Studio or through a Success Pack) on a case-by-case basis. "
"This can make the process slower, since requests are treated in the order "
"they arrive. This is especially true in the months following the release of "
"a new major version, which can lengthen the upgrade delay significantly."
msgstr ""
#: ../../db_management/db_online.rst:74
msgid "The upgrade process is quite simple from your point of view:"
msgstr ""
#: ../../db_management/db_online.rst:76
msgid "You request a test upgrade"
msgstr ""
#: ../../db_management/db_online.rst:77
msgid ""
"Once all tests have been validated **by you**, you upgrade your actual "
"database"
msgstr ""
#: ../../db_management/db_online.rst:79
msgid ""
"The process to request a test or a production (*actual*) upgrade is the "
"same."
msgstr ""
#: ../../db_management/db_online.rst:81
msgid ""
"First, make sure to be connected to the database you want to upgrade and "
"access the `database management page <https://www.odoo.com/my/databases>`__."
msgstr ""
#: ../../db_management/db_online.rst:84
msgid ""
"You have to have an active session with access to the Settings app in the "
"database you want to upgrade for the button to be visible."
msgstr ""
#: ../../db_management/db_online.rst:87
msgid ""
"On the line of the database you want to upgrade, click on the \"Cog\" menu. "
"If an newer version of Odoo is available, you will see an 'Upgrade' button."
msgstr ""
#: ../../db_management/db_online.rst:94
msgid ""
"You have the possibility to choose the target version of the upgrade. By "
"default, we select the highest available version available for your "
"database; if you were already in the process of testing an upgrade, we will "
"automatically select the version you were already testing (even if we "
"released a more recent version during your tests)."
msgstr ""
#: ../../db_management/db_online.rst:103
msgid ""
"By clicking on the \"Test upgrade\" button, an upgrade request will be "
"generated. Only one request can be made at time for each database; if a "
"request has already been made, you will see an 'Upgrade Queued' note instead"
" and asking another request will not be possible."
msgstr ""
#: ../../db_management/db_online.rst:108
msgid ""
"A test upgrade will create a copy of your database, upgrade it and make it "
"available to you automatically once successful. If this is the first test "
"you request for this particular database, a manual testing phase will be "
"done by Odoo.com - this could take time (up to several weeks). Subsequent "
"requests will not go through that manual testing step and will usually be "
"made available in a few hours. Once the test database is available, you "
"should receive an e-mail with the URL of the test database."
msgstr ""
#: ../../db_management/db_online.rst:116
msgid ""
"**Testing your database is the most important step of the upgrade process!**"
" Even though we test all upgrades manually, we do not know your work "
"processes. A change in standard worfklows of Odoo in new versions might "
"require you to change internal processes, or some of the customizations you "
"made through Odoo Studio might now work properly. *It is up to you to make "
"sure that everything works as it should!* You can report issues with your "
"test database through our `Support page <https://www.odoo.com/help>`__."
msgstr ""
#: ../../db_management/db_online.rst:124
msgid ""
"Make sure to do one last test of your upgrade right before the final upgrade"
" (e.g. the day before) to ensure everything will run smoothly. Downgrading "
"is not possible and post-poning an upgrade is always easier than being "
"prevented to work by an upgrade issue after the fact!"
msgstr ""
#: ../../db_management/db_online.rst:129
msgid ""
"Once you are ready and you have validated all your tests, you can click "
"again on the Upgrade button and confirm by clicking on Upgrade (the button "
"with the little rocket!) to switch your production database to the new "
"version. Your database will then be taken offline within the next 10 minutes"
" and will be upgraded automatically; you receive a confirmation e-mail once "
"the process is completed."
msgstr ""
#: ../../db_management/db_online.rst:139
msgid ""
"Your database will be taken offline during the upgrade (usually between "
"30min up to several hours for big databases), so make sure to plan your "
"migration during non-business hours."
msgstr ""
#: ../../db_management/db_online.rst:146
msgid "Duplicating a database"
msgstr ""
#: ../../db_management/db_online.rst:148
msgid ""
"Database duplication, renaming, custom DNS, etc. is not available for trial "
"databases on our Online platform. Paid Databases and \"One App Free\" "
"database can duplicate without problem."
msgstr ""
#: ../../db_management/db_online.rst:153
msgid ""
"In the line of the database you want to duplicate, you will have a few "
"buttons. To duplicate your database, just click **Duplicate**. You will have"
" to give a name to your duplicate, then click **Duplicate Database**."
msgstr ""
#: ../../db_management/db_online.rst:160
msgid ""
"If you do not check the \"For testing purposes\" checkbox when duplicating a"
" database, all external communication will remain active:"
msgstr ""
#: ../../db_management/db_online.rst:163
msgid "Emails are sent"
msgstr ""
#: ../../db_management/db_online.rst:165
msgid ""
"Payments are processed (in the e-commerce or Subscriptions apps, for "
"example)"
msgstr ""
#: ../../db_management/db_online.rst:168
msgid "Delivery orders (shipping providers) are sent"
msgstr ""
#: ../../db_management/db_online.rst:170
msgid "Etc."
msgstr ""
#: ../../db_management/db_online.rst:172
msgid ""
"Make sure to check the checkbox \"For testing purposes\" if you want these "
"behaviours to be disabled."
msgstr ""
#: ../../db_management/db_online.rst:175
msgid ""
"After a few seconds, you will be logged in your duplicated database. Notice "
"that the url uses the name you chose for your duplicated database."
msgstr ""
#: ../../db_management/db_online.rst:179
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../db_management/db_online.rst:187
msgid "Rename a Database"
msgstr ""
#: ../../db_management/db_online.rst:189
msgid ""
"To rename your database, make sure you are connected to the database you "
"want to rename, access the `database management page "
"<https://www.odoo.com/my/databases>`__ and click **Rename**. You will have "
"to give a new name to your database, then click **Rename Database**."
msgstr ""
#: ../../db_management/db_online.rst:200
msgid "Deleting a Database"
msgstr ""
#: ../../db_management/db_online.rst:202
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../db_management/db_online.rst:204
msgid ""
"When you delete your database all the data will be permanently lost. The "
"deletion is instant and for all the Users. We advise you to do an instant "
"backup of your database before deleting it, since the last automated daily "
"backup may be several hours old at that point."
msgstr ""
#: ../../db_management/db_online.rst:210
msgid ""
"From the `database management page <https://www.odoo.com/my/databases>`__, "
"on the line of the database you want to delete, click on the \"Delete\" "
"button."
msgstr ""
#: ../../db_management/db_online.rst:217
msgid ""
"Read carefully the warning message that will appear and proceed only if you "
"fully understand the implications of deleting a database:"
msgstr ""
#: ../../db_management/db_online.rst:223
msgid ""
"After a few seconds, the database will be deleted and the page will reload "
"automatically."
msgstr ""
#: ../../db_management/db_online.rst:227
msgid ""
"If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../db_management/db_online.rst:229
msgid ""
"It is not possible to delete a database if it is expired or linked to a "
"Subscription. In these cases contact `Odoo Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_online.rst:233
msgid ""
"If you want to delete your Account, please contact `Odoo Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:7
msgid "On-premises Database management"
msgstr ""
#: ../../db_management/db_premise.rst:10
msgid "Register a database"
msgstr ""
#: ../../db_management/db_premise.rst:12
msgid ""
"To register your database, you just need to enter your Subscription Code in "
"the banner in the App Switcher. Make sure you do not add extra spaces before"
" or after your subscription code. If the registration is successful, it will"
" turn green and will provide you with the Expiration Date of your freshly-"
"registered database. You can check this Epiration Date in the About menu "
"(Odoo 9) or in the Settings Dashboard (Odoo 10)."
msgstr ""
#: ../../db_management/db_premise.rst:20
msgid "Registration Error Message"
msgstr ""
#: ../../db_management/db_premise.rst:22
msgid ""
"If you are unable to register your database, you will likely encounter this "
"message:"
msgstr ""
#: ../../db_management/db_premise.rst:31
#: ../../db_management/db_premise.rst:110
#: ../../db_management/db_premise.rst:143
msgid "Solutions"
msgstr ""
#: ../../db_management/db_premise.rst:33
msgid "Do you have a valid Enterprise subscription?"
msgstr ""
#: ../../db_management/db_premise.rst:35
msgid ""
"Check if your subscription details get the tag \"In Progress\" on your `Odoo"
" Account <https://accounts.odoo.com/my/subscription>`__ or with your Account"
" Manager"
msgstr ""
#: ../../db_management/db_premise.rst:39
msgid "Have you already linked a database with your subscription reference?"
msgstr ""
#: ../../db_management/db_premise.rst:41
msgid ""
"You can link only one database per subscription. (Need a test or a "
"development database? `Find a partner <https://www.odoo.com/partners>`__)"
msgstr ""
#: ../../db_management/db_premise.rst:45
msgid ""
"You can unlink the old database yourself on your `Odoo Contract "
"<https://accounts.odoo.com/my/subscription>`__ with the button \"Unlink "
"database\""
msgstr ""
#: ../../db_management/db_premise.rst:52
msgid ""
"A confirmation message will appear; make sure this is the correct database "
"as it will be deactivated shortly:"
msgstr ""
#: ../../db_management/db_premise.rst:59
msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../db_management/db_premise.rst:61
#: ../../db_management/db_premise.rst:176
msgid ""
"From July 2016 onward, Odoo 9 now automatically change the uuid of a "
"duplicated database; a manual operation is no longer required."
msgstr ""
#: ../../db_management/db_premise.rst:64
msgid ""
"If it's not the case, you may have multiple databases sharing the same UUID."
" Please check on your `Odoo Contract "
"<https://accounts.odoo.com/my/subscription>`__, a short message will appear "
"specifying which database is problematic:"
msgstr ""
#: ../../db_management/db_premise.rst:73
msgid ""
"In this case, you need to change the UUID on your test databases to solve "
"this issue. You will find more information about this in :ref:`this section "
"<duplicate_premise>`."
msgstr ""
#: ../../db_management/db_premise.rst:76
msgid ""
"For your information, we identify database with UUID. Therefore, each "
"database should have a distinct UUID to ensure that registration and "
"invoicing proceed effortlessly for your and for us."
msgstr ""
#: ../../db_management/db_premise.rst:80
msgid "Check your network and firewall settings"
msgstr ""
#: ../../db_management/db_premise.rst:82
msgid ""
"The Update notification must be able to reach Odoo's subscription validation"
" servers. In other words, make sure that the Odoo server is able to open "
"outgoing connections towards:"
msgstr ""
#: ../../db_management/db_premise.rst:86
msgid "services.odoo.com on port 443 (or 80)"
msgstr ""
#: ../../db_management/db_premise.rst:87
msgid "services.openerp.com on port 443 (or 80) for older deployments"
msgstr ""
#: ../../db_management/db_premise.rst:89
msgid ""
"Once you activated your database, you must keep these ports open, as the "
"Update notification runs once a week."
msgstr ""
#: ../../db_management/db_premise.rst:95
msgid "Error message due to too many users"
msgstr ""
#: ../../db_management/db_premise.rst:97
msgid ""
"If you have more users in your local database than provisionned in your Odoo"
" Enterprise subscription, you may encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:106
msgid ""
"When the message appears you have 30 days before the expiration. The "
"countdown is updated everyday."
msgstr ""
#: ../../db_management/db_premise.rst:112
msgid ""
"**Add more users** on your subscription: follow the link and Validate the "
"upsell quotation and pay for the extra users."
msgstr ""
#: ../../db_management/db_premise.rst:115
msgid "or"
msgstr ""
#: ../../db_management/db_premise.rst:117
msgid ""
"**Deactivate users** as explained in this `Documentation "
"<https://www.odoo.com "
"/documentation/user/13.0/db_management/documentation.html#deactivating-"
"users>`__ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:122
msgid ""
"Once your database has the correct number of users, the expiration message "
"will disappear automatically after a few days, when the next verification "
"occurs. We understand that it can be a bit frightening to see the countdown,"
" so you can :ref:`force an Update Notification <force_ping>` to make the "
"message disappear right away."
msgstr ""
#: ../../db_management/db_premise.rst:129
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:131
msgid ""
"If your database reaches its expiration date before your renew your "
"subscription, you will encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:139
msgid ""
"This **blocking** message appears after a non-blocking message that lasts 30"
" days. If you fail to take action before the end of the countdown, the "
"database is expired."
msgstr ""
#: ../../db_management/db_premise.rst:147
msgid ""
"Renew your subscription: follow the link and renew your subscription - note "
"that"
msgstr ""
#: ../../db_management/db_premise.rst:146
msgid ""
"if you wish to pay by Wire Transfer, your subscription will effectively be "
"renewed only when the payment arrives, which can take a few days. Credit "
"card payments are processed immediately."
msgstr ""
#: ../../db_management/db_premise.rst:149
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:151
msgid ""
"None of those solutions worked for you? Please contact our `Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:160
msgid "Duplicate a database"
msgstr ""
#: ../../db_management/db_premise.rst:162
msgid ""
"You can duplicate your database by accessing the database manager on your "
"server (<odoo-server>/web/database/manager). In this page, you can easily "
"duplicate your database (among other things)."
msgstr ""
#: ../../db_management/db_premise.rst:170
msgid ""
"When you duplicate a local database, it is **strongly** advised to change "
"the duplicated database's uuid (Unniversally Unique Identifier), since this "
"uuid is how your database identifies itself with our servers. Having two "
"databases with the same uuid could result in invoicing problems or "
"registration problems down the line."
msgstr ""
#: ../../db_management/db_premise.rst:179
msgid ""
"The database uuid is currently accessible from the menu **Settings > "
"Technical > System Parameters**, we advise you to use a `uuid generator "
"<https://www.uuidgenerator.net>`__ or to use the unix command ``uuidgen`` to"
" generate a new uuid. You can then simply replace it like any other record "
"by clicking on it and using the edit button."
msgstr ""
#: ../../db_management/documentation.rst:7
msgid "Users and Features"
msgstr ""
#: ../../db_management/documentation.rst:9
msgid ""
"As the administrator of your database, you are responsible for its usage. "
"This includes the Apps you install as well as the number of users currently "
"in use."
msgstr ""
#: ../../db_management/documentation.rst:13
msgid ""
"Odoo is many things (ERP, CMS, CRM application, e-Commerce backend, etc.) "
"but it is *not* a smartphone. You should apply caution when adding/removing "
"features (especially Apps) on your database since this may impact your "
"subscription amount significantly (or switch you from a free account to a "
"paying one on our online platform)."
msgstr ""
#: ../../db_management/documentation.rst:19
msgid ""
"This page contains some information as to how you can manage your Odoo "
"instances. Before carrying any of these procedures, we **strongly** advise "
"to test them on a duplicate of your database first. That way, if something "
"goes wrong, your day-to-day business is not impacted."
msgstr ""
#: ../../db_management/documentation.rst:24
msgid ""
"You can find guides on how to duplicate your databases both for :ref:`online"
" <duplicate_online>` and :ref:`on premise <duplicate_premise>` "
"installations."
msgstr ""
#: ../../db_management/documentation.rst:28
msgid ""
"If you have questions about the content of this page or if you encounter an "
"issue while carrying out these procedures, please contact us through our "
"`support form <https://www.odoo.com/help>`__."
msgstr ""
#: ../../db_management/documentation.rst:34
msgid "Deactivating Users"
msgstr ""
#: ../../db_management/documentation.rst:36
msgid ""
"Make sure you have sufficient **administrative rights** if you want to "
"change the status of any of your users."
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 Users.**"
msgstr ""
#: ../../db_management/documentation.rst:43
#: ../../db_management/documentation.rst:80
msgid "|settings|"
msgstr ""
#: ../../db_management/documentation.rst:43
msgid "|browse_users|"
msgstr ""
#: ../../db_management/documentation.rst:46
msgid "You'll then see the list of your users."
msgstr ""
#: ../../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:56
msgid ""
"In your list of users, click on the user you want to deactivate. As soon as "
"you are on the userform, click on the Action drop down menu, and then click "
"on Archive."
msgstr ""
#: ../../db_management/documentation.rst:64
msgid "The user is now deactivated."
msgstr ""
#: ../../db_management/documentation.rst:66
msgid "**Never** deactivate the main user (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:69
msgid "Uninstalling Apps"
msgstr ""
#: ../../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: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:80
msgid "|browse_apps|"
msgstr ""
#: ../../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:90
msgid ""
"Some applications have dependencies, like Invoicing, eCommerce, etc. "
"Therefore, the system will give you a warning message to advise you of what "
"is about to be removed. If you uninstall your application, all its "
"dependencies will be uninstalled as well (and the data in them will "
"permanently disappear). If you are sure you still want to uninstall it, then"
" click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:97
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:102
msgid "You have finished uninstalling your application."
msgstr ""
#: ../../db_management/documentation.rst:105
msgid "Good to know"
msgstr ""
#: ../../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 "
"uninstall applications for you, we would never be able to tell if relevant "
"data had been removed or if one of your business flow was broken because we "
"*do not know how you work* and therefore cannot validate these kinds of "
"operations."
msgstr ""
#: ../../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 "
"might need. For example, the Website Builder app is needed to be able to "
"show your customer their Quotes in a web page. Even though you might not "
"need or use the Website itself, it is needed for the Online Quotes feature "
"to work properly."
msgstr ""
#: ../../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 "
"will avoid surprises when uninstalling or when receiving your invoices."
msgstr ""
locale/ar/LC_MESSAGES/discuss.po
-658
View File
@@ -1,658 +0,0 @@
# 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-10-03 11:39+0200\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"
"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"
#: ../../discuss.rst:5
msgid "Discuss"
msgstr ""
#: ../../discuss/email_servers.rst:3
msgid "How to use my mail server to send and receive emails in Odoo"
msgstr ""
#: ../../discuss/email_servers.rst:5
msgid ""
"This document is mainly dedicated to Odoo on-premise users who don't benefit"
" from an out-of-the-box solution to send and receive emails in Odoo, unlike "
"`Odoo Online <https://www.odoo.com/trial>`__ & `Odoo.sh "
"<https://www.odoo.sh>`__."
msgstr ""
#: ../../discuss/email_servers.rst:9
msgid ""
"If no one in your company is used to manage email servers, we strongly "
"recommend that you opt for those Odoo hosting solutions. Their email system "
"works instantly and is monitored by professionals. Nevertheless you can "
"still use your own email servers if you want to manage your email server's "
"reputation yourself."
msgstr ""
#: ../../discuss/email_servers.rst:15
msgid ""
"You will find here below some useful information on how to integrate your "
"own email solution with Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:18
msgid ""
"Office 365 email servers don't allow easiliy to send external emails from "
"hosts like Odoo. Refer to the `Microsoft's documentation "
"<https://support.office.com/en-us/article/How-to-set-up-a-multifunction-"
"device-or-application-to-send-email-using-"
"Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to make it work."
msgstr ""
#: ../../discuss/email_servers.rst:24
msgid "How to manage outbound messages"
msgstr ""
#: ../../discuss/email_servers.rst:26
msgid ""
"As a system admin, go to :menuselection:`Settings --> General Settings` and "
"check *External Email Servers*. Then, click *Outgoing Mail Servers* to "
"create one and reference the SMTP data of your email server. Once all the "
"information has been filled out, click on *Test Connection*."
msgstr ""
#: ../../discuss/email_servers.rst:31
msgid "Here is a typical configuration for a G Suite server."
msgstr ""
#: ../../discuss/email_servers.rst:36
msgid "Then set your email domain name in the General Settings."
msgstr ""
#: ../../discuss/email_servers.rst:39
msgid "Can I use an Office 365 server"
msgstr ""
#: ../../discuss/email_servers.rst:40
msgid ""
"You can use an Office 365 server if you run Odoo on-premise. Office 365 SMTP"
" relays are not compatible with Odoo Online."
msgstr ""
#: ../../discuss/email_servers.rst:43
msgid ""
"Please refer to `Microsoft's documentation <https://support.office.com/en-"
"us/article/How-to-set-up-a-multifunction-device-or-application-to-send-"
"email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4>`__ to configure"
" a SMTP relay for your Odoo's IP address."
msgstr ""
#: ../../discuss/email_servers.rst:47
msgid "How to use a G Suite server"
msgstr ""
#: ../../discuss/email_servers.rst:48
msgid ""
"You can use an G Suite server for any Odoo hosting type. To do so you need "
"to setup the SMTP relay service. The configuration steps are explained in "
"`Google documentation "
"<https://support.google.com/a/answer/2956491?hl=en>`__."
msgstr ""
#: ../../discuss/email_servers.rst:55
msgid "Be SPF-compliant"
msgstr ""
#: ../../discuss/email_servers.rst:56
msgid ""
"In case you use SPF (Sender Policy Framework) to increase the deliverability"
" of your outgoing emails, don't forget to authorize Odoo as a sending host "
"in your domain name settings. Here is the configuration for Odoo Online:"
msgstr ""
#: ../../discuss/email_servers.rst:60
msgid ""
"If no TXT record is set for SPF, create one with following definition: "
"v=spf1 include:_spf.odoo.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:62
msgid ""
"In case a SPF TXT record is already set, add \"include:_spf.odoo.com\". e.g."
" for a domain name that sends emails via Odoo Online and via G Suite it "
"could be: v=spf1 include:_spf.odoo.com include:_spf.google.com ~all"
msgstr ""
#: ../../discuss/email_servers.rst:66
msgid ""
"Find `here <https://www.mail-tester.com/spf/>`__ the exact procedure to "
"create or modify TXT records in your own domain registrar."
msgstr ""
#: ../../discuss/email_servers.rst:69
msgid ""
"Your new SPF record can take up to 48 hours to go into effect, but this "
"usually happens more quickly."
msgstr ""
#: ../../discuss/email_servers.rst:72
msgid ""
"Adding more than one SPF record for a domain can cause problems with mail "
"delivery and spam classification. Instead, we recommend using only one SPF "
"record by modifying it to authorize Odoo."
msgstr ""
#: ../../discuss/email_servers.rst:77
msgid "Allow DKIM"
msgstr ""
#: ../../discuss/email_servers.rst:78
msgid ""
"You should do the same thing if DKIM (Domain Keys Identified Mail) is "
"enabled on your email server. In the case of Odoo Online & Odoo.sh, you "
"should add a DNS \"odoo._domainkey\" CNAME record to "
"\"odoo._domainkey.odoo.com\". For example, for \"foo.com\" they should have "
"a record \"odoo._domainkey.foo.com\" that is a CNAME with the value "
"\"odoo._domainkey.odoo.com\"."
msgstr ""
#: ../../discuss/email_servers.rst:86
msgid "How to manage inbound messages"
msgstr ""
#: ../../discuss/email_servers.rst:88
msgid "Odoo relies on generic email aliases to fetch incoming messages."
msgstr ""
#: ../../discuss/email_servers.rst:90
msgid ""
"**Reply messages** of messages sent from Odoo are routed to their original "
"discussion thread (and to the inbox of all its followers) by the catchall "
"alias (**catchall@**)."
msgstr ""
#: ../../discuss/email_servers.rst:94
msgid ""
"**Bounced messages** are routed to **bounce@** in order to track them in "
"Odoo. This is especially used in `Odoo Email Marketing "
"<https://www.odoo.com/page/email-marketing>`__ to opt-out invalid "
"recipients."
msgstr ""
#: ../../discuss/email_servers.rst:98
msgid ""
"**Original messages**: Several business objects have their own alias to "
"create new records in Odoo from incoming emails:"
msgstr ""
#: ../../discuss/email_servers.rst:101
msgid ""
"Sales Channel (to create Leads or Opportunities in `Odoo CRM "
"<https://www.odoo.com/page/crm>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:103
msgid ""
"Support Channel (to create Tickets in `Odoo Helpdesk "
"<https://www.odoo.com/page/helpdesk>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:105
msgid ""
"Projects (to create new Tasks in `Odoo Project <https://www.odoo.com/page"
"/project-management>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:107
msgid ""
"Job Positions (to create Applicants in `Odoo Recruitment "
"<https://www.odoo.com/page/recruitment>`__),"
msgstr ""
#: ../../discuss/email_servers.rst:109
msgid "etc."
msgstr ""
#: ../../discuss/email_servers.rst:111
msgid ""
"Depending on your mail server, there might be several methods to fetch "
"emails. The easiest and most recommended method is to manage one email "
"address per Odoo alias in your mail server."
msgstr ""
#: ../../discuss/email_servers.rst:115
msgid ""
"Create the corresponding email addresses in your mail server (catchall@, "
"bounce@, sales@, etc.)."
msgstr ""
#: ../../discuss/email_servers.rst:117
msgid "Set your domain name in the General Settings."
msgstr ""
#: ../../discuss/email_servers.rst:122
msgid ""
"If you use Odoo on-premise, create an *Incoming Mail Server* in Odoo for "
"each alias. You can do it from the General Settings as well. Fill out the "
"form according to your email provider’s settings. Leave the *Actions to "
"Perform on Incoming Mails* blank. Once all the information has been filled "
"out, click on *TEST & CONFIRM*."
msgstr ""
#: ../../discuss/email_servers.rst:131
msgid ""
"If you use Odoo Online or Odoo.sh, We do recommend to redirect incoming "
"messages to Odoo's domain name rather than exclusively use your own email "
"server. That way you will receive incoming messages without delay. Indeed, "
"Odoo Online is fetching incoming messages of external servers once per hour "
"only. You should set redirections for all the email addresses to Odoo's "
"domain name in your email server (e.g. *catchall@mydomain.ext* to "
"*catchall@mycompany.odoo.com*)."
msgstr ""
#: ../../discuss/email_servers.rst:138
msgid ""
"All the aliases are customizable in Odoo. Object aliases can be edited from "
"their respective configuration view. To edit catchall and bounce aliases, "
"you first need to activate the developer mode from the Settings Dashboard."
msgstr ""
#: ../../discuss/email_servers.rst:146
msgid ""
"Then refresh your screen and go to :menuselection:`Settings --> Technical "
"--> Parameters --> System Parameters` to customize the aliases "
"(*mail.catchall.alias* & * mail.bounce.alias*)."
msgstr ""
#: ../../discuss/email_servers.rst:153
msgid ""
"By default inbound messages are fetched every 5 minutes in Odoo on-premise. "
"You can change this value in developer mode. Go to :menuselection:`Settings "
"--> Technical --> Automation --> Scheduled Actions` and look for *Mail: "
"Fetchmail Service*."
msgstr ""
#: ../../discuss/mail_twitter.rst:3
msgid "How to follow Twitter feed from Odoo"
msgstr ""
#: ../../discuss/mail_twitter.rst:8
msgid ""
"You can follow specific hashtags on Twitter and see the tweets within the "
"Odoo Discuss channels of your choice. The tweets are retrieved periodically "
"from Twitter. An authenticated user can retweet the messages."
msgstr ""
#: ../../discuss/mail_twitter.rst:13
msgid "Setting up the App on Twitter's side"
msgstr ""
#: ../../discuss/mail_twitter.rst:15
msgid ""
"Twitter uses an \"App\" on its side which is opens a gate to which Odoo asks"
" for tweets, and through which a user can retweet. To set up this app, go to"
" http://apps.twitter.com/app/new and put in the values:"
msgstr ""
#: ../../discuss/mail_twitter.rst:19
msgid "Name: this is the name of the application on Twitter"
msgstr ""
#: ../../discuss/mail_twitter.rst:21
msgid ""
"Website: this is the external url of your Odoo database, with \"/web\" "
"added. For example, if your Odoo instance is hosted at "
"\"http://www.example.com\", you should put \"http://www.example.com/web\" in"
" this field."
msgstr ""
#: ../../discuss/mail_twitter.rst:25
msgid ""
"Callback URL: this is the address on which Twitter will respond. Following "
"the previous example you should write "
"\"http://www.example.com/web/twitter/callback\"."
msgstr ""
#: ../../discuss/mail_twitter.rst:28
msgid ""
"Do not forget to accept the terms **Developer agreement** of use and click "
"on **Create your Twitter application** at the bottom of the page."
msgstr ""
#: ../../discuss/mail_twitter.rst:33
msgid "Getting the API key and secret"
msgstr ""
#: ../../discuss/mail_twitter.rst:35
msgid ""
"When on the App dashboard, switch to the **Keys and Access Tokens** tab."
msgstr ""
#: ../../discuss/mail_twitter.rst:40
msgid ""
"And copy those values in Odoo in :menuselection:`Settings--> General "
"Settings--> Twitter discuss integration` and click on **Save** to save the "
"settings."
msgstr ""
#: ../../discuss/mentions.rst:3
msgid "How to grab attention of other users in my messages"
msgstr ""
#: ../../discuss/mentions.rst:5
msgid ""
"You can **mention** a user in a channel or chatter by typing **@user-name**."
" Mentioning a user in the chatter will set them as a follower of the item "
"(if they are not already) and send a message to their inbox. The item "
"containing the mention will also be bolded in the list view. Mentioning a "
"user in a channel will send a message to their inbox. You cannot mention a "
"user in a channel who is not subscribed to the channel. Typing **#channel-"
"name** will provide a link to the mentioned channel in either a chatter or "
"another channel."
msgstr ""
#: ../../discuss/mentions.rst:15
msgid "Direct messaging a user"
msgstr ""
#: ../../discuss/mentions.rst:17
msgid ""
"**Direct messages** are private messages viewable only by the sender and "
"recipient. You can send direct messages to other users from within the "
"Discuss module by creating a new conversation or selecting an existing one "
"from the sidebar. Direct messages can be sent from anywhere in Odoo using "
"the speech bubble icon in the top bar. The online status of other users is "
"displayed to the left of their name. A **green dot** indicates that a user "
"is Online, an **orange dot** that they are Idle, and a **grey dot** that "
"they are offline."
msgstr ""
#: ../../discuss/mentions.rst:28
msgid "Desktop notifications from Discuss"
msgstr ""
#: ../../discuss/mentions.rst:30
msgid ""
"You can choose to see **desktop notifications** when you receive a new "
"direct message. The notification shows you the sender and a brief preview of"
" the message contents. These can be configured or disabled by clicking on "
"the gear icon in the corner of the notification.."
msgstr ""
#: ../../discuss/monitoring.rst:3
msgid "How to be responsive at work thanks to my Odoo inbox"
msgstr ""
#: ../../discuss/monitoring.rst:5
msgid ""
"Use the **Inbox** in Discuss app to monitor updates and progress on "
"everything you do in Odoo. Notifications and messages from everything you "
"follow or in which you are mentioned appear in your inbox."
msgstr ""
#: ../../discuss/monitoring.rst:13
msgid "You can keep an eye on your **Inbox** from any screen."
msgstr ""
#: ../../discuss/monitoring.rst:18
msgid ""
"Marking an item with a check marks the message as **read** and removes it "
"from your inbox. If you would like to save an item for future reference or "
"action, mark it with a star to add it to the **Starred** box. You can star "
"any message or notification in Discuss or any of the item-specific chatters "
"throughout Odoo to keep tabs on it here."
msgstr ""
#: ../../discuss/overview.rst:3
msgid "Why use Odoo Discuss"
msgstr ""
#: ../../discuss/overview.rst:5
msgid ""
"Odoo Discuss is an easy to use messaging app for teams that brings all your "
"organization's communication into one place and seamlessly integrates with "
"the Odoo platform. Discuss lets you send and receive messages from wherever "
"you are in Odoo as well as manage your messages and notifications easily "
"from within the app. Discuss allows you to create **channels** for team "
"chats, conversations about projects, meeting coordination, and more in one "
"simple and searchable interface."
msgstr ""
#: ../../discuss/plan_activities.rst:3
msgid "Get organized by planning activities"
msgstr ""
#: ../../discuss/plan_activities.rst:5
msgid ""
"Planning activities is the perfect way to keep on track with your work. Get "
"reminded of what needs to be done and schedule the next activities to "
"undertake."
msgstr ""
#: ../../discuss/plan_activities.rst:9
msgid ""
"Your activities are available wherever you are in Odoo. It is easy to manage"
" your priorities."
msgstr ""
#: ../../discuss/plan_activities.rst:15
msgid ""
"Activities can be planned and managed from the chatters or in the kanban "
"views. Here is an example for opportunities :"
msgstr ""
#: ../../discuss/plan_activities.rst:22
msgid "Set your activity types"
msgstr ""
#: ../../discuss/plan_activities.rst:24
msgid ""
"A number of generic activities types are available by default in Odoo (e.g. "
"call, email, meeting, etc.). If you would like to set new ones, go to "
":menuselection:`Settings --> General settings --> Activity types`."
msgstr ""
#: ../../discuss/plan_activities.rst:29
msgid "Schedule meetings"
msgstr ""
#: ../../discuss/plan_activities.rst:31
msgid ""
"Activities are planned for specific days. If you need to set hours, go with "
"the *Meeting* activity type. When scheduling one, the calendar will simply "
"open to let you select a time slot."
msgstr ""
#: ../../discuss/plan_activities.rst:36
msgid ""
"If you need to use other activity types with a calendar planning, make sure "
"their *Category* is set as *Meeting*."
msgstr ""
#: ../../discuss/plan_activities.rst:40
msgid "Schedule a chain of activities to follow"
msgstr ""
#: ../../discuss/plan_activities.rst:42
msgid ""
"Odoo helps you easily plan your usual flow of activities. Go to "
":menuselection:`Configuration --> Activity Types` and set the common "
"following steps as *Recommended next activities*."
msgstr ""
#: ../../discuss/plan_activities.rst:49
msgid ""
"Now, when an activity is completed, you can select *Done & schedule next*. "
"The next steps will automatically be suggested to you."
msgstr ""
#: ../../discuss/plan_activities.rst:55
msgid "Have fun getting better organized by planning activities !"
msgstr ""
#: ../../discuss/team_communication.rst:3
msgid "How to efficiently communicate in team using channels"
msgstr ""
#: ../../discuss/team_communication.rst:5
msgid ""
"You can use **channels** to organize discussions between individual teams, "
"departments, projects, or any other group that requires regular "
"communication. By having conversations that everyone in the channel can see,"
" it's easy to keep the whole team in the loop with the latest developments."
msgstr ""
#: ../../discuss/team_communication.rst:12
msgid "Creating a channel"
msgstr ""
#: ../../discuss/team_communication.rst:14
msgid ""
"In Discuss there are two types of channels - **public** and **private**."
msgstr ""
#: ../../discuss/team_communication.rst:17
msgid ""
"A **public channel** can only be created by an administrator with write "
"privileges and can be seen by everyone in the organization. By contrast, a "
"**private channel** can be created by any user and by default is only "
"visible to users who have been invited to this channel."
msgstr ""
#: ../../discuss/team_communication.rst:24
msgid ""
"A public channel is best used when many employees need to access information"
" (such as interdepartmental communication or company announcements), whereas"
" a private channel should be used whenever information should be limited to "
"specific users/employees (such as department specific or sensitive "
"information)."
msgstr ""
#: ../../discuss/team_communication.rst:31
msgid "Configuring a channel"
msgstr ""
#: ../../discuss/team_communication.rst:33
msgid ""
"You can configure a channel's name, description, access rights, automatic "
"subscription, and emailing from :menuselection:`#channel-name --> Settings`."
" Changing channel access rights allows you to control which groups can view "
"each channel. You can make a channel visible by all users, invited users, or"
" users within a selected user group. Note that allowing \"Everyone\" to "
"follow a private channel will let other users view and join it as they would"
" a public channel."
msgstr ""
#: ../../discuss/team_communication.rst:47
msgid "How to set up a mailing list"
msgstr ""
#: ../../discuss/team_communication.rst:49
msgid ""
"A channel can be configured to behave as a mailing list. From within "
":menuselection:`#channel-name --> Settings`, define the email you would like"
" to use. Users can then post to the channel and choose to receive "
"notifications using the defined email address. An envelope icon will appear "
"next to the channel name in the list to indicate that a channel will send "
"messages by email."
msgstr ""
#: ../../discuss/team_communication.rst:57
msgid "Locating a channel"
msgstr ""
#: ../../discuss/team_communication.rst:59
msgid ""
"If you do not see a channel on your dashboard, you can search the list of "
"**public channels** to locate the correct channel or create a new channel by"
" clicking the plus icon."
msgstr ""
#: ../../discuss/team_communication.rst:66
msgid ""
"You can also click the **CHANNELS** heading to browse a list of all public "
"channels. This allows the user to manually **join** and **leave** public "
"channels from a single screen."
msgstr ""
#: ../../discuss/team_communication.rst:71
msgid ""
"It is always wise to search for a channel before creating a new one to "
"ensure that duplicate entries are not created for the same topic."
msgstr ""
#: ../../discuss/team_communication.rst:76
msgid "Using filters to navigate within Discuss"
msgstr ""
#: ../../discuss/team_communication.rst:78
msgid ""
"The topbar search provides access to the same comprehensive search function "
"present in the rest of Odoo. You can apply multiple **filter criteria** and "
"**save filters** for later use. The search function accepts wildcards by "
"using the underscore character \"\\ **\\_**\\ \" to represent a **single "
"character wildcard.**"
msgstr ""
#: ../../discuss/tracking.rst:3
msgid "How to follow a discussion thread and define what I want to hear about"
msgstr ""
#: ../../discuss/tracking.rst:6
msgid "How to follow a discussion thread"
msgstr ""
#: ../../discuss/tracking.rst:7
msgid ""
"You can keep track of virtually any business object in Odoo (an opportunity,"
" a quotation, a task, etc.), by **following** it."
msgstr ""
#: ../../discuss/tracking.rst:14
msgid "How to choose the events to follow"
msgstr ""
#: ../../discuss/tracking.rst:15
msgid ""
"You can choose which types of events you want to be notified about. The "
"example below shows the options available when following a **task** in the "
"**Project** app."
msgstr ""
#: ../../discuss/tracking.rst:23
msgid "How to add other followers"
msgstr ""
#: ../../discuss/tracking.rst:24
msgid ""
"You can invite other users and add channels as followers. Adding a channel "
"as a follower will send messages posted in the chatter to the channel with a"
" link back to the original document."
msgstr ""
#: ../../discuss/tracking.rst:34
msgid "How to be a default follower"
msgstr ""
#: ../../discuss/tracking.rst:35
msgid ""
"You are automatically set as a default follower of any item you create. In "
"some applications like CRM and Project, you can be a default follower of any"
" new record created to get notified of specific events (e.g. a new task "
"created, an opportunity won)."
msgstr ""
#: ../../discuss/tracking.rst:40
msgid ""
"To do so, start following the parent business object (e.g. the sales channel"
" in CRM, the project in Project). Then, choose the events you want to hear "
"about."
msgstr ""
locale/ar/LC_MESSAGES/ecommerce.po
-1454
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/expenses.po
-22
View File
@@ -1,22 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:16+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"
"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"
#: ../../expenses.rst:5
msgid "Expenses"
msgstr ""
locale/ar/LC_MESSAGES/general.po
-1085
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/getting_started.po
-381
View File
@@ -1,381 +0,0 @@
# 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-10-03 11:39+0200\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"
"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"
#: ../../getting_started/documentation.rst:5
msgid "Basics of the QuickStart Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:7
msgid ""
"This document summarizes Odoo Online's services, our Success Pack "
"implementation methodology, and best practices to get started with our "
"product."
msgstr ""
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:14
msgid ""
"Within the context of your project, it is highly recommended to designate "
"and maintain on both sides (your side and ours) **one and only single person"
" of contact** who will take charge and assume responsibilities regarding the"
" project. He also has to have **the authority** in terms of decision making."
msgstr ""
#: ../../getting_started/documentation.rst:20
msgid ""
"**The Odoo Consultant ensures the project implementation from A to Z**: From"
" the beginning to the end of the project, he ensures the overall consistency"
" of the implementation in Odoo and shares his expertise in terms of good "
"practices."
msgstr ""
#: ../../getting_started/documentation.rst:25
msgid ""
"**One and only decision maker on the client side (SPoC)**: He is responsible"
" for the business knowledge transmission (coordinate key users intervention "
"if necessary) and the consistency of the implementation from a business "
"point of view (decision making, change management, etc.)"
msgstr ""
#: ../../getting_started/documentation.rst:31
msgid ""
"**Meetings optimization**: The Odoo consultant is not involved in the "
"process of decision making from a business point of view nor to precise "
"processes and company's internal procedures (unless a specific request or an"
" exception). Project meetings, who will take place once or twice a week, are"
" meant to align on the business needs (SPoC) and to define the way those "
"needs will be implemented in Odoo (Consultant)."
msgstr ""
#: ../../getting_started/documentation.rst:39
msgid ""
"**Train the Trainer approach**: The Odoo consultant provides functional "
"training to the SPoC so that he can pass on this knowledge to his "
"collaborators. In order for this approach to be successful, it is necessary "
"that the SPoC is also involved in its own rise in skills through self-"
"learning via the `Odoo documentation "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning "
"platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
"testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:49
msgid ""
"To make sure all the stakeholders involved are always aligned, it is "
"necessary to define and to make the project scope evolve as long as the "
"project implementation is pursuing."
msgstr ""
#: ../../getting_started/documentation.rst:53
msgid ""
"**A clear definition of the initial project scope**: A clear definition of "
"the initial needs is crucial to ensure the project is running smoothly. "
"Indeed, when all the stakeholders share the same vision, the evolution of "
"the needs and the resulting decision-making process are more simple and more"
" clear."
msgstr ""
#: ../../getting_started/documentation.rst:59
msgid ""
"**Phasing the project**: Favoring an implementation in several coherent "
"phases allowing regular production releases and an evolving takeover of Odoo"
" by the end users have demonstrated its effectiveness over time. This "
"approach also helps to identify gaps and apply corrective actions early in "
"the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:66
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
"important ones (developments). Nevertheless, adoption of the standard "
"solution will be preferred as often as possible in order to optimize project"
" delivery times and provide the user with a long-term stability and fluid "
"scalability of his new tool. Ideally, if an improvement of the software "
"should still be realized, its implementation will be carried out after an "
"experiment of the standard in production."
msgstr ""
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:82
msgid ""
"The gap between the reality of an implementation and the expectations of "
"future users is a crucial factor. Three important aspects must be taken into"
" account from the beginning of the project:"
msgstr ""
#: ../../getting_started/documentation.rst:86
msgid ""
"**Align with the project approach**: Both a clear division of roles and "
"responsibilities and a clear description of the operating modes (validation,"
" problem-solving, etc.) are crucial to the success of an Odoo "
"implementation. It is therefore strongly advised to take the necessary time "
"at the beginning of the project to align with these topics and regularly "
"check that this is still the case."
msgstr ""
#: ../../getting_started/documentation.rst:94
msgid ""
"**Focus on the project success, not on the ideal solution**: The main goal "
"of the SPoC and the Consultant is to carry out the project entrusted to them"
" in order to provide the most effective solution to meet the needs "
"expressed. This goal can sometimes conflict with the end user's vision of an"
" ideal solution. In that case, the SPoC and the consultant will apply the "
"80-20 rule: focus on 80% of the expressed needs and take out the remaining "
"20% of the most disadvantageous objectives in terms of cost/benefit ratio "
"(those proportions can of course change over time). Therefore, it will be "
"considered acceptable to integrate a more time-consuming manipulation if a "
"global relief is noted. Changes in business processes may also be proposed "
"to pursue this same objective."
msgstr ""
#: ../../getting_started/documentation.rst:108
msgid ""
"**Specifications are always EXPLICIT**: Gaps between what is expected and "
"what is delivered are often a source of conflict in a project. In order to "
"avoid being in this delicate situation, we recommend using several types of "
"tools\\* :"
msgstr ""
#: ../../getting_started/documentation.rst:113
msgid ""
"**The GAP Analysis**: The comparison of the request with the standard "
"features proposed by Odoo will make it possible to identify the gap to be "
"filled by developments/customizations or changes in business processes."
msgstr ""
#: ../../getting_started/documentation.rst:118
msgid ""
"**The User Story**: This technique clearly separates the responsibilities "
"between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, "
"and the Consultant who will provide a response to the HOW."
msgstr ""
#: ../../getting_started/documentation.rst:126
msgid ""
"`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A "
"simplified version, a prototype of what is expected to agree on the main "
"lines of expected changes."
msgstr ""
#: ../../getting_started/documentation.rst:130
msgid ""
"**The Mockup**: In the same idea as the Proof of Concept, it will align with"
" the changes related to the interface."
msgstr ""
#: ../../getting_started/documentation.rst:133
msgid ""
"To these tools will be added complete transparency on the possibilities and "
"limitations of the software and/or its environment so that all project "
"stakeholders have a clear idea of what can be expected/achieved in the "
"project. We will, therefore, avoid basing our work on hypotheses without "
"verifying its veracity beforehand."
msgstr ""
#: ../../getting_started/documentation.rst:139
msgid ""
"*This list can, of course, be completed by other tools that would more "
"adequately meet the realities and needs of your project*"
msgstr ""
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:145
msgid ""
"The purpose of the QuickStart methodology is to ensure quick ownership of "
"the tool for end users. Effective communication is therefore crucial to the "
"success of this approach. Its optimization will, therefore, lead us to "
"follow those principles:"
msgstr ""
#: ../../getting_started/documentation.rst:150
msgid ""
"**Sharing the project management documentation**: The best way to ensure "
"that all stakeholders in a project have the same level of knowledge is to "
"provide direct access to the project's tracking document (Project "
"Organizer). This document will contain at least a list of tasks to be "
"performed as part of the implementation for which the priority level and the"
" manager are clearly defined."
msgstr ""
#: ../../getting_started/documentation.rst:158
msgid ""
"The Project Organizer is a shared project tracking tool that allows both "
"detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
#: ../../getting_started/documentation.rst:162
msgid ""
"**Report essential information**: In order to minimize the documentation "
"time to the essentials, we will follow the following good practices:"
msgstr ""
#: ../../getting_started/documentation.rst:166
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:168
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
#: ../../getting_started/documentation.rst:171
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:177
msgid ""
"Odoo is a software known for its flexibility and its important evolution "
"capacity. However, a significant amount of development contradicts a fast "
"and sustainable implementation. This is the reason why it is recommended to:"
msgstr ""
#: ../../getting_started/documentation.rst:182
msgid ""
"**Develop only for a good reason**: The decision to develop must always be "
"taken when the cost-benefit ratio is positive (saving time on a daily basis,"
" etc.). For example, it will be preferable to realize a significant "
"development in order to reduce the time of a daily operation, rather than an"
" operation to be performed only once a quarter. It is generally accepted "
"that the closer the solution is to the standard, the lighter and more fluid "
"the migration process, and the lower the maintenance costs for both parties."
" In addition, experience has shown us that 60% of initial development "
"requests are dropped after a few weeks of using standard Odoo (see "
"\"Adopting the standard as a priority\")."
msgstr ""
#: ../../getting_started/documentation.rst:194
msgid ""
"**Replace, without replicate**: There is a good reason for the decision to "
"change the management software has been made. In this context, the moment of"
" implementation is THE right moment to accept and even be a change initiator"
" both in terms of how the software will be used and at the level of the "
"business processes of the company."
msgstr ""
#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:204
msgid ""
"Whether developments are made or not in the implementation, it is crucial to"
" test and validate the correspondence of the solution with the operational "
"needs of the company."
msgstr ""
#: ../../getting_started/documentation.rst:208
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"for delivering a solution corresponding to the defined specifications; the "
"SPoC will have to test and validate that the solution delivered meets the "
"requirements of the operational reality."
msgstr ""
#: ../../getting_started/documentation.rst:214
msgid ""
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:218
msgid ""
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:220
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:222
msgid ""
"A difference between the specification and the imperatives of operational "
"reality - This is a change that is the responsibility of SPoC."
msgstr ""
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
msgid ""
"Importing the history of transactional data is an important issue and must "
"be answered appropriately to allow the project running smoothly. Indeed, "
"this task can be time-consuming and, if its priority is not well defined, "
"prevent production from happening in time. To do this as soon as possible, "
"it will be decided :"
msgstr ""
#: ../../getting_started/documentation.rst:234
msgid ""
"**Not to import anything**: It often happens that after reflection, "
"importing data history is not considered necessary, these data being, "
"moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
#: ../../getting_started/documentation.rst:239
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
"invoices, open projects, for example), the need to have this information "
"available from the first day of use in production is real. In this case, the"
" import will be made before the production launch."
msgstr ""
#: ../../getting_started/documentation.rst:246
msgid ""
"**To import after production launch**: When the data history needs to be "
"integrated with Odoo mainly for reporting purposes, it is clear that these "
"can be integrated into the software retrospectively. In this case, the "
"production launch of the solution will precede the required imports."
msgstr ""
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
msgid ""
"When your project is put in production, our support teams take care of your "
"questions or technical issues."
msgstr ""
#: ../../getting_started/documentation.rst:258
msgid "See :ref:`support-expectations`."
msgstr ""
locale/ar/LC_MESSAGES/helpdesk.po
-485
View File
@@ -1,485 +0,0 @@
# 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:
# Abdalla Mohamed <abdalla.mhafeez@gmail.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-10-03 09:46+0000\n"
"Last-Translator: Abdalla Mohamed <abdalla.mhafeez@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"
"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"
#: ../../helpdesk.rst:5
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 ""
#: ../../helpdesk/getting_started.rst:6
msgid "Overview"
msgstr "نظرة عامة"
#: ../../helpdesk/getting_started.rst:9
msgid "Getting started with Odoo Helpdesk"
msgstr ""
#: ../../helpdesk/getting_started.rst:11
msgid "Installing Odoo Helpdesk:"
msgstr ""
#: ../../helpdesk/getting_started.rst:13
msgid "Open the Apps module, search for \"Helpdesk\", and click install"
msgstr ""
#: ../../helpdesk/getting_started.rst:19
msgid "Set up Helpdesk teams"
msgstr ""
#: ../../helpdesk/getting_started.rst:21
msgid "By default, Odoo Helpdesk comes with a team installed called \"Support\""
msgstr ""
#: ../../helpdesk/getting_started.rst:26
msgid ""
"To modify this team, or create additional teams, select \"Configuration\" in"
" the purple bar and select \"Settings\""
msgstr ""
#: ../../helpdesk/getting_started.rst:32
msgid ""
"Here you can create new teams, decide what team members to add to this team,"
" how your customers can submit tickets and set up SLA policies and ratings. "
"For the assignation method you can have tickets assigned randomly, balanced,"
" or manually."
msgstr ""
#: ../../helpdesk/getting_started.rst:38
msgid "How to set up different stages for each team"
msgstr ""
#: ../../helpdesk/getting_started.rst:40
msgid ""
"First you will need to activate the developer mode. To do this go to your "
"settings module, and select the link for \"Activate the developer mode\" on "
"the lower right-hand side."
msgstr ""
#: ../../helpdesk/getting_started.rst:47
msgid ""
"Now, when you return to your Helpdesk module and select \"Configuration\" in"
" the purple bar you will find additional options, like \"Stages\". Here you "
"can create new stages and assign those stages to 1 or multiple teams "
"allowing for customizable stages for each team!"
msgstr ""
#: ../../helpdesk/getting_started.rst:53
msgid "Start receiving tickets"
msgstr ""
#: ../../helpdesk/getting_started.rst:56
msgid "How can my customers submit tickets?"
msgstr ""
#: ../../helpdesk/getting_started.rst:58
msgid ""
"Select \"Configuration\" in the purple bar and select \"Settings\", select "
"your Helpdesk team. Under \"Channels you will find 4 options:"
msgstr ""
#: ../../helpdesk/getting_started.rst:64
msgid ""
"Email Alias allows for customers to email the alias you choose to create a "
"ticket. The subject line of the email with become the Subject on the ticket."
msgstr ""
#: ../../helpdesk/getting_started.rst:71
msgid ""
"Website Form allows your customer to go to "
"yourwebsite.com/helpdesk/support-1/submit and submit a ticket via a website "
"form - much like odoo.com/help!"
msgstr ""
#: ../../helpdesk/getting_started.rst:78
msgid ""
"Live Chat allows your customers to submit a ticket via Live Chat on your "
"website. Your customer will begin the live chat and your Live Chat Operator "
"can create the ticket by using the command /helpdesk Subject of Ticket."
msgstr ""
#: ../../helpdesk/getting_started.rst:86
msgid ""
"The final option to submit tickets is thru an API connection. View the "
"documentation `*here* "
"<https://www.odoo.com/documentation/13.0/webservices/odoo.html>`__."
msgstr ""
#: ../../helpdesk/getting_started.rst:91
msgid "Tickets have been created, now what?"
msgstr ""
#: ../../helpdesk/getting_started.rst:93
msgid ""
"Now your employees can start working on them! If you have selecting a manual"
" assignation method then your employees will need to assign themselves to "
"tickets using the \"Assign To Me\" button on the top left of a ticket or by "
"adding themselves to the \"Assigned to\" field."
msgstr ""
#: ../../helpdesk/getting_started.rst:101
msgid ""
"If you have selected \"Random\" or \"Balanced\" assignation method, your "
"tickets will be assigned to a member of that Helpdesk team."
msgstr ""
#: ../../helpdesk/getting_started.rst:104
msgid ""
"From there they will begin working on resolving the tickets! When they are "
"completed, they will move the ticket to the solved stage."
msgstr ""
#: ../../helpdesk/getting_started.rst:108
msgid "How do I mark this ticket as urgent?"
msgstr ""
#: ../../helpdesk/getting_started.rst:110
msgid ""
"On your tickets you will see stars. You can determine how urgent a ticket is"
" but selecting one or more stars on the ticket. You can do this in the "
"Kanban view or on the ticket form."
msgstr ""
#: ../../helpdesk/getting_started.rst:117
msgid ""
"To set up a Service Level Agreement Policy for your employees, first "
"activate the setting under \"Settings\""
msgstr ""
#: ../../helpdesk/getting_started.rst:123
msgid "From here, select \"Configure SLA Policies\" and click \"Create\"."
msgstr ""
#: ../../helpdesk/getting_started.rst:125
msgid ""
"You will fill in information like the Helpdesk team, what the minimum "
"priority is on the ticket (the stars) and the targets for the ticket."
msgstr ""
#: ../../helpdesk/getting_started.rst:132
msgid "What if a ticket is blocked or is ready to be worked on?"
msgstr ""
#: ../../helpdesk/getting_started.rst:134
msgid ""
"If a ticket cannot be resolved or is blocked, you can adjust the \"Kanban "
"State\" on the ticket. You have 3 options:"
msgstr ""
#: ../../helpdesk/getting_started.rst:137
msgid "Grey - Normal State"
msgstr ""
#: ../../helpdesk/getting_started.rst:139
msgid "Red - Blocked"
msgstr ""
#: ../../helpdesk/getting_started.rst:141
msgid "Green - Ready for next stage"
msgstr ""
#: ../../helpdesk/getting_started.rst:143
msgid ""
"Like the urgency stars you can adjust the state in the Kanban or on the "
"Ticket form."
msgstr ""
#: ../../helpdesk/getting_started.rst:150
msgid "How can my employees log time against a ticket?"
msgstr ""
#: ../../helpdesk/getting_started.rst:152
msgid ""
"First, head over to \"Settings\" and select the option for \"Timesheet on "
"Ticket\". You will see a field appear where you can select the project the "
"timesheets will log against."
msgstr ""
#: ../../helpdesk/getting_started.rst:159
msgid ""
"Now that you have selected a project, you can save. If you move back to your"
" tickets, you will see a new tab called \"Timesheets\""
msgstr ""
#: ../../helpdesk/getting_started.rst:165
msgid ""
"Here you employees can add a line to add work they have done for this "
"ticket."
msgstr ""
#: ../../helpdesk/getting_started.rst:169
msgid "How to allow your customers to rate the service they received"
msgstr ""
#: ../../helpdesk/getting_started.rst:171
msgid "First, you will need to activate the ratings setting under \"Settings\""
msgstr ""
#: ../../helpdesk/getting_started.rst:176
msgid ""
"Now, when a ticket is moved to its solved or completed stage, it will send "
"an email to the customer asking how their service went."
msgstr ""
#: ../../helpdesk/invoice_time.rst:3
msgid "Record and invoice time for tickets"
msgstr ""
#: ../../helpdesk/invoice_time.rst:5
msgid ""
"You may have service contracts with your clients to provide them assistance "
"in case of a problem. For this purpose, Odoo will help you record the time "
"spent fixing the issue and most importantly, to invoice it to your clients."
msgstr ""
#: ../../helpdesk/invoice_time.rst:11
msgid "The modules needed"
msgstr ""
#: ../../helpdesk/invoice_time.rst:13
msgid ""
"In order to record and invoice time for tickets, the following modules are "
"needed : Helpdesk, Project, Timesheets, Sales. If you are missing one of "
"them, go to the Apps module, search for it and then click on *Install*."
msgstr ""
#: ../../helpdesk/invoice_time.rst:19
msgid "Get started to offer the helpdesk service"
msgstr ""
#: ../../helpdesk/invoice_time.rst:22
msgid "Step 1 : start a helpdesk project"
msgstr ""
#: ../../helpdesk/invoice_time.rst:24
msgid ""
"To start a dedicated project for the helpdesk service, first go to "
":menuselection:`Project --> Configuration --> Settings` and make sure that "
"the *Timesheets* feature is activated."
msgstr ""
#: ../../helpdesk/invoice_time.rst:31
msgid ""
"Then, go to your dashboard, create the new project and allow timesheets for "
"it."
msgstr ""
#: ../../helpdesk/invoice_time.rst:35
msgid "Step 2 : gather a helpdesk team"
msgstr ""
#: ../../helpdesk/invoice_time.rst:37
msgid ""
"To set a team in charge of the helpdesk, go to :menuselection:`Helpdesk --> "
"Configuration --> Helpdesk Teams` and create a new team or select an "
"existing one. On the form, tick the box in front of *Timesheet on Ticket* to"
" activate the feature. Make sure to select the helpdesk project you have "
"previously created as well."
msgstr ""
#: ../../helpdesk/invoice_time.rst:47
msgid "Step 3 : launch the helpdesk service"
msgstr ""
#: ../../helpdesk/invoice_time.rst:49
msgid ""
"Finally, to launch the new helpdesk service, first go to "
":menuselection:`Sales --> Configuration --> Settings` and make sure that the"
" *Units of Measure* feature is activated."
msgstr ""
#: ../../helpdesk/invoice_time.rst:56
msgid ""
"Then, go to :menuselection:`Products --> Products` and create a new one. "
"Make sure that the product is set as a service."
msgstr ""
#: ../../helpdesk/invoice_time.rst:63
msgid ""
"Here, we suggest that you set the *Unit of Measure* as *Hour(s)*, but any "
"unit will do."
msgstr ""
#: ../../helpdesk/invoice_time.rst:66
msgid ""
"Finally, select the invoicing management you would like to have under the "
"*Sales* tab of the product form. Here, we recommend the following "
"configuration :"
msgstr ""
#: ../../helpdesk/invoice_time.rst:73
msgid "Now, you are ready to start receiving tickets !"
msgstr ""
#: ../../helpdesk/invoice_time.rst:76
msgid "Solve issues and record time spent"
msgstr ""
#: ../../helpdesk/invoice_time.rst:79
msgid "Step 1 : place an order"
msgstr ""
#: ../../helpdesk/invoice_time.rst:81
msgid ""
"You are now in the Helpdesk module and you have just received a ticket from "
"a client. To place a new order, go to :menuselection:`Sales --> Orders --> "
"Orders` and create one for the help desk service product you have previously"
" recorded. Set the number of hours needed to assist the client and confirm "
"the sale."
msgstr ""
#: ../../helpdesk/invoice_time.rst:91
msgid "Step 2 : link the task to the ticket"
msgstr ""
#: ../../helpdesk/invoice_time.rst:93
msgid ""
"If you access the dedicated helpdesk project, you will notice that a new "
"task has automatically been generated with the order. To link this task with"
" the client ticket, go to the Helpdesk module, access the ticket in question"
" and select the task on its form."
msgstr ""
#: ../../helpdesk/invoice_time.rst:102
msgid "Step 3 : record the time spent to help the client"
msgstr ""
#: ../../helpdesk/invoice_time.rst:104
msgid ""
"The job is done and the client's issue is sorted out. To record the hours "
"performed for this task, go back to the ticket form and add them under the "
"*Timesheets* tab."
msgstr ""
#: ../../helpdesk/invoice_time.rst:112
msgid ""
"The hours recorded on the ticket will also automatically appear in the "
"Timesheet module and on the dedicated task."
msgstr ""
#: ../../helpdesk/invoice_time.rst:116
msgid "Step 4 : invoice the client"
msgstr ""
#: ../../helpdesk/invoice_time.rst:118
msgid ""
"To invoice the client, go back to the Sales module and select the order that"
" had been placed. Notice that the hours recorded on the ticket form now "
"appear as the delivered quantity."
msgstr ""
#: ../../helpdesk/invoice_time.rst:125
msgid ""
"All that is left to do, is to create the invoice from the order and then "
"validate it. Now you just have to wait for the client's payment !"
msgstr ""
locale/ar/LC_MESSAGES/index.po
-22
View File
@@ -1,22 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+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"
#: ../../index.rst:3
msgid "Odoo User Documentation"
msgstr ""
locale/ar/LC_MESSAGES/inventory.po
-6466
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/iot.po
-819
View File
@@ -1,819 +0,0 @@
# 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-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"
"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"
#: ../../iot.rst:5
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../iot/config.rst:3
msgid "Configuration"
msgstr "إعداد"
#: ../../iot/config/connect.rst:3
msgid "Connect an IoT Box to your database"
msgstr ""
#: ../../iot/config/connect.rst:5
msgid "Install the Internet of Things (IoT) App on your Odoo Database."
msgstr ""
#: ../../iot/config/connect.rst:10
msgid "Go in the IoT App and click on Connect on the IoT Boxes page."
msgstr ""
#: ../../iot/config/connect.rst:15
msgid "Follow the steps to connect your IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:21
msgid "Ethernet Connection"
msgstr ""
#: ../../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/config/connect.rst:26
msgid "Power on the IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:28
msgid "Then click on the Scan button."
msgstr ""
#: ../../iot/config/connect.rst:34
msgid "WiFi Connection"
msgstr ""
#: ../../iot/config/connect.rst:36
msgid "Power on the IoT Box"
msgstr ""
#: ../../iot/config/connect.rst:38
msgid "Copy the token"
msgstr ""
#: ../../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/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/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-"
"f3f920.runbot16.odoo.com\\|4957098401** should become "
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
#: ../../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/config/connect.rst:70
msgid "You should now see the IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:76
msgid "IoT Box Schema"
msgstr ""
#: ../../iot/config/flash_sdcard.rst:3
msgid "Flashing your SD Card"
msgstr ""
#: ../../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/config/flash_sdcard.rst:9
msgid "Updating your SD Card with Etcher"
msgstr ""
#: ../../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/config/flash_sdcard.rst:15
msgid ""
"Now, download the latest image `here "
"<http://nightly.odoo.com/master/posbox/iotbox/>`__, and extract it from the "
"zip file. Then, open *Etcher* and select the image. Select the drive to "
"flash (where your SD Card is) and click on *Flash*!."
msgstr ""
#: ../../iot/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/config/iot_notfound.rst:3
msgid "IoT Box not found"
msgstr ""
#: ../../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/config/iot_notfound.rst:10
msgid "HTTPS Issues"
msgstr ""
#: ../../iot/config/iot_notfound.rst:12
msgid "Your IoT Box is not found? You probably have https issues!"
msgstr ""
#: ../../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/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/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/config/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr ""
#: ../../iot/config/pos.rst:9
msgid "Prerequisites"
msgstr ""
#: ../../iot/config/pos.rst:11
msgid "Before starting, make sure you have the following:"
msgstr ""
#: ../../iot/config/pos.rst:13
msgid "An IoT Box"
msgstr ""
#: ../../iot/config/pos.rst:15
msgid "A 2A Power adapter with pi 3 b+ 2.5 A"
msgstr ""
#: ../../iot/config/pos.rst:17
msgid "A computer or tablet with an up-to-date web browser"
msgstr ""
#: ../../iot/config/pos.rst:19
msgid ""
"A running SaaS or Odoo instance with the Point of Sale and IoT apps "
"installed"
msgstr ""
#: ../../iot/config/pos.rst:22
msgid "A local network setup with DHCP (this is the default setting)"
msgstr ""
#: ../../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/config/pos.rst:28
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
#: ../../iot/config/pos.rst:30
msgid "An Epson compatible cash drawer"
msgstr ""
#: ../../iot/config/pos.rst:32
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr ""
#: ../../iot/config/pos.rst:35
msgid "Set Up"
msgstr ""
#: ../../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/config/pos.rst:44
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr ""
#: ../../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/config/pos.rst:50
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
#: ../../iot/config/pos.rst:53
msgid ""
"**Cash drawer**: The cash drawer should be connected to the printer with an "
"RJ25 cable."
msgstr ""
#: ../../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 "
"configured in **US QWERTY**. It also must end barcodes with an Enter "
"character (keycode 28). This is most likely the default configuration of "
"your barcode scanner."
msgstr ""
#: ../../iot/config/pos.rst:62
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
#: ../../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/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 "
"functionality will be bypassed when a wired network connection is available "
"on boot."
msgstr ""
#: ../../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/config/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
#: ../../iot/config/pos.rst:80
msgid "Troubleshoot"
msgstr ""
#: ../../iot/config/pos.rst:83
msgid "The PoS cannot connect to the IoT Box"
msgstr ""
#: ../../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"
" if encountered or the IoT Box's IP address in case of success. If no "
"receipt is printed, check the following steps:"
msgstr ""
#: ../../iot/config/pos.rst:91
msgid ""
"Make sure the IoT Box is powered on, indicated by a brightly lit red status "
"LED."
msgstr ""
#: ../../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/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/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/config/pos.rst:106
msgid "Make sure that the POS is not loaded over HTTPS."
msgstr ""
#: ../../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/config/pos.rst:113
msgid "The Barcode Scanner is not working"
msgstr ""
#: ../../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/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/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/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/config/pos.rst:134
msgid "The Barcode Scanner is not working reliably"
msgstr ""
#: ../../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/config/pos.rst:140
msgid "Printing the receipt takes too much time"
msgstr ""
#: ../../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 "
"afterwards it is most likely due to poor network connection between the POS "
"and the IoT Box."
msgstr ""
#: ../../iot/config/pos.rst:148
msgid "Some characters are not correctly printed on the receipt"
msgstr ""
#: ../../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/config/pos.rst:155
msgid "The printer is offline"
msgstr ""
#: ../../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/config/pos.rst:162
msgid "The cashdrawer does not open"
msgstr ""
#: ../../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/livechat.po
-197
View File
@@ -1,197 +0,0 @@
# 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:
# Abdalla Mohamed <abdalla.mhafeez@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"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Abdalla Mohamed <abdalla.mhafeez@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"
"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"
#: ../../livechat/livechat.rst:5
msgid "Live Chat"
msgstr ""
#: ../../livechat/livechat.rst:8
msgid "Chat in real time with website visitors"
msgstr ""
#: ../../livechat/livechat.rst:10
msgid ""
"With Odoo Live Chat, you can establish a direct contact with your website "
"visitors. A simple dialog box will be available on their screen and will "
"allow them to get in touch with one of your sales representatives. This way,"
" you can easily turn prospects into potential business opportunities. You "
"will also be able to provide assistance to your customers. Overall, this is "
"the perfect tool to improve customer satisfaction."
msgstr ""
#: ../../livechat/livechat.rst:19
msgid "Configuration"
msgstr "الإعدادات"
#: ../../livechat/livechat.rst:21
msgid ""
"To get the Live Chat feature, open the Apps module, search for \"Live Chat\""
" and then click on install."
msgstr ""
#: ../../livechat/livechat.rst:27
msgid ""
"The Live Chat module provides you a direct access to your channels. There, "
"operators can easily join and leave the chat."
msgstr ""
#: ../../livechat/livechat.rst:34
msgid "Add the live chat to an Odoo website"
msgstr ""
#: ../../livechat/livechat.rst:36
msgid ""
"If your website was created with Odoo, then the live chat is automatically "
"added to it. All that is left to do, is to go to :menuselection:`Website -->"
" Configuration --> Settings` to select the channel to be linked to the "
"website."
msgstr ""
#: ../../livechat/livechat.rst:45
msgid "Add the live chat to an external website"
msgstr ""
#: ../../livechat/livechat.rst:47
msgid ""
"If your website was not created with Odoo, go to the Live Chat module and "
"then select the channel to be linked. There, you can simply copy paste the "
"code available into your website. A specific url you can send to customers "
"or suppliers for them to access the live chat is also provided."
msgstr ""
#: ../../livechat/livechat.rst:54
msgid "Hide / display the live chat according to rules"
msgstr ""
#: ../../livechat/livechat.rst:56
msgid ""
"Rules for the live chat can be defined on the channel form. For instance, "
"you can choose to display the chat in the countries you speak the language "
"of. On the contrary, you are able to hide the chat in countries your company"
" does not sell in. If you select *Auto popup*, you can also set the length "
"of time it takes for the chat to appear."
msgstr ""
#: ../../livechat/livechat.rst:66
msgid "Prepare automatic messages"
msgstr ""
#: ../../livechat/livechat.rst:68
msgid ""
"On the channel form, in the *Options* section, several messages can be typed"
" to appear automatically on the chat. This will entice visitors to reach you"
" through the live chat."
msgstr ""
#: ../../livechat/livechat.rst:76
msgid "Start chatting with customers"
msgstr ""
#: ../../livechat/livechat.rst:78
msgid ""
"In order to start chatting with customers, first make sure that the channel "
"is published on your website. To do so, select *Unpublished on Website* on "
"the top right corner of the channel form to toggle the *Published* setting. "
"Then, the live chat can begin once an operator has joined the channel."
msgstr ""
#: ../../livechat/livechat.rst:88
msgid ""
"If no operator is available and/or if the channel is unpublished on the "
"website, then the live chat button will not appear to visitors."
msgstr ""
#: ../../livechat/livechat.rst:92
msgid ""
"Conversations initiated by visitors also appear in the Discuss module in "
"addition to popping up as a direct message. Therefore, inquiries can be "
"answered wherever you are in Odoo."
msgstr ""
#: ../../livechat/livechat.rst:96
msgid ""
"If there are several operators who have all joined a channel, the system "
"will dispatch visitor sessions randomly between them."
msgstr ""
#: ../../livechat/livechat.rst:100
msgid "Use commands"
msgstr ""
#: ../../livechat/livechat.rst:102
msgid ""
"Commands are useful shortcuts for completing certain actions or to access "
"information you might need. To use this feature, simply type the commands "
"into the chat. The following actions are available :"
msgstr ""
#: ../../livechat/livechat.rst:106
msgid "**/help** : show a helper message."
msgstr ""
#: ../../livechat/livechat.rst:108
msgid "**/helpdesk** : create a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:110
msgid "**/helpdesk\\_search** : search for a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:112
msgid "**/history** : see 15 last visited pages."
msgstr ""
#: ../../livechat/livechat.rst:114
msgid "**/lead** : create a new lead."
msgstr ""
#: ../../livechat/livechat.rst:116
msgid "**/leave** : leave the channel."
msgstr ""
#: ../../livechat/livechat.rst:119
msgid ""
"If a helpdesk ticket is created from the chat, then the conversation it was "
"generated from will automatically appear as the description of the ticket. "
"The same goes for the creation of a lead."
msgstr ""
#: ../../livechat/livechat.rst:124
msgid "Send canned responses"
msgstr ""
#: ../../livechat/livechat.rst:126
msgid ""
"Canned responses allow you to create substitutes to generic sentences you "
"frequently use. Typing a word instead of several will save you a lot of "
"time. To add canned responses, go to :menuselection:`LIVE CHAT --> "
"Configuration --> Canned Responses` and create as many as you need to. Then,"
" to use them during a chat, simply type \":\" followed by the shortcut you "
"assigned."
msgstr ""
#: ../../livechat/livechat.rst:136
msgid ""
"You now have all of the tools needed to chat in live with your website "
"visitors, enjoy !"
msgstr ""
locale/ar/LC_MESSAGES/manufacturing.po
-1159
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/mobile.po
-38
View File
@@ -1,38 +0,0 @@
# 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-10-03 11:39+0200\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"
"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"
#: ../../mobile/firebase.rst:5
msgid "Mobile"
msgstr ""
#: ../../mobile/firebase.rst:8
msgid "Push Notifications"
msgstr ""
#: ../../mobile/firebase.rst:10
msgid ""
"As of Odoo 12.0, 13.0 or above, there is no more complex configuration to "
"enable push notifications in the mobile app."
msgstr ""
#: ../../mobile/firebase.rst:13
msgid ""
"Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification "
"(OCN)* and make sure that **Push Notifications** is checked."
msgstr ""
locale/ar/LC_MESSAGES/point_of_sale.po
-1653
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/portal.po
-164
View File
@@ -1,164 +0,0 @@
# 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-10-03 11:39+0200\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"
"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"
#: ../../portal/my_odoo_portal.rst:6
msgid "My Odoo Portal"
msgstr ""
#: ../../portal/my_odoo_portal.rst:8
msgid ""
"In this section of the portal, you will find all the communications between "
"you and Odoo: documents such as quotations, sales orders, invoices and "
"subscriptions."
msgstr ""
#: ../../portal/my_odoo_portal.rst:11
msgid ""
"To access this section, you have to log with your username and password to "
"`Odoo <https://www.odoo.com/my/home>`__ . If you are already logged in, just"
" click on your name on the top-right corner and select \"My Account\"."
msgstr ""
#: ../../portal/my_odoo_portal.rst:20
msgid "Quotations"
msgstr ""
#: ../../portal/my_odoo_portal.rst:22
msgid ""
"Here you will find all the quotations sent to you by Odoo. For example, a "
"quotation can be generated for you after adding an application or a user to "
"your database or if your contract has to be renewed."
msgstr ""
#: ../../portal/my_odoo_portal.rst:29
msgid ""
"The *Valid Until* column shows the date through which the quotation is "
"valid; after that date, the quotation will be \"Expired\". By clicking on "
"the quotation, you will see all the details of the offer, such as the "
"pricing and other useful information."
msgstr ""
#: ../../portal/my_odoo_portal.rst:36
msgid ""
"If you want to accept the quotation, just click \"Accept & Pay,\" and the "
"quote will get confirmed. If you don't want to accept it, or you need to ask"
" for some modifications, click on \"Ask Changes Reject.\""
msgstr ""
#: ../../portal/my_odoo_portal.rst:41
msgid "Sales Orders"
msgstr ""
#: ../../portal/my_odoo_portal.rst:43
msgid ""
"All your purchases within Odoo (Upsells, Themes, Applications, etc.) will be"
" registered under this section."
msgstr ""
#: ../../portal/my_odoo_portal.rst:49
msgid ""
"By clicking on the sale order, you can review the details of the products "
"purchased and process the payment."
msgstr ""
#: ../../portal/my_odoo_portal.rst:53
msgid "Invoices"
msgstr ""
#: ../../portal/my_odoo_portal.rst:55
msgid ""
"All the invoices of your subscriptions and/or sales orders will be shown in "
"this section. The tag before the Amount Due will indicate if the invoice has"
" been paid."
msgstr ""
#: ../../portal/my_odoo_portal.rst:62
msgid ""
"Just click on the invoice if you wish to see more information, pay the "
"invoice, or download a PDF version of the document."
msgstr ""
#: ../../portal/my_odoo_portal.rst:66
msgid "Tickets"
msgstr ""
#: ../../portal/my_odoo_portal.rst:68
msgid ""
"When you submit a ticket through `Odoo Support <https://www.odoo.com/help>`,"
" a ticket will be created. Here you can find all the tickets that you have "
"opened, the conversations between you and our Agents, and the statuses and "
"IDs (# Ref) of the tickets."
msgstr ""
#: ../../portal/my_odoo_portal.rst:76
msgid "Subscriptions"
msgstr ""
#: ../../portal/my_odoo_portal.rst:78
msgid ""
"You can access your subscriptions with Odoo from this section. The first "
"page shows you the subscriptions that you have and their status."
msgstr ""
#: ../../portal/my_odoo_portal.rst:84
msgid ""
"By clicking on the subscription you will access all the details regarding "
"your plan: the number of applications purchased, the billing information, "
"and the payment method."
msgstr ""
#: ../../portal/my_odoo_portal.rst:88
msgid ""
"To change the payment method, click on \"Change Payment Method\" and enter "
"the new credit card details."
msgstr ""
#: ../../portal/my_odoo_portal.rst:94
msgid ""
"If you want to remove the credit cards that are saved, you can do so by "
"clicking on \"Manage your payment methods\" at the bottom of the page. Click"
" \"Delete\" to delete the payment method."
msgstr ""
#: ../../portal/my_odoo_portal.rst:101
msgid ""
"At the date of the next invoice, if there is no payment information provided"
" or if your credit card has expired, the status of your subscription will "
"change to \"To Renew\". You will then have 7 days to provide a valid method"
" of payment. After this delay, the subscription will be closed, and you will"
" no longer be able to access the database."
msgstr ""
#: ../../portal/my_odoo_portal.rst:108
msgid "Success Packs"
msgstr ""
#: ../../portal/my_odoo_portal.rst:109
msgid ""
"With a Success Pack/Partner Success Pack, you are assigned an expert to "
"provide unique personalized assistance to help you customize your solution "
"and optimize your workflows as part of your initial implementation. These "
"hours never expire, allowing you to utilize them whenever you need support."
msgstr ""
#: ../../portal/my_odoo_portal.rst:115
msgid ""
"If you need information about how to manage your database see "
":ref:`db_online`"
msgstr ""
locale/ar/LC_MESSAGES/practical.po
-22
View File
@@ -1,22 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2019-10-03 09:47+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"
#: ../../practical.rst:3
msgid "Practical Information"
msgstr ""
locale/ar/LC_MESSAGES/project.po
-1597
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/purchase.po
-1722
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/quality.po
-420
View File
@@ -1,420 +0,0 @@
# 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
# Ali Alrehawi <alrehawi@hotmail.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: Ali Alrehawi <alrehawi@hotmail.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"
#: ../../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 ""
"الحديث عن أوامر التصنيع ، لديك وضعين مختلفين تركز عليها في اودو.\n"
"هاذين الوضعين ستنتج في عمليتين مختلفتين"
#: ../../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/recruitment.po
-22
View File
@@ -1,22 +0,0 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 9.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-11-22 13:16+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"
"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"
#: ../../recruitment.rst:5
msgid "Recruitment"
msgstr ""
locale/ar/LC_MESSAGES/sales.po
-2054
View File
File diff suppressed because it is too large Load Diff
locale/ar/LC_MESSAGES/sms_marketing.po
-515
View File
@@ -1,515 +0,0 @@
# 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
@@ -1,168 +0,0 @@
# 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 ""
locale/ar/LC_MESSAGES/website.po
-1858
View File
File diff suppressed because it is too large Load Diff