[I18N] Update translation terms from Transifex

This commit is contained in:
Odoo Translation Bot
2019-11-18 16:39:27 +01:00
parent 69d8936be7
commit 8b49c8e06a
81 changed files with 84088 additions and 6303 deletions
File diff suppressed because it is too large Load Diff
+22
View File
@@ -0,0 +1,22 @@
# 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 ""
File diff suppressed because it is too large Load Diff
+780
View File
@@ -0,0 +1,780 @@
# 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"
#: ../../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 access "
"rights.**"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:82
msgid "|settings|"
msgstr ""
#: ../../db_management/documentation.rst:44
msgid "|browse_users|"
msgstr ""
#: ../../db_management/documentation.rst:47
msgid "You'll then see the list of your users."
msgstr ""
#: ../../db_management/documentation.rst:52
msgid ""
"The pre-selected filter *Internal Users* shows your paying users (different "
"from the *Portal Users* which are free). If you remove this filter, you'll "
"get all your users (the ones you pay for and the portal ones)"
msgstr ""
#: ../../db_management/documentation.rst:57
msgid ""
"In your list of users, click on the user you want to deactivate. As soon as "
"you are on the userform, go with your mouse cursor on the status **Active** "
"(top right). Click on Active and you will notice that the status will change"
" to **Inactive** immediately."
msgstr ""
#: ../../db_management/documentation.rst:66
msgid "The user is now deactivated."
msgstr ""
#: ../../db_management/documentation.rst:68
msgid "**Never** deactivate the main user (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:71
msgid "Uninstalling Apps"
msgstr ""
#: ../../db_management/documentation.rst:73
msgid ""
"Make sure you first test what you are about to do on a :ref:`duplicate "
"<duplicate_online>` of your database before making any changes (*especially*"
" installing/uninstalling apps)."
msgstr ""
#: ../../db_management/documentation.rst:77
msgid ""
"In your Odoo instance click on **Settings**; in this app, you will be able "
"to see how many applications you have installed. Click on **Browse Apps** to"
" access the list of your installed applications."
msgstr ""
#: ../../db_management/documentation.rst:82
msgid "|browse_apps|"
msgstr ""
#: ../../db_management/documentation.rst:85
msgid ""
"In your applications' dashboard, you will see all the icons of your "
"applications. Click on the application you want to uninstall. Then, on the "
"form of the application, click on **Uninstall**."
msgstr ""
#: ../../db_management/documentation.rst:92
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:99
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:104
msgid "You have finished uninstalling your application."
msgstr ""
#: ../../db_management/documentation.rst:107
msgid "Good to know"
msgstr ""
#: ../../db_management/documentation.rst:109
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:115
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:122
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 ""
+658
View File
@@ -0,0 +1,658 @@
# 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 providers 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 ""
File diff suppressed because it is too large Load Diff
+22
View File
@@ -0,0 +1,22 @@
# 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 ""
+989
View File
@@ -0,0 +1,989 @@
# 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"
#: ../../general.rst:5
msgid "General"
msgstr ""
#: ../../general/auth.rst:3
msgid "Authentication"
msgstr ""
#: ../../general/auth/azure.rst:3
msgid "OAuth"
msgstr ""
#: ../../general/auth/azure.rst:5
msgid ""
"Due to specific requirements in Azure's OAuth implementation, Microsoft "
"Azure OAuth identification is NOT compatible with Odoo at the moment."
msgstr ""
#: ../../general/auth/google.rst:3
msgid "How to allow users to sign in with their Google account"
msgstr ""
#: ../../general/auth/google.rst:5
msgid ""
"Connect to your Google account and go to "
"`https://console.developers.google.com/ "
"<https://console.developers.google.com/>`_."
msgstr ""
#: ../../general/auth/google.rst:7
msgid ""
"Click on **Create Project** and enter the project name and other details."
msgstr ""
#: ../../general/auth/google.rst:15
msgid "Click on **Use Google APIs**"
msgstr ""
#: ../../general/auth/google.rst:20
msgid ""
"On the left side menu, select the sub menu **Credentials** (from **API "
"Manager**) then select **OAuth consent screen**."
msgstr ""
#: ../../general/auth/google.rst:25
msgid ""
"Fill in your address, email and the product name (for example odoo) and then"
" save."
msgstr ""
#: ../../general/auth/google.rst:30
msgid ""
"Then click on **Add Credentials** and select the second option (OAuth 2.0 "
"Client ID)."
msgstr ""
#: ../../general/auth/google.rst:38
msgid ""
"Check that the application type is set on **Web Application**. Now configure"
" the allowed pages on which you will be redirected."
msgstr ""
#: ../../general/auth/google.rst:40
msgid ""
"To achieve this, complete the field **Authorized redirect URIs**. Copy paste"
" the following link in the box: http://mydomain.odoo.com/auth_oauth/signin. "
"Then click on **Create**"
msgstr ""
#: ../../general/auth/google.rst:48
msgid ""
"Once done, you receive two information (your Client ID and Client Secret). "
"You have to insert your Client ID in the **General Settings**."
msgstr ""
#: ../../general/auth/ldap.rst:3
msgid "How to allow users to sign in with LDAP"
msgstr ""
#: ../../general/auth/ldap.rst:5
msgid "Install the LDAP module in General Settings."
msgstr ""
#: ../../general/auth/ldap.rst:7
msgid "Click on **Create** in Setup your LDAP Server."
msgstr ""
#: ../../general/auth/ldap.rst:15
msgid "Choose the company about to use the LDAP."
msgstr ""
#: ../../general/auth/ldap.rst:20
msgid ""
"In **Server Information**, enter the IP address of your server and the port "
"it listens to."
msgstr ""
#: ../../general/auth/ldap.rst:22
msgid "Tick **User TLS** if your server is compatible."
msgstr ""
#: ../../general/auth/ldap.rst:27
msgid ""
"In **Login Information**, enter ID and password of the account used to query"
" the server. If left empty, the server will be queried anonymously."
msgstr ""
#: ../../general/auth/ldap.rst:32
msgid ""
"In **Process Parameter**, enter the domain name of your LDAP server in LDAP "
"nomenclature (e.g. ``dc=example,dc=com``)."
msgstr ""
#: ../../general/auth/ldap.rst:34
msgid "In **LDAP filter**, enter ``uid=%s``"
msgstr ""
#: ../../general/auth/ldap.rst:39
msgid ""
"In **User Information**, tick *Create User* if you want Odoo to create a "
"User profile the first time someone log in with LDAP."
msgstr ""
#: ../../general/auth/ldap.rst:41
msgid ""
"In **Template User**, indicate a template for the new profiles created. If "
"left blanked, the admin profile will be used as template."
msgstr ""
#: ../../general/base_import.rst:3
msgid "Data Import"
msgstr ""
#: ../../general/base_import/adapt_template.rst:3
msgid "How to adapt an import template"
msgstr ""
#: ../../general/base_import/adapt_template.rst:5
msgid ""
"Import templates are provided in the import tool of the most common data to "
"import (contacts, products, bank statements, etc.). You can open them with "
"any spreadsheets software (Microsoft Office, OpenOffice, Google Drive, "
"etc.)."
msgstr ""
#: ../../general/base_import/adapt_template.rst:11
msgid "How to customize the file"
msgstr ""
#: ../../general/base_import/adapt_template.rst:13
msgid ""
"Remove columns you don't need. We advise to not remove the *ID* one (see why"
" here below)."
msgstr ""
#: ../../general/base_import/adapt_template.rst:15
#: ../../general/base_import/import_faq.rst:26
msgid ""
"Set a unique ID to every single record by dragging down the ID sequencing."
msgstr ""
#: ../../general/base_import/adapt_template.rst:20
msgid ""
"When you add a new column, Odoo might not be able to map it automatically if"
" its label doesn't fit any field of the system. If so, find the "
"corresponding field using the search."
msgstr ""
#: ../../general/base_import/adapt_template.rst:27
msgid ""
"Then, use the label you found in your import template in order to make it "
"work straight away the very next time you try to import."
msgstr ""
#: ../../general/base_import/adapt_template.rst:31
msgid "Why an “ID” column"
msgstr ""
#: ../../general/base_import/adapt_template.rst:33
msgid ""
"The **ID** (External ID) is an unique identifier for the line item. Feel "
"free to use the one of your previous software to ease the transition to "
"Odoo."
msgstr ""
#: ../../general/base_import/adapt_template.rst:36
msgid ""
"Setting an ID is not mandatory when importing but it helps in many cases:"
msgstr ""
#: ../../general/base_import/adapt_template.rst:38
msgid ""
"Update imports: you can import the same file several times without creating "
"duplicates;"
msgstr ""
#: ../../general/base_import/adapt_template.rst:39
msgid "Import relation fields (see here below)."
msgstr ""
#: ../../general/base_import/adapt_template.rst:42
msgid "How to import relation fields"
msgstr ""
#: ../../general/base_import/adapt_template.rst:44
msgid ""
"An Odoo object is always related to many other objects (e.g. a product is "
"linked to product categories, attributes, vendors, etc.). To import those "
"relations you need to import the records of the related object first from "
"their own list menu."
msgstr ""
#: ../../general/base_import/adapt_template.rst:48
msgid ""
"You can do it using either the name of the related record or its ID. The ID "
"is expected when two records have the same name. In such a case add \" / "
"ID\" at the end of the column title (e.g. for product attributes: Product "
"Attributes / Attribute / ID)."
msgstr ""
#: ../../general/base_import/import_faq.rst:3
msgid "How to import data into Odoo"
msgstr ""
#: ../../general/base_import/import_faq.rst:6
msgid "How to start"
msgstr ""
#: ../../general/base_import/import_faq.rst:7
msgid ""
"You can import data on any Odoo's business object using either Excel (.xlsx)"
" or CSV (.csv) formats: contacts, products, bank statements, journal entries"
" and even orders!"
msgstr ""
#: ../../general/base_import/import_faq.rst:11
msgid "Open the view of the object you want to populate and click *Import*."
msgstr ""
#: ../../general/base_import/import_faq.rst:16
msgid ""
"There you are provided with templates you can easily populate with your own "
"data. Such templates can be imported in one click; The data mapping is "
"already done."
msgstr ""
#: ../../general/base_import/import_faq.rst:22
msgid "How to adapt the template"
msgstr ""
#: ../../general/base_import/import_faq.rst:24
msgid "Add, remove and sort columns to fit at best your data structure."
msgstr ""
#: ../../general/base_import/import_faq.rst:25
msgid "We advise to not remove the **ID** one (see why in the next section)."
msgstr ""
#: ../../general/base_import/import_faq.rst:31
msgid ""
"When you add a new column, Odoo might not be able to map it automatically if"
" its label doesn't fit any field in Odoo. Don't worry! You can map new "
"columns manually when you test the import. Search the list for the "
"corresponding field."
msgstr ""
#: ../../general/base_import/import_faq.rst:39
msgid ""
"Then, use this field's label in your file in order to make it work straight "
"on the very next time."
msgstr ""
#: ../../general/base_import/import_faq.rst:44
msgid "How to import from another application"
msgstr ""
#: ../../general/base_import/import_faq.rst:46
msgid ""
"In order to re-create relationships between different records, you should "
"use the unique identifier from the original application and map it to the "
"**ID** (External ID) column in Odoo. When you import another record that "
"links to the first one, use **XXX/ID** (XXX/External ID) to the original "
"unique identifier. You can also find this record using its name but you will"
" be stuck if at least 2 records have the same name."
msgstr ""
#: ../../general/base_import/import_faq.rst:54
msgid ""
"The **ID** will also be used to update the original import if you need to "
"re-import modified data later, it's thus good practice to specify it "
"whenever possible."
msgstr ""
#: ../../general/base_import/import_faq.rst:60
msgid "I cannot find the field I want to map my column to"
msgstr ""
#: ../../general/base_import/import_faq.rst:62
msgid ""
"Odoo tries to find with some heuristic, based on the first ten lines of the "
"files, the type of field for each column inside your file. For example if "
"you have a column only containing numbers, only the fields that are of type "
"*Integer* will be displayed for you to choose from. While this behavior "
"might be good and easy for most cases, it is also possible that it goes "
"wrong or that you want to map your column to a field that is not proposed by"
" default."
msgstr ""
#: ../../general/base_import/import_faq.rst:71
msgid ""
"If that happens, you just have to check the ** Show fields of relation "
"fields (advanced)** option, you will then be able to choose from the "
"complete list of fields for each column."
msgstr ""
#: ../../general/base_import/import_faq.rst:79
msgid "Where can I change the date import format?"
msgstr ""
#: ../../general/base_import/import_faq.rst:81
msgid ""
"Odoo can automatically detect if a column is a date, and it will try to "
"guess the date format from a set of most commonly used date formats. While "
"this process can work for many date formats, some date formats will not be "
"recognized. This can cause confusion due to day-month inversions; it is "
"difficult to guess which part of a date format is the day and which part is "
"the month in a date such as '01-03-2016'."
msgstr ""
#: ../../general/base_import/import_faq.rst:83
msgid ""
"To view which date format Odoo has found from your file you can check the "
"**Date Format** that is shown when clicking on **Options** under the file "
"selector. If this format is incorrect you can change it to your liking using"
" the *ISO 8601* to define the format."
msgstr ""
#: ../../general/base_import/import_faq.rst:86
msgid ""
"If you are importing an excel (.xls, .xlsx) file, you can use date cells to "
"store dates as the display of dates in excel is different from the way it is"
" stored. That way you will be sure that the date format is correct in Odoo "
"whatever your locale date format is."
msgstr ""
#: ../../general/base_import/import_faq.rst:91
msgid "Can I import numbers with currency sign (e.g.: $32.00)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:93
msgid ""
"Yes, we fully support numbers with parenthesis to represent negative sign as"
" well as numbers with currency sign attached to them. Odoo also "
"automatically detect which thousand/decimal separator you use (you can "
"change those under **options**). If you use a currency symbol that is not "
"known to Odoo, it might not be recognized as a number though and it will "
"crash."
msgstr ""
#: ../../general/base_import/import_faq.rst:95
msgid ""
"Examples of supported numbers (using thirty-two thousands as an example):"
msgstr ""
#: ../../general/base_import/import_faq.rst:97
msgid "32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:98
msgid "32000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:99
msgid "32,000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:100
msgid "-32000.00"
msgstr ""
#: ../../general/base_import/import_faq.rst:101
msgid "(32000.00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:102
msgid "$ 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:103
msgid "(32000.00 €)"
msgstr ""
#: ../../general/base_import/import_faq.rst:105
msgid "Example that will not work:"
msgstr ""
#: ../../general/base_import/import_faq.rst:107
msgid "ABC 32.000,00"
msgstr ""
#: ../../general/base_import/import_faq.rst:108
msgid "$ (32.000,00)"
msgstr ""
#: ../../general/base_import/import_faq.rst:113
msgid "What can I do when the Import preview table isn't displayed correctly?"
msgstr ""
#: ../../general/base_import/import_faq.rst:115
msgid ""
"By default the Import preview is set on commas as field separators and "
"quotation marks as text delimiters. If your csv file does not have these "
"settings, you can modify the File Format Options (displayed under the Browse"
" CSV file bar after you select your file)."
msgstr ""
#: ../../general/base_import/import_faq.rst:117
msgid ""
"Note that if your CSV file has a tabulation as separator, Odoo will not "
"detect the separations. You will need to change the file format options in "
"your spreadsheet application. See the following question."
msgstr ""
#: ../../general/base_import/import_faq.rst:122
msgid ""
"How can I change the CSV file format options when saving in my spreadsheet "
"application?"
msgstr ""
#: ../../general/base_import/import_faq.rst:124
msgid ""
"If you edit and save CSV files in speadsheet applications, your computer's "
"regional settings will be applied for the separator and delimiter. We "
"suggest you use OpenOffice or LibreOffice Calc as they will allow you to "
"modify all three options (in 'Save As' dialog box > Check the box 'Edit "
"filter settings' > Save)."
msgstr ""
#: ../../general/base_import/import_faq.rst:126
msgid ""
"Microsoft Excel will allow you to modify only the encoding when saving (in "
"'Save As' dialog box > click 'Tools' dropdown list > Encoding tab)."
msgstr ""
#: ../../general/base_import/import_faq.rst:131
msgid "What's the difference between Database ID and External ID?"
msgstr ""
#: ../../general/base_import/import_faq.rst:133
msgid ""
"Some fields define a relationship with another object. For example, the "
"country of a contact is a link to a record of the 'Country' object. When you"
" want to import such fields, Odoo will have to recreate links between the "
"different records. To help you import such fields, Odoo provides 3 "
"mechanisms. You must use one and only one mechanism per field you want to "
"import."
msgstr ""
#: ../../general/base_import/import_faq.rst:135
msgid ""
"For example, to reference the country of a contact, Odoo proposes you 3 "
"different fields to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:137
msgid "Country: the name or code of the country"
msgstr ""
#: ../../general/base_import/import_faq.rst:138
msgid ""
"Country/Database ID: the unique Odoo ID for a record, defined by the ID "
"postgresql column"
msgstr ""
#: ../../general/base_import/import_faq.rst:139
msgid ""
"Country/External ID: the ID of this record referenced in another application"
" (or the .XML file that imported it)"
msgstr ""
#: ../../general/base_import/import_faq.rst:141
msgid "For the country Belgium, you can use one of these 3 ways to import:"
msgstr ""
#: ../../general/base_import/import_faq.rst:143
msgid "Country: Belgium"
msgstr ""
#: ../../general/base_import/import_faq.rst:144
msgid "Country/Database ID: 21"
msgstr ""
#: ../../general/base_import/import_faq.rst:145
msgid "Country/External ID: base.be"
msgstr ""
#: ../../general/base_import/import_faq.rst:147
msgid ""
"According to your need, you should use one of these 3 ways to reference "
"records in relations. Here is when you should use one or the other, "
"according to your need:"
msgstr ""
#: ../../general/base_import/import_faq.rst:149
msgid ""
"Use Country: This is the easiest way when your data come from CSV files that"
" have been created manually."
msgstr ""
#: ../../general/base_import/import_faq.rst:150
msgid ""
"Use Country/Database ID: You should rarely use this notation. It's mostly "
"used by developers as it's main advantage is to never have conflicts (you "
"may have several records with the same name, but they always have a unique "
"Database ID)"
msgstr ""
#: ../../general/base_import/import_faq.rst:151
msgid ""
"Use Country/External ID: Use External ID when you import data from a third "
"party application."
msgstr ""
#: ../../general/base_import/import_faq.rst:153
msgid ""
"When you use External IDs, you can import CSV files with the \"External ID\""
" column to define the External ID of each record you import. Then, you will "
"be able to make a reference to that record with columns like "
"\"Field/External ID\". The following two CSV files give you an example for "
"Products and their Categories."
msgstr ""
#: ../../general/base_import/import_faq.rst:155
msgid ""
"`CSV file for categories "
"<../../_static/example_files/External_id_3rd_party_application_product_categories.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:157
msgid ""
"`CSV file for Products "
"<../../_static/example_files/External_id_3rd_party_application_products.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:161
msgid "What can I do if I have multiple matches for a field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:163
msgid ""
"If for example you have two product categories with the child name "
"\"Sellable\" (ie. \"Misc. Products/Sellable\" & \"Other "
"Products/Sellable\"), your validation is halted but you may still import "
"your data. However, we recommend you do not import the data because they "
"will all be linked to the first 'Sellable' category found in the Product "
"Category list (\"Misc. Products/Sellable\"). We recommend you modify one of "
"the duplicates' values or your product category hierarchy."
msgstr ""
#: ../../general/base_import/import_faq.rst:165
msgid ""
"However if you do not wish to change your configuration of product "
"categories, we recommend you use make use of the external ID for this field "
"'Category'."
msgstr ""
#: ../../general/base_import/import_faq.rst:170
msgid ""
"How can I import a many2many relationship field (e.g. a customer that has "
"multiple tags)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:172
msgid ""
"The tags should be separated by a comma without any spacing. For example, if"
" you want your customer to be linked to both tags 'Manufacturer' and "
"'Retailer' then you will encode \"Manufacturer,Retailer\" in the same column"
" of your CSV file."
msgstr ""
#: ../../general/base_import/import_faq.rst:174
msgid ""
"`CSV file for Manufacturer, Retailer "
"<../../_static/example_files/m2m_customers_tags.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:179
msgid ""
"How can I import a one2many relationship (e.g. several Order Lines of a "
"Sales Order)?"
msgstr ""
#: ../../general/base_import/import_faq.rst:181
msgid ""
"If you want to import sales order having several order lines; for each order"
" line, you need to reserve a specific row in the CSV file. The first order "
"line will be imported on the same row as the information relative to order. "
"Any additional lines will need an addtional row that does not have any "
"information in the fields relative to the order. As an example, here is "
"purchase.order_functional_error_line_cant_adpat.CSV file of some quotations "
"you can import, based on demo data."
msgstr ""
#: ../../general/base_import/import_faq.rst:184
msgid ""
"`File for some Quotations "
"<../../_static/example_files/purchase.order_functional_error_line_cant_adpat.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:186
msgid ""
"The following CSV file shows how to import purchase orders with their "
"respective purchase order lines:"
msgstr ""
#: ../../general/base_import/import_faq.rst:188
msgid ""
"`Purchase orders with their respective purchase order lines "
"<../../_static/example_files/o2m_purchase_order_lines.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:190
msgid ""
"The following CSV file shows how to import customers and their respective "
"contacts:"
msgstr ""
#: ../../general/base_import/import_faq.rst:192
msgid ""
"`Customers and their respective contacts "
"<../../_static/example_files/o2m_customers_contacts.csv>`_."
msgstr ""
#: ../../general/base_import/import_faq.rst:197
msgid "Can I import several times the same record?"
msgstr ""
#: ../../general/base_import/import_faq.rst:199
msgid ""
"If you import a file that contains one of the column \"External ID\" or "
"\"Database ID\", records that have already been imported will be modified "
"instead of being created. This is very usefull as it allows you to import "
"several times the same CSV file while having made some changes in between "
"two imports. Odoo will take care of creating or modifying each record "
"depending if it's new or not."
msgstr ""
#: ../../general/base_import/import_faq.rst:201
msgid ""
"This feature allows you to use the Import/Export tool of Odoo to modify a "
"batch of records in your favorite spreadsheet application."
msgstr ""
#: ../../general/base_import/import_faq.rst:206
msgid "What happens if I do not provide a value for a specific field?"
msgstr ""
#: ../../general/base_import/import_faq.rst:208
msgid ""
"If you do not set all fields in your CSV file, Odoo will assign the default "
"value for every non defined fields. But if you set fields with empty values "
"in your CSV file, Odoo will set the EMPTY value in the field, instead of "
"assigning the default value."
msgstr ""
#: ../../general/base_import/import_faq.rst:213
msgid "How to export/import different tables from an SQL application to Odoo?"
msgstr ""
#: ../../general/base_import/import_faq.rst:215
msgid ""
"If you need to import data from different tables, you will have to recreate "
"relations between records belonging to different tables. (e.g. if you import"
" companies and persons, you will have to recreate the link between each "
"person and the company they work for)."
msgstr ""
#: ../../general/base_import/import_faq.rst:217
msgid ""
"To manage relations between tables, you can use the \"External ID\" "
"facilities of Odoo. The \"External ID\" of a record is the unique identifier"
" of this record in another application. This \"External ID\" must be unique "
"accoss all the records of all objects, so it's a good practice to prefix "
"this \"External ID\" with the name of the application or table. (like "
"'company_1', 'person_1' instead of '1')"
msgstr ""
#: ../../general/base_import/import_faq.rst:219
msgid ""
"As an example, suppose you have a SQL database with two tables you want to "
"import: companies and persons. Each person belong to one company, so you "
"will have to recreate the link between a person and the company he work for."
" (If you want to test this example, here is a <a "
"href=\"/base_import/static/csv/database_import_test.sql\">dump of such a "
"PostgreSQL database</a>)"
msgstr ""
#: ../../general/base_import/import_faq.rst:221
msgid ""
"We will first export all companies and their \"External ID\". In PSQL, write"
" the following command:"
msgstr ""
#: ../../general/base_import/import_faq.rst:227
msgid "This SQL command will create the following CSV file::"
msgstr ""
#: ../../general/base_import/import_faq.rst:234
msgid ""
"To create the CSV file for persons, linked to companies, we will use the "
"following SQL command in PSQL:"
msgstr ""
#: ../../general/base_import/import_faq.rst:240
msgid "It will produce the following CSV file::"
msgstr ""
#: ../../general/base_import/import_faq.rst:248
msgid ""
"As you can see in this file, Fabien and Laurence are working for the Bigees "
"company (company_1) and Eric is working for the Organi company. The relation"
" between persons and companies is done using the External ID of the "
"companies. We had to prefix the \"External ID\" by the name of the table to "
"avoid a conflict of ID between persons and companies (person_1 and company_1"
" who shared the same ID 1 in the orignial database)."
msgstr ""
#: ../../general/base_import/import_faq.rst:250
msgid ""
"The two files produced are ready to be imported in Odoo without any "
"modifications. After having imported these two CSV files, you will have 4 "
"contacts and 3 companies. (the firsts two contacts are linked to the first "
"company). You must first import the companies and then the persons."
msgstr ""
#: ../../general/odoo_basics.rst:3
msgid "Basics"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:3
msgid "How to add a user"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:5
msgid ""
"Odoo provides you with the option to add additional users at any given "
"point."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:9
msgid "Add individual users"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:11
msgid ""
"From the Settings module, go to the submenu :menuselection:`Users --> Users`"
" and click on **CREATE.** First add the name of your new user and the "
"professional email address - the one he will use to log into Odoo instance -"
" and a picture."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:19
msgid ""
"Under Access Rights, you can choose which applications your user can access "
"and use. Different levels of rights are available depending on the app."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:23
msgid ""
"When youre done editing the page and have clicked on **SAVE**, an "
"invitation email will automatically be sent to the user. The user must click"
" on it to accept the invitation to your instance and create a log-in."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:32
msgid ""
"Remember that each additional user will increase your subscription fees. "
"Refer to our `*Pricing page* <https://www.odoo.com/pricing>`__ for more "
"information."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:39
msgid ""
"You can also add a new user on the fly from your dashboard. From the above "
"screenshot, enter the email address of the user you would like to add and "
"click on **INVITE**. The user will receive an email invite containing a link"
" to set his password. You will then be able to define his accesses rights "
"under the :menuselection:`Settings --> Users menu`."
msgstr ""
#: ../../general/odoo_basics/add_user.rst:45
msgid ""
"`Deactivating Users <../../db_management/documentation.html#deactivating-"
"users>`_"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:47
msgid "Todo"
msgstr ""
#: ../../general/odoo_basics/add_user.rst:47
msgid "Add link to How to add companies"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:3
msgid "Manage Odoo in your own language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:5
msgid ""
"Odoo provides you with the option to manage Odoo in different languages, and"
" each user can use Odoo in his own language ."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:9
msgid "Load your desired language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:11
msgid ""
"The first thing to do is to load your desired language on your Odoo "
"instance."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:14
msgid ""
"From the general dashboard click on the **Settings** app; on the top left of"
" the page select :menuselection:`Translations --> Load a Translation`, "
"select a language to install and click on **LOAD.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:23
msgid ""
"If you check the \"Websites to translate\" checkbox you will have the option"
" to change the navigation language on your website."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:27
msgid "Change your language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:29
msgid ""
"You can change the language to the installed language by going to the drop-"
"down menu at the top right side of the screen, choose **Preferences**."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:36
msgid ""
"Then change the Language setting to your installed language and click "
"**SAVE.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:42
msgid "Open a new menu to view the changes."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:45
msgid "Change another user's language"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:47
msgid ""
"Odoo also gives you the possibility for each user to choose his preferred "
"language."
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:50
msgid ""
"To change the language for a different user, choose :menuselection:`Users "
"--> Users` from the Settings app. Here you have a list of all users and you "
"can choose the user who you'd like to change the language for. Select the "
"user and click on **Edit** in the top left corner. Under Preferences you can"
" change the Language to any previously installed language and click "
"**SAVE.**"
msgstr ""
#: ../../general/odoo_basics/choose_language.rst:61
msgid ":doc:`../../website/publish/translate`"
msgstr ""
#: ../../general/unsplash.rst:3
msgid "Unsplash"
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:3
msgid "How to generate an Unsplash access key"
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:6
msgid ""
"**As an SaaS user**, you are ready to use Unsplash. You won't need to follow"
" this guide to set up Unsplash informations, since you will use our own Odoo"
" Unsplash key in a transparent way."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:9
msgid "Generate an Unsplash access key for **non-Saas** users"
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:11
msgid "Create an account on `Unsplash.com <https://unsplash.com/join>`_."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:13
msgid ""
"Go to your `applications dashboard "
"<https://unsplash.com/oauth/applications>`_ and click on **New "
"Application**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:18
msgid "Accept the conditions and click on **Accept terms**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:23
msgid ""
"You will be prompted to insert an **Application name** and a "
"**Description**. Please prefix your application name by \"**Odoo:** \" so "
"that Unsplash can recognize it as an Odoo instance. Once done, click on "
"**Create application**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:28
msgid ""
"You should be redirected to your application details page. Scroll down a bit"
" to find your **access key**."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:34
msgid ""
"**As a non-SaaS user**, you won't be able to register for a production "
"Unsplash key and will be limited to your test key that has a restriction of "
"50 Unsplash requests per hour."
msgstr ""
#: ../../general/unsplash/unsplash_access_key.rst:37
msgid ":doc:`unsplash_application_id`"
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:3
msgid "How to generate an Unsplash application ID"
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:6
msgid ""
"You should first create and set up your Unsplash application with this "
"tutorial: :doc:`unsplash_access_key`."
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:8
msgid ""
"Go to your `applications dashboard "
"<https://unsplash.com/oauth/applications>`_ and click on your newly created "
"Unsplash application under **Your applications**."
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:13
msgid ""
"You will be redirected to your application details page. The **application "
"ID** will be visible in your browser's URL. The URL should be something like"
" ``https://unsplash.com/oauth/applications/<application_id>``"
msgstr ""
#: ../../general/unsplash/unsplash_application_id.rst:19
msgid ""
"**As a non-SaaS user**, you won't be able to register for a production "
"Unsplash key and will be limited to your test key that has a 50 Unsplash "
"requests per hour restriction."
msgstr ""
+381
View File
@@ -0,0 +1,381 @@
# 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 ""
+393
View File
@@ -0,0 +1,393 @@
# 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"
#: ../../helpdesk.rst:5
msgid "Helpdesk"
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 ""
+22
View File
@@ -0,0 +1,22 @@
# 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 ""
File diff suppressed because it is too large Load Diff
+440
View File
@@ -0,0 +1,440 @@
# 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"
#: ../../iot.rst:5
msgid "Internet of Things (IoT)"
msgstr ""
#: ../../iot/connect.rst:3
msgid "Connect an IoT Box to your database"
msgstr ""
#: ../../iot/connect.rst:5
msgid "Install the Internet of Things (IoT) App on your Odoo Database."
msgstr ""
#: ../../iot/connect.rst:10
msgid "Go in the IoT App and click on Connect on the IoT Boxes page."
msgstr ""
#: ../../iot/connect.rst:15
msgid "Follow the steps to connect your IoT Box."
msgstr ""
#: ../../iot/connect.rst:21
msgid "Ethernet Connection"
msgstr ""
#: ../../iot/connect.rst:23
msgid ""
"Connect to the IoT Box all the devices that have to be connected with cables"
" (ethernet, usb devices, etc.)."
msgstr ""
#: ../../iot/connect.rst:26
msgid "Power on the IoT Box."
msgstr ""
#: ../../iot/connect.rst:28
msgid "Then click on the Scan button."
msgstr ""
#: ../../iot/connect.rst:34
msgid "WiFi Connection"
msgstr ""
#: ../../iot/connect.rst:36
msgid "Power on the IoT Box"
msgstr ""
#: ../../iot/connect.rst:38
msgid "Copy the token"
msgstr ""
#: ../../iot/connect.rst:43
msgid ""
"Connect to the IoT Box WiFi Network (make sure there is no ethernet cable "
"plugged in your computer)."
msgstr ""
#: ../../iot/connect.rst:49
msgid ""
"You will be redirected to the IoT Box Homepage (if it doesn't work, connect "
"to the IP address of the box). Give a name to your IoT Box (not required) "
"and paste the token, then click on next."
msgstr ""
#: ../../iot/connect.rst:57
msgid ""
"If you are on Runbot, do not forget to add the -all or -base in the token "
"(e.g. this token **http://375228-saas-11-5-iot-"
"f3f920.runbot16.odoo.com\\|4957098401** should become "
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
msgstr ""
#: ../../iot/connect.rst:63
msgid ""
"Choose the WiFi network you want to connect with (enter the password if "
"there is one) and click on Submit. Wait a few seconds before being "
"redirected to your database."
msgstr ""
#: ../../iot/connect.rst:70
msgid "You should now see the IoT Box."
msgstr ""
#: ../../iot/connect.rst:76
msgid "IoT Box Schema"
msgstr ""
#: ../../iot/flash_sdcard.rst:3
msgid "Flashing your SD Card"
msgstr ""
#: ../../iot/flash_sdcard.rst:5
msgid ""
"In some case, you may need to reflash your IoT Boxs SD Card to benefit from"
" our latest updates."
msgstr ""
#: ../../iot/flash_sdcard.rst:9
msgid "Updating your SD Card with Etcher"
msgstr ""
#: ../../iot/flash_sdcard.rst:11
msgid ""
"Go to Balenas website and download `Etcher <http://wwww.balena.org>`__, "
"Its a free and open-source utility used for burning image files. Install "
"and launch it."
msgstr ""
#: ../../iot/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/flash_sdcard.rst:19
msgid ""
"Now, your image will be automatically updated. You just have to wait 5 "
"minutes for it to finish."
msgstr ""
#: ../../iot/iot_notfound.rst:3
msgid "IoT Box not found"
msgstr ""
#: ../../iot/iot_notfound.rst:5
msgid ""
"When using your IoT Box, a common issue you might encounter is that your box"
" is not found on your database. Fortunately, there are a few easy steps you "
"can follow to find your IoT box."
msgstr ""
#: ../../iot/iot_notfound.rst:10
msgid "HTTPS Issues"
msgstr ""
#: ../../iot/iot_notfound.rst:12
msgid "Your IoT Box is not found? You probably have https issues!"
msgstr ""
#: ../../iot/iot_notfound.rst:14
msgid ""
"To check it, go to your database and verify if your database address starts "
"with an https (like https://www.odoo.com). If this is the case, then you may"
" have problems with your IoT Box image. It should be version 18.12 or later."
msgstr ""
#: ../../iot/iot_notfound.rst:19
msgid ""
"If your IoT Box image is from an earlier version, then you will have to "
"reflash the SD card of your IoT Box to update the image (the latest image "
"can be found `here <http://nightly/odoo.com>`__)."
msgstr ""
#: ../../iot/iot_notfound.rst:23
msgid ""
"You can find the documentation about SD card flashing here (`here "
"<https://docs.google.com/document/d/1bqKsZhWqMqI4mhv4ltF61M_QPiBCHygYjjvkhsCTdaY/edit>`__)."
msgstr ""
#: ../../iot/pos.rst:3
msgid "Use the IoT Box for the PoS"
msgstr ""
#: ../../iot/pos.rst:9
msgid "Prerequisites"
msgstr ""
#: ../../iot/pos.rst:11
msgid "Before starting, make sure you have the following:"
msgstr ""
#: ../../iot/pos.rst:13
msgid "An IoT Box"
msgstr ""
#: ../../iot/pos.rst:15
msgid "A 2A Power adapter with pi 3 b+ 2.5 A"
msgstr ""
#: ../../iot/pos.rst:17
msgid "A computer or tablet with an up-to-date web browser"
msgstr ""
#: ../../iot/pos.rst:19
msgid ""
"A running SaaS or Odoo instance with the Point of Sale and IoT apps "
"installed"
msgstr ""
#: ../../iot/pos.rst:22
msgid "A local network setup with DHCP (this is the default setting)"
msgstr ""
#: ../../iot/pos.rst:24
msgid ""
"An Epson USB TM-T20 Printer or another ESC/POS compatible printer "
"(officially supported printers are listed at the `POS Hardware page "
"<https://www.odoo.com/page/pos-ipad-android-hardware>`__)"
msgstr ""
#: ../../iot/pos.rst:28
msgid "A Honeywell Eclipse USB Barcode Scanner or another compatible scanner"
msgstr ""
#: ../../iot/pos.rst:30
msgid "An Epson compatible cash drawer"
msgstr ""
#: ../../iot/pos.rst:32
msgid "An RJ45 Ethernet Cable (optional, WiFi is built in)"
msgstr ""
#: ../../iot/pos.rst:35
msgid "Set Up"
msgstr ""
#: ../../iot/pos.rst:37
msgid ""
"To connect hardware to the PoS, the first step is to connect an IoT Box to "
"your database. For this, follow this `documentation "
"<https://docs.google.com/document/d/1vhWrSSlSdJcRYe4tjPpXKYVMTD47lVK3ysyYc7tJDlA/edit#>`__."
msgstr ""
#: ../../iot/pos.rst:44
msgid "Then, you have to connect the peripheral devices to your IoT Box."
msgstr ""
#: ../../iot/pos.rst:46
msgid ""
"Officially supported hardware is listed on `the POS Hardware page "
"<https://www.odoo.com/page/pos-ipad-android-hardware>`__, but other hardware"
" might work as well."
msgstr ""
#: ../../iot/pos.rst:50
msgid "**Printer**: Connect an ESC/POS printer to a USB port and power it on."
msgstr ""
#: ../../iot/pos.rst:53
msgid ""
"**Cash drawer**: The cash drawer should be connected to the printer with an "
"RJ25 cable."
msgstr ""
#: ../../iot/pos.rst:56
msgid ""
"**Barcode scanner**: Connect your barcode scanner. In order for your barcode"
" scanner to be compatible it must behave as a keyboard and must be "
"configured in **US QWERTY**. It also must end barcodes with an Enter "
"character (keycode 28). This is most likely the default configuration of "
"your barcode scanner."
msgstr ""
#: ../../iot/pos.rst:62
msgid "**Scale**: Connect your scale and power it on."
msgstr ""
#: ../../iot/pos.rst:64
msgid ""
"**Ethernet**: If you do not wish to use Wi-Fi, plug in the Ethernet cable. "
"Make sure this will connect the IoT Box to the same network as your POS "
"device."
msgstr ""
#: ../../iot/pos.rst:68
msgid ""
"**Wi-Fi**: The current version of the IoT Box has Wi-Fi built in. Make sure "
"not to plug in an Ethernet cable when booting, because all Wi-Fi "
"functionality will be bypassed when a wired network connection is available "
"on boot."
msgstr ""
#: ../../iot/pos.rst:73
msgid ""
"Once it's done, you can connect the IoT Box to your PoS. For this, go in "
"Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the"
" IoT Box you want to connect with. Save the changes."
msgstr ""
#: ../../iot/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
msgstr ""
#: ../../iot/pos.rst:80
msgid "Troubleshoot"
msgstr ""
#: ../../iot/pos.rst:83
msgid "The PoS cannot connect to the IoT Box"
msgstr ""
#: ../../iot/pos.rst:85
msgid ""
"The easiest way to make sure the IoT Box is properly set-up is to turn it on"
" with the printer plugged in as it will print a receipt indicating any error"
" if encountered or the IoT Box's IP address in case of success. If no "
"receipt is printed, check the following steps:"
msgstr ""
#: ../../iot/pos.rst:91
msgid ""
"Make sure the IoT Box is powered on, indicated by a brightly lit red status "
"LED."
msgstr ""
#: ../../iot/pos.rst:94
msgid ""
"Make sure the IoT Box is ready, this is indicated by a brightly lit green "
"status LED just next to the red power status LED. The IoT Box should be "
"ready ~2 minutes after it is started."
msgstr ""
#: ../../iot/pos.rst:98
msgid ""
"Make sure the IoT Box is connected to the same network as your POS device. "
"Both the device and the IoT Box should be visible in the list of connected "
"devices on your network router."
msgstr ""
#: ../../iot/pos.rst:102
msgid ""
"If you specified the IoT Box's IP address in the configuration, make sure it"
" corresponds to the ip address printed on the IoT Box's status receipt."
msgstr ""
#: ../../iot/pos.rst:106
msgid "Make sure that the POS is not loaded over HTTPS."
msgstr ""
#: ../../iot/pos.rst:108
msgid ""
"A bug in Firefox's HTTP implementation might prevent the autodiscovery from "
"working reliably. You could also manually set up the IoT Box's IP address in"
" the POS configuration."
msgstr ""
#: ../../iot/pos.rst:113
msgid "The Barcode Scanner is not working"
msgstr ""
#: ../../iot/pos.rst:115
msgid ""
"The barcode scanner must be configured in US QWERTY and emit an Enter after "
"each barcode. This is the default configuration of most barcode readers. "
"Refer to the barcode reader documentation for more information."
msgstr ""
#: ../../iot/pos.rst:120
msgid ""
"The IoT Box needs a 2A power supply to work with some barcode scanners. If "
"you are not using the provided power supply, make sure the one you use has "
"enough power."
msgstr ""
#: ../../iot/pos.rst:124
msgid ""
"Some barcode scanners will need more than 2A and will not work, or will work"
" unreliably, even with the provided power supply. In those case you can plug"
" the barcode scanner in a self-powered USB hub."
msgstr ""
#: ../../iot/pos.rst:129
msgid ""
"Some poorly built barcode scanners do not advertise themselves as barcode "
"scanners but as a usb keyboard instead, and will not be recognized by the "
"IoT Box."
msgstr ""
#: ../../iot/pos.rst:134
msgid "The Barcode Scanner is not working reliably"
msgstr ""
#: ../../iot/pos.rst:136
msgid ""
"Make sure that no more than one device with 'Scan via Proxy'/'Barcode "
"Scanner' enabled are connected to the IoT Box at the same time."
msgstr ""
#: ../../iot/pos.rst:140
msgid "Printing the receipt takes too much time"
msgstr ""
#: ../../iot/pos.rst:142
msgid ""
"A small delay before the first print is expected, as the IoT Box will do "
"some preprocessing to speed up the next printings. If you suffer delays "
"afterwards it is most likely due to poor network connection between the POS "
"and the IoT Box."
msgstr ""
#: ../../iot/pos.rst:148
msgid "Some characters are not correctly printed on the receipt"
msgstr ""
#: ../../iot/pos.rst:150
msgid ""
"The IoT Box does not support all languages and characters. It currently "
"supports Latin and Cyrillic based scripts, with basic Japanese support."
msgstr ""
#: ../../iot/pos.rst:155
msgid "The printer is offline"
msgstr ""
#: ../../iot/pos.rst:157
msgid ""
"Make sure the printer is connected, powered, has enough paper and has its "
"lid closed, and is not reporting an error. If the error persists, please "
"contact support."
msgstr ""
#: ../../iot/pos.rst:162
msgid "The cashdrawer does not open"
msgstr ""
#: ../../iot/pos.rst:164
msgid ""
"The cashdrawer should be connected to the printer and should be activated in"
" the POS configuration."
msgstr ""
+193
View File
@@ -0,0 +1,193 @@
# 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"
#: ../../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 ""
File diff suppressed because it is too large Load Diff
+38
View File
@@ -0,0 +1,38 @@
# 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 ""
File diff suppressed because it is too large Load Diff
+164
View File
@@ -0,0 +1,164 @@
# 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 ""
+22
View File
@@ -0,0 +1,22 @@
# 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 ""
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
+22
View File
@@ -0,0 +1,22 @@
# 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 ""
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff