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

[I18N] Update translation terms from Transifex

Browse Source
This commit is contained in:
Odoo Translation Bot
2020-09-27 01:31:33 +02:00
parent e218ae4991
commit 5004122011
216 changed files with 179389 additions and 110130 deletions
Download Patch File Download Diff File Expand all files Collapse all files
locale/ru/LC_MESSAGES/accounting.po
+12503 -5420
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/applications.po
+4 -4
View File
@@ -1,15 +1,15 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
locale/ru/LC_MESSAGES/contributing.po
+1737
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/crm.po
+984 -2015
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/db_management.po
+401 -150
View File
@@ -1,15 +1,15 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -21,70 +21,354 @@ msgstr ""
msgid "Online Database management"
msgstr ""
#: ../../db_management/db_online.rst:13
msgid "Duplicating a database"
msgstr ""
#: ../../db_management/db_online.rst:15
#: ../../db_management/db_online.rst:10
msgid ""
"Database duplication, renaming, custom DNS, etc. is not available to free "
"customers of our Online platform."
"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 ""
"Access the `database management page <https://www.odoo.com/my/databases>`__ "
"(you will have to sign in). Next, make sure you are connected as the "
"administrator of the database you want to duplicate. After that, click on "
"the **Manage Your Databases** button."
"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:26
#: ../../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 not 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:140
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:36
msgid "A duplicated database has the same behaviour as a real one:"
#: ../../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:38
#: ../../db_management/db_online.rst:163
msgid "Emails are sent"
msgstr ""
#: ../../db_management/db_online.rst:40
msgid "Payments are processed (in the e-commerce, for example)"
msgstr ""
#: ../../db_management/db_online.rst:42
msgid "Delivery orders (shipping providers) are sent"
msgstr ""
#: ../../db_management/db_online.rst:44
msgid "Etc."
msgstr ""
#: ../../db_management/db_online.rst:46
#: ../../db_management/db_online.rst:165
msgid ""
"It is **strongly** advised to test behaviour using sample customers/products"
" (with a `disposable e-mail <http://www.mailinator.com>`__ address, for "
"Payments are processed (in the e-commerce or Subscriptions apps, for "
"example)"
msgstr ""
#: ../../db_management/db_online.rst:50
#: ../../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:54
#: ../../db_management/db_online.rst:180
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../db_management/db_online.rst:188
msgid "Rename a Database"
msgstr ""
#: ../../db_management/db_online.rst:190
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:201
msgid "Deleting a Database"
msgstr ""
#: ../../db_management/db_online.rst:203
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../db_management/db_online.rst:205
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:211
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:218
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:224
msgid ""
"After a few seconds, the database will be deleted and the page will reload "
"automatically."
msgstr ""
#: ../../db_management/db_online.rst:228
msgid ""
"If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../db_management/db_online.rst:230
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:234
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-premise Database management"
msgid "On-premises Database management"
msgstr ""
#: ../../db_management/db_premise.rst:10
@@ -111,8 +395,9 @@ msgid ""
"message:"
msgstr ""
#: ../../db_management/db_premise.rst:31 ../../db_management/db_premise.rst:97
#: ../../db_management/db_premise.rst:130
#: ../../db_management/db_premise.rst:31
#: ../../db_management/db_premise.rst:110
#: ../../db_management/db_premise.rst:138
msgid "Solutions"
msgstr ""
@@ -123,8 +408,8 @@ 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/contract>`__ or with your Account "
"Manager"
" Account <https://accounts.odoo.com/my/subscription>`__ or with your Account"
" Manager"
msgstr ""
#: ../../db_management/db_premise.rst:39
@@ -140,7 +425,7 @@ msgstr ""
#: ../../db_management/db_premise.rst:45
msgid ""
"You can unlink the old database yourself on your `Odoo Contract "
"<https://accounts.odoo.com/my/contract>`__ with the button \"Unlink "
"<https://accounts.odoo.com/my/subscription>`__ with the button \"Unlink "
"database\""
msgstr ""
@@ -155,7 +440,7 @@ msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../db_management/db_premise.rst:61
#: ../../db_management/db_premise.rst:190
#: ../../db_management/db_premise.rst:171
msgid ""
"From July 2016 onward, Odoo 9 now automatically change the uuid of a "
"duplicated database; a manual operation is no longer required."
@@ -165,7 +450,7 @@ msgstr ""
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/contract>`__, a short message will appear "
"<https://accounts.odoo.com/my/subscription>`__, a short message will appear "
"specifying which database is problematic:"
msgstr ""
@@ -183,41 +468,60 @@ msgid ""
"invoicing proceed effortlessly for your and for us."
msgstr ""
#: ../../db_management/db_premise.rst:82
msgid "Too much users error message"
#: ../../db_management/db_premise.rst:80
msgid "Check your network and firewall settings"
msgstr ""
#: ../../db_management/db_premise.rst:84
#: ../../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:93
#: ../../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:99
#: ../../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:102
msgid "or"
msgstr ""
#: ../../db_management/db_premise.rst:104
#: ../../db_management/db_premise.rst:114
msgid ""
"**Deactivate users** as explained in this `Documentation "
"<https://www.odoo.com "
"/documentation/user/10.0/db_management/documentation.html#deactivating-"
"users>`__ and **Reject** the upsell quotation."
"**Deactivate users** as explained in this `documentation <documentation.html"
"#deactivating-users>`_ and **Reject** the upsell quotation."
msgstr ""
#: ../../db_management/db_premise.rst:109
#: ../../db_management/db_premise.rst:117
msgid ""
"Once your database has the correct number of users, the expiration message "
"will disappear automatically after a few days, when the next verification "
@@ -226,109 +530,58 @@ msgid ""
"message disappear right away."
msgstr ""
#: ../../db_management/db_premise.rst:116
#: ../../db_management/db_premise.rst:124
msgid "Database expired error message"
msgstr ""
#: ../../db_management/db_premise.rst:118
#: ../../db_management/db_premise.rst:126
msgid ""
"If your database reaches its expiration date before your renew your "
"subscription, you will encounter this message:"
msgstr ""
#: ../../db_management/db_premise.rst:126
#: ../../db_management/db_premise.rst:134
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:134
#: ../../db_management/db_premise.rst:142
msgid ""
"Renew your subscription: follow the link and renew your subscription - note "
"that"
msgstr ""
#: ../../db_management/db_premise.rst:133
#: ../../db_management/db_premise.rst:141
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:136
#: ../../db_management/db_premise.rst:144
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:138
#: ../../db_management/db_premise.rst:146
msgid ""
"None of those solutions worked for you? Please contact our `Support "
"<https://www.odoo.com/help>`__"
msgstr ""
#: ../../db_management/db_premise.rst:145
msgid "Force an Update Notification"
msgstr ""
#: ../../db_management/db_premise.rst:147
msgid ""
"Update Notifications happen once every 7 days and keep your database up-to-"
"date with your Odoo Enterprise subscription. If you modify your subscription"
" (i.e. add more users, renew it for a year, etc.), your local database will "
"only be made aware of the change once every 7 days - this can cause "
"discrepancies between the state of your subscription and some notifications "
"in your App Switcher. When doing such an operation on your subscription, you"
" can force an Update using the following procedure:"
msgstr ""
#: ../../db_management/db_premise.rst:154
msgid "Connect to the database with the **Administrator** account"
msgstr ""
#: ../../db_management/db_premise.rst:155
msgid ""
"Switch to the Developer mode by using the **About** option in the top-right "
"menu (in V9) / in **Settings** (in V10): click on **Activate the developer"
" mode**"
msgstr ""
#: ../../db_management/db_premise.rst:158
msgid ""
"Navigate to the \"Settings\" menu, then \"Technical\" > \"Automation\" > "
"\"Scheduled Actions\""
msgstr ""
#: ../../db_management/db_premise.rst:160
msgid ""
"Find \"Update Notification\" in the list, click on it, and finally click on "
"the button \"**RUN MANUALLY**\""
msgstr ""
#: ../../db_management/db_premise.rst:162
msgid "Refresh the page, the \"Expiration\" notification should be gone"
msgstr ""
#: ../../db_management/db_premise.rst:165
msgid ""
"You may have kept the same UUID on different databases and we receive "
"information from those databases too. So please read :ref:`this "
"documentation <duplicate_premise>` to know how to change the UUID. After the"
" change you can force a ping to speed up the verification, your production "
"database will then be correctly identified."
msgstr ""
#: ../../db_management/db_premise.rst:174
msgid "Duplicate a database"
msgstr ""
#: ../../db_management/db_premise.rst:176
#: ../../db_management/db_premise.rst:157
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:184
#: ../../db_management/db_premise.rst:165
msgid ""
"When you duplicate a local database, it is **strongly** advised to change "
"the duplicated database's uuid (Unniversally Unique Identifier), since this "
@@ -337,13 +590,13 @@ msgid ""
"registration problems down the line."
msgstr ""
#: ../../db_management/db_premise.rst:193
#: ../../db_management/db_premise.rst:174
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."
"The database uuid is currently accessible from the menu "
":menuselection:`Settings --> Technical --> System Parameters`, we advise you"
" to use a `uuid generator <https://www.uuidtools.com>`_ 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
@@ -401,76 +654,74 @@ msgstr ""
#: ../../db_management/documentation.rst:39
msgid ""
"In your Odoo instance, click on **Settings**. You will have a section "
"showing you the active users on your database. Click on **Manage access "
"rights.**"
"showing you the active users on your database. Click on **Manage Users.**"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:43
#: ../../db_management/documentation.rst:80
msgid "|settings|"
msgstr ""
#: ../../db_management/documentation.rst:44
#: ../../db_management/documentation.rst:43
msgid "|browse_users|"
msgstr ""
#: ../../db_management/documentation.rst:47
#: ../../db_management/documentation.rst:46
msgid "You'll then see the list of your users."
msgstr ""
#: ../../db_management/documentation.rst:52
#: ../../db_management/documentation.rst:51
msgid ""
"The pre-selected filter *Internal Users* shows your paying users (different "
"from the *Portal Users* which are free). If you remove this filter, you'll "
"get all your users (the ones you pay for and the portal ones)"
msgstr ""
#: ../../db_management/documentation.rst:57
#: ../../db_management/documentation.rst:56
msgid ""
"In your list of users, click on the user you want to deactivate. As soon as "
"you are on the userform, go with your mouse cursor on the status **Active** "
"(top right). Click on Active and you will notice that the status will change"
" to **Inactive** immediately."
"you are on the userform, click on the Action drop down menu, and then click "
"on Archive."
msgstr ""
#: ../../db_management/documentation.rst:66
#: ../../db_management/documentation.rst:64
msgid "The user is now deactivated."
msgstr ""
#: ../../db_management/documentation.rst:68
#: ../../db_management/documentation.rst:66
msgid "**Never** deactivate the main user (*admin*)"
msgstr ""
#: ../../db_management/documentation.rst:71
#: ../../db_management/documentation.rst:69
msgid "Uninstalling Apps"
msgstr ""
#: ../../db_management/documentation.rst:73
#: ../../db_management/documentation.rst:71
msgid ""
"Make sure you first test what you are about to do on a :ref:`duplicate "
"<duplicate_online>` of your database before making any changes (*especially*"
" installing/uninstalling apps)."
msgstr ""
#: ../../db_management/documentation.rst:77
#: ../../db_management/documentation.rst:75
msgid ""
"In your Odoo instance click on **Settings**; in this app, you will be able "
"to see how many applications you have installed. Click on **Browse Apps** to"
" access the list of your installed applications."
msgstr ""
#: ../../db_management/documentation.rst:82
#: ../../db_management/documentation.rst:80
msgid "|browse_apps|"
msgstr ""
#: ../../db_management/documentation.rst:85
#: ../../db_management/documentation.rst:83
msgid ""
"In your applications' dashboard, you will see all the icons of your "
"applications. Click on the application you want to uninstall. Then, on the "
"form of the application, click on **Uninstall**."
msgstr ""
#: ../../db_management/documentation.rst:92
#: ../../db_management/documentation.rst:90
msgid ""
"Some applications have dependencies, like Invoicing, eCommerce, etc. "
"Therefore, the system will give you a warning message to advise you of what "
@@ -480,20 +731,20 @@ msgid ""
" click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:99
#: ../../db_management/documentation.rst:97
msgid ""
"Last, after having checked the warning message (if any), click **Confirm**."
msgstr ""
#: ../../db_management/documentation.rst:104
#: ../../db_management/documentation.rst:102
msgid "You have finished uninstalling your application."
msgstr ""
#: ../../db_management/documentation.rst:107
#: ../../db_management/documentation.rst:105
msgid "Good to know"
msgstr ""
#: ../../db_management/documentation.rst:109
#: ../../db_management/documentation.rst:107
msgid ""
"**Uninstalling apps, managing users, etc. is up to you**: no one else can "
"know if your business flow is broken better than you. If we were to "
@@ -503,7 +754,7 @@ msgid ""
"operations."
msgstr ""
#: ../../db_management/documentation.rst:115
#: ../../db_management/documentation.rst:113
msgid ""
"**Odoo Apps have dependencies**: this means that you may need to install "
"modules that you do not actively use to access some features of Odoo you "
@@ -513,7 +764,7 @@ msgid ""
"to work properly."
msgstr ""
#: ../../db_management/documentation.rst:122
#: ../../db_management/documentation.rst:120
msgid ""
"**Always test app installation/removal on a duplicate** (or on a free trial "
"database): that way you can know what other apps may be required, etc. This "
locale/ru/LC_MESSAGES/discuss.po
+588 -380
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/ecommerce.po
+12 -437
View File
@@ -1,15 +1,15 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -574,7 +574,7 @@ msgid ""
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:3
msgid "How to sell pricier product alternatives (upselling)"
msgid "How to sell pricier alternative products (upselling)"
msgstr ""
#: ../../ecommerce/maximizing_revenue/upselling.rst:5
@@ -659,185 +659,6 @@ msgstr ""
msgid "Get paid"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:3
msgid "How to get paid with payment acquirers"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:5
msgid ""
"Odoo embeds several payment methods to get paid on eCommerce, Sales and "
"Invoicing apps."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:10
msgid "What are the payment methods available"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:13
msgid "Wire transfer"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:15
msgid ""
"Wire Transfer is the default payment method available. The aim is providing "
"your customers with your bank details so they can pay on their own via their"
" bank. This is very easy to start with but slow and inefficient process-"
"wise. Opt for online acquirers as soon as you can!"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:21
msgid "Payment acquirers"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:23
msgid ""
"Redirect your customers to payment platforms to collect money effortless and"
" track the payment status (call-back). Odoo supports more and more platforms"
" over time:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:27
msgid "`Paypal <paypal.html>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:28
msgid "Ingenico"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:29
msgid "Authorize.net"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:30
msgid "Adyen"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:31
msgid "Buckaroo"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:32
msgid "PayUmoney"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:33
msgid "Sips"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:34
msgid "Stripe"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:38
msgid "How to go live"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:40
msgid ""
"Once the payment method ready, make it visible in the payment interface and "
"activate the **Production** mode."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:48
msgid "How to let customers save and reuse credit cards"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:49
msgid ""
"To ease the payment of returning customers, you can let them save and reuse "
"a credit card if they want to. If so, a payment token will be saved in Odoo."
" This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:54
#: ../../ecommerce/shopper_experience/payment.rst:68
msgid "You can turn this on from the acquirer configuration form."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:61
msgid "How to debit credit cards to pay subscriptions"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:62
msgid ""
"`Odoo Subscription <https://www.odoo.com/page/subscriptions>`__ allows to "
"bill services automatically on a recurring basis. Along with it, you can "
"have an automatic debit of the customer's credit card."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:66
msgid "This option is available with Ingenico and Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:73
msgid ""
"That way a payment token will be recorded when the customer goes for the "
"subscription and an automatic debit will occur whenever an invoice is issued"
" from the subscription."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:79
msgid "How to use other acquirers (advanced)"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:81
msgid ""
"Odoo can submit single payment requests and redirect to any payment "
"acquirer. But there is no call-back, i.e. Odoo doesn't track the transaction"
" status. So you will confirm orders manually once you get paid."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:85
msgid "How to:"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:87
msgid "Switch to developer mode."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:89
msgid "Take the **Custom** payment method."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:91
msgid ""
"Set up the payment form (S2S Form Template) as instructed by your payment "
"acquirer. You can start from *default_acquirer_button* that you can "
"duplicate."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:96
msgid "Other configurations"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:98
msgid ""
"Odoo can also be used for more advanced payment processes like installment "
"plans (e.g. `Paypal Installment Plans "
"<https://developer.paypal.com/docs/classic/paypal-payments-standard"
"/integration-guide/installment_buttons>`__)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:102
msgid ""
"Such a customization service is made on-demand by our technical experts "
"based on your own requirements. A business advisor can reach you out for "
"such matter. `Contact us. <https://www.odoo.com/page/contactus>`__"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:109
msgid ":doc:`paypal`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:110
msgid ":doc:`wire_transfer`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment.rst:111
#: ../../ecommerce/shopper_experience/paypal.rst:155
msgid ":doc:`payment_acquirer`"
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:3
msgid "How to manage orders paid with payment acquirers"
msgstr ""
@@ -911,7 +732,7 @@ msgid ""
"orders straight on."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:53
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:54
msgid ""
"If you choose this mode you are requested to select a payment journal in "
"order to record payments in your books. This payment is automatically "
@@ -919,231 +740,33 @@ msgid ""
"account** if you get paid immediately on your bank account. If you don't you"
" can create a specific journal for the payment acquirer (type = Bank). That "
"way, you can track online payments in an intermediary account of your books "
"until you get paid into your bank account (see `How to register credit card "
"payments "
"<../../accounting/receivables/customer_payments/credit_cards.html>`__)."
"until you get paid into your bank account (see "
":doc:`../../general/payment_acquirers/payment_acquirers`)."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:63
msgid "Capture the payment after the delivery"
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:65
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:64
msgid ""
"With this mode, the order is confirmed but the amount is kept on hold. Once "
"the delivery processed, you can capture the payment from Odoo. This mode is "
"only available with Authorize.net."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:72
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:71
msgid ""
"To capture the payment, open the transaction from the order. Then click "
"*Capture Transaction*."
msgstr ""
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:78
#: ../../ecommerce/shopper_experience/payment_acquirer.rst:77
msgid ""
"With other payment acquirers, you can manage the capture in their own "
"interfaces, not from Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:3
msgid "How to get paid with Paypal"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:5
msgid ""
"Paypal is the easiest online payment method to configure. It is also the "
"only one without any subscription fee. We definitely advise it to any "
"starter."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:11
msgid "Set up your Paypal account"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:13
msgid ""
"Create a `Paypal Business Account <https://www.paypal.com>`__ or upgrade "
"your account to *Business account* if you have a basic account."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:16
msgid ""
"Log in to `Paypal <https://www.paypal.com>`__ and open the settings of your "
"**Profile**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:22
msgid "Now enter the menu **My selling tools**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:27
msgid "Let's start with the **Website Preferences**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:29
msgid ""
"Turn on **Auto Return** and enter the **Return URL**: "
"<odoo_instance_url>/shop/confirmation. Verify that this address uses the "
"correct protocol (HTTP/HTTPS)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:36
msgid ""
"Turn on **Payment Data Transfer**. When saving, an **Identity Token** is "
"generated. You will be later requested to enter it in Odoo."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:43
msgid ""
"Then, get back to your profile to activate the **Instant Payment "
"Notification (IPN)** in *My selling tools*."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:46
msgid "Enter the **Notification URL**: <odoo_instance_url>/payment/paypal/ipn"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:51
msgid ""
"Now you must change the encoding format of the payment request sent by Odoo "
"to Paypal. To do so, get back to *My selling tools* and click **PayPal "
"button language encoding** in *More Selling Tools* section."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:58
msgid ""
"Then, click *More Options* and set the two default encoding formats as "
"**UTF-8**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:66
msgid ""
"If you want your customers to pay without creating a Paypal account, "
"**Paypal Account Optional** needs to be turned on."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:74
msgid "Set up Paypal's payment method in Odoo"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:75
msgid ""
"Open Paypal setup form in :menuselection:`Website or Sales or Accounting -->"
" Settings --> Payment Acquirers+`. Enter both your **Email ID** and your "
"**Merchant ID** and check **Use IPN**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:82
msgid ""
"They are both provided in your Paypal profile, under :menuselection:`My "
"business info`."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:85
msgid ""
"Enter your **Identity Token** in Odoo (from *Auto Return* option). To do so,"
" open the *Settings* and activate the **Developer Mode**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:91
msgid ""
"Then, go to :menuselection:`Settings --> Technical --> Parameters --> System"
" Parameters` and create a parameter with following values:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:94
msgid "Key: payment_paypal.pdt_token"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:95
msgid "Value: your Paypal *Identity Token*"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:102
msgid "Go live"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:103
msgid ""
"Your configuration is now ready! You can make Paypal visible on your "
"merchant interface and activate the **Production mode**."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:112
msgid "Transaction fees"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:114
msgid ""
"You can charge an extra to the customer to cover the transaction fees Paypal"
" charges you. Once redirected to Paypal, your customer sees an extra applied"
" to the order amount."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:117
msgid ""
"To activate this, go to the *Configuration* tab of Paypal config form in "
"Odoo and check *Add Extra Fees*. Default fees for US can be seen here below."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:123
msgid ""
"To apply the right fees for your country, please refer to `Paypal Fees "
"<https://www.paypal.com/webapps/mpp/paypal-fees>`__."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:128
msgid "Test the payment flow"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:130
msgid ""
"You can test the entire payment flow thanks to Paypal Sandbox accounts."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:132
msgid ""
"Log in to `Paypal Developer Site <https://developer.paypal.com>`__ with your"
" Paypal credentials. This will create two sandbox accounts:"
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:136
msgid ""
"A business account (to use as merchant, e.g. "
"pp.merch01-facilitator@example.com)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:137
msgid ""
"A default personal account (to use as shopper, e.g. "
"pp.merch01-buyer@example.com)."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:139
msgid ""
"Log in to `Paypal Sandbox <https://www.sandbox.paypal.com>`__ with the "
"merchant account and follow the same configuration instructions."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:142
msgid ""
"Enter your sandbox credentials in Odoo and make sure Paypal is still set on "
"*Test* mode. Also, make sure the confirmation mode of Paypal is not "
"*Authorize & capture the amount, confirm the SO and auto-validate the "
"invoice on acquirer confirmation*. Otherwise a confirmed invoice will be "
"automatically generated when the transaction is completed."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:150
msgid "Run a test transaction from Odoo using the sandbox personal account."
msgstr ""
#: ../../ecommerce/shopper_experience/paypal.rst:154
msgid ":doc:`payment`"
msgstr ""
#: ../../ecommerce/shopper_experience/portal.rst:3
msgid "How customers can access their customer account"
msgstr ""
@@ -1189,54 +812,6 @@ msgid ""
"will see all the documents whose the customer belongs to this company."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:3
msgid "How to get paid with wire transfers"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:5
msgid ""
"**Wire Transfer** is the default payment method available. The aim is "
"providing your customers with your bank details so they can pay on their "
"own. This is very easy to start with but slow and inefficient process-wise. "
"Opt for payment acquirers as soon as you can!"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:13
msgid "How to provide customers with payment instructions"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:14
msgid ""
"Put your payment instructions in the **Thanks Message** of your payment "
"method."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:19
msgid "They will appear to the customers when they place an order."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:26
msgid "How to manage an order once you get paid"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:28
msgid ""
"Whenever a customer pays by wire transfer, the order stays in an "
"intermediary stage **Quotation Sent** (i.e. unpaid order). When you get "
"paid, you confirm the order manually to launch the delivery."
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:35
msgid "How to create other manual payment methods"
msgstr ""
#: ../../ecommerce/shopper_experience/wire_transfer.rst:37
msgid ""
"If you manage a B2B business, you can create other manually-processed "
"payment methods like paying by check. To do so, just rename *Wire Transfer* "
"or duplicate it."
msgstr ""
#: ../../ecommerce/taxes.rst:3
msgid "Collect taxes"
msgstr ""
locale/ru/LC_MESSAGES/email_marketing.po
+284
View File
@@ -0,0 +1,284 @@
# 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: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../email_marketing.rst:5
msgid "Email Marketing"
msgstr ""
#: ../../email_marketing/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:3
msgid "Work with Mailing Lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:5
msgid ""
"Mailing lists can be a goldmine for your company’s marketing department as "
"they can provide leads for sales, focus groups for testing new products, and"
" consumers to provide feedback on satisfaction, for example."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:10
msgid "Create mailing lists"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:12
msgid ""
"Go to :menuselection:`Mailing lists --> Mailing lists --> Create`. Enable "
"the option *Is Public* to make the list visible for users when "
"unsubscribing."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:19
msgid ""
"Once your mailing list is created, you can manually add contacts clicking on"
" *Create*. *Import* a list of contacts if you have it from a previous tool."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:23
msgid "Linking a mailing list to my website"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:26
msgid ""
"Create a mailing list called Newsletter, as you use this strategy to "
"advertise and communicate new ideas to subscribers interested in listening."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:27
msgid ""
"Go to your *Website*, add a *Newsletter* block and choose the respective "
"mailing list."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:34
msgid "Contacts"
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:36
msgid ""
"Under :menuselection:`Mailing Lists --> Mailing List Contacts` see a list of"
" all contacts under all your mailing lists, and the ones you individually "
"created here."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:43
msgid ""
"Open a contact form to see or add different mailing lists to which the "
"contact is or will be part of."
msgstr ""
#: ../../email_marketing/overview/mailing_lists.rst:51
#: ../../email_marketing/overview/manage_unsubscriptions.rst:46
msgid ":doc:`send_emails`"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:3
msgid "Manage Unsubscriptions and Blacklist"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:5
msgid ""
"It is best practice, and legally required, to allow recipients to "
"unsubscribe from mailing lists as you do not want your audience to think "
"that your company is using any tactics that are dishonest or spammy."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:10
msgid "Enable the Blacklist feature"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:12
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable the option "
"*Blacklist Option when Unsubscribing*."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:19
msgid ""
"Now, once the user clicks on the *Unsubscribe* link on your email, he is "
"redirected to the following page:"
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:28
msgid ""
"After clicking on the unsubscribe button when using the test feature, you "
"are sent to an error page (*error 403 - Access Denied*). If you want to be "
"sure the link is working properly, create your mass mail and send it only to"
" a personal email."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:32
msgid ""
"In addition to having the option of unsubscribing from specific mailing "
"lists, the user can also blacklist himself, meaning that he will not receive"
" *any* more emails from you."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:36
msgid ""
"The mailing list has to be configured as *Public* in order to be visible for"
" users."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:38
msgid ""
"Under :menuselection:`Configuration --> Blacklist`, blacklisted email "
"addresses are shown."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:39
msgid ""
"When opening the record, as a *Log note*, a description-history is kept."
msgstr ""
#: ../../email_marketing/overview/manage_unsubscriptions.rst:47
msgid ":doc:`mailing_lists`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:3
msgid "Send Emails Marketing and Manage Campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:5
msgid ""
"Emails allow you to effectively, and at a low cost, reach a large number of "
"consumers while being able to customize your message in a way that resonates"
" with them. It is measurable, and a call-to-action oriented channel."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:10
msgid "Choose the right target and create the message"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:12
msgid "Go to :menuselection:`Mailings --> Create`."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:14
msgid ""
"Choosing *Contacts* as *Recipients* (for example), allows you to add "
"specifications to match just certain contacts, filtering your target."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:21
msgid ""
"With a trial databases, you have a limit of 50 emails per day; on Odoo SH "
"Cloud Platform the limit is 200. There is a possibility to increase these "
"numbers by contacting Odoo Support. To contact Support, `click here "
"<https://www.odoo.com/help>`_."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:25
msgid ""
"Under *Mail Body*, choose a layout and make the modifications needed by "
"dragging, dropping and double-clicking on content. Note that it is possible "
"to start from scratch selecting the *blank* template option."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:34
msgid ""
"Under *Settings*, you can assign someone else as the responsible sender if "
"you do not want it to be you. To do so, change the email address used as the"
" sender (*Send From*)."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:37
msgid ""
"With the *Reply To* radio button, you can also choose to gather answers "
"either on the respective recipients’ records or on a specific email address."
" Note that this option is not available if you target mailing contacts or "
"contacts as recipients."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:45
msgid "Test, send or schedule a mailing"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:53
msgid ""
"*Save*: the work is allocated in the *draft* column in the Kanban view. "
"Modifications can be made while being in this stage. The option *Discard* "
"deletes the email."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:54
msgid ""
"Click on *Test* and send your message to one, or even multiple, test "
"contacts to avoid errors."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:56
msgid ""
"*Send* triggers the email with the next run and put the work on the *queue* "
"column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:58
msgid ""
"*Schedule* allows you to choose a date and time, and puts the email in the "
"*queue* column in the Kanban view."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:61
msgid ""
"The daily limit is applied for **all emails** sent, in other words, "
"throughout all applications. Therefore, if at the end of the day you have "
"remaining ones to be sent, note that they *will not* be sent automatically "
"the next day. You need to force that by opening the email and clicking on "
"*Retry*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:67
msgid "Manage campaigns"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:69
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Mailing "
"Campaigns*."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:71
msgid ""
"The campaign option is effective as it allows you to organize your marketing"
" efforts and have a centralized view of its metrics."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:72
msgid "Go to *Campaign* and click on *Create* to start one."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:80
msgid ""
"If you use the SMS and Social Marketing applications, as well as the Push "
"Notification feature, you see the option to create content for those "
"channels. You also see the *Campaign* menu within those applications. All of"
" this is possible because the applications work integrated."
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:85
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../email_marketing/overview/send_emails.rst:86
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""
locale/ru/LC_MESSAGES/events.po
+429
View File
@@ -0,0 +1,429 @@
# 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: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../events.rst:5
msgid "Events"
msgstr ""
#: ../../events/integrations.rst:3
msgid "Integrations"
msgstr ""
#: ../../events/integrations/integration_sms.rst:3
msgid "Communicating about my Event using SMS Text Messages"
msgstr ""
#: ../../events/integrations/integration_sms.rst:5
msgid ""
"Using SMS as a communication strategy for your event establishes interaction"
" between organizers, attendees, speakers and further targets. It allows your"
" message to be heard whether the goal is to send out reminders, teasers or "
"to advertise."
msgstr ""
#: ../../events/integrations/integration_sms.rst:10
#: ../../events/overview/tickets.rst:9 ../../events/overview/track_talks.rst:9
msgid "Configuration"
msgstr ""
#: ../../events/integrations/integration_sms.rst:13
msgid ""
"Under *Communication* SMS is a standard feature. That means nothing needs to"
" be enabled or installed."
msgstr ""
#: ../../events/integrations/integration_sms.rst:16
msgid ""
"On the other hand, to contact the speakers of your event, you need the *SMS "
"Marketing* application installed, and to enable *Schedule & Tracks* under "
":menuselection:`Events --> Configuration --> Settings`."
msgstr ""
#: ../../events/integrations/integration_sms.rst:23
msgid ""
"The *Schedule & Tracks* feature allows you to manage the agenda and speakers"
" of your event. For more details watch: `Creating an agenda for your event "
"<https://www.odoo.com/slides/slide/create-an-agenda-for-your-"
"event-717?fullscreen=1>`_."
msgstr ""
#: ../../events/integrations/integration_sms.rst:28
msgid "Send SMSs to attendees"
msgstr ""
#: ../../events/integrations/integration_sms.rst:30
msgid ""
"Under *Communication*, the message’s target is the attendees of your event."
msgstr ""
#: ../../events/integrations/integration_sms.rst:32
msgid ""
"You can choose to confirm each registration with the *Registration* "
"template, and to send a reminder shortly before the event takes place with "
"the *Reminder* template."
msgstr ""
#: ../../events/integrations/integration_sms.rst:38
msgid "To make changes in an existing template, click on the external link."
msgstr ""
#: ../../events/integrations/integration_sms.rst:45
msgid "Send SMSs to speakers and further targets"
msgstr ""
#: ../../events/integrations/integration_sms.rst:47
msgid ""
"The benefit of the integration with the *SMS Marketing* application is that "
"you can choose the target you would like your message to be delivered to. To"
" get started, click on *Contact Track Speakers*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:56
msgid ""
"If *Event Track* is not your target (*Recipient*), choose the right one. "
"*Filters* are eligible here."
msgstr ""
#: ../../events/integrations/integration_sms.rst:58
msgid ""
"In the example below, the SMS would be sent to the speakers who are in the "
"stage *Proposal* on *Event Track*."
msgstr ""
#: ../../events/integrations/integration_sms.rst:65
msgid ""
"Credits are required to be able to send SMSs. For more information about "
"Pricing :doc:`click here <../../sms_marketing/pricing/pricing_and_faq>`, "
"and, about IAP Services :doc:`here "
"<../../general/in_app_purchase/in_app_purchase>`."
msgstr ""
#: ../../events/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../events/overview/create_event.rst:3
msgid "Create your First Event"
msgstr ""
#: ../../events/overview/create_event.rst:5
msgid "Some of the reasons why hosting events is essential are:"
msgstr ""
#: ../../events/overview/create_event.rst:7
msgid "To create an engaging experience with your audience;"
msgstr ""
#: ../../events/overview/create_event.rst:8
msgid "To generate word of mouth about your company;"
msgstr ""
#: ../../events/overview/create_event.rst:9
msgid "To allow networking;"
msgstr ""
#: ../../events/overview/create_event.rst:10
msgid ""
"To provide an opportunity for sales representatives to walk their prospects "
"through the product and even their pipeline."
msgstr ""
#: ../../events/overview/create_event.rst:14
msgid "Get started"
msgstr ""
#: ../../events/overview/create_event.rst:16
msgid ""
"Under the menu *Events*, have a view of all existing events and some key "
"information, such as the number of expected and confirmed attendees."
msgstr ""
#: ../../events/overview/create_event.rst:23
msgid ""
"To start a new one, click on *Create* and fill in the form with all the "
"needed information. Enable *Website Menu* to have the menus *Introduction*, "
"*Location*, and *Register* being shown on your event’s website page."
msgstr ""
#: ../../events/overview/create_event.rst:31
msgid ""
"To personalize these pages, click on *Edit* to open the `website builder "
"<https://www.odoo.com/slides/slide/website-basics-643?fullscreen=1>`_, and "
"edit content by dragging and dropping blocks."
msgstr ""
#: ../../events/overview/create_event.rst:40
msgid "Tab: Tickets"
msgstr ""
#: ../../events/overview/create_event.rst:43
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
":doc:`Tickets and Online Ticketing <tickets>`."
msgstr ""
#: ../../events/overview/create_event.rst:46
msgid ""
"Now, under the *Tickets* Tab, add lines to include the different ticket "
"types you offer. Include the price, the start and end dates for "
"registrations, and even the maximum number of tickets that can be sold."
msgstr ""
#: ../../events/overview/create_event.rst:48
msgid ""
"The *Reserved Seats* and *Unconfirmed Seat Reservations* are counted as "
"attendees are marked as :doc:`confirmed <track_attendees>` or not."
msgstr ""
#: ../../events/overview/create_event.rst:55
msgid "Tab: Communication"
msgstr ""
#: ../../events/overview/create_event.rst:58
msgid ""
"Choose the email and/or SMS message template, as well as the frequency with "
"which you would like to communicate with your attendees under the tab "
"*Communication*."
msgstr ""
#: ../../events/overview/create_event.rst:61
msgid ""
"Create a template on the fly or choose an existing one. Define the "
"*Interval* (2, 7, 15..) for the *Unit* (days, hours, weeks, etc.), and the "
"*Trigger* action (after registration, after the event, etc.)."
msgstr ""
#: ../../events/overview/create_event.rst:68
msgid "Tab: Questions"
msgstr ""
#: ../../events/overview/create_event.rst:70
msgid ""
"Go to :menuselection:`Configuration --> Settings` and enable *Questions*."
msgstr ""
#: ../../events/overview/create_event.rst:72
msgid ""
"Now, under the tab *Questions*, edit your questions and answers, choosing if"
" you would like your questionnaire to be asked per order or per "
"registration."
msgstr ""
#: ../../events/overview/create_event.rst:75
msgid ""
"Example of a registration for 3 attendees: if enabling the option *Ask each "
"attendee*, the questionnaire is shown 3 times, meaning that answers can vary"
" for each attendee; if *Ask each attendee* is not enabled, the questionnaire"
" is shown once, resulting in a global answer."
msgstr ""
#: ../../events/overview/create_event.rst:81
msgid ""
"Once your event is *Confirmed*, you can manage attendees badges, and mark "
"the event as *Finished*. Events marked as *Finished* can be *Set to draft*, "
"putting the event back to an *Unconfirmed* stage from which it can be edited"
" and used again."
msgstr ""
#: ../../events/overview/create_event.rst:90
msgid "Publish your event"
msgstr ""
#: ../../events/overview/create_event.rst:92
msgid "*Go to Website* and turn *Published* on."
msgstr ""
#: ../../events/overview/create_event.rst:99
msgid ":doc:`track_attendees`"
msgstr ""
#: ../../events/overview/create_event.rst:100
#: ../../events/overview/track_attendees.rst:45
msgid ":doc:`tickets`"
msgstr ""
#: ../../events/overview/create_event.rst:101
#: ../../events/overview/track_attendees.rst:46
msgid ":doc:`track_talks`"
msgstr ""
#: ../../events/overview/tickets.rst:3
msgid "Selling Tickets"
msgstr ""
#: ../../events/overview/tickets.rst:5
msgid ""
"If you automate processes, you save time. If you give attendees multiple "
"payment options to choose from, you allow flexibility and open margins for "
"more registrations to happen."
msgstr ""
#: ../../events/overview/tickets.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Settings` and activate *Tickets* and"
" *Online Ticketing*."
msgstr ""
#: ../../events/overview/tickets.rst:13
msgid ""
"*Tickets* allow tickets to be sold "
":ref:`events/create_event/through_sales_orders`. *Online Ticketing* allows "
"the sale of tickets to happen "
":ref:`events/create_event/through_the_website`."
msgstr ""
#: ../../events/overview/tickets.rst:22
msgid "Through Sales Orders"
msgstr ""
#: ../../events/overview/tickets.rst:24
msgid ""
"On the *Sales* application, choose the event product you created and add it "
"as a product line. A window pops-up, allowing you to choose the event for "
"which you want to create the sales order."
msgstr ""
#: ../../events/overview/tickets.rst:32
msgid ""
"Remember to create a product form for the event registration, under "
"*Product*, in the *Sales* application, and to add that same product under "
"your event’s form."
msgstr ""
#: ../../events/overview/tickets.rst:43
msgid "Through the Website"
msgstr ""
#: ../../events/overview/tickets.rst:45
msgid ""
"On the website, once tickets are added to the cart, the user can continue "
"the transaction choosing among the payment methods you chose to have "
"available."
msgstr ""
#: ../../events/overview/tickets.rst:53
msgid ":doc:`../../general/payment_acquirers/payment_acquirers`"
msgstr ""
#: ../../events/overview/track_attendees.rst:3
msgid "Track your Attendees"
msgstr ""
#: ../../events/overview/track_attendees.rst:5
msgid ""
"Attendees are at the heart of your event. Keeping track of their number and "
"managing their registration and attendance is necessary for planning and "
"analyzing reasons."
msgstr ""
#: ../../events/overview/track_attendees.rst:9
msgid "Attendees list and attendance"
msgstr ""
#: ../../events/overview/track_attendees.rst:11
msgid ""
"Once attendees have registered or bought their tickets, they are added to "
"the *Attendees* list."
msgstr ""
#: ../../events/overview/track_attendees.rst:12
msgid ""
"Tickets sold through sales orders validate attendees as soon as the "
"quotation is confirmed."
msgstr ""
#: ../../events/overview/track_attendees.rst:18
msgid ""
"The check mark button is used to confirm the registration. Once a "
"registration is confirmed, attendance can be marked."
msgstr ""
#: ../../events/overview/track_attendees.rst:26
msgid "Bagdes and cancellations"
msgstr ""
#: ../../events/overview/track_attendees.rst:28
msgid ""
"On the attendees form, choose to send badges manually by clicking on *Send "
"By Email*. *Cancel Registration* to have that attendee being moved to the "
"*Cancelled* stage."
msgstr ""
#: ../../events/overview/track_attendees.rst:36
msgid ""
"To see a list of your canceled attendees, under *Filters*, add a *Custom "
"Filter* choosing *Status > is > Cancelled*."
msgstr ""
#: ../../events/overview/track_attendees.rst:44
#: ../../events/overview/track_talks.rst:49
msgid ":doc:`../integrations/integration_sms`"
msgstr ""
#: ../../events/overview/track_talks.rst:3
msgid "Track and Manage Talks"
msgstr ""
#: ../../events/overview/track_talks.rst:5
msgid ""
"Allow partners to submit talk proposals so they can share their knowledge "
"and expertise. Good speakers and talks are what make your event great."
msgstr ""
#: ../../events/overview/track_talks.rst:11
msgid ""
"Go to :menuselection:`Events --> Configuration --> Settings` and enable "
"*Schedule & Tracks*."
msgstr ""
#: ../../events/overview/track_talks.rst:14
msgid ""
"Now, in your event's form, once *Website menu* is enabled, the options "
"*Tracks on Website* and *Track Proposals on Website* become available. "
"Enabling them adds the menus *Talks*, *Talk Proposals*, and *Agenda* to your"
" website."
msgstr ""
#: ../../events/overview/track_talks.rst:20
msgid ""
"Besides having the ability to suggest their own talks, the website now "
"allows users to see a list of the whole agenda and scheduled talks."
msgstr ""
#: ../../events/overview/track_talks.rst:28
msgid ""
"To handle tracks internally and not have the menus *Talks*, *Talk "
"Proposals*, and *Agenda* online, use the menu *Tracks* individually."
msgstr ""
#: ../../events/overview/track_talks.rst:32
msgid "Publishing speaker proposals"
msgstr ""
#: ../../events/overview/track_talks.rst:34
msgid ""
"Once partners have filled in the appropriate form and submitted their "
"proposals, a new *Proposal* is instantly created under the menu *Track*."
msgstr ""
#: ../../events/overview/track_talks.rst:41
msgid ""
"If the proposal is accepted and can go online, simply open its form and "
"click on *Go to Website*. From the website page, turn *Published* on."
msgstr ""
locale/ru/LC_MESSAGES/expense.po
+340
View File
@@ -0,0 +1,340 @@
# 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: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../expense/expense.rst:5
msgid "Expenses"
msgstr ""
#: ../../expense/expense.rst:8
msgid "How to set expense types"
msgstr ""
#: ../../expense/expense.rst:9
msgid ""
"The first step to track expenses is to configure the expense types (managed "
"as products in Odoo) that your company allows, from the *Configuration* "
"menu. When a specific expense is reimbursed at a fixed price, set a cost on "
"the product. Otherwise keep the cost at 0.0 and employees will report the "
"real cost per expense."
msgstr ""
#: ../../expense/expense.rst:17
msgid "Here are some examples to configure:"
msgstr ""
#: ../../expense/expense.rst:19
msgid "Restaurant:"
msgstr ""
#: ../../expense/expense.rst:21 ../../expense/expense.rst:27
msgid "Cost: 0.00 (the cost of the ticket will be recorded on every expense)"
msgstr ""
#: ../../expense/expense.rst:22
msgid "Travel with Personal Car:"
msgstr ""
#: ../../expense/expense.rst:24
msgid "Cost: 0.30 (the price per mile reimbursed by the company is fixed)"
msgstr ""
#: ../../expense/expense.rst:25
msgid "Hotel:"
msgstr ""
#: ../../expense/expense.rst:29
msgid "Others:"
msgstr ""
#: ../../expense/expense.rst:31
msgid "Cost: 0.0"
msgstr ""
#: ../../expense/expense.rst:33
msgid ""
"Don't forget to set an expense tax on each expense type (and an account if "
"you use Odoo Accounting). It's usually a good practice to use a tax that is "
"configured with :ref:`Tax Included in Price <taxes/included-in-price>`. That"
" way, employees report expenses with prices including taxes, which is "
"usually the expected behaviour."
msgstr ""
#: ../../expense/expense.rst:41
msgid ""
"The *Sales* app allows you to specify unit of measures for your expense "
"types (units, miles, nights, etc.). Go to :menuselection:`Sales --> "
"Configuration --> Settings` and check *Some products may be sold/purchased "
"in different units of measure (advanced)*."
msgstr ""
#: ../../expense/expense.rst:48
msgid "How to record expenses"
msgstr ""
#: ../../expense/expense.rst:51
msgid "Manually"
msgstr ""
#: ../../expense/expense.rst:53
msgid ""
"As an employee (Employee in user access rights), you can record expenses "
"from :menuselection:`My Expenses --> Expenses to Submit`."
msgstr ""
#: ../../expense/expense.rst:59
msgid ""
"Select the related product and enter either the total amount you paid (with "
"Quantity = 1) or the unit price if Quantity is countable (e.g. number of "
"hotel nights)."
msgstr ""
#: ../../expense/expense.rst:62
msgid "Enter the expense date."
msgstr ""
#: ../../expense/expense.rst:63
msgid ""
"Choose if you paid the bill on your own (and expect to be reimbursed) or if "
"the company paid directly (e.g. if you used a company's credit card)."
msgstr ""
#: ../../expense/expense.rst:65
msgid ""
"Set the bill reference, add some notes if requested and attach a photo/scan "
"of the receipt from the discussion thread. That will help the manager and "
"the accountant validate it."
msgstr ""
#: ../../expense/expense.rst:73
msgid "In one click from emails"
msgstr ""
#: ../../expense/expense.rst:74
msgid ""
"Let your employees record their expenses from a simple email. Make a "
"snapshot of the receipt and send it by email, or simply forward a bill!"
msgstr ""
#: ../../expense/expense.rst:77
msgid ""
"The only thing to do is setting up an email alias in "
":menuselection:`Expenses --> Configuration --> Settings` (e.g. *expenses* "
"@mycompany.odoo.com). For security purposes, only authenticated employee "
"emails (cfr. *Work Email* in employee detail form) are accepted."
msgstr ""
#: ../../expense/expense.rst:83
msgid ""
"The expense product is set automatically if the mail subject contains the "
"product's internal reference in first position. Type the expense amount in "
"the mail subject to set it on the expense too (e.g. Ref001 Food 100€)."
msgstr ""
#: ../../expense/expense.rst:88
msgid "How to submit expenses to managers"
msgstr ""
#: ../../expense/expense.rst:90
msgid ""
"When you are ready to submit your expenses to your manager (e.g. at the end "
"of a business trip, or once a month), go to the menu :menuselection:`My "
"Expenses --> Expenses to Submit`. Select all expenses from the list view and"
" click on :menuselection:`Action --> Submit to Manager`. Save the newly "
"created expense report (i.e. set of expenses), and wait for your manager to "
"approve it."
msgstr ""
#: ../../expense/expense.rst:100
msgid ""
"You can also submit expenses one by one from the *Submit to Manager* button "
"on the form view of an expense."
msgstr ""
#: ../../expense/expense.rst:103
msgid ""
"All your submitted expense reports can be found in :menuselection:`Expenses "
"--> My Expenses --> Expense Reports`."
msgstr ""
#: ../../expense/expense.rst:108
msgid "How to approve expenses"
msgstr ""
#: ../../expense/expense.rst:110
msgid ""
"HR and team managers get an overview of all expense reports to validate from"
" the top menu :menuselection:`To Approve --> Expense Reports to Approve`. "
"Such users must have at least *Officers* access rights for *Expenses*."
msgstr ""
#: ../../expense/expense.rst:117
msgid ""
"They can review expense reports, approve or reject them, as well as "
"providing feedback thanks to the integrated communication tool."
msgstr ""
#: ../../expense/expense.rst:123
msgid ""
"As a team manager you can easily find the expense reports of your team "
"members. You need to be set as manager in the detail form of those "
"employees."
msgstr ""
#: ../../expense/expense.rst:131
msgid "How to post expenses in accounting"
msgstr ""
#: ../../expense/expense.rst:133
msgid ""
"Once expense reports approved by managers, the accounting department goes to"
" :menuselection:`Expenses --> Accountant --> Expense Reports To Post` to "
"check accounts, products and taxes. They can click *Post Journal Entries* to"
" post related journal entries into your books. To do so, the user must have "
"following access rights:"
msgstr ""
#: ../../expense/expense.rst:139
msgid "Accounting: Accountant or Adviser"
msgstr ""
#: ../../expense/expense.rst:140
msgid "Expenses: Manager"
msgstr ""
#: ../../expense/expense.rst:143
msgid ""
"To post an expense, a *Home Address* must be set on the employee. If you get"
" a related blocking message when posting, click the employee, go to "
"*Personal Information* tab and select/create the contact of your employee in"
" the address book. A contact has been automatically created if this person "
"is using Odoo."
msgstr ""
#: ../../expense/expense.rst:150
msgid "How to reimburse employees"
msgstr ""
#: ../../expense/expense.rst:152
msgid ""
"You can now see all the expense reports to reimburse in "
":menuselection:`Expenses --> Accountant --> Expense Reports To Pay`. To "
"record the payment or pay by check, click *Register a Payment*."
msgstr ""
#: ../../expense/expense.rst:156
msgid "See how you can easily manage the payment process in Odoo:"
msgstr ""
#: ../../expense/expense.rst:158
msgid ":doc:`../accounting/payables/pay/check`"
msgstr ""
#: ../../expense/expense.rst:159
msgid ":doc:`../accounting/payables/pay/sepa`"
msgstr ""
#: ../../expense/expense.rst:163
msgid "How to re-invoice expenses to your customers"
msgstr ""
#: ../../expense/expense.rst:165
msgid ""
"If you track expenses on customer projects, you can charge them back to your"
" customers automatically."
msgstr ""
#: ../../expense/expense.rst:169
msgid "Setup"
msgstr ""
#: ../../expense/expense.rst:171
msgid "Enable **Customer Billing** in the Expenses settings"
msgstr ""
#: ../../expense/expense.rst:173
msgid ""
"Go to the product configuration menu and set the invoicing method on all "
"your Expense types:"
msgstr ""
#: ../../expense/expense.rst:176
msgid ""
"Ordered quantities : it will invoice expenses based on the ordered quantity"
msgstr ""
#: ../../expense/expense.rst:179
msgid ""
"Delivered quantities :it will invoice expenses based on the expenses "
"quantity"
msgstr ""
#: ../../expense/expense.rst:182
msgid "At cost: will invoice expenses at their real cost."
msgstr ""
#: ../../expense/expense.rst:184
msgid ""
"At sales price: will invoice based on a fixed sales price set on the sale "
"order."
msgstr ""
#: ../../expense/expense.rst:191
msgid "Create an order"
msgstr ""
#: ../../expense/expense.rst:193
msgid ""
"As a salesman, create and confirm a Sales Order for the services delivered "
"to your customer. If you don't put any expense in the order, it will be "
"added automatically once posted by the accountant."
msgstr ""
#: ../../expense/expense.rst:198
msgid "Link the expense to the Sale Order."
msgstr ""
#: ../../expense/expense.rst:204
msgid "Submit, validate and post expenses"
msgstr ""
#: ../../expense/expense.rst:206
msgid ""
"As a manager, make sure the analytic account is set on every expense line on"
" approving expenses reports. Click the line to add one if missing. Employees"
" are already able to set one when submitting."
msgstr ""
#: ../../expense/expense.rst:213
msgid "As an accountant, post journal entries."
msgstr ""
#: ../../expense/expense.rst:216
msgid "Invoice expenses"
msgstr ""
#: ../../expense/expense.rst:218
msgid ""
"Now you can invoice the order. It shows up in :menuselection:`Sales --> "
"Invoicing --> Sales` to Invoice. The expenses have been added automatically "
"in the order lines. Such items show up in blue (i.e. to invoice)."
msgstr ""
#: ../../expense/expense.rst:226
msgid "e (i.e. to invoice)."
msgstr ""
locale/ru/LC_MESSAGES/fsm.po
+386
View File
@@ -0,0 +1,386 @@
# 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: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../fsm.rst:5
msgid "Field Service"
msgstr ""
#: ../../fsm/helpdesk.rst:3
msgid "Helpdesk"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:3
msgid "Plan Onsite Interventions from Helpdesk Tickets"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:4
msgid ""
"The integration with the Helpdesk application lets your helpdesk team manage"
" interventions requests directly. It speeds up processes as you can plan "
"field services tasks from tickets."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:8
#: ../../fsm/sales/create_quotations.rst:8
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:9
#: ../../fsm/worksheets/customize_worksheets.rst:9
msgid "Enable the feature"
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:9
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams --> "
"Edit` and enable :menuselection:`Onsite Interventions --> Save`."
msgstr ""
#: ../../fsm/helpdesk/plan_onsite.rst:17
msgid ""
"Now once your helpdesk team needs, they have the option to *Plan "
"Intervention* from tickets."
msgstr ""
#: ../../fsm/overview.rst:3
msgid "Overview"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:3
msgid "Invoicing Time and Material to Customers"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:4
msgid ""
"Track the exact time spent on a task and give customers the ability to sign "
"their worksheet report onsite. Invoice customers as soon as the work is "
"complete, leaving you, and the customer, with the confidence that they will "
"be charged for the exact right hours and material used."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:9
msgid "Get the exact time spent on a task"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:10
msgid ""
"Click on *Start* to launch the timer. You can *Pause* at any moment and "
"*Resume* when you would like to continue."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:17
msgid ""
"Click on *Stop* once the work is done to confirm the total time spent and "
"add a description."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:24
msgid "Sign and send reports & validate stock-picking"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:25
msgid ""
"Now, fill your *Worksheet* and add the used products clicking on *Products*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:31
msgid ""
"Click on *Start* if you need to record additional time for the same "
"activity. The time recorded will be added to the already created and signed "
"worksheet. Then, create a new invoice for the time added."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:34
msgid ""
"*Mark as done* to close the task and to invoice your intervention. It also "
"validates the stock-picking keeping your inventory up-to-date."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:37
msgid ""
"*Sign Report* generates a detailed worksheet report for the customer to "
"sign. Send it through email clicking on *Send Report*."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:41
msgid "Invoice your time and material"
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:42
msgid ""
"Under :menuselection:`All Tasks --> To Invoice`, find a list of all tasks "
"marked as done but that have not been invoiced. Convenient feature as it "
"allows accountants to easily access all finished tasks at once."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:52
msgid ""
"Invoice all tasks at once selecting them all and going to "
":menuselection:`Action --> Create Invoice`."
msgstr ""
#: ../../fsm/overview/invoicing_time.rst:60
msgid ":doc:`../../project/advanced/feedback`"
msgstr ""
#: ../../fsm/overview/keep_track.rst:3
msgid "Keeping Track of Stock"
msgstr ""
#: ../../fsm/overview/keep_track.rst:4
msgid ""
"The integration with the Inventory application makes possible to track the "
"material used and automatically keep your stock up to date."
msgstr ""
#: ../../fsm/overview/keep_track.rst:8
msgid "Set up your Field Service project"
msgstr ""
#: ../../fsm/overview/keep_track.rst:9
msgid ""
"Go to :menuselection:`Field Service --> Configuration --> Projects` and make"
" sure the option *Products on Tasks* is enabled."
msgstr ""
#: ../../fsm/overview/keep_track.rst:15
msgid ""
"Now, add the materials used in the intervention to the worksheet, and once "
"the task is *Marked as done*, the stock-picking is automatically validated "
"and the inventory evaluation is automatically updated."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:3
msgid "Manage your Employees’ Schedules and Time Off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:4
msgid ""
"The integration with the *Time off* application allows you to quickly see "
"your employees’ availabilities. It will avoid conflicts and errors between "
"employees schedules and interventions."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:8
msgid "Effortlessly see employees’ time off"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:9
msgid ""
"No configuration needs to be done. Once the employees’ time has been "
"validated in the *Time off* application, cells will be grayed for those days"
" in your Gantt view."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:13
msgid ""
"It also adapts to the working calendar of the employee. Example: the "
"employee works part-time (from Monday to Wednesday). So, Thursday and Friday"
" will also be greyed, in addition to the weekends."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:20
msgid "Easily manage employees’ schedules"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:21
msgid ""
"From the Gantt view (under *Planning by User, Project or Worksheet*), click "
"on the plus sign to add a new task or on the magnifying glass to plan an "
"existing one."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:29
msgid "Unassigned tasks"
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:30
msgid ""
"If you need to plan an intervention but you do not know yet who will take "
"care of it, you can leave the task unassigned. It will still be shown in the"
" Gantt view. Simply drag and drop the responsible person he can be assigned."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:39
msgid ""
"Create projects per team, or per working site, and have a more accurate and "
"dynamic database."
msgstr ""
#: ../../fsm/overview/manage_employees_schedule.rst:42
msgid ":doc:`../../project/overview/setup`"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:3
msgid "Planning an Itinerary"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:5
msgid ""
"Having an itinerary being shown based on the chronological order of the "
"activities and on the best route to take, makes employees’ life easier and "
"the workload more efficient."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:9
msgid "Have an itinerary displayed directly in Odoo"
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:10
msgid "Go to *Settings* and under *Map view* click on *Get token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:15
msgid ""
"Click on :menuselection:`Start mapping for free --> fill the Username, email"
" and password fields --> agree with their Terms of Service and Privacy "
"Policy --> Get started`. You will be redirected to your account. Scrolling "
"the page down you will find *Access tokens*. Copy the *Default public "
"token*."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:24
msgid "Back in Odoo, paste it on :menuselection:`Token --> Save`."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:29
msgid ""
"Now, your maps will show the itinerary based on the scheduled time and best "
"route."
msgstr ""
#: ../../fsm/overview/planning_itinerary.rst:36
msgid ""
"This is an optional feature, as you can still have access to a map view "
"without a Mapbox account."
msgstr ""
#: ../../fsm/sales.rst:3
msgid "Sales"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:3
msgid "Create Quotations from Tasks"
msgstr ""
#: ../../fsm/sales/create_quotations.rst:4
msgid ""
"Allowing quotations to be created from tasks delivers a more efficient "
"service as it allows space for preventive actions, while making the flow "
"easy for employees."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:9
msgid ""
"First, go to :menuselection:`Field Service --> Configuration --> Settings` "
"and enable the option *Extra Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:16
msgid ""
"Second, go to :menuselection:`Configuration --> Projects` and enable *Extra "
"Quotations*."
msgstr ""
#: ../../fsm/sales/create_quotations.rst:23
msgid "You can now create *New Quotations* directly from your tasks."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:3
msgid "Create Onsite Interventions Tasks from Sales Orders"
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:4
msgid ""
"By allowing your sales team to open onsite interventions tasks will create a"
" seamless experience for your customers. It also allows them to first "
"receive a quotation with the materials that will be used plus the service "
"price to be approved before the work even starts."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:10
msgid ""
"Go to :menuselection:`Sales --> Products --> Create` or edit an existing "
"one. Select: under :menuselection:`General Information --> Product Type: "
"Service`; under :menuselection:`Sales --> Service Invoicing Policy: "
"Timesheet on task --> Service Tracking: Create a task in an existing project"
" --> Project --> Worksheet Template --> Save`."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:19
msgid ""
"Now, once you have *Confirmed* a *quotation*, a task will be created in the "
"respective project you have chosen."
msgstr ""
#: ../../fsm/sales/onsite_tasks_from_sales_orders.rst:28
msgid ""
"One of the greatest benefits here is that you can have different *Worksheets"
" Templates* under the same project and product, for example."
msgstr ""
#: ../../fsm/worksheets.rst:3
msgid "Worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:3
msgid "Customize Worksheet Reports"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:4
msgid ""
"Personalizing your customer reports, also called *worksheets*, allows you to"
" have different descriptions of the work for each type of intervention. It "
"speeds up the flow for your employees while giving customers a detailed "
"summary, which can be reviewed and signed onsite."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:10
msgid ""
"Go to :menuselection:`Field Service --> Configuration` and enable "
":menuselection:`Worksheet Templates --> Save`."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:18
msgid "Designing worksheets"
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:19
msgid ""
"Under :menuselection:`Configuration --> Worksheet Templates`, click on "
"*Create* and start to *Design Worksheet Template*. You will be redirected to"
" the *Studio* application."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:27
msgid ""
"With the freedom of *Studio*, drag and drop fields to create a report "
"tailored to your needs. Once you are done, click on *Close* and get an "
"overview of the work done."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:30
msgid ""
"*Worksheets* is where you can see how many times the worksheet has been "
"used/completed under a task. *Analysis* examines all the worksheets under "
"that given template and generates a graph."
msgstr ""
#: ../../fsm/worksheets/customize_worksheets.rst:38
msgid ""
"`Studio Basics <https://www.odoo.com/slides/slide/studio-"
"basics-710?fullscreen=1>`_"
msgstr ""
locale/ru/LC_MESSAGES/general.po
+2189 -188
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/getting_started.po
+225 -513
View File
@@ -1,15 +1,15 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -18,650 +18,362 @@ msgstr ""
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../getting_started/documentation.rst:5
msgid "Odoo Online Implementation"
msgid "Basics of the QuickStart Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:7
msgid ""
"This document summarizes **Odoo's Online services**, our Success Pack "
"**implementation methodology**, and *best practices* to **get started** with"
" our product."
"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:11
msgid ""
"*We recommend that new Odoo Online customers read this document before the "
"kick-off call with our project manager. This way, we save time and don't "
"have to use your hours from the success pack discussing the basics.*"
#: ../../getting_started/documentation.rst:12
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:16
#: ../../getting_started/documentation.rst:14
msgid ""
"*If you have not read this document, our project manager will review this "
"with you at the time of the kick-off call.*"
"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 "Getting Started"
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:22
#: ../../getting_started/documentation.rst:25
msgid ""
"Do not wait for the kick-off meeting to begin playing with the software. The"
" more exposure you have with Odoo, the more time you will save later during "
"the implementation."
msgstr ""
#: ../../getting_started/documentation.rst:26
msgid ""
"Once you purchase an Odoo Online subscription, you will receive instructions"
" by e-mail on how to activate or create your database. From this email, you "
"can activate your existing Odoo database or create a new one from scratch."
"**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 ""
"If you did not receive this email, e.g. because the payment was made by "
"someone else in your company, contact our support using our `online support "
"form <https://www.odoo.com/help>`__."
"**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:38
#: ../../getting_started/documentation.rst:39
msgid ""
"Fill in the sign-in or sign-up screens and you will get your first Odoo "
"database ready to be used."
"**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 :doc:`Odoo documentation <../index>`, `The elearning "
"platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
#: ../../getting_started/documentation.rst:41
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:51
msgid ""
"In order to familiarize yourself with the user interface, take a few minutes"
" to create records: *products, customers, opportunities or projects / "
"tasks*. Follow the blinking dots, they give you tips about the user "
"interface as shown in the picture below."
"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:47
msgid "|left_pic|"
msgstr ""
#: ../../getting_started/documentation.rst:47
msgid "|right_pic|"
msgstr ""
#: ../../getting_started/documentation.rst:50
#: ../../getting_started/documentation.rst:55
msgid ""
"Once you get used to the user interface, have a look at the implementation "
"planners. These are accessible from the Settings app, or from the top "
"progress bar on the right hand side of the main applications."
"**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:58
msgid "These implementation planners will:"
msgstr ""
#: ../../getting_started/documentation.rst:60
msgid "help you define your goals and KPIs for each application,"
msgstr ""
#: ../../getting_started/documentation.rst:62
msgid "guide you through the different configuration steps,"
msgstr ""
#: ../../getting_started/documentation.rst:64
msgid "and provide you with tips and tricks to getting the most out of Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:66
#: ../../getting_started/documentation.rst:61
msgid ""
"Fill in the first steps of the implementation planner (goals, expectations "
"and KPIs). Our project manager will review them with you during the "
"implementation process."
"**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:73
#: ../../getting_started/documentation.rst:68
msgid ""
"If you have questions or need support, our project manager will guide you "
"through all the steps. But you can also:"
msgstr ""
#: ../../getting_started/documentation.rst:76
msgid ""
"Read the documentation on our website: "
"`https://www.odoo.com/documentation/user "
"<https://www.odoo.com/documentation/user>`__"
msgstr ""
#: ../../getting_started/documentation.rst:79
msgid ""
"Watch the videos on our eLearning platform (Free with your first Success "
"Pack): `https://odoo.thinkific.com/courses/odoo-functional "
"<https://odoo.thinkific.com/courses/odoo-functional>`__"
"**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:82
msgid "Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:84
msgid ""
"Watch the webinars on our `Youtube channel "
"<https://www.youtube.com/user/OpenERPonline>`__"
"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:85
#: ../../getting_started/documentation.rst:88
msgid ""
"Or send your questions to our online support through our `online support "
"form <https://www.odoo.com/help>`__."
"**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:89
msgid "What do we expect from you?"
msgstr ""
#: ../../getting_started/documentation.rst:91
#: ../../getting_started/documentation.rst:96
msgid ""
"We are used to deploying fully featured projects within 25 to 250 hours of "
"services, which is much faster than any other ERP vendor on the market. Most"
" projects are completed between 1 to 9 calendar months."
"**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:95
#: ../../getting_started/documentation.rst:110
msgid ""
"But what really **differentiates between a successful implementation and a "
"slow one, is you, the customer!** From our experience, when our customer is "
"engaged and proactive the implementation is smooth."
"**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:100
msgid "Your internal implementation manager"
msgstr ""
#: ../../getting_started/documentation.rst:102
#: ../../getting_started/documentation.rst:115
msgid ""
"We ask that you maintain a single point of contact within your company to "
"work with our project manager on your Odoo Implementation. This is to ensure"
" efficiency and a single knowledge base in your company. Additionally, this "
"person must:"
"**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:107
#: ../../getting_started/documentation.rst:120
msgid ""
"**be available at least 2 full days a week** for the project, otherwise you "
"risk slowing down your implementation. More is better with the fastest "
"implementations having a full time project manager."
"**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:111
#: ../../getting_started/documentation.rst:128
msgid ""
"**have authority to take decisions** on their own. Odoo usually transforms "
"all departments within a company for the better. There can be many small "
"details that need quick turn arounds for answers and if there is too much "
"back and forth between several internal decision makers within your company "
"it could potentially seriously slow everything down."
"`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:117
#: ../../getting_started/documentation.rst:132
msgid ""
"**have the leadership** to train and enforce policies internally with full "
"support from all departments and top management, or be part of top "
"management."
"**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:121
msgid "Integrate 90% of your business, not 100%"
msgstr ""
#: ../../getting_started/documentation.rst:123
#: ../../getting_started/documentation.rst:135
msgid ""
"You probably chose Odoo because no other software allows for such a high "
"level of automation, feature coverage, and integration. But **don't be an "
"extremist.**"
"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:127
#: ../../getting_started/documentation.rst:141
msgid ""
"Customizations cost you time, money, are more complex to maintain, add risks"
" to the implementation, and can cause issues with upgrades."
"*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:130
msgid ""
"Standard Odoo can probably cover 90% of your business processes and "
"requirements. Be flexible on the remaining 10%, otherwise that 10% will cost"
" you twice the original project price. One always underestimates the hidden "
"costs of customization."
msgstr ""
#: ../../getting_started/documentation.rst:134
msgid ""
"**Do it the Odoo way, not yours.** Be flexible, use Odoo the way it was "
"designed. Learn how it works and don't try to replicate the way your old "
"system(s) works."
msgstr ""
#: ../../getting_started/documentation.rst:138
msgid ""
"**The project first, customizations second.** If you really want to "
"customize Odoo, phase it towards the end of the project, ideally after "
"having been in production for several months. Once a customer starts using "
"Odoo, they usually drop about 60% of their customization requests as they "
"learn to perform their work flows out of the box, or the Odoo way. It is "
"more important to have all your business processes working than customizing "
"a screen to add a few fields here and there or automating a few e-mails."
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:147
msgid ""
"Our project managers are trained to help you make the right decisions and "
"measure the tradeoffs involved but it is much easier if you are aligned with"
" them on the objectives. Some processes may take more time than your "
"previous system(s), however you need to weigh that increase in time with "
"other decreases in time for other processes. If the net time spent is "
"decreased with your move to Odoo than you are already ahead."
"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:155
msgid "Invest time in learning Odoo"
msgstr ""
#: ../../getting_started/documentation.rst:157
#: ../../getting_started/documentation.rst:152
msgid ""
"Start your free trial and play with the system. The more comfortable you are"
" with navigating Odoo, the better your decisions will be and the quicker and"
" easier your training phases will be."
"**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:161
#: ../../getting_started/documentation.rst:160
msgid ""
"Nothing replaces playing with the software, but here are some extra "
"resources:"
"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:164
msgid ""
"Documentation: `https://www.odoo.com/documentation/user "
"<https://www.odoo.com/documentation/user>`__"
"**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:167
msgid ""
"Introduction Videos: `https://www.odoo.com/r/videos "
"<https://www.odoo.com/r/videos>`__"
#: ../../getting_started/documentation.rst:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:170
msgid ""
"Customer Reviews: `https://www.odoo.com/blog/customer-reviews-6 "
"<https://www.odoo.com/blog/customer-reviews-6>`__"
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
#: ../../getting_started/documentation.rst:174
msgid "Get things done"
msgstr ""
#: ../../getting_started/documentation.rst:176
#: ../../getting_started/documentation.rst:173
msgid ""
"Want an easy way to start using Odoo? Install Odoo Notes to manage your to-"
"do list for the implementation: `https://www.odoo.com/page/notes "
"<https://www.odoo.com/page/notes>`__. From your Odoo home, go to Apps and "
"install the Notes application."
"Training sessions on the standard or customized solution will be organized."
msgstr ""
#: ../../getting_started/documentation.rst:177
msgid "Customizations and Development"
msgstr ""
#: ../../getting_started/documentation.rst:179
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:184
msgid "This module allows you to:"
msgstr ""
#: ../../getting_started/documentation.rst:186
msgid "Manage to-do lists for better interactions with your consultant;"
msgstr ""
#: ../../getting_started/documentation.rst:188
msgid "Share Odoo knowledge & good practices with your employees;"
msgstr ""
#: ../../getting_started/documentation.rst:190
msgid ""
"Get acquainted with all the generic tools of Odoo: Messaging, Discussion "
"Groups, Kanban Dashboard, etc."
"**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:197
#: ../../getting_started/documentation.rst:196
msgid ""
"This application is even compatible with the Etherpad platform "
"(http://etherpad.org). To use these collaborative pads rather than standard "
"Odoo Notes, install the following add-on: Memos Pad."
"**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 "What should you expect from us?"
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr ""
#: ../../getting_started/documentation.rst:205
msgid "Subscription Services"
msgstr ""
#: ../../getting_started/documentation.rst:208
msgid "Cloud Hosting"
#: ../../getting_started/documentation.rst:206
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:210
msgid ""
"Odoo provides a top notch cloud infrastructure including backups in three "
"different data centers, database replication, the ability to duplicate your "
"instance in 10 minutes, and more!"
"**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
#: ../../getting_started/documentation.rst:216
msgid ""
"Odoo Online SLA: `https://www.odoo.com/page/odoo-online-sla "
"<https://www.odoo.com/page/odoo-online-sla>`__\\"
msgstr ""
#: ../../getting_started/documentation.rst:217
msgid ""
"Odoo Online Security: `https://www.odoo.com/page/security "
"<https://www.odoo.com/fr_FR/page/security>`__"
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""
#: ../../getting_started/documentation.rst:220
msgid ""
"Privacy Policies: `https://www.odoo.com/page/odoo-privacy-policy "
"<https://www.odoo.com/page/odoo-privacy-policy>`__"
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""
#: ../../getting_started/documentation.rst:224
msgid "Support"
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr ""
#: ../../getting_started/documentation.rst:226
#: ../../getting_started/documentation.rst:225
msgid ""
"Your Odoo Online subscription includes an **unlimited support service at no "
"extra cost, 24/5, Monday to Friday**. To cover 24 hours, our teams are in "
"San Francisco, Belgium and India. Questions could be about anything and "
"everything from: how to use or configure, bugfix requests, payments or "
"subscription issues."
"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:232
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:231
msgid ""
"Our support can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
"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:235
#: ../../getting_started/documentation.rst:237
msgid ""
"Note: The support team cannot develop new features, customize, import data "
"or train your users. These services are provided by your dedicated project "
"manager, as part of the Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:240
msgid "Upgrades"
"**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:242
msgid ""
"Once every two months, Odoo releases a new version. You will get an upgrade "
"button within the **Manage Your Databases** screen. Upgrading your database "
"is at your own discretion, but allows you to benefit from new features."
"**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:247
#: ../../getting_started/documentation.rst:249
msgid ""
"We provide the option to upgrade in a test environment so that you can "
"evaluate a new version or train your team before the roll out. Simply fill "
"our `online support form <https://www.odoo.com/help>`__ to make this "
"request."
"**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:252
msgid "Success Pack Services"
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:254
#: ../../getting_started/documentation.rst:258
msgid ""
"The Success Pack is a package of premium hour-based services performed by a "
"dedicated project manager and business analyst. The list of services "
"according to your success pack is detailed online: `https://www.odoo.com"
"/pricing-packs <https://www.odoo.com/pricing-packs>`__"
"When your project is put in production, our support teams take care of your "
"questions or technical issues."
msgstr ""
#: ../../getting_started/documentation.rst:259
msgid ""
"The goal of the project manager is to help you get to production within the "
"defined time frame and budget, i.e. the initial number of hours defined in "
"your success pack."
msgstr ""
#: ../../getting_started/documentation.rst:263
msgid "His/her role includes:"
msgstr ""
#: ../../getting_started/documentation.rst:265
msgid ""
"**Project Management:** review of your objectives & expectations, phasing of"
" the implementation (road map), mapping of your business needs and the Odoo "
"features."
msgstr ""
#: ../../getting_started/documentation.rst:269
msgid "**Customized Support:** by phone, e-mail or webinar."
msgstr ""
#: ../../getting_started/documentation.rst:271
msgid ""
"**Training, Coaching, and Onsite Consulting:** remote trainings via screen "
"sharing or training on premises. For on premise training sessions, you will "
"be expected to pay extra for travel expenses and accommodations for your "
"consultant."
msgstr ""
#: ../../getting_started/documentation.rst:276
msgid ""
"**Configuration:** decisions about how to implement specific needs in Odoo "
"and advanced configuration. (e.g. logistic routes, advanced pricing "
"structures, etc.)"
msgstr ""
#: ../../getting_started/documentation.rst:280
msgid ""
"**Data Import**: we can do it or assist you on how to do it with a template "
"prepared by the project manager."
msgstr ""
#: ../../getting_started/documentation.rst:283
msgid ""
"If you have subscribed to **Studio**, you benefit from following extra "
"services:"
msgstr ""
#: ../../getting_started/documentation.rst:286
msgid ""
"**Customization of screens:** Studio takes the Drag and Drop approach to "
"customize most screens in any way you see fit."
msgstr ""
#: ../../getting_started/documentation.rst:289
msgid ""
"**Customization of reports (PDF):** Studio itself will not allow you to "
"customize the reports yourself, however our project managers have access to "
"developers for advanced customizations."
msgstr ""
#: ../../getting_started/documentation.rst:293
msgid ""
"**Website Design:** standard themes are provided to get started at no extra "
"cost. However, our project manager can coach you on how to utilize the "
"building blocks of the website designer. The time spent will consume hours "
"of your success pack."
msgstr ""
#: ../../getting_started/documentation.rst:298
msgid ""
"**Workflow automations:** e.g. setting values in fields based on triggers, "
"sending reminders by emails, automating actions, etc. For very advanced "
"automations, our project managers have access to Odoo developers."
msgstr ""
#: ../../getting_started/documentation.rst:303
msgid ""
"If any customization is needed, Odoo Studio App will be required. "
"Customizations made through Odoo Studio App will be maintained and upgraded "
"at each Odoo upgrade, at no extra cost."
msgstr ""
#: ../../getting_started/documentation.rst:307
msgid ""
"All time spent to perform these customizations by our Business Analysts will"
" be deducted from your Success Pack."
msgstr ""
#: ../../getting_started/documentation.rst:310
msgid ""
"In case of customizations that would require a developer’s intervention, a "
"recurring maintenance fee will be charged on the customer subscription, to "
"cover maintenance and upgrade services. This cost will be based on hours "
"spent by the developer: 4€ or $5/month, per hour of development will be "
"added to the subscription fee."
msgstr ""
#: ../../getting_started/documentation.rst:316
msgid ""
"**Example:** a customization that took 2 hours of development will cost: 2 "
"hours deducted from the Success Pack for the customization development 2 * "
"$5 = $10/month as recurring fee for the maintenance of this customization"
msgstr ""
#: ../../getting_started/documentation.rst:321
msgid "Implementation Methodology"
msgstr ""
#: ../../getting_started/documentation.rst:323
msgid ""
"We follow a **lean and hands-on methodology**, that is used to put customers"
" in production in a short period of time and at a low cost."
msgstr ""
#: ../../getting_started/documentation.rst:326
msgid ""
"After the kick-off meeting, we define a phasing plan to deploy Odoo "
"progressively, by groups of apps."
msgstr ""
#: ../../getting_started/documentation.rst:332
msgid ""
"The goal of the **Kick-off call** is for our project manager to come to an "
"understanding of your business in order to propose an implementation plan "
"(phasing). Each phase is the deployment of a set applications that you will "
"fully use in production at the end of the phase."
msgstr ""
#: ../../getting_started/documentation.rst:338
msgid "For every phase, the steps are the following:"
msgstr ""
#: ../../getting_started/documentation.rst:340
msgid ""
"**On Boarding:** Odoo's project manager will review Odoo's business flows "
"with you, according to your business. The goal is to train you, validate the"
" business process and configure according to your specific needs."
msgstr ""
#: ../../getting_started/documentation.rst:345
msgid ""
"**Data:** created manually or imported from your existing system. You are "
"responsible to export the data from your existing system and Odoo's project "
"manager will import them in Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:349
msgid ""
"**Training:** once your applications are set up, your data imported, and the"
" system is working smoothly, you will train your users. There will be some "
"back and forth with your Odoo project manager to answer questions and "
"process your feedback."
msgstr ""
#: ../../getting_started/documentation.rst:354
msgid "**Production**: Once everyone is trained, your users start using Odoo."
msgstr ""
#: ../../getting_started/documentation.rst:357
msgid ""
"Once you are comfortable using Odoo, we will fine-tune the process and "
"**automate** some tasks and do the remaining customizations (**extra screens"
" and reports**)."
msgstr ""
#: ../../getting_started/documentation.rst:361
msgid ""
"Once all applications are deployed and users are comfortable on Odoo, our "
"project manager will not work on your project anymore (unless you have new "
"needs) and you will use the support service if you have further questions."
msgstr ""
#: ../../getting_started/documentation.rst:367
msgid "Managing your databases"
msgstr ""
#: ../../getting_started/documentation.rst:369
msgid ""
"To access your databases, go to Odoo.com, sign in and click **My Databases**"
" in the drop-down menu at the top right corner."
msgstr ""
#: ../../getting_started/documentation.rst:375
msgid ""
"Odoo gives you the opportunity to test the system before going live or "
"before upgrading to a newer version. Do not mess up your working environment"
" with test data!"
msgstr ""
#: ../../getting_started/documentation.rst:379
msgid ""
"In that purpose, you can create as many free trials as you want (available "
"for 15 days). Those instances can be instant copies of your working "
"environment. To do so, go to the Odoo.com account in **My Organizations** "
"page and click **Duplicate**."
msgstr ""
#: ../../getting_started/documentation.rst:390
msgid ""
"You can find more information on how to manage your databases :ref:`here "
"<db_management/documentation>`."
msgstr ""
#: ../../getting_started/documentation.rst:394
msgid "Customer Success"
msgstr ""
#: ../../getting_started/documentation.rst:396
msgid ""
"Odoo is passionate about delighting our customers and ensuring that they "
"have all the resources needed to complete their project."
msgstr ""
#: ../../getting_started/documentation.rst:399
msgid ""
"During the implementation phase, your point of contact is the project "
"manager and eventually the support team."
msgstr ""
#: ../../getting_started/documentation.rst:402
msgid ""
"Once you are in production, you will probably have less interaction with "
"your project manager. At that time, we will assign a member of our Client "
"Success Team to you. They are specialized in the long-term relationship with"
" our customers. They will contact you to showcase new versions, improve the "
"way you work with Odoo, assess your new needs, etc..."
msgstr ""
#: ../../getting_started/documentation.rst:409
msgid ""
"Our internal goal is to keep customers for at least 10 years and offer them "
"a solution that grows with their needs!"
msgstr ""
#: ../../getting_started/documentation.rst:412
msgid "Welcome aboard and enjoy your Odoo experience!"
msgstr ""
#: ../../getting_started/documentation.rst:415
msgid ":doc:`../../db_management/documentation`"
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr ""
locale/ru/LC_MESSAGES/helpdesk.po
+875
View File
@@ -0,0 +1,875 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
# Sergey Vilizhanin, 2020
# Irina Fedulova <istartlin@gmail.com>, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../helpdesk.rst:5
msgid "Helpdesk"
msgstr "Техподдержка"
#: ../../helpdesk/advanced.rst:3
msgid "Advanced"
msgstr "Расширенный"
#: ../../helpdesk/advanced/after_sales.rst:3
msgid "After Sales Features"
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:5
msgid ""
"As your business grows, having the right tool to support your helpdesk team "
"on recording, tracking and managing issues raised easy and efficiently, is "
"key. Odoo’s Helpdesk application allows you to generate credit notes, manage"
" returns, products, repairs, grant coupons, and even plan onsite "
"interventions from a ticket’s page."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:11
msgid "Set up the after sales services"
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable the after sales options: *Refunds, Returns, Coupons, Repairs and "
"Onsite Interventions*."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:20
msgid "Generate credit notes from tickets"
msgstr "Создать сторно из заявки"
#: ../../helpdesk/advanced/after_sales.rst:22
msgid ""
"You can use a credit note to refund a customer or adjust the amount due. For"
" that, simply go to your ticket page, click on *Refund* and select the "
"corresponding *Invoice*. Clicking on *Reverse* generates a credit note, and "
"you can *Post* it while still being in the *Helpdesk* app."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:30
msgid "Allow product returns from tickets"
msgstr "Разрешить возврат товара по заявке"
#: ../../helpdesk/advanced/after_sales.rst:32
msgid ""
"The process of a product return from your customer back to your warehouse is"
" taken into action when, at the ticket page, you choose the option *Return*."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:39
msgid "Grant coupons from tickets"
msgstr "Предоставляйте купоны из заявок"
#: ../../helpdesk/advanced/after_sales.rst:41
msgid ""
"First, be sure to have your *Coupon Program* planned in the *Sales* or "
"*Website* application. Then, in *Helpdesk*, open your ticket, click on "
"*Coupon*, and choose the respective one."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:48
msgid "Repairs from tickets"
msgstr "Ремонт по заявке"
#: ../../helpdesk/advanced/after_sales.rst:50
msgid ""
"Clicking on *Repair* option, on your ticket page, a new repair order form is"
" shown. Fill in the information as needed and choose the next step."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:57
msgid "Plan onsite interventions from tickets"
msgstr "Планируйте вмешательства на месте из заявок"
#: ../../helpdesk/advanced/after_sales.rst:59
msgid ""
"At the ticket's page click on *Plan Intervention*, and set up your onsite "
"intervention exactly the same way as if you were on the *Field Service* "
"application."
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:67
msgid ":doc:`../../fsm/overview/invoicing_time`"
msgstr ""
#: ../../helpdesk/advanced/after_sales.rst:68
msgid ""
"`Coupons <https://www.odoo.com/slides/slide/coupon-"
"programs-640?fullscreen=1>`_"
msgstr ""
"`Купоны <https://www.odoo.com/slides/slide/coupon-programs-640?fullscreen=1>"
" `_"
#: ../../helpdesk/advanced/after_sales.rst:69
msgid ":doc:`../../manufacturing/repair/repair`"
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:3
msgid "Allow Customers to Close their Tickets"
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:5
msgid ""
"Allowing customers to close their tickets gives them autonomy and minimize "
"misunderstandings about when an issue is considered solved, or not. It makes"
" communication and actions more efficient."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:9
msgid "Configure the feature"
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:11
msgid ""
"To configure the feature go to :menuselection:`Helpdesk --> Settings --> "
"Helpdesk Teams --> Edit` and enable *Ticket closing*."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:18
msgid ""
"In order to designate to which stage the ticket migrates to once it is "
"closed, go to :menuselection:`Helpdesk --> Overview --> Tickets`."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:25
msgid ""
"You can either create a new Kanban stage or work with an existing one. For "
"both scenarios, go to :menuselection:`Helpdesk --> Settings --> Edit Stage` "
"and enable *Closing Stage*."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:32
msgid ""
"If a closing stage is not specified, by default, the ticket is moved to the "
"last stage; contrarily, if you have more than one stage set as closing, the "
"ticket is put in the first one."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:36
msgid "The Costumer Portal"
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:38
msgid ""
"Now, once the user logs into his Portal, the option *Close this ticket* is "
"available."
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:45
msgid "Get reports on tickets closed by costumers"
msgstr ""
#: ../../helpdesk/advanced/close_tickets.rst:47
msgid ""
"To do an analysis of the tickets that have been closed by costumers go to "
":menuselection:`Helpdesk --> Reporting --> Tickets --> Filters --> Add "
"Custom filter --> Closed by partner --> Applied`."
msgstr ""
#: ../../helpdesk/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../helpdesk/overview/forum_and_elearning.rst:3
msgid "Forum and eLearning"
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:6
msgid "Forum"
msgstr "Форум"
#: ../../helpdesk/overview/forum_and_elearning.rst:8
msgid ""
"To go above and beyond email, live chat, web forms, and phone lines, offer "
"your customers a support forum. This way, customers might become more "
"attached to your company as they would be investing time to get into details"
" of your business. You also encourage the exchange of experiences and "
"knowledge, supporting the feeling of belonging to a community (your "
"community!)."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:14
#: ../../helpdesk/overview/forum_and_elearning.rst:52
#: ../../helpdesk/overview/ratings.rst:10
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:11
msgid "Set up"
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:16
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Team` and "
"enable *Help Center*."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:23
msgid ""
"Create, or edit a forum by clicking on the external link. Among the editing "
"options, choose if you would like the *Forum Mode* to be *Questions*: only "
"one answer is allowed per question or *Discussions*: multiple answers are "
"allowed per question."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:31
msgid ""
"From now on, logged in users can start their discussions. To keep track of "
"posts, go to :menuselection:`Website --> Forum --> Posts`."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:38
msgid ""
"Turn tickets into forum posts by simply clicking on *Share on the Forum* on "
"the ticket's page."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:45
msgid "eLearning"
msgstr "Онлайн-обучение"
#: ../../helpdesk/overview/forum_and_elearning.rst:47
msgid ""
"In addition to a forum, offer online courses. When doing so, you link your "
"customers and users’ needs and questions to useful content, helping to boost"
" efficiency as they can also find their answers there."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:54
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable *eLearning*."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:61
msgid ""
"Once the structure and content of your course are ready, *Publish* it by "
"clicking on *Unpublished*."
msgstr ""
#: ../../helpdesk/overview/forum_and_elearning.rst:67
msgid ""
"To keep track of your course statistics, go to *eLearning* and *View "
"Course*."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:3
msgid "Getting Started"
msgstr "начните"
#: ../../helpdesk/overview/getting_started.rst:5
msgid ""
"Helpdesk teams provide your customers with support to queries or errors they"
" might encounter while using your product/service. Therefore, a successful "
"scheme where you can organize multiple teams with their customized pipeline,"
" visibilities settings, and ticket traceability is essential."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:10
msgid "Set up teams"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:12
msgid ""
"To modify or create teams, go to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:14
msgid ""
"Setting up multiple teams allows you to group tickets by your channels "
"(example: BE/US), or by your support services' types (example: IT, "
"accounting, admin, etc.)."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:21
msgid "Team’s productivity and visibility"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:23
msgid ""
"Teams can have individual *Assignment Methods* to ensure that tickets get "
"redirected to the right person:"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:26
msgid ""
"*Manually*: tickets are manually assigned, allowing employees to manage "
"their own workload and target tickets they are experts at;"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:28
msgid ""
"*Random*: tickets are randomly assigned and everyone gets the same amount. "
"This method ensures that all tickets are handled as the assignment happens "
"automatically;"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:30
msgid ""
"*Balanced*: tickets are assigned to the person with the least amount of "
"tickets so that everyone fairly gets the same amount. Thereby, you ensure "
"that all tickets get to be taken care of."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:40
msgid ""
"For the *Random* and *Balanced* assignment methods, you can set the *Team "
"Members* among whom tickets are assigned. Leave the field empty to include "
"all employees (with the proper access rights)."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:43
msgid ""
"The *Team Visibility* feature allows you to specify who can see and access "
"the team’s tickets. Therefore, ticket’s with sensible information are only "
"seen by the right people. Leave the field empty to include all employees "
"(with the proper access rights)."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:46
msgid "Set up stages and share it among teams"
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:48
msgid ""
"To set up stages, go to :menuselection:`Helpdesk --> Configuration --> "
"Stages`. Then, create and/or edit stages as you need and set specific teams "
"to use certain stages under *Team*."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:55
msgid ""
"Stages can be shared between one or multiple teams, allowing you to adapt "
"the pipeline to your individual needs. They also apply a visibility and "
"access rule, as other teams are not able to see or use the stage."
msgstr ""
#: ../../helpdesk/overview/getting_started.rst:64
msgid ":doc:`../../general/odoo_basics/add_user`"
msgstr ""
#: ../../helpdesk/overview/ratings.rst:3
msgid "Ratings"
msgstr "Рейтинги"
#: ../../helpdesk/overview/ratings.rst:5
msgid ""
"Allow customers to rate their experience with your helpdesk teams to "
"strengthen your credibility and gain their trust. Reviews can also influence"
" a customer’s decision and open space for feedback that can help you improve"
" the quality of your services."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:12
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable *Ratings on tickets*. The feature automatically adds a default email "
"template on the non-folded *closing stage(s)* of that team."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:21
msgid ""
"To edit the email template and the stage(s) set as the closing ones, go to "
"the Kanban view of your helpdesk team and click on *Settings*, then on *Edit"
" Stage*."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:28
msgid ""
"Now, once a ticket reaches the stage(s) designated as the *Closing Stage*, "
"an email is sent to the customer."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:35
msgid ""
"Ratings can be seen on the :doc:`chatter <../../project/tasks/collaborate>` "
"of each ticket, under the *See Customer Satisfaction* link on the main "
"dashboard, and through *Reporting*."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:39
msgid "Ratings visible on the customer portal"
msgstr ""
#: ../../helpdesk/overview/ratings.rst:41
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams` and "
"enable *Display Rating on Customer Portal*. Now, by clicking on the helpdesk"
" team’s name on their ticket, customers can see its ratings."
msgstr ""
#: ../../helpdesk/overview/ratings.rst:51
msgid ":doc:`../../portal/my_odoo_portal`"
msgstr ""
#: ../../helpdesk/overview/ratings.rst:52
#: ../../helpdesk/overview/receiving_tickets.rst:88
#: ../../helpdesk/overview/sla.rst:47
msgid ":doc:`../advanced/close_tickets`"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:3
msgid "Start Receiving Tickets"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:5
msgid ""
"Offering a variety of channels from where your customers can contact you "
"grants them flexibility and the right to choose the best one for themselves."
" And, in order to make sure inquiries across all channels get addressed, it "
"is essential to have a solution where all interactions come in one place."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:11
msgid "Channels options to submit tickets"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, and "
"enable the following features as you want them to be available to your "
"users."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:21
msgid "Email Alias"
msgstr "Псевдоним электронной почты"
#: ../../helpdesk/overview/receiving_tickets.rst:24
msgid ""
"Let your customers submit tickets by sending an email to your support email "
"address. The subject line of the email becomes the title of the ticket and "
"the content is shown in the Chatter."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:26
msgid ""
"Select *Configure domain name* to be redirected to *Settings* and, from "
"there, enable *External Email Servers* to determine or change your *Alias "
"Domain*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:35
msgid ""
"Using your own email server is required to send and receive emails in Odoo "
"Community and Enterprise. Online users benefit from a ready-to-use email "
"server."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:39
msgid "Website Form"
msgstr "Форма на веб-сайте"
#: ../../helpdesk/overview/receiving_tickets.rst:41
msgid ""
"Allow your customers to submit a ticket by filling in a form through your "
"website."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:42
msgid ""
"Once the feature is activated, get redirected to your website by clicking on"
" *Go to Website*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:49
msgid ""
"From the website page customize the form as you like. Then, publish it by "
"clicking on *Unpublished*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:56
msgid "Live Chat"
msgstr "Живой чат"
#: ../../helpdesk/overview/receiving_tickets.rst:59
msgid ""
"Through live interactions with your website visitors, helpdesk tickets can "
"be instantly created and redirected to the right person."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:61
msgid ""
"Click on your helpdesk team's name - for the example below: *Customer Care* "
"- and :doc:`set up your channel <../../livechat/overview/get_started>`."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:68
msgid ""
"Now, your operators can create tickets by using the :doc:`command "
"<../../livechat/overview/responses>` */helpdesk (subject_of_ticket)*."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:72
msgid "Prioritize tickets"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:74
msgid ""
"Use the stars to prioritize your tickets. The most urgent ones appear at the"
" top of your list on the Kanban view."
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:77
msgid "1 star = *Low priority*"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:78
msgid "2 stars = *High priority*"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:79
msgid "3 stars = *Urgent*"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:87
#: ../../helpdesk/overview/reports.rst:60
msgid ":doc:`sla`"
msgstr ""
#: ../../helpdesk/overview/receiving_tickets.rst:89
msgid ":doc:`../../discuss/advanced/email_servers`"
msgstr ""
#: ../../helpdesk/overview/reports.rst:3
msgid "Reports for a Better Support"
msgstr ""
#: ../../helpdesk/overview/reports.rst:5
msgid ""
"An efficient customer service solution should have a built-in reporting "
"option. Reports allow you to track trends, identify areas for improvement, "
"manage employees’ workloads and, most importantly, meet your customer’s "
"expectations."
msgstr ""
#: ../../helpdesk/overview/reports.rst:10
msgid "Cases"
msgstr ""
#: ../../helpdesk/overview/reports.rst:12
msgid "Some examples of the reports Odoo Helpdesk can generate include:"
msgstr ""
#: ../../helpdesk/overview/reports.rst:14
msgid "The number of tickets *grouped by* team and ticket type."
msgstr ""
#: ../../helpdesk/overview/reports.rst:17
msgid ""
"In this manner, you are able to evaluate which ticket types have been the "
"most frequent ones, plus the workload of your teams."
msgstr ""
#: ../../helpdesk/overview/reports.rst:19
msgid ""
"Apply *Time Ranges* if you would like to make comparisons to a *Previous "
"Period* or a *Previous Year*."
msgstr ""
#: ../../helpdesk/overview/reports.rst:25
msgid "The number of tickets closed per day, per team."
msgstr ""
#: ../../helpdesk/overview/reports.rst:27
msgid ""
"Get an overview of how many requests each team is closing per day in order "
"to measure their performance. Identify productivity levels to understand how"
" many requests they are able to handle."
msgstr ""
#: ../../helpdesk/overview/reports.rst:35
msgid ""
"Filter it by *Assignee* to see Key Performance Indicators (KPI) per agent."
msgstr ""
#: ../../helpdesk/overview/reports.rst:37
msgid ""
"The number of hours tickets are taking to be solved, grouped by team and "
"ticket type."
msgstr ""
#: ../../helpdesk/overview/reports.rst:39
msgid ""
"Check if your expectations are met by *measuring* the *Time to close "
"(hours)*. Your customers not only expect fast responses but they also want "
"their issues to be handled quickly."
msgstr ""
#: ../../helpdesk/overview/reports.rst:48
msgid "Save filters"
msgstr ""
#: ../../helpdesk/overview/reports.rst:50
msgid ""
"Save the filters you use the most and avoid having to reconstruct them every"
" time they are needed. To do so, set the groups, filters, and measures "
"needed. Then, go to *Favorites*."
msgstr ""
#: ../../helpdesk/overview/reports.rst:59
msgid ":doc:`receiving_tickets`"
msgstr ""
#: ../../helpdesk/overview/sla.rst:3
msgid "Service Level Agreements (SLA)"
msgstr ""
#: ../../helpdesk/overview/sla.rst:5
msgid ""
"Service Level Agreements (SLA) are commitments you make with your customers "
"to outline how a service is delivered. It bolsters trust between you and "
"your customers as it makes clear what needs to be done, to what standard, "
"and when."
msgstr ""
#: ../../helpdesk/overview/sla.rst:10
msgid "Create your policies"
msgstr ""
#: ../../helpdesk/overview/sla.rst:13
msgid ""
"First, enable the feature on the settings of the team you would like "
"policies to be applied, going to :menuselection:`Helpdesk --> Configuration "
"--> Helpdesk Teams`."
msgstr ""
#: ../../helpdesk/overview/sla.rst:15
msgid ""
"Create your policies through the team’s settings page or go to "
":menuselection:`Helpdesk --> Configuration --> SLA Policies`."
msgstr ""
#: ../../helpdesk/overview/sla.rst:23
msgid ""
"Choose to which **Team** the policy is relevant and the **Minimum Priority**"
" a ticket needs to have for the policy to be applied."
msgstr ""
#: ../../helpdesk/overview/sla.rst:27
msgid ""
"**Target** is the stage a ticket needs to reach within the period defined to"
" satisfy the SLA. The period is based on the ticket’s creation date, and a "
"deadline is set on the ticket’s form once it matches an SLA policy rule. If "
"a ticket has more than one policy applied to it, the closest deadline of all"
" SLAs is the one considered."
msgstr ""
#: ../../helpdesk/overview/sla.rst:29
msgid ""
"When a ticket has satisfied an SLA policy, the SLA tag appears in green and "
"the deadline field is not shown anymore."
msgstr ""
#: ../../helpdesk/overview/sla.rst:37
msgid "SLA Analysis"
msgstr ""
#: ../../helpdesk/overview/sla.rst:39
msgid ""
"Go to :menuselection:`Helpdesk --> Reporting --> SLA Status Analysis`. Apply"
" *Filters* and *Group by* to identify tickets that should be prioritized and"
" keep track of upcoming deadlines."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice.rst:3
msgid "Timesheet and Invoice"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:3
msgid "Invoice Time Spent on Tickets (Prepaid Support Services)"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:5
msgid ""
"Have the option to work with prepaid support services, meaning that a sales "
"order and a corresponding invoice are issued and, once the service is done, "
"you can deduct the time spent. Odoo allows it to happen because the "
"applications are fully integrated, resulting in faster responses to your "
"customer needs."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:14
msgid "Step 1: Set up a helpdesk team"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:17
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk Teams`, create"
" or edit an existing team, and enable *Timesheet on Ticket* and *Time "
"Reinvoicing*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:20
msgid ""
"Select or create a project under *Timesheet on Ticket*. The selected/created"
" is the one at which employees timesheet on by default. However, it can be "
"ultimately modified on each ticket."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:28
msgid "Step 2: Set up a service"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:31
msgid ""
"Go to :menuselection:`Sales --> Configuration --> Settings` and enable "
"*Units of Measure* to optionally be able to choose *hours* (for example) as "
"the unit of measure of your service."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:33
msgid ""
"Then, go to :menuselection:`Sales --> Products --> Products`, create or edit"
" an existing one, and set its *Product Type* as *Service*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:40
msgid ""
"Now, select the invoicing management you would like to have under the "
"*Sales* tab. We recommend the following configuration:"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:47
msgid ""
"This configuration ensures that the customer is invoiced by the number of "
"hours predicted in the sales order, meaning that less or extra hours "
"recorded are not taken into account. It also ensures that every time a sales"
" order is confirmed, a new task is created under the right project, "
"automating the process."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:53
msgid ""
"We recommend setting up a specific project, as it was done for this flow "
"example. The important thing to remember is that the sales order item needs "
"to be set on the corresponding project or task, in order to reinvoice the "
"time spent on a ticket."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:58
msgid "Prevision an invoice and record time"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:61
msgid "Step 1: Place an order"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:63
msgid ""
"Go to :menuselection:`Sales --> Orders --> Orders` and create one for the "
"helpdesk service product you have previously set up, with the customer who "
"needs the ticket to be opened. Set the number of hours needed to assist the "
"customer and *Confirm* the order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:72
msgid "Step 2: Invoice the customer"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:74
msgid "In *Sales*, select the respective sales order to *Create Invoice*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:82
msgid "Step 3: Link the task to the ticket"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:84
msgid ""
"Now, in *Helpdesk*, create or edit the respective ticket and link it to the "
"task created by the confirmation of the sales order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:92
msgid "Step 4: Record the time spent"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:94
msgid ""
"Still on the respective helpdesk ticket, record the hours performed under "
"the *Timesheets* tab."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:100
msgid ""
"Note that the hours recorded on the ticket form are shown on the *Delivered*"
" column in the sales order."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:108
msgid ""
"Hours recorded on the ticket are automatically shown in *Timesheets* and on "
"the dedicated task."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:111
msgid ":doc:`reinvoice_from_project`"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/invoice_time.rst:112
msgid ":doc:`../../inventory/management/products/uom`"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:3
msgid "Invoice Time Spent on Tickets (Postpaid Support Services)"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:5
msgid ""
"Directly pull the billable time you have tracked on your helpdesk tickets "
"into sales orders and invoices through a project task. It gives you more "
"control over what you charge your client, and it is more efficient."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:10
msgid "Configuration"
msgstr "Настройка"
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:13
msgid ""
"Go to :menuselection:`Helpdesk --> Configuration --> Helpdesk team --> Edit`"
" and enable the options *Timesheet on Ticket* and *Time Reinvoicing*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:15
msgid ""
"Under *Timesheet on Ticket*, choose the *Project* to which tickets (and "
"timesheets) will be linked by default. Open its *External link* to enable "
"the feature *Bill from tasks*."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:22
msgid "Create a sales order and an invoice"
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:24
msgid ""
"Now, once you have recorded the time you spent on the helpdesk ticket, under"
" the *Timesheets* tab, access the task clicking on its name."
msgstr ""
#: ../../helpdesk/timesheet_and_invoice/reinvoice_from_project.rst:31
msgid "*Create Sales Order* and proceed to create the invoice."
msgstr ""
locale/ru/LC_MESSAGES/index.po
+9 -5
View File
@@ -1,15 +1,19 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Vasiliy Korobatov <korobatov@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Vasiliy Korobatov <korobatov@gmail.com>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -19,4 +23,4 @@ msgstr ""
#: ../../index.rst:3
msgid "Odoo User Documentation"
msgstr ""
msgstr "Документация пользователя Odoo"
locale/ru/LC_MESSAGES/inventory.po
+4570 -5031
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/iot.po
+1041
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/livechat.po
+275
View File
@@ -0,0 +1,275 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../livechat/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""
#: ../../livechat/overview/get_started.rst:5
msgid ""
"Live Chat has the highest satisfaction rating of any communication tool. It "
"allows fast responses and it is accessible and convenient, as your customers"
" can keep doing what they are doing while interacting with you. Remember: "
"your customers want to talk to you, so let's make it easy."
msgstr ""
#: ../../livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""
#: ../../livechat/overview/get_started.rst:12
msgid ""
"Once *Live Chat* is installed on your database, if your website was created "
"with Odoo, the application is automatically added to it. All that is left to"
" do is to go to :menuselection:`Website --> Configuration --> Settings --> "
"Live Chat`."
msgstr ""
#: ../../livechat/overview/get_started.rst:21
msgid ""
"Select the channel to be linked to your website or create one on the fly."
msgstr ""
#: ../../livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""
#: ../../livechat/overview/get_started.rst:30
msgid ""
"- **Operators**: add agents to respond to the chat requests. Add as many as "
"you like, and keep in mind that operators that do not show any activity in "
"Odoo for more than 30min are considered disconnected."
msgstr ""
#: ../../livechat/overview/get_started.rst:33
msgid ""
"- **Options**: set the default text to be shown on the live chat button; an "
"automated welcome message to be seen by visitors when a conversation is "
"initiated, and the text that prompts the user to initiate a chat."
msgstr ""
#: ../../livechat/overview/get_started.rst:36
msgid ""
"- **Channel Rules**: choose an action for a given URL, and/or per country. "
"In the example below, the chat window automatically pops-up 3 seconds after "
"users (from any country) land on the contact us page."
msgstr ""
#: ../../livechat/overview/get_started.rst:43
msgid ""
"GeoIP, which refers to the process of finding a computer terminal’s "
"geographical location by its IP address, must be installed on your server. "
"Otherwise, under *Channel Rules*, countries are not taken into account."
msgstr ""
#: ../../livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""
#: ../../livechat/overview/get_started.rst:51
msgid ""
"If your website was not created with Odoo, you can find the code to be added"
" to your own, under the *Widget* tab."
msgstr ""
#: ../../livechat/overview/get_started.rst:52
msgid ""
"Odoo also offers an URL you can send to users so they can have access to a "
"single live chat page."
msgstr ""
#: ../../livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""
#: ../../livechat/overview/get_started.rst:61
msgid ""
"Conversations initiated by visitors pop up as a direct message, and are "
"shown in *Discuss*. Therefore, inquiries can be answered wherever you are in"
" Odoo."
msgstr ""
#: ../../livechat/overview/get_started.rst:69
msgid ""
"Conversations are dispatched based on the current workload of the online "
"operators."
msgstr ""
#: ../../livechat/overview/get_started.rst:72
msgid "Leave or join a channel"
msgstr ""
#: ../../livechat/overview/get_started.rst:74
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel under *Live Chat*, and *Join Channel* or *Leave Channel*."
msgstr ""
#: ../../livechat/overview/get_started.rst:82
#: ../../livechat/overview/responses.rst:48
msgid ":doc:`ratings`"
msgstr ""
#: ../../livechat/overview/get_started.rst:83
#: ../../livechat/overview/ratings.rst:45
msgid ":doc:`responses`"
msgstr ""
#: ../../livechat/overview/ratings.rst:3
msgid "Ratings"
msgstr "Рейтинги"
#: ../../livechat/overview/ratings.rst:5
msgid ""
"Giving users the opportunity to rate their interactions can help you "
"improving the experience you offer. That means staying on top of your "
"customers' needs, besides keeping track of your operators’ performances."
msgstr ""
#: ../../livechat/overview/ratings.rst:10
msgid "Customer Rating"
msgstr "Рейтинг клиентов"
#: ../../livechat/overview/ratings.rst:12
msgid ""
"Once the user chooses to close the chat window, he can rate his interaction."
msgstr ""
#: ../../livechat/overview/ratings.rst:14
msgid ""
"If the user is *Not satisfied* or *Highly dissatisfied*, a field allowing "
"for an explanation is shown."
msgstr ""
#: ../../livechat/overview/ratings.rst:15
msgid "A copy of the conversation can also be sent by email."
msgstr ""
#: ../../livechat/overview/ratings.rst:22
msgid "The rating is shown on the chat window itself for the operator."
msgstr ""
#: ../../livechat/overview/ratings.rst:28
msgid "And under :menuselection:`Report --> Customer Ratings`."
msgstr ""
#: ../../livechat/overview/ratings.rst:35
msgid "Make the rating public"
msgstr ""
#: ../../livechat/overview/ratings.rst:37
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings`, access your "
"channel form, click on *Go to Website* and on *Unpublished*, to publish the "
"rating of that channel on your website."
msgstr ""
#: ../../livechat/overview/responses.rst:3
msgid "Commands and Canned Responses"
msgstr ""
#: ../../livechat/overview/responses.rst:5
msgid ""
"Using canned responses can help you save time and have a previous, well-"
"thought response, to some of your most common questions and comments."
msgstr ""
#: ../../livechat/overview/responses.rst:9
msgid "Use commands"
msgstr "используйте команды"
#: ../../livechat/overview/responses.rst:11
msgid ""
"Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
#: ../../livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""
#: ../../livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""
#: ../../livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""
#: ../../livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../livechat/overview/responses.rst:0
msgid ""
"- For *helpdesk tickets*: make sure the application is installed on your "
"database and the option *Live Chat* under :menuselection:`Helpdesk --> "
"Configuration --> Helpdesk Teams` is enabled."
msgstr ""
#: ../../livechat/overview/responses.rst:0
msgid ""
"- For *leads*: the *CRM* application must be installed on your database."
msgstr ""
#: ../../livechat/overview/responses.rst:26
msgid ""
"To access the ticket or lead created from the chat, click on the shortcut "
"link."
msgstr ""
#: ../../livechat/overview/responses.rst:33
msgid ""
"Helpdesk tickets created from the chat automatically add the conversation as"
" a description of the ticket. The same goes for the creation of a lead."
msgstr ""
#: ../../livechat/overview/responses.rst:37
msgid "Send canned responses"
msgstr "Присылайте фиксированные ответы"
#: ../../livechat/overview/responses.rst:40
msgid ""
"Canned responses allow you to have a full piece of text being placed when "
"you type a shortcut word. To create them, go to :menuselection:`Live Chat "
"--> Configuration --> Canned Responses`."
msgstr ""
#: ../../livechat/overview/responses.rst:41
msgid ""
"To use them during a conversation, simply type **:** followed by the "
"shortcut word you created."
msgstr ""
locale/ru/LC_MESSAGES/manufacturing.po
+1123 -482
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/marketing_automation.po
+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.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../marketing_automation.rst:5
msgid "Marketing Automation"
msgstr "Marketing Automation"
#: ../../marketing_automation/advanced.rst:3
msgid "Advanced"
msgstr "Расширенный"
#: ../../marketing_automation/advanced/understanding_metrics.rst:3
msgid "Understanding Metrics"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:4
msgid ""
"Metrics are values that help you measure progress and can be a powerful way "
"of linking your employees to goals."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:9
msgid ""
"When you create a workflow in Odoo, its visual content already shows metrics"
" in a graph form and in numbers."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:10
msgid "Let’s consider the example below:"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:19
msgid ""
"The *Target* - business object - is *Lead/Opportunity* and was narrowed down"
" to the ones whose *Tag Name* contain the description “Product”, and have an"
" email address set."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:20
msgid "A total number of 20 records match the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:28
msgid ""
"Out of those 20 records, 25 have become participants, in other words, they "
"have matched the criteria."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:36
msgid ""
"Every time the system runs, updating numbers and triggering actions, it will"
" look at the *Target* model and check if new records have been added or "
"modified, keeping the flow up-to-date."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:41
msgid ""
"The filter here is applied to *all* activities. Leads that lose the tag in "
"the meantime will be excluded from later activities."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:45
msgid ""
"*Records* is a real-time number, therefore while the workflow is running, "
"changes in opportunity records can be made - delete, add, adjustment - "
"updating the number of records, but not changing the number of participants,"
" as the metric *will not* exclude opportunities that have been set as "
"participants before. It will just add new ones. For this reason, the number "
"of *Records* can be different from the number of *Participants*."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
msgid ""
"You can also have filters applied to activities individually, under "
"*Domain*. A useful feature to specify an individual filter that will only be"
" performed if the records satisfied both filters, the activity and its "
"domain one."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:0
msgid ""
"Example: for an activity sending an SMS, you could make sure a phone number "
"is set to avoid triggering a SMS that would never be sent and crash."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:64
msgid ""
"*Success* is the number of times the searching for participants - that match"
" the filter(s) of that activity - was performed successfully in relation to "
"the total number of participants."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:65
msgid ""
"If a participant does not match the conditions, it will be added to "
"*Rejected*."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:71
msgid ""
"Hovering over the graph, you can see the number of successful and rejected "
"participants, per day, for the last 15 days."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:75
msgid ""
"Every time a new record is added to the *Target* model, it will be "
"automatically added to the workflow, and, it will start the workflow from "
"the beginning (parent action)."
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:79
msgid ":doc:`../overview/automate_actions`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:80
msgid ":doc:`../overview/segment`"
msgstr ""
#: ../../marketing_automation/advanced/understanding_metrics.rst:81
msgid ":doc:`../overview/test`"
msgstr ""
#: ../../marketing_automation/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../marketing_automation/overview/automate_actions.rst:3
msgid "Automate Actions and Create a Workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:4
msgid ""
"Automated workflows are a sign that you are building intelligent, data-"
"driven, multifaceted campaigns to enable the delivery of the right message, "
"to the right prospects, at the right time. It also speeds up processes and "
"creates a seamless experience for employees."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:9
msgid "Segment and create a campaign"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:10
msgid "Go to :menuselection:`Campaigns --> Create`."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:12
msgid ""
"In the example below, the *Marketing Automation* application is fully "
"integrated with *Contacts*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:14
msgid ""
"But it can also be integrated with other apps like CRM, as long as they are "
"installed in your database."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:23
msgid ""
"Depending on the criteria, the *target model updates itself* while the "
"campaign is running. That means that every new record that meets the "
"criteria will be added to the workflow."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:25
msgid ""
"Example: a campaign starts for leads that have no salesman assigned. If at "
"some point, those leads get to have a salesman assigned to it, the campaign "
"will stop running."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:29
msgid "Create a parent activity and start to build a workflow"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:30
msgid "Click on *Add new activity*."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:37
msgid ""
"*Trigger* is the field to set for the activity to start to de deployed."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:39
msgid ""
"Adopt an *Expiry Duration* if you would like to stop actions from being "
"executed after a certain amount of time and in subsequence to the trigger."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:42
msgid ""
"Under *Domain* you can narrow down your target, even more, applying filters "
"for this specific activity."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:47
msgid "Add Child Activities"
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:48
msgid ""
"A *child activity* is an action that will take place based on a condition."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:50
msgid ""
"You can either create or add a child activity if on the previous one: the "
"email was opened or not, the email was replied or not, the link was clicked "
"or not, the email bounced back."
msgstr ""
#: ../../marketing_automation/overview/automate_actions.rst:59
#: ../../marketing_automation/overview/test.rst:53
msgid ":doc:`segment`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:3
msgid "Segment the Database with Filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:4
msgid "Filters let you reach a granular level of detail in your records."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:7
msgid "How to work with filters"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:8
msgid ""
"When working with filters, you will see that some of the rules have an arrow"
" button next to it, informing you that the parameter has more variables "
"within it."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:18
msgid ""
"More than one parameter line - *node* (+) - can be added under what is "
"called a *branch* (...)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:19
msgid "To exclude a *node* or a *branch*, click on *Delete node* (x)."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:27
msgid ""
"Every time a new branch is created, you can choose if you would like the "
"records to match *all* criteria of the upcoming rules, or *any*, meaning one"
" rule or the other."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:32
msgid "Use cases"
msgstr "Используйте различные варианты"
#: ../../marketing_automation/overview/segment.rst:34
msgid ""
"**Scenario**: narrow the target down to new opportunities in the pipeline."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:39
msgid "**Scenario**: narrow the target down to suppliers."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:44
msgid ""
"**Scenario**: narrow the leads down to the ones that contain a certain tag "
"name."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:49
msgid ""
"**Scenario**: narrow the target down to the attendees of a specific event "
"that purchase a specific category of ticket."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:55
msgid "**Scenario**: narrow the target down to the employees who have kids."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:60
msgid ""
"**Scenario**: narrow the target down to records with a helpdesk ticket "
"solved."
msgstr ""
#: ../../marketing_automation/overview/segment.rst:66
#: ../../marketing_automation/overview/test.rst:52
msgid ":doc:`automate_actions`"
msgstr ""
#: ../../marketing_automation/overview/segment.rst:67
msgid ":doc:`../../general/tags/take_tags`"
msgstr ""
#: ../../marketing_automation/overview/test.rst:3
msgid "Launch a Test and Start a Campaign"
msgstr ""
#: ../../marketing_automation/overview/test.rst:4
msgid ""
"Before starting a campaign, launching a test allows you to run the workflow "
"on a test contact and view the sequence of events in action, avoiding "
"mistakes."
msgstr ""
#: ../../marketing_automation/overview/test.rst:8
msgid "Launch a test"
msgstr "Launch a test"
#: ../../marketing_automation/overview/test.rst:9
msgid "Click on *Launch a test*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:12
msgid ""
"Once you have selected the test contact, *Run* the parent activity and the "
"subsequent ones as needed. *Run* and *Stop* activities individually. To stop"
" the whole workflow click on *Stop*."
msgstr ""
#: ../../marketing_automation/overview/test.rst:22
msgid ""
"Launching a test does not add data to your metrics with the purpose of not "
"introducing wrong inputs to reports."
msgstr ""
#: ../../marketing_automation/overview/test.rst:27
msgid "Start and stop a workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:28
msgid ""
"Click on *Start* to run the workflow, and on *Stop* to interrupt it. The "
"interruption and new start can happen at any moment. The current status will"
" be shown on the status bar."
msgstr ""
#: ../../marketing_automation/overview/test.rst:38
msgid "Participants and their specific workflow"
msgstr ""
#: ../../marketing_automation/overview/test.rst:39
msgid ""
"*Participants* are all the records that have ever been involved in the "
"campaign."
msgstr ""
#: ../../marketing_automation/overview/test.rst:47
msgid ""
"If you click on *Participants* and open a record, you will find the specific"
" activities the record went/are/will go through, as well as when the "
"workflow was triggered to him. If you wish to cancel an activity click on "
"*Cancel*."
msgstr ""
locale/ru/LC_MESSAGES/mobile.po
+45
View File
@@ -0,0 +1,45 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Ivan Yelizariev <yelizariev@it-projects.info>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../mobile/firebase.rst:5
msgid "Mobile"
msgstr "Мобильный"
#: ../../mobile/firebase.rst:8
msgid "Push Notifications"
msgstr "Push-уведомления"
#: ../../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 ""
"Для Odoo 12.0, 13.0 или более поздней версии больше нет сложной "
"конфигурации, чтобы включить push-уведомления в мобильном приложении."
#: ../../mobile/firebase.rst:13
msgid ""
"Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud "
"Notification (OCN)` and make sure that **Push Notifications** is checked."
msgstr ""
locale/ru/LC_MESSAGES/planning.po
+157
View File
@@ -0,0 +1,157 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../planning.rst:5
msgid "Planning"
msgstr "Планирование"
#: ../../planning/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../planning/overview/duplicate_a_planning.rst:3
msgid "Create a Schedule and Make Encoding Easier"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:5
msgid ""
"Organize regular schedules or forecast projects in a long term basis. Create"
" shifts to manage your tasks, assign employees, and stay organized at a high"
" level."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:9
msgid "Organize your team by roles"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:11
msgid ""
"Go to :menuselection:`Configuration --> Roles --> Create`. Optionally, go to"
" the *Employees* application, select the respective employee, and under "
"*Work Information* select the *Default Planning Role*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:20
msgid "Make shifts recurrent"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:22
msgid ""
"While creating a shift, select *Repeat* and configure as needed, saving you "
"from the need of re-planning it."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:30
msgid ""
"Repeated shifts are generated for the next six months. A modification is "
"possible in :doc:`Developer mode <../../general/developer_mode/activate>`, "
"from *Settings*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:38
msgid "To duplicate a shift in the Gantt view, press CTRL + drag and drop."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:41
msgid "Save shifts as templates"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:43
msgid ""
"If creating a shift on the fly and know you might use that template in the "
"future, click on *Save as a Template*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:51
msgid ""
"To create a template in advance, go to :menuselection:`Configuration --> "
"Shifts Templates --> Create`."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:55
msgid "Duplicate a planning from the previous week"
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:57
msgid ""
"When in the Gantt view, either under *Schedule by Employee, Role or "
"Project*, instead of re-planning shifts that have been planned before, "
"simply click on *Copy Previous Week*."
msgstr ""
#: ../../planning/overview/duplicate_a_planning.rst:65
msgid ""
"The integration with the *Time off* and *Employee* applications, show you "
"grayed cells to the days when the employee does not work and is on vacation "
"time, for example."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:3
msgid "Send Planned Shifts and Give Employees Autonomy Over Shifts"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:5
msgid ""
"If you are not on top of your tasks and shifts you might fall behind, losing"
" productivity. Allowing your employees to have a say over shifts helps you "
"to be on top of your workload, and gives them flexibility."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:10
msgid "Publish and send the planned week by email"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:12
msgid ""
"Once you have your shifts planned, click on *Send Schedule*. Select *Include"
" Open shift* if you would like the *Unassigned* shifts to be seen."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:19
msgid ""
"Choose if you just want to *Publish* or *Publish and Send*. If you *Publish "
"and Send*, employees get an email that redirects them to their planned "
"tasks:"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:26
msgid ""
"Employees will not be able to see shifts until they have been published."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:29
msgid "Let employees unassign themselves from shifts"
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:31
msgid ""
"Go to *Configuration* and enable *Allow Unassignment*. From now on, when an "
"employee opens his tasks, he can indicate his unavailability clicking on *I "
"am unavailable*. The shift will be opened again, allowing someone else to "
"take it."
msgstr ""
#: ../../planning/overview/send_planned_shifts.rst:44
msgid "Employees have portal access; users have access to the database."
msgstr ""
locale/ru/LC_MESSAGES/point_of_sale.po
+1356 -2500
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/portal.po
+213
View File
@@ -0,0 +1,213 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
# Константин Коровин <korovin74@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Константин Коровин <korovin74@gmail.com>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../portal/my_odoo_portal.rst:6
msgid "My Odoo Portal"
msgstr "Мой портал Odoo"
#: ../../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 ""
"В этой секции портала вы найдете всю коммуникацию между вами и Odoo: "
"документы, такие как коммерческие предложения, заказы на продажу, счета и "
"подписки."
#: ../../portal/my_odoo_portal.rst:12
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 ""
"Здесь вы найдете все коммерческие предложения, направленные Odoo. Например, "
"коммерческое предложение может быть создана для вас после добавления заявки "
"или пользователя в вашу базу данных или когда ваш контракт нужно обновить."
#: ../../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 ""
"Колонка * Действительно до * показывает дату, до которой действует "
"коммерческое предложение; после этой даты коммерческое предложение будет "
"&quot;просроченные&quot;. Нажав на коммерческое предложение, вы увидите все "
"детали предложения, такие как цена и другая полезная информация."
#: ../../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 ""
"Если вы хотите принять коммерческое предложение, просто нажмите "
"&quot;Принять и Оплатить,&quot; и коммерческое предложение будет "
"подтверждена. Если вы не хотите подтверждать ее или вы хотите попросить о "
"некоторых изменениях, нажмите &quot;Попросить об отклонении изменений.&quot;"
#: ../../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 ""
"Все ваши покупки внутри Odoo (к продаже, Темы, Модули и т.д.) будут "
"зарегистрированы в этой секцией."
#: ../../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 ""
"Просто нажмите на счет, если вы хотите увидеть больше информации, оплатить "
"счет или скачать PDF-версию документа."
#: ../../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 ""
"Когда вы отправляете заявку через `Поддержку Odoo "
"<https://www.odoo.com/help> `, Будет создан заявку. Здесь вы можете найти "
"все заявки, которые вы открыли, разговор между вами и нашими агентами, "
"статусы и ID (# Ref) заявок."
#: ../../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 ""
"Вы можете получить доступ к вашим подписок через Odoo из этого раздела. "
"Первая страница показывает вам подписки, которые у вас есть, и их статус."
#: ../../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 ""
"Чтобы изменить способ оплаты, нажмите на &quot;Изменить способ оплаты&quot; "
"и введите новые данные кредитной карты."
#: ../../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 ""
"Если вы хотите удалить сохраненные кредитные карты, вы можете сделать это, "
"нажав на &quot;Управление вашими методами платежа&quot; внизу страницы. "
"Нажмите &quot;Удалить&quot;, чтобы удалить метод платежа."
#: ../../portal/my_odoo_portal.rst:102
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 ""
"Если вам нужна информация о том, как управлять своей базой данных, смотрите:"
" ref: `db_online`"
locale/ru/LC_MESSAGES/practical.po
+9 -5
View File
@@ -1,15 +1,19 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo Business package.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Vasiliy Korobatov <korobatov@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo Business 10.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-06-07 09:30+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Vasiliy Korobatov <korobatov@gmail.com>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -19,4 +23,4 @@ msgstr ""
#: ../../practical.rst:3
msgid "Practical Information"
msgstr ""
msgstr "Практическая информация"
locale/ru/LC_MESSAGES/project.po
+803 -1398
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/purchase.po
+1211 -1997
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/quality.po
+466
View File
@@ -0,0 +1,466 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Ivan Yelizariev <yelizariev@it-projects.info>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../quality.rst:5
msgid "Quality"
msgstr "Качество"
#: ../../quality/alert.rst:3
msgid "Alert"
msgstr "Предупреждение"
#: ../../quality/alert/alert_mo.rst:3
msgid "Generate a Quality Alert from a Manufacturing Order"
msgstr ""
#: ../../quality/alert/alert_mo.rst:5
msgid ""
"Speaking of manufacturing orders, you have two different situations to "
"consider in Odoo. Those two will result in two different processes:"
msgstr ""
#: ../../quality/alert/alert_mo.rst:8
msgid "You work with a simple manufacturing flow;"
msgstr ""
#: ../../quality/alert/alert_mo.rst:10
msgid "You work with a complex manufacturing flow that includes routings."
msgstr ""
#: ../../quality/alert/alert_mo.rst:13
msgid "Simple manufacturing flow"
msgstr ""
#: ../../quality/alert/alert_mo.rst:15
msgid ""
"If you work with simple manufacturing orders, the *Quality Alerts* will be "
"launched from the manufacturing order itself. When manufacturing a product "
"for which you need to process quality controls, a button *Quality Alert* "
"will appear on the top of your manufacturing order."
msgstr ""
#: ../../quality/alert/alert_mo.rst:23
msgid ""
"By clicking on the button, you can specify the quality problem that arose "
"during the process."
msgstr ""
#: ../../quality/alert/alert_mo.rst:29
msgid ""
"If one of the quality checks failed, the button will be highlighted on the "
"document. If not, the button won’t be highlighted."
msgstr ""
#: ../../quality/alert/alert_mo.rst:36 ../../quality/checks/quality_mo.rst:50
msgid "Manufacturing Flow with Routings"
msgstr ""
#: ../../quality/alert/alert_mo.rst:38
msgid ""
"If you work with routings defined on your manufacturing orders, the quality "
"alerts will be launched directly from the work orders on which the quality "
"checks took place."
msgstr ""
#: ../../quality/alert/alert_mo.rst:48
msgid ""
"Then, a button *Quality Alert* will be available from the work order view. "
"When you click on the button, you can specify the quality problem that "
"appeared during the process."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:3
msgid "Generate a Quality Alert from a Transfer"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:6
msgid "Use the Quality Alert"
msgstr ""
#: ../../quality/alert/alert_transfer.rst:8
msgid ""
"Every time you perform some *Quality Checks* on a transfer, a *Quality "
"Alert* button appears. You can always use it. The button is automatically "
"highlighted once you have a failed quality check for the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:16
msgid ""
"If you click on that *Quality Alert* button, you can specify what was the "
"problem with the product."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:22
msgid ""
"The *Quality Alert* that is created from the transfer can be found via the "
"button appearing on the top right corner of the transfer."
msgstr ""
#: ../../quality/alert/alert_transfer.rst:28
msgid ""
"You can also access all your *Quality Alerts* via the menu, accessible under"
" *Control*."
msgstr ""
#: ../../quality/checks.rst:3
msgid "Checks"
msgstr "Проверки"
#: ../../quality/checks/quality_mo.rst:3
msgid "Perform Quality Checks on Manufacturing Orders"
msgstr ""
#: ../../quality/checks/quality_mo.rst:5
msgid ""
"There are two different situations to consider and that will differ in Odoo "
"processes:"
msgstr ""
#: ../../quality/checks/quality_mo.rst:8
msgid "You work with simple manufacturing flows;"
msgstr ""
#: ../../quality/checks/quality_mo.rst:10
msgid ""
"You work with complex manufacturing flows that are represented by the use of"
" routings in Odoo."
msgstr ""
#: ../../quality/checks/quality_mo.rst:13
msgid "Simple Manufacturing Flow"
msgstr ""
#: ../../quality/checks/quality_mo.rst:16
#: ../../quality/checks/quality_mo.rst:53
#: ../../quality/checks/quality_transfers.rst:6
msgid "Create the Quality Control Point"
msgstr ""
#: ../../quality/checks/quality_mo.rst:18
msgid ""
"To create a quality control point, open the quality app and go to "
":menuselection:`Control --> Control Points`. There, hit create. Make sure to"
" select *Manufacturing* as operation and choose the type of quality check "
"you want to perform."
msgstr ""
#: ../../quality/checks/quality_mo.rst:27
#: ../../quality/checks/quality_mo.rst:69
#: ../../quality/checks/quality_transfers.rst:17
msgid "Process the Quality Check"
msgstr ""
#: ../../quality/checks/quality_mo.rst:29
msgid ""
"Once your *Quality Control Point* has been created, you can create a "
"manufacturing order for your product. Now, and before marking the "
"manufacturing as done, you can register the *Quality Checks*."
msgstr ""
#: ../../quality/checks/quality_mo.rst:39
msgid ""
"Once you have performed your quality checks, you can find them via the "
"*Quality Checks* button available on the manufacturing order form."
msgstr ""
#: ../../quality/checks/quality_mo.rst:46
msgid ""
"If you want to access all your quality checks, you can do this by opening "
"the quality checks menu, under quality control."
msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid ""
"If you want to create a *Quality Control Point*, open the *Quality* app and "
"go to :menuselection:`Control --> Control Points`. Then, click on create. "
"Make sure to select *Manufacturing* as operation and select the work order "
"operation on which the quality check should be performed."
msgstr ""
#: ../../quality/checks/quality_mo.rst:64
msgid ""
"Choosing the work order operation is necessary if you want the quality "
"checks to be performed in the work orders. After that, you can choose the "
"type of quality check."
msgstr ""
#: ../../quality/checks/quality_mo.rst:71
msgid ""
"Once your *Quality Control Point* has been configured, create a "
"manufacturing order for your product. You have to plan it if you want to "
"generate the necessary work orders."
msgstr ""
#: ../../quality/checks/quality_mo.rst:78
msgid ""
"Now, process the work order and your quality check will appear. In this "
"example, the quality check requests to enter the serial number of the Table "
"Top component."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:3
msgid "Perform Quality Checks on Transfers"
msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid ""
"To create a *Quality Control Point*, open the *Quality* application. Then, "
"go to :menuselection:`Quality Control --> Control Points --> Create`. Now, "
"you can define the quality control point you want to apply to a specific "
"product. Don’t forget to select a transfer operation type."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:19
msgid ""
"Let’s say that we will receive a laptop. First, create a planned receipt for"
" the product. Then, on the receipt, you will see a *Quality Checks* button "
"that appears to proceed to the quality check you configured before."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:27
msgid ""
"By clicking on it, the instruction set on the quality control point will be "
"displayed and will require the check value."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:33
msgid ""
"Once the quality check is done, you can find it linked to the corresponding "
"transfer and access it by clicking on the button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:39
msgid ""
"But, if the quality check failed, the stat button will appear in red "
"(instead of green) and Odoo will suggest you to create a *Quality Alert* by "
"highlighting the corresponding button."
msgstr ""
#: ../../quality/checks/quality_transfers.rst:46
msgid ""
"The quality checks can also be found in the *Quality* application by opening"
" the *Quality Checks* menu, under *Quality Control*."
msgstr ""
#: ../../quality/control.rst:3
msgid "Control"
msgstr "Контроль"
#: ../../quality/control/control_points.rst:3
msgid "Define Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:5
msgid ""
"Quality is an important factor when it comes to products or services. "
"Nowadays, quality has become the differentiating factor for all goods and "
"services. It is vital for businesses to deliver products that meet or exceed"
" expectations. It also helps minimize waste."
msgstr ""
#: ../../quality/control/control_points.rst:10
msgid ""
"That is why most manufacturers would not think of eliminating the quality "
"control from their manufacturing process. After all, removing quality "
"controls would dramatically increase the number of defective products that "
"the company then has to rework or scrap."
msgstr ""
#: ../../quality/control/control_points.rst:15
msgid ""
"Then, using business applications to ensure data quality is important. With "
"Odoo insuring the rear, any major problem can be avoided before occurring!"
msgstr ""
#: ../../quality/control/control_points.rst:20
msgid "Quality Control Points"
msgstr "Контрольные точки качества"
#: ../../quality/control/control_points.rst:22
msgid ""
"To create a *Quality Control Point*, go to :menuselection:`Quality --> "
"Quality Control --> Control Points`. Once there, define the product on which"
" the quality control point should take place. The operation at which it "
"takes place also is to be defined here."
msgstr ""
#: ../../quality/control/control_points.rst:27
msgid ""
"The *Quality Control Points* take place during transfers or during the "
"manufacturing process of the products. If working with routings on *Bill of "
"Materials*, you have to precise at which step of the manufacturing process "
"the quality control point needs to be applied."
msgstr ""
#: ../../quality/control/control_points.rst:32
msgid ""
"The *Control Type* defines at which frequency the quality checks should take"
" place:"
msgstr ""
#: ../../quality/control/control_points.rst:35
msgid ""
"**All operations**: all the operations automatically generate quality checks"
" to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid ""
"**Randomly**: the quality checks only perform on x% of the operation. The "
"percentage needs to be defined on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:41
msgid ""
"**Periodically**: the quality checks are performed periodically. The "
"periodicity is based on the defined period (once a day, once a week)."
msgstr ""
#: ../../quality/control/control_points.rst:50
msgid "Quality Control Point Types"
msgstr ""
#: ../../quality/control/control_points.rst:52
msgid ""
"Now, one thing remains to be configured: the type of quality check. There "
"are several types that can be used: text, take a picture, pass-fail, take a "
"measure, register consumed material, register by-product, and print label."
msgstr ""
#: ../../quality/control/control_points.rst:58
msgid ""
"Some types are available only with the manufacturing application installed."
msgstr ""
#: ../../quality/control/control_points.rst:62
msgid "Text"
msgstr "Текст"
#: ../../quality/control/control_points.rst:64
msgid ""
"This control point type allows giving instructions to workers during the "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:80
msgid "Take a Picture"
msgstr "сделать изображение"
#: ../../quality/control/control_points.rst:82
msgid ""
"This control point type asks to take a picture of the product applied in a "
"transfer or when manufacturing it."
msgstr ""
#: ../../quality/control/control_points.rst:98
msgid ""
"This process can be simplified by using a connected :doc:`camera "
"<../../iot/devices/measurement_tool>`."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:104
msgid ""
"*Pass-Fail* requires to specify if the products pass or fail specific "
"criteria. It can be applied for both transfers or manufacturing orders."
msgstr ""
#: ../../quality/control/control_points.rst:111
msgid ""
"For this kind of type, there is the possibility to define a failure message "
"giving instructions to follow in case of failure."
msgstr ""
#: ../../quality/control/control_points.rst:127
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:129
msgid ""
"Taking measures requires to enter the product’s measurements during a "
"transfer or during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:132
msgid ""
"To use it, it necessary to specify the norm for your product’s measurements,"
" but also a tolerance threshold. Doing so, all the products with good "
"measures can are automatically accepted."
msgstr ""
#: ../../quality/control/control_points.rst:140
msgid ""
"As for *Pass-Fail*, this type allows defining a failure message that gives "
"instructions to the worker."
msgstr ""
#: ../../quality/control/control_points.rst:156
msgid ""
"This process can be simplified by using connected :doc:`measurement tools "
"<../../iot/devices/camera>`."
msgstr ""
#: ../../quality/control/control_points.rst:159
msgid "Register Consumed Materials"
msgstr ""
#: ../../quality/control/control_points.rst:161
msgid ""
"When using *Register Consumed Materials*, it is required to register the "
"component’s serial/lot numbers during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:165
#: ../../quality/control/control_points.rst:182
msgid "This type is only available when working with routings."
msgstr ""
#: ../../quality/control/control_points.rst:176
msgid "Register By-Products"
msgstr ""
#: ../../quality/control/control_points.rst:178
msgid ""
"With *Register By-Products*, it is required to register the serial/lot "
"number of the by-products that are manufactured."
msgstr ""
#: ../../quality/control/control_points.rst:193
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:195
msgid ""
"*Print Label*, as its name points out, allows printing labels to add to the "
"product during the manufacturing process."
msgstr ""
#: ../../quality/control/control_points.rst:207
msgid ""
"This process can be simplified by using a connected :doc:`printer "
"<../../iot/devices/printer>`."
msgstr ""
locale/ru/LC_MESSAGES/sales.po
+2413 -1180
View File
File diff suppressed because it is too large Load Diff
locale/ru/LC_MESSAGES/sms_marketing.po
+563
View File
@@ -0,0 +1,563 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Андрей Гусев <gaussgss@gmail.com>, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
# Sergey Vilizhanin, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../sms_marketing.rst:5
msgid "SMS Marketing"
msgstr "SMS-маркетинг"
#: ../../sms_marketing/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:3
msgid "Contact Lists and Blacklist"
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:5
msgid ""
"Creating your own list of contacts, or importing it, is useful when you want"
" to create specific groups of people, such as the subscribers of your "
"newsletter. It is also the best way to get started if you are coming from "
"another system and already have built an audience. It makes the SMS "
"distribution easier."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11
msgid "Contact lists"
msgstr "Список контактов"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:13
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16
msgid ""
"Choose a name for your *Mailing list*, and activate the option *Is Public* "
"if you would like to make the mailing list accessible to your recipients in "
"the unsubscription page (allowing users to update their subscription "
"preferences)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22
msgid "History with the Log Notes"
msgstr "История с записями журнала"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:25
msgid ""
"A record of the mailings sent is kept on the recipient's chatter (whether it"
" is a contact or an opportunity, for example)."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:28
msgid ""
"This is important as you and team members can easily keep track and see a "
"history of the interactions with your contacts or prospects. Example: your "
"sales representative can easily find out which SMS mailing promotions a "
"customer has received or not."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35
msgid "Blacklist"
msgstr "Чёрный список"
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:38
msgid ""
"If you are coming from another software and have a list of clients who have "
"already asked to be blacklisted, you can import those entries to your "
"database."
msgstr ""
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:39
msgid ""
"For that, go to :menuselection:`Configuration --> Phone Blacklist --> "
"Import`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:3
msgid "Integrations and Templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:5
msgid ""
"Using SMS to reach people can be a strategy not just used for advertisement "
"purposes, but also as a reminder of events or issued invoices to your "
"costumers, for example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:9
msgid "Campaigns"
msgstr "Кампании"
#: ../../sms_marketing/overview/integrations_and_template.rst:11
msgid ""
"First, make sure to have the necessary feature activated. Go to the "
":menuselection:`Email Marketing app --> Configuration --> Settings` and "
"enable *Mailing Campaigns*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:17
msgid ""
"Now, the menu *Campaigns* is also available on the *SMS Marketing* app, "
"allowing you to manage and have an overview of your SMS mailings under "
"campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:23
msgid ""
"This feature is especially useful if you have aggregated campaigns, as you "
"have a global reporting view. In addition to that, you can create stages in "
"your Kanban view to better organize the work being done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:31
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:34
msgid ""
"Sending SMSs through the contact’s form is available by default in Odoo. It "
"makes your work easier if you need to send an SMS to a specific contact, for"
" example."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:36
msgid ""
"For that, go to the *Contacts* app, select the contact and click on the "
"*SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:41
msgid ""
"If you would like to send a message to multiple contacts at once, choose the"
" *List View*, select all the contacts needed, and under *Action* select "
"*Send SMS*."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:48
msgid "Set up SMS templates"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:50
msgid ""
"To set up *SMS Templates*, activate the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, then go to "
":menuselection:`Technical --> SMS Templates`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:60
msgid ""
"Use *Dynamic Placeholders* to adapt automatically the content of the SMS to "
"the context."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:63
msgid "SMS Text Messaging is available throughout Odoo:"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:65
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:66
msgid "*Subscription*: alert customers about their subscription."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:67
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:68
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:69
msgid ""
"*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:70
msgid ""
"*Sign*: receive a validation code to verify your identity before signing a "
"document online."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:71
msgid ""
"*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:72
msgid ""
"*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:75
msgid ""
"For more information about SMS integrations in Odoo and a list of frequently"
" asked questions, go to :doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:79
msgid ":doc:`../../social_marketing/overview/campaigns`"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:80
msgid ":doc:`../../discuss/advanced/email_template`"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:3
msgid "Build, Send and Get Reports from a SMS Mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:5
msgid ""
"Using SMS Marketing as part of your communication strategies can empower you"
" to expand your markets, considering that in some countries emails are not "
"very used or used at all. It also helps to boost conversion rates, as this "
"strategy has a high open-rate percentage among people who use smartphones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:11
msgid "Get started"
msgstr "Начать"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:13
msgid "Go to :menuselection:`SMS Marketing --> Create`."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:18
msgid ""
"Specify a *subject* name to help you remembering what the mailing is about."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:20
msgid ""
"Under *Recipients*, choose to whom you would like the SMS to be sent. If you"
" choose *Contact*, all your Odoo contacts (vendor, customers, etc.) receive "
"your SMS."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:22
msgid ""
"From there, you can refine your recipient list with the *add filter* option."
" In the example below, the message would be sent to the contacts living in "
"Belgium."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:27
msgid ""
"The *Mailing list* option, on the other hand, allows you to choose the "
"specific mailing lists you created to group specific contacts. You are "
"allowed to select multiple ones."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:34
msgid ""
"Under the *SMS Content* tab, links can be included and Odoo automatically "
"generates *link trackers* in order to generate data about these links."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:36
msgid ""
"Under *Settings* you have the option *Include opt-out link*. If activated, "
"the contact is able to unsubscribe from the mailing list."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:43
msgid ""
"In the *Link Tracker* menu under *Configuration*, you can see the history of"
" your sent links, access them and look at statistics."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:50
msgid "Double-check that you have the phone number of your contacts saved."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:53
msgid "Send a mailing"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:57
msgid ""
"Once you have your mailing created, you must choose when you would like it "
"to be delivered:"
msgstr ""
"После создания почтовой рассылки необходимо выбрать, когда она будет "
"доставлена:"
#: ../../sms_marketing/overview/sms_mailing_reports.rst:59
msgid ""
"*Put in Queue*: the mailing is triggered with the next automatic run. "
"Interesting option if you do not need the message to be sent at a specific "
"time."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:61
msgid ""
"*Send Now*: sends the message immediately. Use this option if the recipient "
"list is not excessive."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:62
msgid ""
"*Schedule*: allows you to choose a day and time. Best option for mailings "
"that you would like to send during a specific event, to promote an offer "
"while it is active, or to simply plan your content strategy in advance."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:65
msgid ""
"*Test*: allows you to send an SMS to one or multiple numbers for test "
"purposes. Check, for example, if the link provided lands on the right page "
"while making sure they are responsive. If sending it to multiple numbers, "
"you must remember to use a comma between them."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:70
msgid "Visualize reports"
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:72
msgid ""
"Under the *Reporting* menu apply filters, measures, and adopt different "
"layouts to do analyses of the performance of your SMS mailings."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:79
msgid ""
"You can also check the price to send an SMS for your country by clicking on "
"the *Information* icon."
msgstr ""
#: ../../sms_marketing/overview/sms_mailing_reports.rst:86
msgid ""
"**Buy Credits:** in order to take advantage of the app and its features, "
"make sure you have purchased credits. For more information: "
":doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/pricing.rst:3
msgid "Pricing and FAQ"
msgstr "Цены и часто задаваемые вопросы"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:3
msgid "SMS Pricing and FAQ"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:6
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:7
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
"prepaid credits* to work."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:11
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:12
msgid "There are 2 types: GSM7 and UNICODE."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:14
msgid ""
"**GSM7** is the standard format, with a limit of 160 characters per message,"
" that includes the following characters:"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:23
msgid ""
"**UNICODE** is the format applied if a special character, that *is not* in "
"the GSM7 list, is used. Limit per SMS: 70 characters."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:27
msgid ""
"For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above"
" these limits, the content is divided into a multi-part message* and the "
"limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. The "
"system will inform you in real-time about the number of SMS your message "
"represents."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:34
msgid "How much does it cost to send an SMS?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:35
msgid ""
"The price of an SMS depends on the destination and the length (number of "
"characters) of the message."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:37
msgid ""
"To see the **price per country, please consult**: `Odoo SMS - FAQ <https"
"://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:39
msgid ""
"The number of SMSs a message represents will be always available to you in "
"your database."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:49
msgid "How do I buy credits?"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:50
msgid "Go to :menuselection:`Settings --> Buy Credits`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:57
msgid "Or go to :menuselection:`Settings --> View my Services`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:65
msgid ""
"If you are on Odoo Online (SAAS) and have the Enterprise version, you "
"benefit from free trial credits to test the feature."
msgstr ""
"Если вы на Odoo Online (SAAS) и у вас версия Enterprise, для тестирования "
"функции вы пользуетесь бесплатными пробными кредитам."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:70
msgid "More common questions"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:72
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:74
msgid "No, credits do not expire."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:77
msgid ""
"**Can I send an SMS to a phone number (which is not a mobile phone) because "
"I see the icon in front of the field “phone”?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:80
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:83
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:85
msgid "Yes."
msgstr "Да."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:88
msgid "**Can the recipient answer to me?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:90
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:93
msgid ""
"**What happens if I send multiple SMS but I do not have enough credits to "
"send them all?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:95
msgid ""
"The whole transaction is counted as a single one, so no SMS will be sent "
"until you have enough credits to send them all."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:99
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:101
msgid ""
"Yes, the SMS is logged as a note under the chatter of the corresponding "
"record, and a complete history of the SMSs sent is available on "
":doc:`Developer mode <../../general/developer_mode/activate>` under "
":menuselection:`Technical --> SMS`."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:107
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:109
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:112
msgid ""
"**If I have a number that does not exist in the list of recipients, will I "
"lose credits?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:114
msgid ""
"Not if the phone number is in the wrong format (e.g. too many digits). "
"Otherwise, if the SMS is sent to the wrong person or to a fake number, the "
"credit will be lost."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:118
msgid ""
"**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
" ticket for a festival)?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:120
msgid ""
"The SMS will not be delivered to that kind of number, so you won’t be "
"charged."
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:123
msgid ""
"**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:125
msgid "Only the ones that have an invalid format."
msgstr "Только те, которые имеют недопустимый формат."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:128
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../sms_marketing/pricing/pricing_and_faq.rst:130
msgid ""
"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""
locale/ru/LC_MESSAGES/social_marketing.po
+362
View File
@@ -0,0 +1,362 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../social_marketing.rst:5
msgid "Social Marketing"
msgstr "Меркетинг соцсетей"
#: ../../social_marketing/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../social_marketing/overview/campaigns.rst:3
msgid "Connecting to my Marketplace with Campaigns"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:5
msgid ""
"Whether your goal is to sell a new product, explain the value of your "
"services or advertise your event, a campaign helps you to connect with your "
"marketplace. They normally involve multiple channels, so it is fundamental "
"to have a solution with which you can plan, execute, track, and analyze your"
" content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:10
msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:16
msgid ""
"As you create content, tabs for that specific channel are shown. The "
"overview of the campaign displays global metrics such as:"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:19
msgid ""
"*Revenue*: number of users who, from a link in your content, finished a "
"transaction (paid)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:20
msgid ""
"*Quotations*: number of users who, from a link in your content, have started"
" but not finished a transaction (did not pay)."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:22
msgid ""
"*Leads*: users who have filled out your contact form, from a link in your "
"content."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:25
msgid ""
"To be able to *Send New Mailing*, make sure the feature is enabled in the "
"*Email Marketing* application, under :menuselection:`Email Marketing --> "
"Configuration --> Settings`. To be able to *Send SMS*, the *SMS Marketing* "
"application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:30
msgid ""
"*Social Marketing* works integrated with other applications such as *Sales*,"
" *Invoicing*, *CRM* and *Website*."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:34
#: ../../social_marketing/overview/manage_social.rst:77
msgid ":doc:`./push_notifications`"
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:35
#: ../../social_marketing/overview/push_notifications.rst:66
msgid ":doc:`./manage_social`"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:3
msgid "Interact with Customers and Visitors with Live Chat"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:5
msgid ""
"One of the ways you can build stronger relationships with your customers is "
"by making yourself available through live chat. Live chats can have a big "
"impact not just on your customer service, but also on sales performance, as "
"it gives users a chance of having real-time, fast, and effective "
"interaction."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:11
msgid "Configuration"
msgstr "Настройка"
#: ../../social_marketing/overview/livechat.rst:13
msgid ""
"Go to :menuselection:`Website --> Configuration --> Settings --> Live Chat` "
"select the appropriate channel, and set it up."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:20
msgid ""
"Under *Channel Rules*, choose when the chat pop-up appears, and an action "
"for a given URL and/or country. Note that to take the country into account, "
"GeoIP must be installed on your server."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:24
msgid "The *Live Chat* application must be installed on your database."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:27
msgid "Monitor your visitors"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:29
msgid ""
"Under the *Visitors* menu, see the visitors that landed on one of your "
":ref:`social_marketing/website_tracked_pages` online or offline."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:34
msgid ""
"You can send emails (if an email address has been saved), send SMSs (if a "
"phone number has been saved), send a push notification (if the user has "
"subscribed to it), and even send a live chat request that will be received "
"by the user once they move to a tracked page."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:36
msgid ""
"Open a record to see details including the visited pages, and the first and "
"last date and time the user was connected."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:43
msgid ""
"Your online visitors will be authenticated if they are linked to a lead or "
"an existing partner."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:44
msgid ""
"If you do not use the *Website* app, you can add a live chat widget to your "
"own website."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:49
msgid "Website’s tracked pages"
msgstr ""
#: ../../social_marketing/overview/livechat.rst:51
msgid ""
"To define which pages are tracked, on the *Website* application, go to "
":menuselection:`Website --> Configuration --> Pages` and enable the option "
"*Track*, on the respective pages."
msgstr ""
#: ../../social_marketing/overview/livechat.rst:60
msgid ":doc:`../../livechat/overview/get_started`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:3
msgid "Manage Social Media Pages and Create Content"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:5
msgid ""
"Once you are present on social media platforms, it is important to keep them"
" up-to-date. However, that might feel like a full-time job. Having a "
"solution that allows you to create, schedule, keep track, engage with your "
"audience and measure results saves you time and helps you to successfully "
"execute your online strategy, from posts to results."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:12
msgid "Add accounts and create your feed"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:14
msgid ""
"Click on *Add Stream* and grant the required permissions to add your "
"accounts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:21
msgid "You can link a Facebook page for which you are the admin."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:23
msgid ""
"You are then redirected to your *Feed* and a column with the publications is"
" automatically added."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:25
msgid ""
"You can then add new accounts and/or streams, such as Facebook mentions, and"
" customize your Kanban view."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:31
msgid ""
"Adding social media accounts to your feed will also link KPIs. To get "
"redirected to the statistics page of the social account, click on "
"*Insights*."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:39
msgid "Link a LinkedIn account"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:41
msgid ""
"Go to :menuselection:`Social Marketing --> Configuration --> Social Media`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:48
msgid ""
"LinkedIn is in Beta Version, therefore, the feed is not available. Only the "
"creation of content."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:51
msgid "Publish content"
msgstr "опубликовать содержание"
#: ../../social_marketing/overview/manage_social.rst:53
msgid ""
"Click on :menuselection:`Social Marketing --> Feed --> New Post`, or go to "
":menuselection:`Social Marketing --> Posts → Create`."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:60
msgid "Choose to upload your post right away or to schedule it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:61
msgid "Saving your post will apply a draft status to it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:64
msgid "Overview and plan your posts with a calendar view"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:67
msgid ""
"Through the calendar view, besides having an overview of your planned day, "
"week or month, also see your drafted, scheduled and published posts."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:68
msgid "Drag and drop (scheduled posts) to change their scheduled date."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:70
msgid ""
"Double-click on a date to create a post directly from the *Calendar view*, "
"and click on an existing one to edit it."
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:78
#: ../../social_marketing/overview/push_notifications.rst:67
msgid ":doc:`./campaigns`"
msgstr ""
#: ../../social_marketing/overview/manage_social.rst:79
msgid ":doc:`./livechat`"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:3
msgid "Use Web Push Notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:5
msgid ""
"Web Push Notifications deliver messages to your user’s device without the "
"need to be on your website, or for them to give personal information. They "
"can be used to inform your users about news, articles and content posted, "
"practical messages like traffic and weather updates, flight information, "
"sales alerts, coupons, and product updates."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:11
msgid "Ask users for permission"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:13
msgid ""
"In the *Website* application go to :menuselection:`Website --> Configuration"
" --> Settings` and enable *Web Push Notifications*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:20
msgid ""
"Choose your message, icon, and delay time (which is the wait time for the "
"permission request to be shown once the user lands on your page)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:28
msgid "Send notifications"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:31
msgid "Individually"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:33
msgid "You can send individual messages through the menu *Visitors*."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:40
msgid "To a group"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:42
msgid ""
"Target a bigger segment by selecting multiple visitors in the *View List* "
"(e.g.: all visitors that visited your Homepage)."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:50
msgid ""
"Visitors records are kept under *Visitors* for a week, before getting "
"archived."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:53
msgid "By rules"
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:55
msgid ""
"Or go to :menuselection:`Social Marketing --> Posts --> Create`. Under *Web "
"Notification options*, apply filters to send your message to the records "
"that match the rules you set."
msgstr ""
#: ../../social_marketing/overview/push_notifications.rst:63
msgid "The feature only works with Odoo Website application."
msgstr ""
locale/ru/LC_MESSAGES/studio.po
+942
View File
@@ -0,0 +1,942 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ivan Yelizariev <yelizariev@it-projects.info>, 2020
# Irina Fedulova <istartlin@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Irina Fedulova <istartlin@gmail.com>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../studio.rst:5
msgid "Studio"
msgstr "Студия"
#: ../../studio/concepts.rst:3
msgid "Concepts"
msgstr "понятие"
#: ../../studio/concepts/understanding_automated_actions.rst:3
msgid "Understanding Automated Actions"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:6
msgid ""
"Automated actions are used to trigger actions. They are based on conditions "
"and happen on top of Odoo’s default business logic."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:9
msgid ""
"Examples of automated actions include: creating a next activity upon a "
"quote's confirmation; adding a user as a follower of a confirmed invoice if "
"its total is higher than a certain amount; or preventing a lead from "
"changing stage if a field is not filled in."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:16
msgid ""
"Let's understand how to properly define *when* an automated action runs and "
"*how* to create one:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:18
msgid ""
"The first step is to choose the :doc:`Model <understanding_general>` on "
"which the action is applied."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:19
msgid ""
"The **Trigger** field defines the event that causes the automated action to "
"happen:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:21
msgid ""
"*On Creation*: when a new record is created. Note that the record is created"
" once saved for the first time."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:23
msgid ""
"*On Update*: when the record is updated. Note that the update happens once "
"the record is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:24
msgid ""
"*On Creation & Update*: on the creation and/or on the update of a record "
"once the form is saved."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:25
msgid "*On Deletion*: on the removal of a record under the condition set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:26
msgid ""
"*Based on Form Modification*: when the value of the specified *Trigger* "
"field is changed in the interface (user sees the changes before saving the "
"record). Note that this action can only be used with the *Execute Python "
"Code* action type."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:29
msgid ""
"*Based on Timed Condition*: a delay happens after a specific date/time. Set "
"a *Delay after trigger date* if you need a delay to happen before the "
"*Trigger Date*. Example: to send a reminder 15min before a meeting. If the "
"date/time is not set on the form of the model chosen, the date/time "
"considered is the one of the creation/update of the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:34
msgid "For every Trigger option, **conditions** can be applied, such as:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:36
msgid ""
"*Before Update Domain*: if designated, this condition must be satisfied "
"before the record is updated."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:38
msgid ""
"*Apply on*: if designated, this condition must be satisfied before executing"
" the action rule (*Action To Do*), and after the update."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:41
msgid ""
"The **Active** option is to be turned off when the rule should be hidden and"
" not executed."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:43
msgid ""
"Under **Action To Do** choose the type of server action that must be "
"executed once records meet the *Trigger* conditions:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:45
msgid ""
"*Execute Python Code*: a block of code is executed. A *Help* tab with the "
"variables that can be used is available."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:47
msgid "*Create New Record*: a new record with new values is created."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:48
msgid "*Update a Record*: updates the record that triggered the action."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:49
msgid ""
"*Execute several actions*: defines an action that triggers other server "
"actions."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:50
msgid ""
"*Send Email*: an automatic :doc:`email "
"<../../discuss/advanced/email_template>` is sent."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:51
msgid ""
"*Add Followers*: :doc:`followers <../../project/tasks/collaborate>` are "
"notified of changes in the task."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:53
msgid ""
"*Create Next Activity*: creates an activity such as: *Call*, *Email*, "
"*Reminder*."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:54
msgid ""
"*Send SMS Text Message*: sends an :doc:`SMS "
"<../../sms_marketing/pricing/pricing_and_faq>`."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:57
msgid "Example"
msgstr "пример"
#: ../../studio/concepts/understanding_automated_actions.rst:59
msgid ""
"This is the process of which the update of the *Email* field on the "
"Lead/Opportunity *Model*, with a *Trigger Condition* set to *On Update*, "
"goes through:"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:66
msgid "The user creates the record without an email address set."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:67
msgid "The user updates the record defining an email address."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:68
msgid ""
"Once the change is saved, the automation checks if any of the *Watched "
"Fields* are being updated (for the example: field name *email_from* (Email)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:70
msgid ""
"If true, it checks if the record matches the *Before Update Domain* (for the"
" example: *email is not set*)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:72
msgid ""
"If true, it checks (*after the update*) whether the record matches the "
"*Apply on* domain (for the example: *email is set*)."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:74
msgid "If true, the chosen *Action To Do* is performed on the record."
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:77
msgid ":doc:`understanding_general`"
msgstr ""
#: ../../studio/concepts/understanding_automated_actions.rst:78
msgid ":doc:`../use_cases/automated_actions`"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:3
msgid "Understanding General Concepts"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:7
msgid ""
"Odoo Studio is a toolbox that allows you to add models or adapt "
"functionalities on top of Odoo’s standard behavior without coding knowledge."
" You can also create custom views and modify existing ones without having to"
" get into the XML code."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:11
msgid ""
"Even for experienced developers, typing out code requires time. By using "
"Odoo Studio, you can quickly get your models up and going and focus on the "
"crucial parts of your application. The result is a user-friendly solution "
"that makes customizations and designing new applications easy with or "
"without programming skills."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:15
msgid "Getting started"
msgstr "Начиная работу"
#: ../../studio/concepts/understanding_general.rst:17
msgid ""
"One you start using Odoo Studio, you automatically create a new *module* "
"that contains all your modifications. These modifications can be done on "
"existing screens (*views*), by adding new *fields* in existing applications,"
" or by creating an entirely new *model*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:22
msgid "What is a Module?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:25
msgid ""
"An Odoo **Module** can contain a number of elements, such as: business "
"objects (models), object views, data files, web controllers, and static web "
"data. An application is a collection of modules."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:29
msgid ""
"In object-oriented programming, models usually represent a concept from the "
"real world. Example: Odoo has models for Sales Orders, Users, Countries, "
"etc. If you were to build an application to manage Real Estate sales, a "
"model that represents the Properties for sale would probably be your first "
"step."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:38
msgid "What is a Model (also called Object)?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:40
msgid ""
"A **Model** determines the logical structure of a database and fundamentally"
" determines in which manner data can be stored, organized, and manipulated. "
"In other words, a model is a table of information that can be bridged with "
"other tables."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:45
msgid "What are Fields?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:47
msgid ""
"**Fields** compose models. It is where a record (a piece of data) is "
"registered."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:49
msgid ""
"Example: on the Real Estate application, fields on the Properties model "
"would include the price, address, a picture, a link to the current owner, "
"etc."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:50
msgid ""
"There are 2 main types of fields in Odoo: *basic (or scalar) fields* and "
"*relational fields*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:53
msgid ""
"Basic fields represent simple values, like numbers or text. Relational "
"fields represent relations between models. So, if you have a model for "
"*Customers* and another one for *Properties*, you would use a relational "
"field to link each Property to its Customer."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:56
msgid "Relational Fields in detail"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:59
msgid ""
"**Relational Fields** provide the option to link the data of one model with "
"the data of another model."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:60
msgid ""
"In Odoo, relational field types are: *One2many*, *Many2one*, *Many2many*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:66
msgid ""
"An **One2many** field is a *one-way* direction of selecting *multiple* "
"records from a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:68
msgid ""
"Example: a Sales Order can contain multiple Sales Order Lines, which also "
"contain multiple fields of information."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:69
msgid ""
"A **Many2one** field is a *one-way* direction of selecting *one* record from"
" a table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:70
msgid ""
"Example: you can have many product categories, but each product can only "
"belong to one category."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:71
msgid ""
"A **Many2many** field is a *two-way* direction of selecting records from a "
"table."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:72
msgid "Example: multiple tags can be added to a lead’s form."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:75
msgid "An *One2many* field must have a *Many2one* related to it."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:78
msgid "What are Views?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:80
msgid ""
"**Views** define how records are displayed. They are specified in XML which "
"means that they can be edited independently from the models that they "
"represent. There are various types of views in Odoo, and each of them "
"represents a mode of visualization. Some examples are: *form*, *list*, "
"*kanban*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:85
msgid "What is a Menu?"
msgstr ""
#: ../../studio/concepts/understanding_general.rst:87
msgid ""
"A **Menu** is a button that executes and action. In Odoo Studio, to create "
"menus (models) and rearrange their hierarchy, click on *Edit Menu*."
msgstr ""
#: ../../studio/concepts/understanding_general.rst:95
msgid "`Studio Basics <https://www.odoo.com/fr_FR/slides/studio-31>`_"
msgstr ""
#: ../../studio/how_to.rst:3
msgid "How To"
msgstr ""
#: ../../studio/how_to/export_import.rst:3
msgid "Export and Import Modules"
msgstr ""
#: ../../studio/how_to/export_import.rst:5
msgid ""
"When you do customizations in Odoo Studio, a new module is created in your "
"database, making it easy to use Studio for prototyping."
msgstr ""
#: ../../studio/how_to/export_import.rst:8
msgid ""
"To export these customizations, activate Studio on the main dashboard and, "
"under the menu *Customizations*, click on *Export*. The default filename is "
"*customizations.zip*."
msgstr ""
#: ../../studio/how_to/export_import.rst:16
msgid ""
"The module created contains the definition of custom models and fields, as "
"well as the UI elements of any customization in an XML format."
msgstr ""
#: ../../studio/how_to/export_import.rst:18
msgid ""
"To import and install the customizations in another instance, connect to the"
" destination database, activate Studio and, under *Customizations*, click on"
" *Import*."
msgstr ""
#: ../../studio/how_to/export_import.rst:25
msgid ""
"Studio does not know which apps are customized (because the same view can be"
" modified on different apps), therefore, it *does not* add the underlying "
"modules as dependencies of the exported module. In other words, the "
"applications installed on the source database should be installed on the "
"destination database."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:3
msgid "Customizing the Rainbow Man"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:5
msgid ""
"The Rainbow Man in Odoo is an animation shown once the user completes "
"certain tasks and clicks on certain buttons. It is a way to make the "
"software fun to use, and rewarding, for employees."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:13
msgid ""
"On most buttons in Odoo, such as *Send by Email*, *Confirm* or *Cancel*, "
"once they are selected in Studio, under their *Properties*, the *Rainbow "
"Man* effect can be applied."
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:14
msgid "By default, the feature is active:"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:16
msgid "when opportunities are marked as won;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:17
msgid "when users empty their inboxes;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:18
msgid "when the user finishes a tour;"
msgstr ""
#: ../../studio/how_to/rainbow_man.rst:19
msgid "when the user finishes doing reconciliations."
msgstr ""
#: ../../studio/how_to/reports.rst:3
msgid "Customizing Reports"
msgstr ""
#: ../../studio/how_to/reports.rst:9
msgid ""
"Odoo uses HTML and CSS technologies to create reports. HTML is a markup "
"language that uses tags, also called elements. It is the core of any webpage"
" because it provides its basic structure. CSS interacts with HTML elements "
"to add style to the page, establishing how the HTML is shown to the user. "
"Odoo’s reports also use Bootstrap’s grid layout, which is the containers, "
"rows, and columns to align content, and support Odoo's website themes."
msgstr ""
#: ../../studio/how_to/reports.rst:11
msgid ""
"When creating a new report, choose the purpose of it and if you would like "
"the report to include header and footer (company logo, name, address, phone,"
" email address, etc.)."
msgstr ""
#: ../../studio/how_to/reports.rst:17
msgid ""
"Under the tab **Add**, you find the fields to be dragged and dropped to the "
"view. *Fields*, *Data tables*, *Subtotal & Total*, and *Address Book* are "
"dynamic elements (meaning that they need a :doc:`one2many or a many2many "
"<../concepts/understanding_general>` related object). *Text*, *Title Block*,"
" *Image*, and *Text in Cell* are static elements."
msgstr ""
#: ../../studio/how_to/reports.rst:26
msgid ""
"Once the element is added to the view, select it to see its **Options**. The"
" first section shows the hierarchy of the selected object and its "
"properties, allowing you to individually edit them. Fields with related "
"objects have their directives shown on *Field Expression*."
msgstr ""
#: ../../studio/how_to/reports.rst:34
msgid ""
"Under **Visible if**, define the rule(s) to set visibility conditions to "
"fields."
msgstr ""
#: ../../studio/how_to/reports.rst:36
msgid ""
"Example: if choosing to display a product image, you could set a visibility "
"rule to only display the ones that are *set* in the product form, avoiding "
"having a plain icon when they are not set."
msgstr ""
#: ../../studio/how_to/reports.rst:40
msgid ""
"**Visible for** is used to set which :doc:`groups "
"<../../general/odoo_basics/add_user>` can have access to specific elements "
"in the report. **Limit visibility to groups**, under *Report*, sets the "
"visibility of the report to specifics groups, meaning that users belonging "
"to other groups do not see the same final document."
msgstr ""
#: ../../studio/how_to/reports.rst:46
msgid ""
"Under the **Report** tab, name your report, choose the paper format, and if "
"the report should be added to the *Print* menu list on its respective "
"document form."
msgstr ""
#: ../../studio/how_to/reports.rst:53
msgid ""
"If activating the :doc:`Developer mode "
"<../../general/developer_mode/activate>`, additional fields such as *Class* "
"under *Options*, and *Reload from attachment* under *Report*, become "
"visible."
msgstr ""
#: ../../studio/how_to/reports.rst:56
msgid ""
"*Class*: add custom CSS classes to the selected element (e.g. Bootstrap "
"classes such as *text-danger*)."
msgstr ""
#: ../../studio/how_to/reports.rst:59
msgid ""
"*Reload from attachment*: saves the report as an attachment of the document "
"when printed. When the report is reprinted, it re-downloads that attachment "
"instead of re-printing it. This means that if the underlying record (e.g. "
"Invoice) changes when compared to the first impression, the report does not "
"reflect the changes because they were done after the attachment was created."
" This is typically useful for reports linked to documents that should not "
"change, such as Invoices."
msgstr ""
#: ../../studio/how_to/reports.rst:67
msgid ""
"Actions in Odoo Studio can be undone until you *Close* the toolbox. Once you"
" have closed Studio, changes can not be undone anymore."
msgstr ""
#: ../../studio/use_cases.rst:3
msgid "Use Cases"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:3
msgid "Advanced Use Cases: Automated Actions"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:5
msgid ""
"**Case scenario 1: when a Belgian lead is created, a 3-stars priority should"
" be automatically applied.**"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:8
msgid "Under *Automations*, click on *Create* and set the following rules:"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:10
msgid "*Model*: Lead/Opportunity"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:11
msgid "*Active*: On"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:12
msgid "*Trigger*: On Creation & Update"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:13
msgid "*Apply on*: Country > Country Name = Belgium"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:14
#: ../../studio/use_cases/filters_status_bar.rst:53
msgid "*Action To Do*: Update the Record"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:15
msgid "*Data to Write*: Lead/Opportunity > Value > 3"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:22
msgid ""
"Check :doc:`this doc <filters_status_bar>` in order to have another "
"automated action example."
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:25
msgid ":doc:`../concepts/understanding_automated_actions`"
msgstr ""
#: ../../studio/use_cases/automated_actions.rst:26
#: ../../studio/use_cases/filters_status_bar.rst:61
#: ../../studio/use_cases/models_fields.rst:138
#: ../../studio/use_cases/views.rst:28
msgid ":doc:`../concepts/understanding_general`"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:3
msgid "Advanced Use Cases: Filters and Status Bar"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:5
msgid ""
"**Case scenario 1: on Sales, set a filter on Belgian customers and define it"
" as the default one (the user should still be able to unset the filter).**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:8
msgid ""
"On your customer’s page, use *Filters* > *Add Custom Filter* to group "
"customers by country. Now, under *Favorites*, *Save Current Search* enabling"
" *Use by default* and *Save*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:15
msgid ""
"On *Filter Rules* in Studio mode, select the respective filter and enable "
"*Default Filter*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:21
msgid ""
"**Case scenario 2: add a status bar on the product form to manage its life "
"cycle. Set the values: ‘Prototype’, ‘In use’ and ‘Deprecated’. By default, "
"the Kanban view must be grouped by status.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:26
msgid ""
"On your product form, *Add a pipeline status bar* and name its values. "
"Status bars are *selection* fields that give you the ability to follow a "
"specific flow. They are useful to show you the progress that has been made."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:28
msgid ""
"On the *Views* menu, access *Kanban* and, under its *View* options, set the "
"*Default Group by* as *Pipeline status bar*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:34
msgid ""
"Now, open your product form and set the right status for that product. As "
"you move products throughout stages (also through the product’s form), "
"stages are shown in the Kanban view."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:38
msgid ""
"To make modifications in the pipeline status bar, for example, remember to "
"go back to *Form View*."
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:44
msgid ""
"**Case scenario 2.a: when a product goes from ‘In use’ to ‘Deprecate’, set "
"its cost to 0€.**"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:46
msgid ""
"Create an :doc:`automated action "
"<../concepts/understanding_automated_actions>` with the selected values:"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:49
msgid "*Model*: Product Template"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:50
msgid "*Trigger*: On Update"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:51
msgid "*First Domain*: Pipeline status bar = In use"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:52
msgid "*Second Domain*: Pipeline status bar = Deprecated"
msgstr ""
#: ../../studio/use_cases/filters_status_bar.rst:54
msgid "*Data to Write*: Cost (Product Template) > Value > 0"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:3
msgid "Advanced Use Cases: Creating Models and Adding Fields"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:5
msgid ""
"**Case scenario 1: on the leads’ form, if the chosen country is France, show"
" a field 'Pay by check?'**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:8
msgid ""
"On your leads’ form, add a *Related Field* to *Country > Country Name*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:10
msgid ""
"Now, add a *Checkbox* field and define its invisibility options as *Country*"
" (carefully select the one just created) *> is not = > France.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:11
msgid "You can now hide the related field created (*Country*) if you wish."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:19
msgid ""
"Another approach is to use the country’s ID. To do so, go to "
":menuselection:`Contacts --> Configuration --> Countries`, select France "
"(for example), and on the URL check its *ID*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:21
msgid ""
"The related field invisibility path should now be *Country* (carefully "
"select the one just created) *> is not = > 75*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:22
msgid "Again, hide the related field with the country’s ID if you prefer."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:28
msgid ""
"**Case scenario 2: create a model called 'Properties' and add fields called:"
" company, value, name, address, active, image.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:31
msgid ""
"From the dashboard, (optionally) start a new module. Then, click on *Edit "
"Menu* and start a *New Menu* (model). Set your menu name and *Confirm*. Now,"
" on its form, drag & drop the necessary fields."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:39
msgid ""
"**Case scenario 2.a: now, you would like to have a model called 'Regions' to"
" which each property must be linked. And, on 'Regions', you would like to "
"see the properties for each region.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:43
msgid ""
"Go to *Edit Menu > New Menu* and create your menu, calling it *Regions*. Add"
" the necessary fields on its form by dragging & dropping them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:45
msgid ""
"Now, in the form view of *Properties*, add a *Many2one* field with a "
"relation to your model *Region*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:48
msgid ""
"The *Existing Fields* are the ones that are on the current model but not yet"
" in the view."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:60
msgid ""
"Now, go to the model *Regions*, select the form view, and add a status "
"button selecting *Regions (Properties)* as your relational field."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:62
msgid ""
"*Status buttons* are computed fields, meaning that they count the numbers of"
" records on the related model, and allow you to access them."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:69
msgid ""
"When searching for relations, click on *Search more* and filter it by "
"*Custom*. This way you avoid creating duplicates."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:76
msgid ""
"**Case scenario 2.b: in the model 'Properties', show all the tags as "
"checkboxes instead of tags.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:78
msgid ""
"Once the field *Tags* is added to the form, select it and, under its "
"*Properties > Widgets*, choose *Checkboxes*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:85
msgid ""
"**Case scenario 3: on the leads’ form, add a selection field with the "
"values:'Tags' & 'List' & 'Checkboxes'. According to the value of the field, "
"show tags as many2many_tags, many2many_radio, or many2many(_list).**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:89
msgid ""
"In your form view, add a *Tags* field and relate it to *Partners Tag*. Under"
" *Properties*, define its *Widget* as *Many2many*. Do the same process "
"another 2 times for *Checkboxes* and *Tags*."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:96
msgid "Now, add a *Selection* field and the necessary values."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:99
msgid ""
"Continue by selecting your *Tags* fields, one by one, to set their "
"*Invisible* options according to their *Widget*. In the example below, the "
"invisibility rule for the *Partner Tags* is set as: *Select Tag type > is "
"not = > Tags.*"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:105
msgid ""
"**Case scenario 4: on a quotation’s form, add a selection field called "
"'Manager Validation' with the values: ‘Accepted’ and ‘Refused’. Only a sales"
" manager can see it, and the field should be set as mandatory if the untaxed"
" amount is higher than 500€.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:109
msgid ""
"On your quotation form, add a *Selection* field with the values *Accepted* "
"and *Refused*. Set its *Required* condition as *Untaxed Amount > 500* and "
"the *Limit visibility to groups* as *Sales / Administrator* or managers."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:117
msgid "**Case scenario 5: change the tooltip of a field for all views.**"
msgstr ""
#: ../../studio/use_cases/models_fields.rst:119
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>` "
"and open Studio."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:122
msgid ""
"Select the necessary field and, under *Properties*, click on *More* to write"
" your tooltip message on *Field Help*. The tooltip message is the "
"explanatory message shown when the user hovers the field. The message here "
"written is displayed on all views forms where the field is added."
msgstr ""
#: ../../studio/use_cases/models_fields.rst:129
msgid ""
"The *Field Help* message can only be applied to *new* fields. If you would "
"like to change/apply a tooltip for a specific field, use the *Help Tooltip* "
"option under *Properties*."
msgstr ""
#: ../../studio/use_cases/views.rst:3
msgid "Advanced Use Cases: Views"
msgstr ""
#: ../../studio/use_cases/views.rst:5
msgid ""
"**Case scenario 1: in Sales, show orders in a Kanban View instead of a List "
"View.**"
msgstr ""
#: ../../studio/use_cases/views.rst:7
msgid ""
"From the Sales page, access Studio and, under *Views*, set the *Kanban* "
"option as the default one."
msgstr ""
#: ../../studio/use_cases/views.rst:14
msgid ""
"**Case scenario 2: allow for the list of leads to be edited inline without "
"having to switch to the form view.**"
msgstr ""
#: ../../studio/use_cases/views.rst:19
msgid ""
"On the *List View*, under *View* > *Editable*, choose between *New record on"
" top* or *New record at the bottom*. This way, besides defining the order in"
" which new records are displayed in the view, you are able to edit them."
msgstr ""
#: ../../studio/use_cases/views.rst:21
msgid ""
"If the field is left blank, no editing is possible and records are shown "
"based on your column preferences on the lead's page (front-end)."
msgstr ""
locale/ru/LC_MESSAGES/support.po
+468
View File
@@ -0,0 +1,468 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Gennady Marchenko <gennadym@gmail.com>, 2020
# Martin Trigaux, 2020
# ILMIR <karamov@it-projects.info>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: ILMIR <karamov@it-projects.info>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../support.rst:5
msgid "Support"
msgstr "Поддержка"
#: ../../support/supported_versions.rst:6
msgid "Supported versions"
msgstr "Поддерживаемые версии"
#: ../../support/supported_versions.rst:9
msgid ""
"Odoo provides support and bug fixing **for the 3 last major versions** of "
"Odoo."
msgstr "Оду предоставляет поддержку и багфиксы для 3 последних версий"
#: ../../support/supported_versions.rst:11
msgid ""
"Users hosted on **Odoo Online** may use intermediary versions (sometimes "
"called *SaaS versions*) that are supported as well. These versions are not "
"published for Odoo.sh or On-Premise installations."
msgstr ""
"Пользователи пользующиеся **Odoo Online** могут использовать промежуточные "
"версии (иногда называемые *SaaS версиями*), которые также поддерживаются. "
"Эти версии не публикуются для Odoo.sh или локальной установки."
#: ../../support/supported_versions.rst:17
msgid "What's the support status of my Odoo?"
msgstr "Каков статус поддержки моего Odoo?"
#: ../../support/supported_versions.rst:19
msgid "This matrix shows the support status of every version."
msgstr "Эта матрица показывает статус поддержки каждой версии."
#: ../../support/supported_versions.rst:21
msgid "**Major releases are in bold type.**"
msgstr "**Основные выпуски выделены жирным шрифтом.**"
#: ../../support/supported_versions.rst:24
msgid "Odoo Online"
msgstr "Оду Онлайн"
#: ../../support/supported_versions.rst:24
msgid "Odoo.sh"
msgstr "Odoo.sh"
#: ../../support/supported_versions.rst:24
msgid "On-Premise"
msgstr "Локальная установка"
#: ../../support/supported_versions.rst:24
msgid "Release date"
msgstr "Дата выпуска"
#: ../../support/supported_versions.rst:26
msgid "**Odoo 14.0**"
msgstr ""
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
#: ../../support/supported_versions.rst:26
msgid "🏁"
msgstr ""
#: ../../support/supported_versions.rst:26
msgid "October 2020"
msgstr ""
#: ../../support/supported_versions.rst:28
msgid "**Odoo 13.0**"
msgstr "**Оду 13.0**"
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:28
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:32
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
#: ../../support/supported_versions.rst:36
msgid "|green|"
msgstr "|зеленый|"
#: ../../support/supported_versions.rst:28
msgid "October 2019"
msgstr "Октябрь 2019"
#: ../../support/supported_versions.rst:30
msgid "Odoo 12.saas~3"
msgstr "Оду 12.saas~3"
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:30
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:34
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "N/A"
msgstr "Н/A"
#: ../../support/supported_versions.rst:30
msgid "August 2019"
msgstr "Август 2019"
#: ../../support/supported_versions.rst:32
msgid "**Odoo 12.0**"
msgstr "**Оду 12.0**"
#: ../../support/supported_versions.rst:32
msgid "October 2018"
msgstr "Октябрь 2018"
#: ../../support/supported_versions.rst:34
msgid "Odoo 11.saas~3"
msgstr "Оду 11.saas~3"
#: ../../support/supported_versions.rst:34
msgid "April 2018"
msgstr "Апрель 2018"
#: ../../support/supported_versions.rst:36
msgid "**Odoo 11.0**"
msgstr "**Оду 11.0**"
#: ../../support/supported_versions.rst:36
msgid "October 2017"
msgstr "Октябрь 2017"
#: ../../support/supported_versions.rst:36
msgid "*End-of-support is planned for October 2020*"
msgstr "*Прекращение поддержки запланировано на Октябрь 2020*"
#: ../../support/supported_versions.rst:38
msgid "Odoo 10.saas~15"
msgstr "Оду 10.saas~15"
#: ../../support/supported_versions.rst:38
#: ../../support/supported_versions.rst:40
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:44
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:48
#: ../../support/supported_versions.rst:50
msgid "|orange|"
msgstr "|оранжевый|"
#: ../../support/supported_versions.rst:38
msgid "March 2017"
msgstr "Март 2017"
#: ../../support/supported_versions.rst:40
msgid "Odoo 10.saas~14"
msgstr "Оду 10.saas~14"
#: ../../support/supported_versions.rst:40
msgid "January 2017"
msgstr "Январь 2017"
#: ../../support/supported_versions.rst:42
msgid "**Odoo 10.0**"
msgstr "**Оду 10.0**"
#: ../../support/supported_versions.rst:42
#: ../../support/supported_versions.rst:46
#: ../../support/supported_versions.rst:50
msgid "|red|"
msgstr "|красный|"
#: ../../support/supported_versions.rst:42
msgid "October 2016"
msgstr "Октябрь 2016"
#: ../../support/supported_versions.rst:44
msgid "Odoo 9.saas~11"
msgstr "Оду 9.saas~11"
#: ../../support/supported_versions.rst:44
msgid "May 2016"
msgstr "Май 2016"
#: ../../support/supported_versions.rst:46
msgid "**Odoo 9.0**"
msgstr "**Оду 9.0**"
#: ../../support/supported_versions.rst:46
msgid "October 2015"
msgstr "Октябрь 2015"
#: ../../support/supported_versions.rst:48
msgid "Odoo 8.saas~6"
msgstr "Оду 8.saas~6"
#: ../../support/supported_versions.rst:48
msgid "February 2015"
msgstr "Февраль 2015"
#: ../../support/supported_versions.rst:50
msgid "**Odoo 8.0**"
msgstr "**Оду 8.0**"
#: ../../support/supported_versions.rst:50
msgid "September 2014"
msgstr "Сентябрь 2014"
#: ../../support/supported_versions.rst:56
msgid "|green| Supported version"
msgstr "|зеленый| Поддерживаемая версия"
#: ../../support/supported_versions.rst:58
msgid "|red| End-of-support"
msgstr "|красный| Прекращение поддержки"
#: ../../support/supported_versions.rst:60
msgid "N/A Never released for this platform"
msgstr "Н/А Никогда не выпускалась для этой платформы"
#: ../../support/supported_versions.rst:62
msgid ""
"|orange| Some of our older customers may still run this version on our Odoo "
"Online servers, we provide help only on blocking issues and advise you to "
"upgrade."
msgstr ""
"|оранжевый| Некоторые из наших старых клиентов могут до сих пор запускать "
"данную версию на наших серверах Оду Онлайн, мы предоставляем помощь только "
"по проблемам блокирующим работу и советуем вам обновиться"
#: ../../support/supported_versions.rst:64
msgid "🏁 Future version, not released yet"
msgstr "🏁 Будущая версия, еще не выпущенная"
#: ../../support/supported_versions.rst:77
msgid "I run an older version of Odoo/OpenERP/TinyERP"
msgstr "Я запускаю более старую версию Оду/OpenERP/TinyERP"
#: ../../support/supported_versions.rst:79
msgid ""
"OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform."
msgstr ""
"OpenERP 7.0, 6.1, 6.0 and 5.0 больше не поддерживается ни на какой платформе"
#: ../../support/supported_versions.rst:81
msgid ""
"TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform."
msgstr ""
"TinyERP 4.0, 3.0, 2.0 and 1.0 больше не поддерживается ни на какой платформе"
#: ../../support/supported_versions.rst:83
msgid ""
"You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
msgstr ""
"Вам следует подумать об `обновлении <https://upgrade.odoo.com/>` вашей базы "
"данных"
#: ../../support/what_can_i_expect.rst:8
msgid "What can I expect from the support service?"
msgstr ""
#: ../../support/what_can_i_expect.rst:12
msgid "5 days a week"
msgstr ""
#: ../../support/what_can_i_expect.rst:14
msgid ""
"Your Odoo Online subscription includes **unlimited 24hr support at no extra "
"cost, Monday to Friday**. Our teams are located around the world to ensure "
"you have support, no matter your location. Your support representative could"
" be communicating to you from San Francisco, Belgium, or India!"
msgstr ""
#: ../../support/what_can_i_expect.rst:19
msgid ""
"Our support team can be contacted through our `online support form "
"<https://www.odoo.com/help>`__."
msgstr ""
#: ../../support/what_can_i_expect.rst:23
msgid "What kind of support is included?"
msgstr ""
#: ../../support/what_can_i_expect.rst:25
msgid ""
"Providing you with relevant material (guidelines, product documentation, "
"etc...)"
msgstr ""
#: ../../support/what_can_i_expect.rst:27
msgid ""
"Answers to issues that you may encounter in your standard Odoo database (eg."
" “I cannot close my Point of Sale” or “I cannot find my sales KPIs?”)"
msgstr ""
#: ../../support/what_can_i_expect.rst:29
msgid "Questions related to your account, subscription, or billing"
msgstr ""
#: ../../support/what_can_i_expect.rst:30
msgid ""
"Bug resolution (blocking issues or unexpected behaviour not due to "
"misconfiguration or customization)"
msgstr ""
#: ../../support/what_can_i_expect.rst:32
msgid ""
"Issues that might occur in a test database after upgrading to a newer "
"version"
msgstr ""
#: ../../support/what_can_i_expect.rst:34
msgid ""
"*Odoo Support does not make changes to your production database without your"
" agreement and gives you the material and knowledge to do it yourself!*"
msgstr ""
#: ../../support/what_can_i_expect.rst:39
msgid "What kind of support is not included?"
msgstr ""
#: ../../support/what_can_i_expect.rst:41
msgid ""
"Questions that require us to understand your business processes in order to "
"help you implement your database"
msgstr ""
#: ../../support/what_can_i_expect.rst:43
msgid ""
"Training on how to use our software (we will direct you to our many "
"resources)"
msgstr ""
#: ../../support/what_can_i_expect.rst:44
msgid "Import of documents into your database"
msgstr ""
#: ../../support/what_can_i_expect.rst:45
msgid ""
"Guidance on which configurations to apply inside of an application or the "
"database"
msgstr ""
#: ../../support/what_can_i_expect.rst:46
msgid ""
"How to set up configuration models (Examples include: Inventory Routes, "
"Payment Terms, Warehouses, etc)"
msgstr ""
#: ../../support/what_can_i_expect.rst:48
msgid "Any intervention on your own servers/deployments of Odoo"
msgstr ""
#: ../../support/what_can_i_expect.rst:49
msgid ""
"Any intervention on your own third party account (Ingenico, Authorize, UPS, "
"etc)"
msgstr ""
#: ../../support/what_can_i_expect.rst:50
msgid ""
"Questions or issues related to specific developments or customizations done "
"either by Odoo or a third party (this is specific only to your database or "
"involving code)"
msgstr ""
#: ../../support/what_can_i_expect.rst:54
msgid ""
"You can get this type of support with a `Success Pack <https://www.odoo.com"
"/pricing-packs>`__. With a pack, one of our consultants will analyze the way"
" your business runs and tell you how you can get the most out of your Odoo "
"Database. We will handle all configurations and coach you on how to use "
"Odoo."
msgstr ""
#: ../../support/where_can_i_get_support.rst:6
msgid "Where to find help?"
msgstr ""
#: ../../support/where_can_i_get_support.rst:10
msgid "Odoo Enterprise"
msgstr "Odoo для Предприятий"
#: ../../support/where_can_i_get_support.rst:12
msgid ""
"Users who have a valid Odoo Enterprise subscription may always contact our "
"support teams through our `support form <https://www.odoo.com/help>`_, no "
"matter the hosting type you chose (Odoo Online, Odoo.sh or on your own "
"server)."
msgstr ""
#: ../../support/where_can_i_get_support.rst:16
msgid "Please include in your request:"
msgstr ""
#: ../../support/where_can_i_get_support.rst:18
msgid "your subscription number"
msgstr ""
#: ../../support/where_can_i_get_support.rst:19
msgid ""
"the URL of your database if your database is hosted by Odoo (Odoo Online or "
"Odoo.sh)"
msgstr ""
#: ../../support/where_can_i_get_support.rst:21
msgid "Our agents will get back to you as soon as possible."
msgstr ""
#: ../../support/where_can_i_get_support.rst:25
msgid "Odoo Community"
msgstr ""
#: ../../support/where_can_i_get_support.rst:27
msgid "*Odoo Community users don't get access to the support service.*"
msgstr ""
#: ../../support/where_can_i_get_support.rst:29
msgid "Here are some resources that might help you:"
msgstr ""
#: ../../support/where_can_i_get_support.rst:31
msgid "Our `documentation pages <https://www.odoo.com/page/docs>`_."
msgstr ""
#: ../../support/where_can_i_get_support.rst:32
msgid ""
"Ask your question on the `community forum "
"<https://www.odoo.com/forum/help-1>`_."
msgstr ""
#: ../../support/where_can_i_get_support.rst:33
msgid ""
"`Buy Odoo Enterprise "
"<https://www.odoo.com/documentation/13.0/setup/enterprise.html>`_ to get the"
" support and bugfix services."
msgstr ""
locale/ru/LC_MESSAGES/survey.po
+241
View File
@@ -0,0 +1,241 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Sergey Vilizhanin, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../survey.rst:5
msgid "Survey"
msgstr "Опрос"
#: ../../survey/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../survey/overview/create.rst:3
msgid "Get Started with Surveys"
msgstr ""
#: ../../survey/overview/create.rst:5
msgid ""
"Surveys can be used for a range of purposes that can go from collecting "
"customer feedback, evaluate the success of an event, measure how pleased "
"customers are with your products/services, gauge whether employees are happy"
" and satisfied with their work environment, and even to find out what your "
"market is thinking."
msgstr ""
#: ../../survey/overview/create.rst:11
msgid "Get started"
msgstr "Начать"
#: ../../survey/overview/create.rst:13
msgid ""
"When creating your survey, choose a *Title* and *Category*. The *Category* "
"field is used to know in which context the survey is being conducted, as "
"different applications might use it for different purposes such as "
"recruitment, certification, or employee appraisal."
msgstr ""
#: ../../survey/overview/create.rst:22
msgid "Tab: Questions"
msgstr ""
#: ../../survey/overview/create.rst:24
msgid "Add sections and questions by clicking on the respective links."
msgstr ""
#: ../../survey/overview/create.rst:27
msgid ""
"On the *Sections and Questions* form, once the question type is chosen and "
"the answer added, under the tab *Options*, enable *Mandatory Answer*, and "
"set an *Error message* to be shown when the user tries to submit the survey "
"without answering the respective question."
msgstr ""
#: ../../survey/overview/create.rst:29
msgid ""
"Depending on the *Question Type*, the tab *Options* aggregates extra and "
"different possibilities. Examples:"
msgstr ""
#: ../../survey/overview/create.rst:31
msgid ""
"*Single Line Text Box* - can choose a minimum and maximum text length "
"(number of characters - spaces do not count), and its error message."
msgstr ""
#: ../../survey/overview/create.rst:33
msgid ""
"*Multiple choice: multiple answers allowed*: choose between radio buttons or"
" a dropdown menu list, and if you would like to have a comment field. If the"
" user select an answer and type a comment, the values are separately "
"recorded. Or, enable the comment field to be displayed as an answer choice, "
"with which a text type field is displayed."
msgstr ""
#: ../../survey/overview/create.rst:37
msgid ""
"*Matrix Type*: choose if you would like to have one or multiple choices per "
"row."
msgstr ""
#: ../../survey/overview/create.rst:44
msgid "Tab: Description"
msgstr ""
#: ../../survey/overview/create.rst:46
msgid ""
"Write a *Description* to be displayed under the title of the survey's "
"homepage."
msgstr ""
#: ../../survey/overview/create.rst:53
msgid "Click on *Edit* to personalize your pages with the website builder."
msgstr ""
#: ../../survey/overview/create.rst:56
msgid "Tab: Options"
msgstr ""
#: ../../survey/overview/create.rst:58
msgid ""
"Under the tab *Options*, choose the *Layout* of your questions. If choosing "
"*One page per section* or *One page per question*, an option *Back Button* "
"becomes available, which allows the user to go back pages."
msgstr ""
#: ../../survey/overview/create.rst:67
msgid "Test and share the survey"
msgstr ""
#: ../../survey/overview/create.rst:70
msgid ""
"Once your Survey is ready, *Test* it to avoid *Sharing* it with potential "
"errors. As answers get collected, click on *Answers* to access all the "
"details of the respondent and his answers."
msgstr ""
#: ../../survey/overview/create.rst:72
msgid ""
"By default, a filter *Except Test Entries* is applied to keep the list of "
"entries clean with only real participants."
msgstr ""
#: ../../survey/overview/create.rst:79
msgid ""
"Another way to access detailed answers is by going to "
":menuselection:`Participations --> Participations`."
msgstr ""
#: ../../survey/overview/create.rst:80
msgid "Click on *See results* to be redirected to an analytical page."
msgstr ""
#: ../../survey/overview/create.rst:87
#: ../../survey/overview/time_random.rst:34
msgid ":doc:`scoring`"
msgstr ""
#: ../../survey/overview/create.rst:88 ../../survey/overview/scoring.rst:35
msgid ":doc:`time_random`"
msgstr ""
#: ../../survey/overview/scoring.rst:3
msgid "Scoring Surveys"
msgstr ""
#: ../../survey/overview/scoring.rst:5
msgid ""
"To measure your respondent’s performance, knowledge of a subject, or overall"
" satisfaction, attach points to the answers of specific questions. The "
"points are summed up to give your respondent a final score."
msgstr ""
#: ../../survey/overview/scoring.rst:9
msgid ""
"On your survey’s form, click on *Add a question* and, under the tab "
"*Options*, choose between *Scoring with answers at the end* or *Scoring "
"without answers at the end*. Now, on your question’s form, set the right "
"answer and score."
msgstr ""
#: ../../survey/overview/scoring.rst:17
msgid ""
"Set the percentage score the user needs to achieve to have successfully "
"taken the survey. If enabling *Certificate*, choose its template. The "
"certification is automatically sent by email to the users who successfully "
"finish it."
msgstr ""
#: ../../survey/overview/scoring.rst:25
msgid ""
"Enable *Login required* to be able to *Give Badges*. Badges are related to "
"the eLearning section of your website. Besides the logged-in user, visitors "
"of the website that access the page *Courses* can also see the granted "
"badges."
msgstr ""
#: ../../survey/overview/time_random.rst:3
msgid "Time and Randomize Questions"
msgstr ""
#: ../../survey/overview/time_random.rst:6
msgid "Time Limit"
msgstr ""
#: ../../survey/overview/time_random.rst:10
msgid ""
"On timed surveys, respondents need to complete the survey within a certain "
"period of time. It can be used to ensure that all respondents get the same "
"amount of time to find the answers, or to decrease the chance of having them"
" looking at external resources."
msgstr ""
#: ../../survey/overview/time_random.rst:11
msgid "Set the *Time limit* under the tab *Options*."
msgstr ""
#: ../../survey/overview/time_random.rst:17
msgid ""
"A timer is shown on the pages so the user can keep track of the remaining "
"time. Surveys not \\ submitted by the *Time limit* do not have their answers"
" saved."
msgstr ""
#: ../../survey/overview/time_random.rst:21
msgid "Selection"
msgstr "Выбор"
#: ../../survey/overview/time_random.rst:25
msgid ""
"When you randomize a survey, you allow for the questions to be shuffled in a"
" random order every time someone opens the questionnaire. This can be useful"
" to avoid having respondents looking at each others' answers."
msgstr ""
#: ../../survey/overview/time_random.rst:27
msgid ""
"To do so, under the tab *Options*, enable *Randomized per section*. Now, "
"under the tab *Questions*, set how many of the questions in that section "
"should be taken into account during the shuffling."
msgstr ""
locale/ru/LC_MESSAGES/timesheets.po
+225
View File
@@ -0,0 +1,225 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015-TODAY, Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2020
# Ekaterina <nawsikaya@bk.ru>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 15:13+0000\n"
"Last-Translator: Ekaterina <nawsikaya@bk.ru>, 2020\n"
"Language-Team: Russian (https://www.transifex.com/odoo/teams/41243/ru/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ru\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3);\n"
#: ../../timesheets.rst:5
msgid "Timesheets"
msgstr "Табели"
#: ../../timesheets/overview.rst:3
msgid "Overview"
msgstr "Обзор"
#: ../../timesheets/overview/compare.rst:3
msgid "Compare Hours and do Analyses"
msgstr ""
#: ../../timesheets/overview/compare.rst:5
msgid ""
"Make sure your employees’ workload is being fairly distributed and control "
"your tasks to get powerful insights when comparing planned versus effective "
"hours."
msgstr ""
#: ../../timesheets/overview/compare.rst:9
msgid "Compare the planned and effective hours of your tasks"
msgstr ""
#: ../../timesheets/overview/compare.rst:11
msgid ""
"Go to :menuselection:`Project --> Reporting --> Tasks Analysis`, select the "
"*Pivot* view and refine your *Measures* to *Effective Hours* and *Planned "
"Hours*."
msgstr ""
#: ../../timesheets/overview/compare.rst:18
msgid ""
"Still on *Project*, under :menuselection:`Reporting --> Planning Analysis` "
"find a pivot view with an analysis of allocated and effective hours of your "
"tasks by user and start date, or by any of the other available filters."
msgstr ""
#: ../../timesheets/overview/compare.rst:27
msgid "HR analysis"
msgstr ""
#: ../../timesheets/overview/compare.rst:29
msgid ""
"Under :menuselection:`Timesheets --> Reporting --> Timesheet/Attendance` "
"have an overview of the worked hours and allocated time of your employees."
msgstr ""
#: ../../timesheets/overview/get_started.rst:3
msgid "Get Started with Timesheets"
msgstr ""
#: ../../timesheets/overview/get_started.rst:5
msgid ""
"When you use timesheets (from any device, anywhere) to track the time spent "
"on tasks, you are able to bill customers for the exact right amount they "
"should be billed. In addition to it, add a description of the work done to "
"have a reliable tracking and history, and compare the forecasted times, all "
"in favor of becoming a more proactive company."
msgstr ""
#: ../../timesheets/overview/get_started.rst:11
msgid "Choose an encoding unit"
msgstr ""
#: ../../timesheets/overview/get_started.rst:14
msgid ""
"Under :menuselection:`Timesheets --> Configuration --> Settings`, choose the"
" unit of measure to register your timesheet. This provides tools and widgets"
" to help you encoding."
msgstr ""
#: ../../timesheets/overview/get_started.rst:15
msgid "*Minimal duration* is the minimum time at which a task is recorded."
msgstr ""
#: ../../timesheets/overview/get_started.rst:18
msgid ""
"*Rounding up* allows you to time up or down to the nearest minutes or hours."
" For example: if the interval is set to 30min, a 14min entry will show up in"
" reports as 0min, and a 29min entry as 30min."
msgstr ""
#: ../../timesheets/overview/get_started.rst:25
msgid "Reportings are expressed in hours, the default value."
msgstr ""
#: ../../timesheets/overview/get_started.rst:28
msgid "Create a task from a SO & timesheet on it"
msgstr ""
#: ../../timesheets/overview/get_started.rst:30
msgid ""
"Under the *General Settings* of your product, categorize it as a service."
msgstr ""
#: ../../timesheets/overview/get_started.rst:34
msgid ""
"On the *Sales* tab, (section *Sales Invoicing Policy*) choose if you want to"
" invoice customers based on the quantity previous ordered (the one sent on a"
" quotation, for instance), on the time recorded (while the service was being"
" executed), or by manually adding the time spent when creating the invoice."
msgstr ""
#: ../../timesheets/overview/get_started.rst:37
msgid ""
"Chose the right *Service Tracking* for you and, from now on, when a sales "
"order is confirmed, Odoo automatically creates a task/project (if that was "
"the chosen option) and allows you to timesheet on it."
msgstr ""
#: ../../timesheets/overview/get_started.rst:44
msgid "Choose an Invoicing Policy"
msgstr ""
#: ../../timesheets/overview/get_started.rst:46
msgid ""
"Go to :menuselection:`Timesheets --> Configuration --> Settings` and choose "
"if you want the recorded time to be directly invoiced, or if it should be "
"approved first."
msgstr ""
#: ../../timesheets/overview/get_started.rst:54
msgid "Send reminders"
msgstr ""
#: ../../timesheets/overview/get_started.rst:57
msgid ""
"Choose to have an automatic email being sent to all users and managers who "
"have not recorded their times."
msgstr ""
#: ../../timesheets/overview/get_started.rst:59
msgid ""
"Go to :menuselection:`Timesheets --> Configuration --> Settings` and enable "
"the *Employee Reminder* and *Manager Reminder* features."
msgstr ""
#: ../../timesheets/overview/get_started.rst:66
msgid ""
"Odoo Timesheets continues to run even if there is no internet connection. "
"The data syncs once you are back online."
msgstr ""
#: ../../timesheets/overview/time_off.rst:3
msgid "Create Timesheets upon Time Off Validation"
msgstr ""
#: ../../timesheets/overview/time_off.rst:5
msgid ""
"Odoo automatically timesheets on project/tasks upon time off requests. This "
"allows for better overall control over the validation of timesheets, as it "
"does not leave place for forgetfulness and questions after hours that have "
"not been timesheeted by the employee."
msgstr ""
#: ../../timesheets/overview/time_off.rst:9
msgid ""
"Activate the :doc:`Developer mode <../../general/developer_mode/activate>`, "
"go to *Timesheets*, and change the *Project* and *Task* set by default, if "
"you like."
msgstr ""
#: ../../timesheets/overview/time_off.rst:16
msgid ""
"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`. Select"
" or create the needed type, and decide if you would like the requests to be "
"validated or not."
msgstr ""
#: ../../timesheets/overview/time_off.rst:26
msgid ""
"Now, once the employee has requested his time off and the request has been "
"validated (or not, depending on the setting chosen), the time is "
"automatically allocated on *Timesheets*, under the respective project and "
"task."
msgstr ""
#: ../../timesheets/overview/time_off.rst:27
msgid ""
"On the example below, the user requested *Paid Time off* from July 13th to "
"15th."
msgstr ""
#: ../../timesheets/overview/time_off.rst:33
msgid ""
"Considering that validation is not required, the requested time off is "
"automatically displayed in *Timesheets*. If validation is necessary, the "
"time is automatically allocated after the responsible person for validating "
"does it so."
msgstr ""
#: ../../timesheets/overview/time_off.rst:41
msgid ""
"Click on the magnifying glass, hovering over the concerned cell, to access "
"all the aggregated data on that cell (day), and see details regarding the "
"project/task."
msgstr ""
#: ../../timesheets/overview/time_off.rst:49
msgid ":doc:`compare`"
msgstr ""
locale/ru/LC_MESSAGES/website.po
+1763 -779
View File
File diff suppressed because it is too large Load Diff