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/uk/LC_MESSAGES/accounting.po
+8256 -7062
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/applications.po
+4 -8
View File
@@ -3,17 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -23,4 +19,4 @@ msgstr ""
#: ../../applications.rst:3
msgid "Applications"
msgstr "Заявки"
msgstr ""
locale/uk/LC_MESSAGES/contributing.po
+1735
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/crm.po
+326 -476
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/db_management.po
+87 -356
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/discuss.po
+453 -594
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/ecommerce.po
+92 -1100
View File
File diff suppressed because it is too large Load Diff
locale/uk/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: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/uk/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: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/uk/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: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/uk/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: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/uk/LC_MESSAGES/general.po
+1853 -442
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/getting_started.po
+68 -230
View File
@@ -3,17 +3,13 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -23,7 +19,7 @@ msgstr ""
#: ../../getting_started/documentation.rst:5
msgid "Basics of the QuickStart Methodology"
msgstr "Базова методологія швидкого старту"
msgstr ""
#: ../../getting_started/documentation.rst:7
msgid ""
@@ -31,13 +27,10 @@ msgid ""
"implementation methodology, and best practices to get started with our "
"product."
msgstr ""
"Цей документ підсумовує послуги Odoo Online, методологію впровадження наших "
"Пакетів Послуг та найкращі практичні поради для початку роботи з нашим "
"продуктом."
#: ../../getting_started/documentation.rst:12
msgid "1. The SPoC (*Single Point of Contact*) and the Consultant"
msgstr "1. Єдина контактна особа та консультант"
msgid "The SPoC (*Single Point of Contact*) and the Consultant"
msgstr ""
#: ../../getting_started/documentation.rst:14
msgid ""
@@ -46,10 +39,6 @@ msgid ""
" 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 ""
@@ -58,9 +47,6 @@ msgid ""
" of the implementation in Odoo and shares his expertise in terms of good "
"practices."
msgstr ""
"**Консультант Odoo забезпечує реалізацію проекту від А до Я**: від початку "
"до кінця проекту він забезпечує загальну послідовність впровадження Odoo та "
"ділиться своїм досвідом з точки зору належної практики."
#: ../../getting_started/documentation.rst:25
msgid ""
@@ -69,10 +55,6 @@ msgid ""
"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 ""
@@ -83,12 +65,6 @@ msgid ""
" meant to align on the business needs (SPoC) and to define the way those "
"needs will be implemented in Odoo (Consultant)."
msgstr ""
"**Оптимізація зустрічей**: консультант Odoo не бере участі у процесі "
"прийняття рішень з точки зору бізнесу, а також не має чітких процесів та "
"внутрішніх процедур компанії (крім конкретного запиту чи винятку). Зустрічі "
"щодо проекту, які відбудуться раз або два на тижні, призначені для "
"узгодження бізнес-потреб (єдина контактна особа) та визначення способу "
"реалізації цих потреб в Odoo (консультант)."
#: ../../getting_started/documentation.rst:39
msgid ""
@@ -96,35 +72,22 @@ msgid ""
"training to the SPoC so that he can pass on this knowledge to his "
"collaborators. In order for this approach to be successful, it is necessary "
"that the SPoC is also involved in its own rise in skills through self-"
"learning via the `Odoo documentation "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `The elearning "
"platform <https://odoo.thinkific.com/courses/odoo-functional>`__ and the "
"testing of functionalities."
"learning via the :doc:`Odoo documentation <../index>`, `The elearning "
"platform <https://odoo.com/learn>`_ and the testing of functionalities."
msgstr ""
"**Підготовка до навчання**: консультант Odoo надає функціональну підготовку "
"для єдиної контактної особи, щоб вона могла передавати ці знання своїм "
"співробітникам. Для того, щоби цей підхід був успішним, необхідно, щоби "
"контактна особа також брала участь у власному підвищенні навичок шляхом "
"самостійного навчання за допомогою `Документації Odoo "
"<http://www.odoo.com/documentation/user/10.0/index.html>`__, `Платформи "
"електронного навчання <https://odoo.thinkific.com/courses/odoo-"
"functional>`__ та тестування функціональних можливостей."
#: ../../getting_started/documentation.rst:47
msgid "2. Project Scope"
msgstr "2. Сфера застосування проекту"
#: ../../getting_started/documentation.rst:49
msgid "Project Scope"
msgstr ""
#: ../../getting_started/documentation.rst:51
msgid ""
"To make sure all the stakeholders involved are always aligned, it is "
"necessary to define and to make the project scope evolve as long as the "
"project implementation is pursuing."
msgstr ""
"Аби переконатися, що всі зацікавлені сторони завжди узгоджують процеси між "
"собою, необхідно визначати та вносити зміст проекту поки реалізується "
"проект."
#: ../../getting_started/documentation.rst:53
#: ../../getting_started/documentation.rst:55
msgid ""
"**A clear definition of the initial project scope**: A clear definition of "
"the initial needs is crucial to ensure the project is running smoothly. "
@@ -132,13 +95,8 @@ msgid ""
"the needs and the resulting decision-making process are more simple and more"
" clear."
msgstr ""
"**Чітке визначення початкового обсягу проекту**: Чітке визначення початкових"
" потреб має вирішальне значення для забезпечення безперебійного виконання "
"проекту. Дійсно, коли всі зацікавлені сторони поділяють одне і те ж бачення,"
" еволюцію потреб та процес прийняття рішень є більш простими та "
"зрозумілішими."
#: ../../getting_started/documentation.rst:59
#: ../../getting_started/documentation.rst:61
msgid ""
"**Phasing the project**: Favoring an implementation in several coherent "
"phases allowing regular production releases and an evolving takeover of Odoo"
@@ -146,13 +104,8 @@ msgid ""
"approach also helps to identify gaps and apply corrective actions early in "
"the implementation."
msgstr ""
"**Поступова реалізація проекту**: Сприяння впровадженню на декількох "
"узгоджених етапах, що дозволяють регулярно впроваджувати продукцію, та "
"поступово охоплювати Odoo кінцевими споживачами, довели свою ефективність із"
" часом. Цей підхід також допомагає виявити прогалини та застосовувати "
"коригувальні дії на початку впровадження."
#: ../../getting_started/documentation.rst:66
#: ../../getting_started/documentation.rst:68
msgid ""
"**Adopting standard features as a priority**: Odoo offers a great "
"environment to implement slight improvements (customizations) or more "
@@ -163,30 +116,19 @@ msgid ""
"should still be realized, its implementation will be carried out after an "
"experiment of the standard in production."
msgstr ""
"**Прийняття стандартних функцій в якості пріоритету**: Odoo пропонує чудове "
"середовище для здійснення незначних удосконалень (налаштувань) або більш "
"важливих (доробок). Тим не менше, прийняття стандартного рішення буде "
"віддавати перевагу якомога частіше, щоб оптимізувати час доставки проекту та"
" надавати користувачеві довгострокову стабільність та масштабність його "
"нового інструмента. В ідеалі, якщо поліпшення програмного забезпечення все-"
"таки має бути реалізоване, його впровадження буде здійснено після "
"експерименту зі стандартним впровадженням."
#: ../../getting_started/documentation.rst:80
msgid "3. Managing expectations"
msgstr "3. Управління очікуваннями"
#: ../../getting_started/documentation.rst:82
msgid "Managing expectations"
msgstr ""
#: ../../getting_started/documentation.rst:84
msgid ""
"The gap between the reality of an implementation and the expectations of "
"future users is a crucial factor. Three important aspects must be taken into"
" account from the beginning of the project:"
msgstr ""
"Розрив між реальним впровадження та майбутніми очікуваннями користувачів є "
"вирішальним чинником. З початку проекту необхідно враховувати три важливі "
"аспекти:"
#: ../../getting_started/documentation.rst:86
#: ../../getting_started/documentation.rst:88
msgid ""
"**Align with the project approach**: Both a clear division of roles and "
"responsibilities and a clear description of the operating modes (validation,"
@@ -195,14 +137,8 @@ msgid ""
"at the beginning of the project to align with these topics and regularly "
"check that this is still the case."
msgstr ""
"**Співпрацювати з підходом до проекту**: Як чіткий розподіл ролей та "
"відповідальності, так і чіткий опис режимів роботи (перевірка, вирішення "
"проблем та ін.) мають вирішальне значення для успішного впровадження Odoo. "
"Тому настійно рекомендуємо вживати необхідний час на початку проекту, щоби "
"вирівнятися з цими темами, і регулярно перевіряти, чи усе ще так, як було "
"заплановано."
#: ../../getting_started/documentation.rst:94
#: ../../getting_started/documentation.rst:96
msgid ""
"**Focus on the project success, not on the ideal solution**: The main goal "
"of the SPoC and the Consultant is to carry out the project entrusted to them"
@@ -216,69 +152,43 @@ msgid ""
"global relief is noted. Changes in business processes may also be proposed "
"to pursue this same objective."
msgstr ""
"**Зосередьтеся на успіху проекту, а не на ідеальному рішенні**: Головною "
"метою єдиної контактної особи та консультанта є виконання завданого ними "
"проекту, щоби забезпечити найефективніше рішення для задоволення виражених "
"потреб. Ця мета іноді може суперечити баченню ідеального рішення клієнта. У "
"такому випадку контактна особа та консультант застосовуватимуть правило "
"80-20: зосередитись на 80% виражених потреб та вилучити решту 20% найбільш "
"невигідних цілей з точки зору співвідношення витрат і вигоди (ці відсотки, "
"звичайно, можуть бути зміненими з часом). Тому, якщо глобальне рішення буде "
"визначено, буде прийнято інтегрувати найбільш трудомістку маніпуляцію. Зміни"
" в бізнес-процесах також можуть бути запропоновані для досягнення цієї ж "
"мети."
#: ../../getting_started/documentation.rst:108
#: ../../getting_started/documentation.rst:110
msgid ""
"**Specifications are always EXPLICIT**: Gaps between what is expected and "
"what is delivered are often a source of conflict in a project. In order to "
"avoid being in this delicate situation, we recommend using several types of "
"tools\\* :"
msgstr ""
"**Технічні характеристики завжди є ВИКЛЮЧНИМИ**: прогалини між тим, що "
"очікується і що доставляється, часто є джерелом конфлікту в проекті. Щоб "
"уникнути перебування в цій делікатній ситуації, ми рекомендуємо "
"використовувати кілька типів інструментів\\* :"
#: ../../getting_started/documentation.rst:113
#: ../../getting_started/documentation.rst:115
msgid ""
"**The GAP Analysis**: The comparison of the request with the standard "
"features proposed by Odoo will make it possible to identify the gap to be "
"filled by developments/customizations or changes in business processes."
msgstr ""
"**GAP аналіз**: порівняння запиту клієнта зі стандартними функціями, "
"запропонованими компанією Odoo, дозволить визначити розрив, який повинен "
"бути заповнений розробками/налаштуваннями або змінами бізнес-процесів."
#: ../../getting_started/documentation.rst:118
#: ../../getting_started/documentation.rst:120
msgid ""
"**The User Story**: This technique clearly separates the responsibilities "
"between the SPoC, responsible for explaining the WHAT, the WHY and the WHO, "
"and the Consultant who will provide a response to the HOW."
msgstr ""
"**Історія користувача**: Це технічно розділяє обов'язки між SPoC, "
"відповідальним за поясненням ЩО, ЧОМУ та ХТО, та консультантом, хто надасть "
"відповідь на питання ЯК."
#: ../../getting_started/documentation.rst:126
#: ../../getting_started/documentation.rst:128
msgid ""
"`The Proof of Concept <https://en.wikipedia.org/wiki/Proof_of_concept>`__ A "
"simplified version, a prototype of what is expected to agree on the main "
"lines of expected changes."
msgstr ""
"`Доказ концепції <https://en.wikipedia.org/wiki/Proof_of_concept>`__ "
"Cпрощена версія, прототип того, що очікується, узгоджується з основними "
"лініями очікуваних змін."
#: ../../getting_started/documentation.rst:130
#: ../../getting_started/documentation.rst:132
msgid ""
"**The Mockup**: In the same idea as the Proof of Concept, it will align with"
" the changes related to the interface."
msgstr ""
"**Макет**: у тій же ідеї, що й PoC, який буде відповідати змінам, пов'язаним"
" з інтерфейсом."
#: ../../getting_started/documentation.rst:133
#: ../../getting_started/documentation.rst:135
msgid ""
"To these tools will be added complete transparency on the possibilities and "
"limitations of the software and/or its environment so that all project "
@@ -286,37 +196,26 @@ msgid ""
"project. We will, therefore, avoid basing our work on hypotheses without "
"verifying its veracity beforehand."
msgstr ""
"До цих інструментів буде додано повну прозорість щодо можливостей та "
"обмежень програмного забезпечення та його оточення, щоб усі зацікавлені "
"сторони проекту могли чітко розуміти, що можна очікувати/досягти у проекті. "
"Тому ми не будемо базувати нашу роботу на гіпотезах, не перевіряючи "
"заздалегідь їх правдивість."
#: ../../getting_started/documentation.rst:139
#: ../../getting_started/documentation.rst:141
msgid ""
"*This list can, of course, be completed by other tools that would more "
"adequately meet the realities and needs of your project*"
msgstr ""
"*Цей список, звичайно, можна доповнити іншими інструментами, які би більш "
"адекватно відповідали реаліям та потребам вашого проекту*"
#: ../../getting_started/documentation.rst:143
msgid "4. Communication Strategy"
msgstr "4. Комунікаційна стратегія"
#: ../../getting_started/documentation.rst:145
msgid "Communication Strategy"
msgstr ""
#: ../../getting_started/documentation.rst:147
msgid ""
"The purpose of the QuickStart methodology is to ensure quick ownership of "
"the tool for end users. Effective communication is therefore crucial to the "
"success of this approach. Its optimization will, therefore, lead us to "
"follow those principles:"
msgstr ""
"Метою методології Швидкого старту є забезпечення швидкого володіння цим "
"інструментом для кінцевих користувачів. Тому ефективне спілкування має "
"вирішальне значення для успіху цього підходу. Тому його оптимізація приведе "
"нас до таких принципів:"
#: ../../getting_started/documentation.rst:150
#: ../../getting_started/documentation.rst:152
msgid ""
"**Sharing the project management documentation**: The best way to ensure "
"that all stakeholders in a project have the same level of knowledge is to "
@@ -325,62 +224,46 @@ msgid ""
"performed as part of the implementation for which the priority level and the"
" manager are clearly defined."
msgstr ""
"**Спільне використання документації з управління проектами**: Найкращий "
"спосіб забезпечити усіх зацікавлених сторін проекту володінням однаковим "
"рівнем знань, забезпечити прямий доступ до документу відстеження проекту "
"(Організатор проекту). Цей документ міститиме, принаймні, список завдань, що"
" будуть виконуватися як частина реалізації, для чого чітко визначений рівень"
" пріоритету та менеджер. "
#: ../../getting_started/documentation.rst:158
#: ../../getting_started/documentation.rst:160
msgid ""
"The Project Organizer is a shared project tracking tool that allows both "
"detailed tracking of ongoing tasks and the overall progress of the project."
msgstr ""
"Організатор проекту - це інструмент відстеження проектів, який дозволяє як "
"детальне відстеження поточних завдань, так і загальний прогрес проекту."
#: ../../getting_started/documentation.rst:162
#: ../../getting_started/documentation.rst:164
msgid ""
"**Report essential information**: In order to minimize the documentation "
"time to the essentials, we will follow the following good practices:"
msgstr ""
"**Зверніть увагу на важливу інформацію**: щоб мінімізувати час документації "
"до найважливіших вимог, ми дотримуємось наступних правильних практик:"
#: ../../getting_started/documentation.rst:166
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr "Протоколи зустрічі будуть обмежені лише рішеннями та перевірками;"
#: ../../getting_started/documentation.rst:168
msgid "Meeting minutes will be limited to decisions and validations;"
msgstr ""
#: ../../getting_started/documentation.rst:170
msgid ""
"Project statuses will only be established when an important milestone is "
"reached;"
msgstr ""
"Статуси проекту визначаються лише тоді, коли досягнуто важливого етапу;"
#: ../../getting_started/documentation.rst:171
#: ../../getting_started/documentation.rst:173
msgid ""
"Training sessions on the standard or customized solution will be organized."
msgstr ""
"Будуть організовані навчальні курси по стандартному або індивідуальному "
"рішенню."
#: ../../getting_started/documentation.rst:175
msgid "5. Customizations and Development"
msgstr "5. Налаштування та розробка"
#: ../../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 ""
"Odoo - це програмне забезпечення, відоме своєю гнучкістю та важливою "
"здатністю до еволюції. Однак значна частина розвитку суперечить швидкій та "
"стабільній реалізації. Ось чому рекомендується:"
#: ../../getting_started/documentation.rst:182
#: ../../getting_started/documentation.rst:184
msgid ""
"**Develop only for a good reason**: The decision to develop must always be "
"taken when the cost-benefit ratio is positive (saving time on a daily basis,"
@@ -393,17 +276,8 @@ msgid ""
"requests are dropped after a few weeks of using standard Odoo (see "
"\"Adopting the standard as a priority\")."
msgstr ""
"**Розвиватися лише з вагомих причин**: рішення про розробку завжди повинно "
"бути прийняте, коли співвідношення витрат і вигод є позитивним (економія "
"часу на щоденній основі тощо). Наприклад, краще реалізувати значний "
"розвиток, щоб скоротити час щоденної експлуатації, а не виконувати операцію "
"лише один раз на квартал. Загальновизнано, що чим ближче рішення до "
"стандарту, тим легше і більш плавно відбувається процес міграції, і чим "
"нижчі витрати на обслуговування для обох сторін. Крім того, досвід показує "
"нам, що 60% первинних запитів на розробку знищуються через кілька тижнів "
"використання стандартного Odoo (див. \"Прийняття стандарту як пріоритет\")."
#: ../../getting_started/documentation.rst:194
#: ../../getting_started/documentation.rst:196
msgid ""
"**Replace, without replicate**: There is a good reason for the decision to "
"change the management software has been made. In this context, the moment of"
@@ -411,70 +285,53 @@ msgid ""
" both in terms of how the software will be used and at the level of the "
"business processes of the company."
msgstr ""
"**Заміна без реплікації**: є вагомі підстави для прийняття рішення про зміну"
" програмного забезпечення для управління. У цьому контексті момент "
"реалізації є правильним моментом прийняття і навіть є ініціатором зміни як з"
" точки зору використання програмного забезпечення, так і на рівні бізнес-"
"процесів компанії."
#: ../../getting_started/documentation.rst:202
msgid "6. Testing and Validation principles"
msgstr "6. Тестування та принципи перевірки"
#: ../../getting_started/documentation.rst:204
msgid "Testing and Validation principles"
msgstr ""
#: ../../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:208
#: ../../getting_started/documentation.rst:210
msgid ""
"**Role distribution**: In this context, the Consultant will be responsible "
"for delivering a solution corresponding to the defined specifications; the "
"SPoC will have to test and validate that the solution delivered meets the "
"requirements of the operational reality."
msgstr ""
"**Розподіл ролей**: у цьому контексті консультант буде відповідати за "
"надання рішення, що відповідає визначеним специфікаціям; контактна особа "
"повинна буде протестувати та підтвердити, що рішення, яке постачається, "
"відповідає вимогам операційної реальності."
#: ../../getting_started/documentation.rst:214
#: ../../getting_started/documentation.rst:216
msgid ""
"**Change management**: When a change needs to be made to the solution, the "
"noted gap is caused by:"
msgstr ""
"**Управління змінами**: коли необхідно внести зміни до рішення, зазначений "
"розрив обумовлений:"
#: ../../getting_started/documentation.rst:218
#: ../../getting_started/documentation.rst:220
msgid ""
"A difference between the specification and the delivered solution - This is "
"a correction for which the Consultant is responsible"
msgstr ""
"Різницею між специфікацією та доставленим рішенням - це виправлення, за яке "
"відповідає консультант."
#: ../../getting_started/documentation.rst:220
#: ../../getting_started/documentation.rst:223
msgid "**or**"
msgstr "**або**"
msgstr ""
#: ../../getting_started/documentation.rst:222
#: ../../getting_started/documentation.rst:225
msgid ""
"A difference between the specification and the imperatives of operational "
"reality - This is a change that is the responsibility of SPoC."
msgstr ""
"Різницею між специфікацією та вимогами операційної реальності - це зміна, на"
" яку відповідає контактна особа."
#: ../../getting_started/documentation.rst:226
msgid "7. Data Imports"
msgstr "7. Імпорт даних"
#: ../../getting_started/documentation.rst:229
msgid "Data Imports"
msgstr ""
#: ../../getting_started/documentation.rst:228
#: ../../getting_started/documentation.rst:231
msgid ""
"Importing the history of transactional data is an important issue and must "
"be answered appropriately to allow the project running smoothly. Indeed, "
@@ -482,23 +339,15 @@ msgid ""
"prevent production from happening in time. To do this as soon as possible, "
"it will be decided :"
msgstr ""
"Імпорт історії транзакційних даних є важливою проблемою, і відповідним чином"
" потрібно відповісти на це, щоб забезпечити безперебійну роботу проекту. "
"Дійсно, це завдання може зайняти багато часу, і, якщо його пріоритет не є "
"чітко визначеним, запобігти впровадженню вчасно. Щоб зробити це якомога "
"швидше, буде вирішено:"
#: ../../getting_started/documentation.rst:234
#: ../../getting_started/documentation.rst:237
msgid ""
"**Not to import anything**: It often happens that after reflection, "
"importing data history is not considered necessary, these data being, "
"moreover, kept outside Odoo and consolidated for later reporting."
msgstr ""
"**Не імпортувати нічого**: Часто буває, що після відображення імпортування "
"історії даних стає не необхідним, причому ці дані зберігаються поза межами "
"Odoo і консолідуються для подальшої звітності."
#: ../../getting_started/documentation.rst:239
#: ../../getting_started/documentation.rst:242
msgid ""
"**To import a limited amount of data before going into production**: When "
"the data history relates to information being processed (purchase orders, "
@@ -506,36 +355,25 @@ msgid ""
"available from the first day of use in production is real. In this case, the"
" import will be made before the production launch."
msgstr ""
"**Щоб імпортувати обмежену кількість даних перед початком впровадження**: "
"коли історія даних стосується оброблюваної інформації (наприклад, замовлення"
" на купівлю, рахунки-фактури, відкриті проекти), необхідність мати цю "
"інформацію з першого дня використання у впровадженні - це реально. У цьому "
"випадку імпорт буде здійснюватися до початку запуску впровадження."
#: ../../getting_started/documentation.rst:246
#: ../../getting_started/documentation.rst:249
msgid ""
"**To import after production launch**: When the data history needs to be "
"integrated with Odoo mainly for reporting purposes, it is clear that these "
"can be integrated into the software retrospectively. In this case, the "
"production launch of the solution will precede the required imports."
msgstr ""
"**Імпорт після запуску впровадження**: коли історія даних повинна бути "
"інтегрована з Odoo, в основному для цілей звітування, то очевидно, що вони "
"можуть бути інтегровані в програмне забезпечення ретроспективно. У цьому "
"випадку запуск впровадження буде передувати необхідному імпорту."
#: ../../getting_started/documentation.rst:253
msgid "8. Support"
msgstr "8. Підтримка"
#: ../../getting_started/documentation.rst:256
msgid "Support"
msgstr ""
#: ../../getting_started/documentation.rst:255
#: ../../getting_started/documentation.rst:258
msgid ""
"When your project is put in production, our support teams take care of your "
"questions or technical issues."
msgstr ""
"Коли ваш проект береться у виконання, наші команди підтримки піклуються про "
"ваші запитання чи технічні проблеми."
#: ../../getting_started/documentation.rst:258
#: ../../getting_started/documentation.rst:261
msgid "See :ref:`support-expectations`."
msgstr "Перегляньте :ref:`support-expectations`."
msgstr ""
locale/uk/LC_MESSAGES/helpdesk.po
+682 -429
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/index.po
+7 -4
View File
@@ -3,14 +3,17 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:40+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
locale/uk/LC_MESSAGES/inventory.po
+2152 -2215
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/iot.po
+36 -41
View File
@@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -64,22 +64,35 @@ msgid "Power on the IoT Box."
msgstr "Увімкніть IoT Box."
#: ../../iot/config/connect.rst:28
msgid "Then click on the Scan button."
msgstr "Потім натисніть на кнопку Сканувати."
msgid ""
"Read the Pairing Code from a screen or a receipt printer connected to the "
"IoT Box."
msgstr ""
#: ../../iot/config/connect.rst:34
#: ../../iot/config/connect.rst:32
msgid "Input the Pairing Code and click on the Pair button."
msgstr ""
#: ../../iot/config/connect.rst:35
msgid ""
"Recent changes in modern web browsers forced us to modify the connection "
"wizard. If your screen is different from the screenshots, make sure that the"
" ``iot_pairing`` module is installed."
msgstr ""
#: ../../iot/config/connect.rst:40
msgid "WiFi Connection"
msgstr "З'єднання з WiFi"
#: ../../iot/config/connect.rst:36
#: ../../iot/config/connect.rst:42
msgid "Power on the IoT Box"
msgstr "Увімкніть IoT Box."
#: ../../iot/config/connect.rst:38
#: ../../iot/config/connect.rst:44
msgid "Copy the token"
msgstr "Скопіюйте токен"
#: ../../iot/config/connect.rst:43
#: ../../iot/config/connect.rst:48
msgid ""
"Connect to the IoT Box WiFi Network (make sure there is no ethernet cable "
"plugged in your computer)."
@@ -87,7 +100,7 @@ msgstr ""
"Підключіть WiFi до IoT Box (переконайтеся, що в комп'ютері не підключено "
"кабель Ethernet)."
#: ../../iot/config/connect.rst:49
#: ../../iot/config/connect.rst:53
msgid ""
"You will be redirected to the IoT Box Homepage (if it doesn't work, connect "
"to the IP address of the box). Give a name to your IoT Box (not required) "
@@ -97,7 +110,7 @@ msgstr ""
"підключіться до IP-адреси коробки). Дайте назву вашому IoT Box (не "
"обов'язково) і вставте токен, а потім натисніть кнопку Далі."
#: ../../iot/config/connect.rst:57
#: ../../iot/config/connect.rst:60
msgid ""
"If you are on Runbot, do not forget to add the -all or -base in the token "
"(e.g. this token **http://375228-saas-11-5-iot-"
@@ -109,7 +122,7 @@ msgstr ""
"f3f920.runbot16.odoo.com\\|4957098401** повинен стати "
"**http://375228-saas-11-5-iot-f3f920-all.runbot16.odoo.com\\|4957098401**)."
#: ../../iot/config/connect.rst:63
#: ../../iot/config/connect.rst:66
msgid ""
"Choose the WiFi network you want to connect with (enter the password if "
"there is one) and click on Submit. Wait a few seconds before being "
@@ -119,11 +132,11 @@ msgstr ""
"є) і натисніть кнопку Надіслати. Зачекайте кілька секунд, перш ніж "
"перенаправитися у базу даних."
#: ../../iot/config/connect.rst:70
#: ../../iot/config/connect.rst:72
msgid "You should now see the IoT Box."
msgstr "Тепер ви можете бачити IoT Box."
#: ../../iot/config/connect.rst:76
#: ../../iot/config/connect.rst:78
msgid "IoT Box Schema"
msgstr "Схема IoT Box"
@@ -145,13 +158,10 @@ msgstr "Оновлення вашої SD картки через Etcher"
#: ../../iot/config/flash_sdcard.rst:11
msgid ""
"Go to Balena’s website and download `Etcher <http://wwww.balena.org>`__, "
"Go to Balena’s website and download `Etcher <https://www.balena.io/>`__, "
"It’s a free and open-source utility used for burning image files. Install "
"and launch it."
msgstr ""
"Перейдіть на веб-сайт Balena та завантажте `Etcher "
"<http://wwww.balena.org>`__, Це безкоштовно, а утиліти з відкритим кодом "
"використовуються для для запису фалів зображень. Встановіть та запустіть це."
#: ../../iot/config/flash_sdcard.rst:15
msgid ""
@@ -211,19 +221,12 @@ msgstr ""
msgid ""
"If your IoT Box image is from an earlier version, then you will have to "
"reflash the SD card of your IoT Box to update the image (the latest image "
"can be found `here <http://nightly/odoo.com>`__)."
"can be found `here <http://nightly.odoo.com/master/posbox/iotbox/>`__)."
msgstr ""
"Якщо ваше зображення IoT Box старішої версії, тоді вам необхідно "
"перезаписати SD картку вашого IoT Box, щоби оновити зображення (найновіше "
"зображення можна знайти `тут <http://nightly/odoo.com>`__)."
#: ../../iot/config/iot_notfound.rst:23
msgid ""
"You can find the documentation about SD card flashing here (`here "
"<https://docs.google.com/document/d/1bqKsZhWqMqI4mhv4ltF61M_QPiBCHygYjjvkhsCTdaY/edit>`__)."
#: ../../iot/config/iot_notfound.rst:24
msgid ":doc:`flash_sdcard`"
msgstr ""
"Ви можете знайти документацію про перепрошивку SD картки (`тут "
"<https://docs.google.com/document/d/1bqKsZhWqMqI4mhv4ltF61M_QPiBCHygYjjvkhsCTdaY/edit>`__)."
#: ../../iot/config/pos.rst:3
msgid "Use the IoT Box for the PoS"
@@ -292,12 +295,8 @@ msgstr "Встановіть"
#: ../../iot/config/pos.rst:37
msgid ""
"To connect hardware to the PoS, the first step is to connect an IoT Box to "
"your database. For this, follow this `documentation "
"<https://docs.google.com/document/d/1vhWrSSlSdJcRYe4tjPpXKYVMTD47lVK3ysyYc7tJDlA/edit#>`__."
"your database. For this, follow this :doc:`documentation <connect>`."
msgstr ""
"Щоби підключити обладнання, першим кроком є підключення IoT Box до вашої "
"бази даних. Для цього перегляньте `документацію "
"<https://docs.google.com/document/d/1vhWrSSlSdJcRYe4tjPpXKYVMTD47lVK3ysyYc7tJDlA/edit#>`__."
#: ../../iot/config/pos.rst:44
msgid "Then, you have to connect the peripheral devices to your IoT Box."
@@ -369,13 +368,9 @@ msgstr ""
#: ../../iot/config/pos.rst:73
msgid ""
"Once it's done, you can connect the IoT Box to your PoS. For this, go in "
"Point of Sale > Configuration > PoS, tick the box \"IoT Box\" and select the"
" IoT Box you want to connect with. Save the changes."
":menuselection:`Point of Sale --> Configuration --> PoS`, tick the box \"IoT"
" Box\" and select the IoT Box you want to connect with. Save the changes."
msgstr ""
"Як тільки це зроблено, ви можете підключити IoT Box до вашої точки продажу. "
"Для цього перейдіть у Точку продажу > Налаштування > Точка продажу, позначте"
" \"IoT Box\" і виберіть IoT Box, із яким ви хочете з'єднатися. Збережіть "
"зміни."
#: ../../iot/config/pos.rst:77
msgid "Set up is done, you can launch a new PoS Session."
locale/uk/LC_MESSAGES/livechat.po
+198 -175
View File
@@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,230 +22,253 @@ msgstr ""
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (n % 10 ==0 || (n % 10 >=5 && n % 10 <=9) || (n % 100 >=11 && n % 100 <=14 )) ? 2: 3);\n"
#: ../../livechat/livechat.rst:5
msgid "Live Chat"
msgstr "Живий чат"
#: ../../livechat/overview.rst:3
msgid "Overview"
msgstr "Загальний огляд"
#: ../../livechat/livechat.rst:8
msgid "Chat in real time with website visitors"
msgstr "Спілкуйтеся з відвідувачами сайту в реальному часі"
#: ../../livechat/livechat.rst:10
msgid ""
"With Odoo Live Chat, you can establish a direct contact with your website "
"visitors. A simple dialog box will be available on their screen and will "
"allow them to get in touch with one of your sales representatives. This way,"
" you can easily turn prospects into potential business opportunities. You "
"will also be able to provide assistance to your customers. Overall, this is "
"the perfect tool to improve customer satisfaction."
#: ../../livechat/overview/get_started.rst:3
msgid "Get Started with Live Chat"
msgstr ""
"З Онлайн-чатом Odoo ви можете встановити прямий контакт із відвідувачами "
"вашого веб-сайту. Просте діалогове вікно з'явиться на екрані та дозволить їм"
" зв'язатися з одним із ваших торгових представників. Таким чином, ви можете "
"легко перетворити ліди у нагоди. Ви також зможете надавати допомогу своїм "
"клієнтам. Загалом, це ідеальний інструмент для покращення задоволеності "
"клієнтів."
#: ../../livechat/livechat.rst:19
msgid "Configuration"
msgstr "Налаштування"
#: ../../livechat/livechat.rst:21
#: ../../livechat/overview/get_started.rst:5
msgid ""
"To get the Live Chat feature, open the Apps module, search for \"Live Chat\""
" and then click on install."
"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/livechat.rst:27
#: ../../livechat/overview/get_started.rst:10
msgid "Set up"
msgstr ""
#: ../../livechat/overview/get_started.rst:12
msgid ""
"The Live Chat module provides you a direct access to your channels. There, "
"operators can easily join and leave the chat."
"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/livechat.rst:34
msgid "Add the live chat to an Odoo website"
msgstr "Додайте онлайн-чат на веб-сайт Odoo"
#: ../../livechat/livechat.rst:36
#: ../../livechat/overview/get_started.rst:21
msgid ""
"If your website was created with Odoo, then the live chat is automatically "
"added to it. All that is left to do, is to go to :menuselection:`Website -->"
" Configuration --> Settings` to select the channel to be linked to the "
"website."
"Select the channel to be linked to your website or create one on the fly."
msgstr ""
"Якщо ваш веб-сайт був створений за допомогою Odoo, то автоматично буде "
"доданий онлайн-чат. Все, що потрібно зробити, це перейти на :menuselection"
":`Веб-сайт --> Налаштування --> Налаштування`, щоби вибрати канал, який буде"
" пов'язаний з веб-сайтом."
#: ../../livechat/livechat.rst:45
msgid "Add the live chat to an external website"
msgstr "Додайте онлайн-чат на зовнішній веб-сайт"
#: ../../livechat/overview/get_started.rst:27
msgid "For both scenarios, under:"
msgstr ""
#: ../../livechat/livechat.rst:47
#: ../../livechat/overview/get_started.rst:30
msgid ""
"If your website was not created with Odoo, go to the Live Chat module and "
"then select the channel to be linked. There, you can simply copy paste the "
"code available into your website. A specific url you can send to customers "
"or suppliers for them to access the live chat is also provided."
"- **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 ""
"Якщо ваш веб-сайт не був створений за допомогою Odoo, перейдіть до модуля "
"Онлайн-чат, а потім виберіть канал, який потрібно прив'язати. Там ви можете "
"просто скопіювати доступний код на свій веб-сайт. Також надається конкретна "
"URL-адреса, яку ви можете надіслати клієнтам або постачальникам для доступу "
"до чату."
#: ../../livechat/livechat.rst:54
msgid "Hide / display the live chat according to rules"
msgstr "Сховайте/покажіть онлайн-чат відповідно до правил"
#: ../../livechat/livechat.rst:56
#: ../../livechat/overview/get_started.rst:33
msgid ""
"Rules for the live chat can be defined on the channel form. For instance, "
"you can choose to display the chat in the countries you speak the language "
"of. On the contrary, you are able to hide the chat in countries your company"
" does not sell in. If you select *Auto popup*, you can also set the length "
"of time it takes for the chat to appear."
"- **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/livechat.rst:66
msgid "Prepare automatic messages"
msgstr "Підготуйте автоматичні повідомлення"
#: ../../livechat/livechat.rst:68
#: ../../livechat/overview/get_started.rst:36
msgid ""
"On the channel form, in the *Options* section, several messages can be typed"
" to appear automatically on the chat. This will entice visitors to reach you"
" through the live chat."
"- **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/livechat.rst:76
msgid "Start chatting with customers"
msgstr "Почніть спілкуватися з клієнтами"
#: ../../livechat/livechat.rst:78
#: ../../livechat/overview/get_started.rst:43
msgid ""
"In order to start chatting with customers, first make sure that the channel "
"is published on your website. To do so, select *Unpublished on Website* on "
"the top right corner of the channel form to toggle the *Published* setting. "
"Then, the live chat can begin once an operator has joined the channel."
"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/livechat.rst:88
#: ../../livechat/overview/get_started.rst:48
msgid "External options"
msgstr ""
#: ../../livechat/overview/get_started.rst:51
msgid ""
"If no operator is available and/or if the channel is unpublished on the "
"website, then the live chat button will not appear to visitors."
"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/livechat.rst:92
#: ../../livechat/overview/get_started.rst:52
msgid ""
"Conversations initiated by visitors also appear in the Discuss module in "
"addition to popping up as a direct message. Therefore, inquiries can be "
"answered wherever you are in Odoo."
"Odoo also offers an URL you can send to users so they can have access to a "
"single live chat page."
msgstr ""
"Розмова, ініційована відвідувачами, також з'вляється у модулі Обговорення "
"крім того, що з'являється як пряме повідомлення. Тому на запити можна "
"відповісти, де б ви не були в Odoo."
#: ../../livechat/livechat.rst:96
#: ../../livechat/overview/get_started.rst:59
msgid "Managing chat requests"
msgstr ""
#: ../../livechat/overview/get_started.rst:61
msgid ""
"If there are several operators who have all joined a channel, the system "
"will dispatch visitor sessions randomly between them."
"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/livechat.rst:100
#: ../../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/livechat.rst:102
#: ../../livechat/overview/responses.rst:11
msgid ""
"Commands are useful shortcuts for completing certain actions or to access "
"information you might need. To use this feature, simply type the commands "
"into the chat. The following actions are available :"
"Commands are shortcuts that do specific actions within the chat window:"
msgstr ""
"Команди є корисними для виконання певних дій або доступу до інформації, яка "
"вам може знадобитися. Щоби використовувати цю функцію, просто введіть "
"команди в чат. Доступні наступні дії:"
#: ../../livechat/livechat.rst:106
msgid "**/help** : show a helper message."
msgstr "**/help** : показати допоміжне повідомлення."
#: ../../livechat/overview/responses.rst:13
msgid "**/help**: shows a help message."
msgstr ""
#: ../../livechat/livechat.rst:108
msgid "**/helpdesk** : create a helpdesk ticket."
msgstr "**/helpdesk** : створити заявку служби підтримки."
#: ../../livechat/overview/responses.rst:14
msgid "**/helpdesk**: creates a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:110
msgid "**/helpdesk\\_search** : search for a helpdesk ticket."
msgstr "**/helpdesk\\_search** : шукати заявку для служби підтримки."
#: ../../livechat/overview/responses.rst:15
msgid "**/helpdesk_search**: searches for a helpdesk ticket."
msgstr ""
#: ../../livechat/livechat.rst:112
msgid "**/history** : see 15 last visited pages."
msgstr "**/history** : дивитись 15 останніх відвіданих сторінок."
#: ../../livechat/overview/responses.rst:16
msgid "**/history**: shows the last 15 visited pages."
msgstr ""
#: ../../livechat/livechat.rst:114
msgid "**/lead** : create a new lead."
msgstr "**/lead** : створити новий лід."
#: ../../livechat/overview/responses.rst:17
msgid "**/lead**: creates a new lead."
msgstr ""
#: ../../livechat/livechat.rst:116
msgid "**/leave** : leave the channel."
msgstr "**/leave** : залишити канал."
#: ../../livechat/overview/responses.rst:18
msgid "**/leave**: leaves the channel."
msgstr ""
#: ../../livechat/livechat.rst:119
#: ../../livechat/overview/responses.rst:0
msgid ""
"If a helpdesk ticket is created from the chat, then the conversation it was "
"generated from will automatically appear as the description of the ticket. "
"The same goes for the creation of a lead."
"- 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/livechat.rst:124
#: ../../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/livechat.rst:126
#: ../../livechat/overview/responses.rst:40
msgid ""
"Canned responses allow you to create substitutes to generic sentences you "
"frequently use. Typing a word instead of several will save you a lot of "
"time. To add canned responses, go to :menuselection:`LIVE CHAT --> "
"Configuration --> Canned Responses` and create as many as you need to. Then,"
" to use them during a chat, simply type \":\" followed by the shortcut you "
"assigned."
"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 ""
"Фіксовані відповіді дозволяють створювати замінники загальних речень, які ви"
" часто використовуєте. Введіть слово замість кількох, це заощадить вам "
"багато часу. Щоб додати фіксовані відповіді, перейдіть до :menuselection"
":`ОНЛАЙН-ЧАТ --> Налаштування --> Фіксовані відповіді` та створіть стільки "
"відповідей, скільки потрібно. Щоби використовувати їх під час чату, просто "
"введіть \":\" до ярлика, який ви призначили."
#: ../../livechat/livechat.rst:136
#: ../../livechat/overview/responses.rst:41
msgid ""
"You now have all of the tools needed to chat in live with your website "
"visitors, enjoy !"
"To use them during a conversation, simply type **:** followed by the "
"shortcut word you created."
msgstr ""
"Тепер у вас є всі інструменти, необхідні для спілкування в онлайн з "
"відвідувачами вашого сайту. Насолоджуйтеся!"
locale/uk/LC_MESSAGES/manufacturing.po
+300 -133
View File
@@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -149,11 +149,11 @@ msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:24
msgid ""
"Before creating your *BoM*, you have to create the product using the *BoM* "
"and, at least, one of the components. Go to the *Master Data* menu > "
"*Products* and create both the finished product and the component."
"and, at least, one of the components. Go to the :menuselection:`Master Data "
"menu --> Products` and create both the finished product and the component."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:29
#: ../../manufacturing/management/bill_configuration.rst:28
msgid ""
"Once done, go to the *Bills of Materials* menu under *Master Data*. Now, "
"create it. Choose the product from the dropdown menu and add your components"
@@ -161,64 +161,64 @@ msgid ""
"*Manufacture this Product*."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:38
#: ../../manufacturing/management/bill_configuration.rst:37
msgid "Using the same BoM to describe Variants"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:40
#: ../../manufacturing/management/bill_configuration.rst:39
msgid ""
"As said above, you can use *BoM* for *Product Variants*. It is basically the"
" same as for the standard product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:43
#: ../../manufacturing/management/bill_configuration.rst:42
msgid ""
"If your *BoM* is for one variant only, then specify which one in the "
"*Product Variant* field. If not, specify the variant it is consumed for on "
"each component line. You can add several variants for each component."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:52
#: ../../manufacturing/management/bill_configuration.rst:51
msgid "Adding a routing"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:54
#: ../../manufacturing/management/bill_configuration.rst:53
msgid ""
"You can add routing to your *BoM*. You will do this if you need to define a "
"series of operations required by your manufacturing process. To use it, "
"enable the *Work Orders* feature in the *Manufacturing* app settings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:63
#: ../../manufacturing/management/bill_configuration.rst:62
msgid ""
"Each *BoM* can have only one routing while each routing can be used multiple"
" times."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:66
#: ../../manufacturing/management/bill_configuration.rst:65
msgid ""
"Now that you have created your routing, add it to your *BoM*. You can select"
" when, in the work operations, your components are consumed with the "
"dropdown menu."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:74
#: ../../manufacturing/management/bill_configuration.rst:73
msgid "Adding By-Products"
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:76
#: ../../manufacturing/management/bill_configuration.rst:75
msgid ""
"In Odoo, a *by-product* is any product produced by a *BoM* in addition to "
"the primary product."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:79
#: ../../manufacturing/management/bill_configuration.rst:78
msgid ""
"To add *by-products* to a *BoM*, you will first need to enable them from the"
" *Manufacturing* app settings."
msgstr ""
#: ../../manufacturing/management/bill_configuration.rst:85
#: ../../manufacturing/management/bill_configuration.rst:84
msgid ""
"Once the feature is enabled, you can add your *By-Products* to your *BoMs*. "
"You can add as many *By-Products* as you want. Just keep in mind that you "
@@ -248,7 +248,7 @@ msgstr ""
#: ../../manufacturing/management/flexible_components_consumption.rst:16
#: ../../manufacturing/management/kit_shipping.rst:31
#: ../../manufacturing/management/kit_shipping.rst:66
#: ../../manufacturing/management/subcontracting.rst:9
#: ../../manufacturing/management/subcontracting.rst:26
#: ../../manufacturing/management/use_mps.rst:9
msgid "Configuration"
msgstr "Налаштування"
@@ -755,153 +755,320 @@ msgid ""
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:3
msgid "Subcontract the manufacturing"
msgid "Subcontract your Manufacturing"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:5
msgid ""
"Some businesses subcontract the production of some finished products through"
" subcontractors. This can be easily managed through Odoo."
"Outsourcing a portion of some or all your company’s manufacturing needs is "
"not easy. To make it work right, you have to:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:8
msgid "Manage the inventory of raw materials at your subcontractor;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:9
msgid ""
"Ship new materials to your subcontractors based on your forecasted demand;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:11
msgid ""
"Go to the *Manufacturing app > Configuration > Settings* and tick the box "
"*Subcontracting*."
"Keep track of manufacturing operations done at the subcontractor location;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:17
#: ../../manufacturing/management/subcontracting.rst:13
msgid "Control incoming goods quality;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:14
msgid "Control subcontractors bills."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:16
msgid ""
"You can now define subcontracted *Bill of Materials*. Therefore, you need to"
" go to *Manufacturing > Master Data > Bill of Materials* and hit *Create*. "
"In this *BoM*, list the components which will be used by the subcontractor "
"to manufacture the subcontracted finished product. Specify that the *BoM* "
"type is *Subcontracting*."
"Here is an example of subcontracting the manufacturing of “C”, which is "
"produced out of raw materials “A” and “B”."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:22
msgid "You can also define subcontractors on the BoM."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:24
msgid "If no subcontractor is set, the BoM can be used by any subcontractor"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:26
msgid "If some are set, the BoM can only be used for those subcontractors"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:32
msgid "Receive or buy a subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:34
msgid "You have two options to trigger the subcontracting of a product:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:36
#: ../../manufacturing/management/subcontracting.rst:23
msgid ""
"**Option A**: You can buy the subcontracted product from your subcontractor"
"With its subcontracting feature, Odoo helps you handle this flow easily."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:28
msgid ""
"To use the subcontracting feature, go to :menuselection:`Manufacturing --> "
"Configuration --> Settings` and tick the box *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:35
msgid ""
"To define if a product must be subcontracted, use a *Bill of Materials "
"(BoM)* of type *Subcontracting*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:38
msgid "**Option B**: You can directly receive the subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:40
msgid "Let’s start with option A (option B is just a simpler version of it)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:42
msgid ""
"Create a new purchase order. The vendor must be a subcontractor. The unit "
"price should be the cost you are paying to the subcontractor for the "
"subcontracting (thus, it’s not necessarily the total cost of the "
"subcontracted product)."
"To create a new *BoM*, go to :menuselection:`Manufacturing --> Master Data "
"--> Bill of Materials` and hit create. Then, list the components your "
"subcontractor needs to manufacture the product. For costing purposes, you "
"might want to register all the components, even the ones that are sourced "
"directly from the subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:50
#: ../../manufacturing/management/subcontracting.rst:44
msgid ""
"The validation of the purchase order automatically creates the receipt. "
"Whenever you receive the product, you can validate the receipt. The "
"following stock moves are created:"
"Once you have set the *BoM Type* to *Subcontracting*, specify one or several"
" subcontractors."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:52
msgid "Basic Subcontracting Flow"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:54
msgid "For the components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:56
msgid "From Subcontracting To Production"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:58
msgid "For the subcontracted product"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:60
msgid "From Production to Subcontracting"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:62
msgid "From Subcontracting to Stock"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:64
msgid ""
"The *Subcontracting Location* represents the place where the products are at"
" your subcontractor’s warehouse. It is configured as an internal location, "
"the components that are sent to the subcontractor are still valued in your "
"stock."
"To let your subcontractor know how many products you need, create and send "
"them purchase orders (PO). To do so, open the *Purchase* app and create a "
"new one. Be sure to send the PO to a vendor that is defined as a "
"subcontractor on the *BoM*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:69
#: ../../manufacturing/management/subcontracting.rst:63
msgid ""
"For option B, you can simply create the receipt manually with a partner of "
"type subcontractor defined on it."
"Once the *PO* is validated (1), a pending receipt is created. When the "
"products are received, validate the receipt (2), with the actual quantity "
"received. Then Odoo automatically created several inventory moves:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:73
msgid "Resupply the subcontractor with the components"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:75
#: ../../manufacturing/management/subcontracting.rst:68
msgid ""
"There are 3 ways to manage the resupply of your subcontractor with the "
"components:"
"Consume the components at the subcontractor’s location, based on the *BoM* "
"(3);"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:80
msgid "**Manually**: You create a delivery order in which you set the"
#: ../../manufacturing/management/subcontracting.rst:70
msgid "Produce finished goods at the subcontractor’s location (4);"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:71
msgid ""
"Move products from the subcontractor’s location to YourCompany through the "
"validated receipt (5)."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:74
msgid ""
"Of course, Odoo does all the transactions for you, automatically. Simply "
"control the vendor bill with the usual matching process with the purchase "
"order."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:79
msgid "subcontractor as a partner and you choose the components to deliver."
msgid ""
"The *PO* is optional. If you create a receipt manually, with the right "
"subcontractor, Odoo still performs all the moves. Useful if the "
"subcontractor does not bill a fixed price per item, but rather the time and "
"materials used."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:85
msgid "Inventory Valuation"
msgstr "Оцінка запасу"
#: ../../manufacturing/management/subcontracting.rst:87
msgid "The cost of the manufactured product “C” is defined as:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:89
msgid "**With reordering rules**: You can define a *reordering rule*"
msgid "**C = A + B + s**"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:86
#: ../../manufacturing/management/subcontracting.rst:91
msgid "With:"
msgstr "З:"
#: ../../manufacturing/management/subcontracting.rst:93
msgid "**A**: Cost of raw materials coming from YourCompany;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:96
msgid "**B**: Cost of raw materials sourced directly from the"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:96
msgid "subcontractor;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:98
msgid "**s**: Cost of the subcontracted service."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:100
msgid ""
"on the *Subcontracting location* to ensure that they are always enough "
"components sent to your subcontractors. When the reordering rule is "
"triggered, a delivery order is created for the product is automatically "
"created."
"Sending raw materials to your subcontractors (**A**) does not impact the "
"inventory valuation, the components still belonging to your company. To "
"manage this, the *Subcontracting Location* is configured as an *Internal "
"Location* so that the components are still valued in the inventory."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:97
msgid "**On order**: You can also deliver the components to your"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:95
#: ../../manufacturing/management/subcontracting.rst:106
msgid ""
"subcontractors each time you order a subcontracted product. For this, you "
"need to tick the route *Resupply Subcontractor on Order* on the wanted "
"Then, the vendor price set on the product C form has to be what has to be "
"paid to the subcontractor for his parts and service time: **B + s**. The "
"product cost has to be: **A + B + s**, how much the product is valued in the"
" accounting."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:111
msgid ""
"Finally, the subcontractor bill matches the purchase order, with the "
"proposed price coming from the finished products C."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:115
msgid ""
"If managing the replenishment of raw materials **B** at your subcontractor’s"
" location is not needed, simply include the cost of **B** in the "
"subcontractor’s price **s** and remove the products *B* from the *BoM*."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:121
msgid "Traceability"
msgstr "Відстеження"
#: ../../manufacturing/management/subcontracting.rst:123
msgid ""
"In case the products received from the subcontractor contain tracked "
"components, their serial or lot numbers need to be specified during the "
"receipt."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:127
msgid ""
"On the receipt of the subcontracted product, a *Record Components* button "
"appears when necessary. Click on it to open a dialog and record the "
"serial/lot numbers of the components. If the finished product is also "
"tracked, its serial/lot number can be registered here too."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:136
msgid ""
"For audit purposes, it is possible to check the lot numbers recorded on a "
"receipt by using the icon on the right of the finished products:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:144
msgid "Automate Replenishment of Subcontractors"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:146
msgid ""
"To manage the resupply of your subcontractor, activate *Multi-locations* in "
":menuselection:`Inventory --> Configuration --> Configuration`. Then, the "
"inventory at the subcontractor location can be tracked."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:151
msgid ""
"It is possible to resupply subcontractors by sending products from the "
"company locations, or by sending products from another supplier to the "
"subcontractors."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:156
msgid "Replenishment from the warehouse"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:158
msgid ""
"Resupplying subcontractors manually is the simplest approach. To do so, "
"create delivery orders in which the subcontractor is set as a delivery "
"address and fill the components to deliver."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:162
msgid ""
"To automate the subcontractors’ replenishment propositions, there are two "
"approaches:"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:165
msgid "Reordering rules;"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:166
msgid "Replenish on order flow."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:168
msgid ""
"For the first one, just define a reordering rule on the subcontracting "
"location, with a minimum and maximum inventory level. When the reordering "
"rule is triggered, a delivery order is created to ship the components to the"
" subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:177
msgid ""
"The second approach is to use a “pull” flow. Here, the demand in the "
"finished product (real demand or forecasted one through the Master "
"Production Schedule) triggers the replenishment of the subcontractor. To do "
"so, select the route *Resupply Subcontractor on Order* on the wanted "
"components."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:188
msgid "Replenishment from another supplier"
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:190
msgid ""
"When purchasing items to another supplier, it is possible to ask him to "
"deliver the subcontractor directly. To do so, activate the *Drop Shipping* "
"feature in :menuselection:`Purchase --> Configuration --> Configuration`."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:195
msgid ""
"Now, set the *Dropship* option in the *Deliver To* field of the *Other "
"Information* tab. Then, provide the address of the subcontractor for the "
"shipping."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:203
msgid ""
"That way, the supplier can ship items directly and you simply receive and "
"pay the bill. However, it is still required to validate receipts for the "
"subcontractor."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:212
msgid "Quality Control"
msgstr "Контроль якості"
#: ../../manufacturing/management/subcontracting.rst:214
msgid ""
"Controlling the quality of the products manufactured by subcontractors is "
"possible thanks to the Odoo Quality app. Quality checks can be made on a "
"manufacturing step but, because the manufacturing process is handled by an "
"external party, it can be defined on the product reception."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:224
msgid ""
"To create a quality check at the receipt, open the *Quality* app and create "
"a new *Control Point* on the reception."
msgstr ""
#: ../../manufacturing/management/subcontracting.rst:231
msgid ""
"By doing so, a quality check is automatically created each time a finished "
"product is received."
msgstr ""
#: ../../manufacturing/management/unbuild.rst:3
msgid "Unbuild a product"
msgstr "Розбирання товару"
@@ -990,8 +1157,8 @@ msgstr ""
#: ../../manufacturing/management/use_mps.rst:11
msgid ""
"Go to the *Manufacturing app > Configuration > Settings* and activate the "
"Master Production Schedule feature before hitting save."
"Go to the :menuselection:`Manufacturing app --> Configuration --> Settings` "
"and activate the Master Production Schedule feature before hitting save."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:18
@@ -1002,10 +1169,10 @@ msgstr ""
#: ../../manufacturing/management/use_mps.rst:20
msgid ""
"Now, go in *Planning > Master Production Schedule* and click on add a "
"product. You can now define your safety stock target (= the stock you want "
"to have on hand at the end of the period) and the minimum and maximum "
"quantities to replenish."
"Now, go in :menuselection:`Planning --> Master Production Schedule` and "
"click on add a product. You can now define your safety stock target (= the "
"stock you want to have on hand at the end of the period) and the minimum and"
" maximum quantities to replenish."
msgstr ""
#: ../../manufacturing/management/use_mps.rst:29
@@ -1143,11 +1310,11 @@ msgstr "Загальний огляд"
msgid "Repair Management"
msgstr "Управління ремонтом"
#: ../../manufacturing/repair/repair.rst:3
#: ../../manufacturing/repair/repair.rst:5
msgid "Repair products"
msgstr "Ремонт товарів"
#: ../../manufacturing/repair/repair.rst:5
#: ../../manufacturing/repair/repair.rst:7
msgid ""
"The Odoo *Repair* app allows you to manage a complete after sales process "
"but also to simply repair products you have manufactured, if they present a "
@@ -1157,11 +1324,11 @@ msgstr ""
"а також просто ремонтувати вироби, які ви виготовили, якщо вони є "
"дефектними."
#: ../../manufacturing/repair/repair.rst:10
#: ../../manufacturing/repair/repair.rst:12
msgid "Create a Repair Order"
msgstr "Створіть замовлення на ремонт"
#: ../../manufacturing/repair/repair.rst:12
#: ../../manufacturing/repair/repair.rst:14
msgid ""
"Once in the app, you can access your existing *Repair Orders* and create a "
"new one."
@@ -1169,11 +1336,11 @@ msgstr ""
"Опинившись у програмі, ви зможете отримати доступ до існуючих *Замовлень на "
"ремонт* та створити нове."
#: ../../manufacturing/repair/repair.rst:19
#: ../../manufacturing/repair/repair.rst:21
msgid "Manage a repair"
msgstr "Керування ремонтом"
#: ../../manufacturing/repair/repair.rst:21
#: ../../manufacturing/repair/repair.rst:23
msgid ""
"When a customer sends you a product for repair, create a new *Repair Order*."
" Fill it in with all the information you may need such as the product, the "
@@ -1185,7 +1352,7 @@ msgstr ""
"клієнт, якщо він має бути виписаний після або перед ремонтом, деталей, які "
"можуть знадобитися і т.д."
#: ../../manufacturing/repair/repair.rst:29
#: ../../manufacturing/repair/repair.rst:31
msgid ""
"Once everything is done, you can then send the repair quotation to your "
"customer. If it is approved, you can confirm the repair. You will then be "
@@ -1195,6 +1362,6 @@ msgstr ""
"вашому клієнту. Якщо це буде схвалено, ви можете підтвердити ремонт. Після "
"цього ви зможете запустити та завершити ремонт, коли він буде завершений."
#: ../../manufacturing/repair/repair.rst:36
#: ../../manufacturing/repair/repair.rst:38
msgid "You can now invoice the repair."
msgstr "Тепер ви можете виставити рахунок на ремонт."
locale/uk/LC_MESSAGES/marketing_automation.po
+380
View File
@@ -0,0 +1,380 @@
# 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
# Alina Lisnenko <alinasemeniuk1@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: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/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 "Запустити тест"
#: ../../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/uk/LC_MESSAGES/mobile.po
+9 -8
View File
@@ -4,16 +4,16 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -39,8 +39,9 @@ msgstr ""
#: ../../mobile/firebase.rst:13
msgid ""
"Simply go to *Settings* > *General Settings* > *Odoo Cloud Notification "
"(OCN)* and make sure that **Push Notifications** is checked."
"Simply go to :menuselection:`Settings --> General Settings --> Odoo Cloud "
"Notification (OCN)` and make sure that **Push Notifications** is checked."
msgstr ""
"Просто перейдіть у *Налаштування* > *Загальні налаштування* > *Хмарні "
"Сповіщення Odoo (OCN)* та переконайтеся, що **Push-сповіщення** позначені."
"Просто перейдіть на :menuselection:`Налаштування --> Загальні налаштування "
"--> Сповіщення Odoo Cloud (OCN)` та переконайтеся, що позначені **Пуш-"
"сповіщення**."
locale/uk/LC_MESSAGES/planning.po
+165
View File
@@ -0,0 +1,165 @@
# 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
# Alina Lisnenko <alinasemeniuk1@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: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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 ""
"Перейдіть на :menuselection:`Налаштування --> Ролі --> Створити`. Додатково "
"перейдіть у модуль *Співробітники*, оберіть відповідного співробітника і під"
" вкладкою *Робоча інформація* оберіть *Роль планування за замовчуванням*."
#: ../../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/uk/LC_MESSAGES/point_of_sale.po
+802 -971
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/portal.po
+12 -21
View File
@@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-10-03 11:39+0200\n"
"PO-Revision-Date: 2019-10-03 09:46+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -36,16 +36,12 @@ msgstr ""
"документи, такі як комерційні пропозиції, замовлення на продаж, рахунки та "
"підписки."
#: ../../portal/my_odoo_portal.rst:11
#: ../../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\"."
"`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 ""
"Щоб отримати доступ до цієї секції, вам необхідно увійти з ім'ям користувача"
" та паролем в `Odoo <https://www.odoo.com/my/home>`__ . Якщо ви вже увійшли,"
" просто натисніть на ваше ім'я у верхньому правому куті та оберіть \"Мій "
"обліковий запис\"."
#: ../../portal/my_odoo_portal.rst:20
msgid "Quotations"
@@ -182,19 +178,14 @@ msgstr ""
"натиснувши на \"Управління вашими методами платежу\" внизу сторінки. "
"Натисніть \"Видалити\", щоби видалити метод платежу."
#: ../../portal/my_odoo_portal.rst:101
#: ../../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."
"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 ""
"На дату наступного рахунку, якщо не надано жодної інформації про платіж або,"
" якщо ваша кредитна картка протермінована, статус вашої підписки зміниться "
"на \"Оновити\". Тоді у вас буде 7 днів надати дійсний метод платежу. Після "
"цієї затримки, підписку буде закрито, і ви більше не зможете отримати доступ"
" до вашої бази даних."
#: ../../portal/my_odoo_portal.rst:108
msgid "Success Packs"
locale/uk/LC_MESSAGES/practical.po
+7 -4
View File
@@ -3,14 +3,17 @@
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 11.0\n"
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-10-19 10:03+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2018\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
locale/uk/LC_MESSAGES/project.po
+864 -1867
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/purchase.po
+15 -123
View File
@@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-10-03 09:47+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -98,11 +98,11 @@ msgstr "Нижче наведено шаблон використаних сто
#: ../../purchase/purchases/master/import.rst:33
msgid ""
"`Template download "
"<https://docs.google.com/spreadsheets/d/1N8c_eejLV_8NhYMGCfZau_oGCnRkUIT9nwdX7n0shhY/edit#gid=964193981>`__"
":download:`Click here to download the template "
"<../../../_static/example_files/vendor_pricelists_template.csv>`"
msgstr ""
"`Завантажити шаблон "
"<https://docs.google.com/spreadsheets/d/1N8c_eejLV_8NhYMGCfZau_oGCnRkUIT9nwdX7n0shhY/edit#gid=964193981>`__"
":download:`Натисніть тут, щоб завантажити "
"шаблон<../../../_static/example_files/vendor_pricelists_template.csv>`"
#: ../../purchase/purchases/master/suppliers.rst:3
msgid "Set multiple vendors on a product"
@@ -424,13 +424,9 @@ msgstr ""
#: ../../purchase/purchases/rfq/3_way_matching.rst:9
msgid ""
"To define whether the vendor bill should be paid or not, you can use what we"
" call *3-way matching*. It refers to the comparaison of the information "
" call *3-way matching*. It refers to the comparison of the information "
"appearing on the *Purchase Order*, the *Vendor Bill* and the *Receipt*."
msgstr ""
"Щоб визначити, чи повинен бути оплачений рахунок постачальника, ви можете "
"використовувати так зване *3-стороннє узгодження*. Це стосується порівняння "
"інформації, яка відображається у *замовленні на купівлю*, *рахунку "
"постачальника* та *надходженні*."
#: ../../purchase/purchases/rfq/3_way_matching.rst:14
msgid ""
@@ -968,111 +964,7 @@ msgstr ""
" натиснувши на кнопку **Створити та редагувати**. У полі **Дата замовлення**"
" виберіть дату, до якої ви хочете перейти до фактичного замовлення."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Receipt"
msgstr "Надходження"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoming Shipments"
msgstr "Вхідні відправлення"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor"
msgstr "Постачальник"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "You can find a vendor by its Name, TIN, Email or Internal Reference."
msgstr ""
"Ви можете знайти продавця за своїм ім'ям, ІПН, електронною поштою або "
"внутрішнім посиланням."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Vendor Reference"
msgstr "Референс постачальника"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the sales order or bid sent by the vendor. It's used to do the "
"matching when you receive the products as this reference is usually written "
"on the delivery order sent by your vendor."
msgstr ""
"Посилання на замовлення на продаж або пропозицію вашого постачальника. Він "
"використовується для виконання відповідності, коли ви отримуєте товари, "
"оскільки це посилання, як правило, написано в посиланні на доставку, "
"надісланої вашим постачальником."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Order Date"
msgstr "Дата замовлення"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Depicts the date where the Quotation should be validated and converted into "
"a purchase order."
msgstr ""
"Визначає дату, коли комерційна пропозиція повинна бути підтвердженою та "
"перетвореною у замовлення на купівлю."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Source Document"
msgstr "Джерело документа"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Reference of the document that generated this purchase order request (e.g. a"
" sales order)"
msgstr ""
"Посилання на документ, який створив цей запит на замовлення на купівлю "
"(наприклад, замовлення на продаж)"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Deliver To"
msgstr "Доставити на"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "This will determine operation type of incoming shipment"
msgstr "Це визначатиме тип операції вхідної доставки"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Drop Ship Address"
msgstr "Адреса дроп-шипінгу"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"Put an address if you want to deliver directly from the vendor to the "
"customer. Otherwise, keep empty to deliver to your own company."
msgstr ""
"Введіть адресу, якщо ви хочете доставити безпосередньо від продавця до "
"клієнта. Інакше залишайте порожніми, щоб доставити до своєї компанії."
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Destination Location Type"
msgstr "Тип місцезнаходження призначення:"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Technical field used to display the Drop Ship Address"
msgstr ""
"Технічне поле, яке використовується для відображення адреси дроп-шипінгу"
#: ../../purchase/purchases/rfq/create.rst:0
msgid "Incoterm"
msgstr "Інкотерм"
#: ../../purchase/purchases/rfq/create.rst:0
msgid ""
"International Commercial Terms are a series of predefined commercial terms "
"used in international transactions."
msgstr ""
"Міжнародні комерційні умови, комплект міжнародних правил з тлумачення "
"найбільш широко використовуваних торговельних термінів в галузі міжнародної "
"торгівлі."
#: ../../purchase/purchases/rfq/create.rst:32
msgid "View *Request for Quotation* in our Online Demonstration"
msgstr ""
"Перегляньте *Запит на комерційну пропозицію* в нашій демоверсії онлайн"
#: ../../purchase/purchases/rfq/create.rst:34
#: ../../purchase/purchases/rfq/create.rst:28
msgid ""
"In **Products**, click on Add an item. Select the product you wish to order "
"in the **Product** menu. Specify the **Quantity** by inserting the number "
@@ -1093,7 +985,7 @@ msgstr ""
"що для цього постачальника вказано адресу електронної пошти або введіть "
"нову)."
#: ../../purchase/purchases/rfq/create.rst:48
#: ../../purchase/purchases/rfq/create.rst:40
msgid ""
"After having clicked on **Send**, you will notice that the RFQ's status will"
" switch from **Draft** to **RFQ Sent**."
@@ -1101,7 +993,7 @@ msgstr ""
"Після натискання кнопки **Надіслати** ви помітите, що статус Комерційної "
"пропозиції перейде з **Чернетки** в **Надіслану комерційну пропозицію**."
#: ../../purchase/purchases/rfq/create.rst:54
#: ../../purchase/purchases/rfq/create.rst:46
msgid ""
"Once your supplier has replied with an offer, update the RfQ by clicking on "
"**Edit** to fit the quotation (prices, taxes, expected delivery lead time, "
@@ -1112,7 +1004,7 @@ msgstr ""
"очікувана вартість доставки, умови платежу тощо), а потім натисніть кнопку "
"**Зберегти**, щоб оформити замовлення на купівлю."
#: ../../purchase/purchases/rfq/create.rst:59
#: ../../purchase/purchases/rfq/create.rst:51
msgid ""
"To proceed with the order, click on **Confirm Order** to send the order to "
"the supplier. The RfQ's status will switch to **Purchase Order**."
@@ -1121,7 +1013,7 @@ msgstr ""
"відправити замовлення постачальнику. Статус Комерційної пропозиції перейде у"
" **Замовлення на купівлю**."
#: ../../purchase/purchases/rfq/create.rst:65
#: ../../purchase/purchases/rfq/create.rst:57
msgid ""
"The status of the RfQ will change to PURCHASE ORDER. Tabs in the upper right"
" corner of the order will show 1 Shipment and 0 Invoice."
locale/uk/LC_MESSAGES/quality.po
+148 -97
View File
@@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-11-20 09:24+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -159,9 +159,10 @@ msgstr ""
#: ../../quality/checks/quality_mo.rst:18
msgid ""
"To create a quality control point, open the quality app and go to *Control >"
" Control Points*. There, hit create. Make sure to select *Manufacturing* as "
"operation and choose the type of quality check you want to perform."
"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
@@ -192,9 +193,9 @@ msgstr ""
#: ../../quality/checks/quality_mo.rst:55
msgid ""
"If you want to create a *Quality Control Point*, open the *Quality* app and "
"go to *Control > Control Points*. Then, click on create. Make sure to select"
" *Manufacturing* as operation and select the work order operation on which "
"the quality check should be performed."
"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
@@ -225,9 +226,9 @@ msgstr ""
#: ../../quality/checks/quality_transfers.rst:8
msgid ""
"To create a *Quality Control Point*, open the *Quality* application. Then, "
"go to *Quality Control > Control Points > Create*. Now, you can define the "
"quality control point you want to apply to a specific product. Don’t forget "
"to select a transfer operation type."
"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
@@ -270,146 +271,196 @@ msgstr "Контроль"
msgid "Define Quality Control Points"
msgstr ""
#: ../../quality/control/control_points.rst:6
#: ../../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:8
msgid ""
"If it is the first *Quality Control Point* that you create, know that you "
"need to open the *Quality* app. Then, go to *Quality Control > Control "
"Points*. Once there, you have to define the product on which the quality "
"control will take place, as well as the operation at which it should take "
"place."
msgstr ""
#: ../../quality/control/control_points.rst:14
msgid ""
"The *Quality Control Points* can take place during transfers or during the "
"manufacturing process of the products. If you work with routings on your "
"*Bill of Materials*, you have to precise at which step of the manufacturing "
"process the quality control point should be applied."
msgstr ""
#: ../../quality/control/control_points.rst:19
msgid ""
"The control type defines at which frequency the quality checks should take "
"place:"
msgstr ""
#: ../../quality/control/control_points.rst:22
msgid ""
"All Operations: all the operations will generate quality checks to perform;"
"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:24
#: ../../quality/control/control_points.rst:27
msgid ""
"Randomly: the quality checks will only be performed on x% of the operation. "
"You must define the percentage yourself, on the control point;"
msgstr ""
#: ../../quality/control/control_points.rst:26
msgid ""
"Periodically: the quality checks will be performed periodically. The "
"periodicity is based on the period you define (once a day, once a week)."
"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 "Quality Control Point Types"
msgid ""
"The *Control Type* defines at which frequency the quality checks should take"
" place:"
msgstr ""
#: ../../quality/control/control_points.rst:34
#: ../../quality/control/control_points.rst:35
msgid ""
"Now that the rest is configured, you need to define the type of quality "
"check."
"**All operations**: all the operations automatically generate quality checks"
" to perform;"
msgstr ""
#: ../../quality/control/control_points.rst:38
msgid ""
"Some of the types are only available with the manufacturing application."
"**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 "Text"
msgstr "Текст"
#: ../../quality/control/control_points.rst:43
msgid ""
"This control point type allows you to give instructions to your workers "
"during the transfer, or the manufacturing process."
"**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:56
msgid "Take a Picture"
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 ""
"This control point type asks you to take a picture of the product in a "
"transfer, or when manufacturing it."
"Some types are available only with the manufacturing application installed."
msgstr ""
#: ../../quality/control/control_points.rst:71
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:62
msgid "Text"
msgstr "Текст"
#: ../../quality/control/control_points.rst:73
#: ../../quality/control/control_points.rst:64
msgid ""
"This type of control point requires that you specify if the products pass or"
" fail a specific text. It can be applied for both transfers or manufacturing"
" orders."
"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 ""
"For this kind of control point type, you have the possibility to define a "
"failure message that will give instructions to follow in case of quality "
"check failure."
"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:94
msgid "Take a Measure"
msgstr ""
#: ../../quality/control/control_points.rst:96
#: ../../quality/control/control_points.rst:98
msgid ""
"This control point type requires you to enter the product’s measurements "
"during a transfer, or during the manufacturing process."
"This process can be simplified by using a connected :doc:`camera "
"<../../iot/devices/measurement_tool>`."
msgstr ""
#: ../../quality/control/control_points.rst:102
msgid ""
"For this kind of control point type, you also have the possibility to define"
" a failure message that will give instructions to the worker."
msgid "Pass-Fail"
msgstr ""
#: ../../quality/control/control_points.rst:115
#: ../../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:117
#: ../../quality/control/control_points.rst:161
msgid ""
"This control point type requires you register the component serial/lot "
"numbers during the manufacturing process. It is only available if you work "
"with routings."
"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:128
#: ../../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:130
#: ../../quality/control/control_points.rst:178
msgid ""
"With this control point type, you must register the serial/lot number of the"
" by-products that are manufactured. It is also only available with routings."
"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:141
#: ../../quality/control/control_points.rst:193
msgid "Print Label"
msgstr ""
#: ../../quality/control/control_points.rst:143
#: ../../quality/control/control_points.rst:195
msgid ""
"This control point type allows you to print labels to add to the product "
"during the manufacturing process."
"*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/uk/LC_MESSAGES/sales.po
+1350 -780
View File
File diff suppressed because it is too large Load Diff
locale/uk/LC_MESSAGES/sms_marketing.po
+338 -298
View File
@@ -4,17 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Martin Trigaux, 2019
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-11-20 09:24+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:41+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -26,354 +26,417 @@ msgstr ""
msgid "SMS Marketing"
msgstr "SMS-маркетинг"
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:3
msgid "Build, send and get reports from a SMS mailing"
#: ../../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/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:5
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:5
msgid ""
"Why to use SMS? Using SMS Marketing as part of my communication strategies "
"can empower me to expand my markets, considering that in some countries "
"emails are not very used or used at all. It also helps to boost my "
"conversion rate, as this strategy has a high open-rate percentage among "
"people who use smartphones - people usually don’t keep unread SMSs!"
"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/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:8
msgid ""
"With Odoo’s SMS Marketing app you can plan, organize, schedule and keep "
"track of your mailings with its easy to use interface."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:12
msgid "Install the app"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:14
msgid "Go to *Apps*, search for *SMS Marketing* and click on *Install*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:17
msgid "Build an SMS mailing"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:19
msgid "Go to *SMS Marketing > Create*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:24
msgid ""
"First, I’ll be able to specify a *subject* name that will help me to "
"remember what the mailing is about. Under *recipients*, I’ll choose to whom "
"I’d like the SMS to be sent. If I choose *Contact*, all my Odoo contacts "
"(vendor, customers, etc.) will receive my SMS. From there, I can refine my "
"recipient list with the *add filter* option. In the example below, I choose "
"to send it to my contacts living in Belgium."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:31
msgid ""
"The *Mailing list* option, on the other hand, allows me to choose mailing "
"lists I’ve created with specific contacts or people who have subscribed to "
"my Newsletters, or both! I’m allowed to select more than one *Mailing list*."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:36
msgid ""
"Under the *SMS Content* tab, links can be included and Odoo will "
"automatically generate *link trackers*. Thank to those, I’ll be able to get "
"data about those links."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:38
msgid ""
"On *Settings* I have the option *include opt-out link* available. If "
"activated, the contact will be able to unsubscribe from the mailing list "
"he’s not interested in anymore."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:43
msgid ""
"in the *Link Tracker* menu under *Configuration*, I can see the history of "
"my sent links, access them and look at statistics."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:48
msgid "Double-check that you have the phone number of your contacts saved!"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:52
msgid "Sending my mailing"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:56
msgid ""
"Once I have my mailing created, I must choose when I would like it to be "
"delivered:"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:58
msgid ""
"**Put in queue**: the mailing will be triggered with the next automatic run."
" Interesting option if I don’t mind when the triggering will happen."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:59
msgid ""
"**Send now**: sends the message immediately. Advised to use this option if "
"there are not that many recipients."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:60
msgid ""
"**Schedule**: allows me to choose a day and time. Best option for mailings "
"that I would like to send during a specific event, to promote an offer while"
" it is active or to simply plan my content strategy in advance."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:61
msgid ""
"**Test**: allows me to send an SMS to one or multiple numbers for test "
"purposes. Check, for example, if the link provided lands on the right page "
"while making sure they are responsive. If sending it to multiple numbers, I "
"must remember to use a comma between them."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:65
msgid "Visualize reports"
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:66
msgid ""
"On the *Reporting* menu, with just a few clicks, I am capable of applying "
"filters, measures and adopt different layouts to do an analysis of the "
"performance of my SMS mailings."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:71
msgid ""
"I can also check the price to send an SMS on your country when clicking on "
"the *information* icon when creating a new SMS."
msgstr ""
#: ../../sms_marketing/SMS_mkt_build_send-and_get_reports_from_a_SMS_mailing.rst:76
msgid ""
"**Buy Credits!** In order to take advantage of the app and its features, "
"make sure you’ve purchased credits. For more information on that access: "
":doc:`../sms_marketing/fqapricing`"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:3
msgid "Contact lists and Blacklist"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:6
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:11
msgid "Contact lists"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:7
msgid ""
"Creating my own list of contacts, or importing it, is useful when I want to "
"create specific groups of people, such as the subscribers of my newsletter. "
"It is also the best way to get started if I am coming from another system "
"and already have built an audience. It makes the SMS distribution a lot "
"easier."
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:13
msgid "Go to :menuselection:`Contacts lists --> Contacts lists --> Create`."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:9
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:16
msgid ""
"Go to *Contacts lists > Contacts lists > Create*. I’ll choose a name for my "
"*Mailing list*, and activate the option *Public* if I would like to make the"
" mailing list accessible to my recipients in the unsubscription page to "
"allow them to update their subscription preferences."
"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/SMS_mkt_contact_lists_and_blacklist.rst:12
msgid ""
"Once inside the list, I can again *Create* or *Import* contacts for that "
"specific list."
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:18
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:22
msgid "History with the Log Notes"
msgstr ""
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:19
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:25
msgid ""
"A record of the mailings sent is kept in the chatter of the recipient "
"(whether it is a contact or an opportunity, for example)."
"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/SMS_mkt_contact_lists_and_blacklist.rst:24
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:28
msgid ""
"This is important as I and my team can easily keep track and see a history "
"of interactions with my contacts or prospects, granting me the ability to "
"better understand them. Example: my sales representative can easily find out"
" which SMS mailing promotions a customer has received or not."
"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/SMS_mkt_contact_lists_and_blacklist.rst:29
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:35
msgid "Blacklist"
msgstr "Чорний список"
#: ../../sms_marketing/SMS_mkt_contact_lists_and_blacklist.rst:30
#: ../../sms_marketing/overview/contact_lists_and_blacklist.rst:38
msgid ""
"If I’m coming from another software and have a list of clients who have "
"already asked to be blacklisted from my news, I can import those entries in "
"my database. For that, I’ll go to *Configuration > Phone Blacklist > "
"Import*."
"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/SMS_mkt_integrations_and_template.rst:3
#: ../../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/SMS_mkt_integrations_and_template.rst:4
#: ../../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. As you know, one of the biggest benefits of using "
"Odoo is the capability of the apps to be integrated. With the SMS Marketing "
"app isn’t different!"
"purposes, but also as a reminder of events or issued invoices to your "
"costumers, for example."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:9
msgid "Organize Email Marketing and SMS campaigns"
msgstr ""
#: ../../sms_marketing/overview/integrations_and_template.rst:9
msgid "Campaigns"
msgstr "Кампанії"
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:10
#: ../../sms_marketing/overview/integrations_and_template.rst:11
msgid ""
"First, make sure to have the necessary feature activated. Go to the *Email "
"Marketing app > Configuration > Settings> activate the option Mailing "
"Campaigns*."
"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/SMS_mkt_integrations_and_template.rst:15
#: ../../sms_marketing/overview/integrations_and_template.rst:17
msgid ""
"Now, I’ll also have the menu *Campaigns* included in my *SMS Marketing* "
"page, allowing me to have an overview of my SMS mailings and my email "
"marketing ones."
"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/SMS_mkt_integrations_and_template.rst:20
#: ../../sms_marketing/overview/integrations_and_template.rst:23
msgid ""
"This feature is especially useful if I have aggregated campaigns, as I have "
"a global reporting view. In addition to that, I can create stages in my "
"kanban view to better organize the work being done."
"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/SMS_mkt_integrations_and_template.rst:26
#: ../../sms_marketing/overview/integrations_and_template.rst:31
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:27
#: ../../sms_marketing/overview/integrations_and_template.rst:34
msgid ""
"Sending SMSs through the contact’s form is available by default in Odoo. It "
"makes my work easier if I need to send an SMS to a specific contact, for "
"example. For that, I’ll go to the *Contacts* app, select the contact and "
"click on the *SMS* icon next to the phone number."
"makes your work easier if you need to send an SMS to a specific contact, for"
" example."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:33
#: ../../sms_marketing/overview/integrations_and_template.rst:36
msgid ""
"If I’d like to send a message in a batch here, I could go to *List View > "
"select all the contacts > Action > Send SMS*."
"For that, go to the *Contacts* app, select the contact and click on the "
"*SMS* icon next to the phone number."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:39
msgid "Set up SMS Templates"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:40
#: ../../sms_marketing/overview/integrations_and_template.rst:41
msgid ""
"To set up *SMS Templates*, I’ll go to the *Settings* app and activate the "
"*developer mode*. Now, back to *Settings* app, I’ll go to *Technical > "
"Phone/SMS section > SMS Templates* and create the content I need."
"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/SMS_mkt_integrations_and_template.rst:48
#: ../../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/SMS_mkt_integrations_and_template.rst:52
msgid ""
"SMS Text Messaging is available throughout Odoo! Here are some of our extra "
"notable integrations:"
#: ../../sms_marketing/overview/integrations_and_template.rst:63
msgid "SMS Text Messaging is available throughout Odoo:"
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:54
#: ../../sms_marketing/overview/integrations_and_template.rst:65
msgid "*CRM*: send SMSs to your leads and opportunities."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:55
#: ../../sms_marketing/overview/integrations_and_template.rst:66
msgid "*Subscription*: alert customers about their subscription."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:56
#: ../../sms_marketing/overview/integrations_and_template.rst:67
msgid "*Accounting*: send payment reminders."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:57
#: ../../sms_marketing/overview/integrations_and_template.rst:68
msgid "*Marketing Automation*: automate your SMS marketing campaigns."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:58
#: ../../sms_marketing/overview/integrations_and_template.rst:69
msgid ""
"*Inventory*: send an automatic confirmation when a delivery order is done."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:59
#: ../../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/SMS_mkt_integrations_and_template.rst:60
#: ../../sms_marketing/overview/integrations_and_template.rst:71
msgid ""
"*SEPA debit payment provider*: send a verification code to your customers."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:61
#: ../../sms_marketing/overview/integrations_and_template.rst:72
msgid ""
"*Studio*: send an SMS according to your needs by using automated actions."
msgstr ""
#: ../../sms_marketing/SMS_mkt_integrations_and_template.rst:63
#: ../../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 `Pricing and FQA <fqapricing.html>`__."
" asked questions, go to :doc:`../pricing/pricing_and_faq`."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:3
#: ../../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/fqapricing.rst:6
msgid "Pricing"
msgstr "Ціноутворення"
#: ../../sms_marketing/fqapricing.rst:7
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service which requires "
"prepaid credits to work. The price of an SMS depends on the destination and "
"the length of the message. With 1 credit, I can send up to 92 SMSs."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:6
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:9
#: ../../sms_marketing/pricing/pricing_and_faq.rst:7
msgid ""
"**For more information, please consult our FAQ page**: `Odoo SMS - FAQ "
"<https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_"
"SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
"prepaid credits* to work."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:11
msgid ""
"To buy credits I will go to *Settings > Buy Credits* (under *Send SMS*); or"
" go to *Settings > View my Services* (under *Odoo IAP*)."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:11
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:18
#: ../../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."
@@ -381,138 +444,115 @@ msgstr ""
"Якщо ви на Odoo Online (SAAS) і у вас версія Enterprise, для тестування "
"функції ви користуєтесь безкоштовними пробними кредитами."
#: ../../sms_marketing/fqapricing.rst:21
msgid "FAQ"
msgstr "FAQ"
#: ../../sms_marketing/pricing/pricing_and_faq.rst:70
msgid "More common questions"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:22
#: ../../sms_marketing/pricing/pricing_and_faq.rst:72
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:24
msgid "No, your credits won’t expire."
#: ../../sms_marketing/pricing/pricing_and_faq.rst:74
msgid "No, credits do not expire."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:26
#: ../../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/fqapricing.rst:28
#: ../../sms_marketing/pricing/pricing_and_faq.rst:80
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:30
#: ../../sms_marketing/pricing/pricing_and_faq.rst:83
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:32
#: ../../sms_marketing/pricing/pricing_and_faq.rst:85
msgid "Yes."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:34
#: ../../sms_marketing/pricing/pricing_and_faq.rst:88
msgid "**Can the recipient answer to me?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:36
#: ../../sms_marketing/pricing/pricing_and_faq.rst:90
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:38
#: ../../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/fqapricing.rst:40
#: ../../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/fqapricing.rst:42
#: ../../sms_marketing/pricing/pricing_and_faq.rst:99
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:44
#: ../../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 SMS sent is available under Settings> "
"Activate the developer mode > Technical > SMS."
"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/fqapricing.rst:46
#: ../../sms_marketing/pricing/pricing_and_faq.rst:107
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:48
#: ../../sms_marketing/pricing/pricing_and_faq.rst:109
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:50
#: ../../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/fqapricing.rst:52
#: ../../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/fqapricing.rst:54
#: ../../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/fqapricing.rst:56
#: ../../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/fqapricing.rst:58
#: ../../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/fqapricing.rst:60
#: ../../sms_marketing/pricing/pricing_and_faq.rst:125
msgid "Only the ones that have an invalid format."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:62
#: ../../sms_marketing/pricing/pricing_and_faq.rst:128
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:64
#: ../../sms_marketing/pricing/pricing_and_faq.rst:130
msgid ""
"Please find our Privacy Policy here: `Odoo IPA Purchase Privacy Policy "
"<https://iap.odoo.com/privacy#sms>`__"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:66
msgid "**How many types of SMS exist and how many characters make 1 SMS?**"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:68
msgid "There are 2 types of SMS message:"
msgstr ""
#: ../../sms_marketing/fqapricing.rst:70
msgid ""
"*Standard* (GSM-7): contains only characters from the GSM-7 set, which can "
"be seen in the following picture."
msgstr ""
#: ../../sms_marketing/fqapricing.rst:75
msgid ""
"*Unicode*: contains at least one character that is not in the previous "
"table. For Standard SMS the size limit is 160 characters, and for Unicode is"
" 70. Above these limits, the content is divided into a multi-part message. "
"The system will inform you in real-time about the number of SMS your message"
" represents."
"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""
locale/uk/LC_MESSAGES/social_marketing.po
+294 -159
View File
@@ -4,16 +4,17 @@
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019
# Martin Trigaux, 2020
# Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 13.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-11-20 10:20+0100\n"
"PO-Revision-Date: 2019-11-20 09:24+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2019\n"
"POT-Creation-Date: 2020-09-22 16:26+0200\n"
"PO-Revision-Date: 2020-09-22 14:42+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
@@ -22,205 +23,339 @@ msgstr ""
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (n % 10 ==0 || (n % 10 >=5 && n % 10 <=9) || (n % 100 >=11 && n % 100 <=14 )) ? 2: 3);\n"
#: ../../social_marketing.rst:5
#: ../../social_marketing/social_marketing/social_marketing.rst:2
msgid "Social Marketing"
msgstr "Меркетинг соцмереж"
#: ../../social_marketing/social_marketing.rst:3
msgid "Advanced Topics"
msgstr "Розширені теми"
#: ../../social_marketing/overview.rst:3
msgid "Overview"
msgstr "Загальний огляд"
#: ../../social_marketing/social_marketing/social_marketing.rst:4
msgid ""
"One of the biggest challenges of a company is to engage efficiently with "
"their community. Odoo Social helps you to meet your audience with the help "
"of several supports: social media, push notifications, or live chat request."
#: ../../social_marketing/overview/campaigns.rst:3
msgid "Connecting to my Marketplace with Campaigns"
msgstr ""
"Одним із найбільших випробувань компанії є ефективна співпраця з її "
"аудиторією. Соцмережі Odoo допомагають вам зустрітися з вашою аудиторію за "
"допомогою деякої підтримки: соцмережі, push-сповіщення або запит на живий "
"чат."
#: ../../social_marketing/social_marketing/social_marketing.rst:10
msgid "Add your social media and create your feed"
msgstr "Додайте ваші соцмережі та створіть канал"
#: ../../social_marketing/social_marketing/social_marketing.rst:12
#: ../../social_marketing/overview/campaigns.rst:5
msgid ""
"You first need to add your social media accounts. To do that, add a Stream "
"and choose your social media account. You’ll need to grant permissions to "
"Odoo Social Marketing application."
"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 ""
"Спершу вам потрібно додати ваші облікові записи соцмереж. Щоб зробити це, "
"додайте Стрім та оберіть ваш обліковий запис соцмережі. Вам потрібно буде "
"надати доступ до модуля Маркетинг соцмереж Odoo."
#: ../../social_marketing/social_marketing/social_marketing.rst:19
#: ../../social_marketing/overview/campaigns.rst:10
msgid "Go to :menuselection:`Social Marketing --> Campaigns --> Create`."
msgstr ""
#: ../../social_marketing/overview/campaigns.rst:16
msgid ""
"Once it’s done, you’ll be redirected to your Feed and a column will be "
"automatically added with the publications of your freshly added account. You"
" can then add new streams to your Feed and customize your Kanban view as you"
" like."
"As you create content, tabs for that specific channel are shown. The "
"overview of the campaign displays global metrics such as:"
msgstr ""
"Після того, як це буде виконано, вас буде перенаправлено на ваш канал, і "
"буде автоматично додано колонку з публікаціями щойно доданого облікового "
"запису. Потім ви можете додати нові стріми на ваш канал та налаштувати ваш "
"перегляд канбану, як вам подобається.."
#: ../../social_marketing/social_marketing/social_marketing.rst:28
#: ../../social_marketing/overview/campaigns.rst:19
msgid ""
"Adding social media accounts to your Feed will also add some KPIs on it:"
"*Revenue*: number of users who, from a link in your content, finished a "
"transaction (paid)."
msgstr ""
"Додаючи облікові записи соцмереж до вашого каналу, на нього також KPI:"
#: ../../social_marketing/social_marketing/social_marketing.rst:30
msgid "Audience: Number of followers of your channel"
msgstr "Аудиторія: Кількість підписників вашого каналу"
#: ../../social_marketing/social_marketing/social_marketing.rst:32
msgid "Engagement: Number of times people have engaged with your posts"
msgstr "Залучення: Кількість людей, залучених до ваших публікацій"
#: ../../social_marketing/social_marketing/social_marketing.rst:35
msgid "Stories: Number of times people who have engaged with your channel"
msgstr "Історії: Кількість людей, залучених до вашого каналу"
#: ../../social_marketing/social_marketing/social_marketing.rst:35
#: ../../social_marketing/overview/campaigns.rst:20
msgid ""
"have created stories on their friend’s or follower’s feed (Shares, "
"Retweet,..)"
"*Quotations*: number of users who, from a link in your content, have started"
" but not finished a transaction (did not pay)."
msgstr ""
"створили історії на каналі свого друга чи підписника (Поширення, Ретвіти,..)"
#: ../../social_marketing/social_marketing/social_marketing.rst:37
#: ../../social_marketing/overview/campaigns.rst:22
msgid ""
"You can access more information by clicking on the “Insights” link: this "
"will lead you to statistics of the selected social medium."
"*Leads*: users who have filled out your contact form, from a link in your "
"content."
msgstr ""
"Ви можете отримати більше інформації, натиснувши на посилання “Інформація”: "
"це направить вас на статистику обраної соцмережі."
#: ../../social_marketing/social_marketing/social_marketing.rst:41
#: ../../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/social_marketing/social_marketing.rst:43
#: ../../social_marketing/overview/manage_social.rst:53
msgid ""
"To publish content on your social media accounts or send a push notification"
" to your subscribed users, either go to your Feed and click on New Post, or "
"use the “Posts” menu and create it from there. Select all the accounts where"
" you want to post your content, write your post and get an instant preview "
"of how it will look when published."
"Click on :menuselection:`Social Marketing --> Feed --> New Post`, or go to "
":menuselection:`Social Marketing --> Posts → Create`."
msgstr ""
"Щоб опублікувати вміст на ваші облікові записи соцмереж або надіслати push-"
"сповіщення вашому підписаному користувачу, просто перейдіть на ваш Канал та "
"натисніть Нова публікація, або використовуйте меню “Публікації” та створіть "
"публікацію звідти. Оберіть облікові записи, де ви хочете опублікувати ваш "
"вміст, напишіть пост та отримайте миттєвий попередній перегляд того, як "
"виглядатиме пост після його опублікування."
#: ../../social_marketing/social_marketing/social_marketing.rst:49
#: ../../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 ""
"If you select the push notifications, you’ll get some additional fields on "
"the form that will allow you to complete the push notifications "
"configuration and choose your segment between all your subscribed users. You"
" can also send push notifications via the Visitors menu, as explained in the"
" previous paragraph."
"Through the calendar view, besides having an overview of your planned day, "
"week or month, also see your drafted, scheduled and published posts."
msgstr ""
"Якщо ви оберете push-сповіщення, ви отримаєте деякі додаткові поля на формі,"
" яка дозволить вам заповнювати налаштування push-сповіщень та обере сегмент "
"між усіма вашими підписниками. Ви також можете надсилати push-сповіщення "
"через меню Відвідувачі, як пояснено у попередньому параграфі."
#: ../../social_marketing/social_marketing/social_marketing.rst:56
msgid "Enable push notifications on your website"
msgstr "Увімкніть push-сповіщення на вашому сайті"
#: ../../social_marketing/overview/manage_social.rst:68
msgid "Drag and drop (scheduled posts) to change their scheduled date."
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:58
#: ../../social_marketing/overview/manage_social.rst:70
msgid ""
"The push notifications system uses a Firebase account, configured by "
"default. This feature allows you to send push notifications to your "
"website’s visitors after they subscribed to it. To enable push notifications"
" on your website, go to the Website application Settings, and configure the "
"notifications permission request."
"Double-click on a date to create a post directly from the *Calendar view*, "
"and click on an existing one to edit it."
msgstr ""
"Система push-сповіщень використовує обліковий запис Firebase, налаштований "
"за замовчуванням. Ця функція дозволяє вам надсилати push-сповіщення "
"відвідувачам вашого веб-сайту після їхньої підписки на нього. Щоби увімкнути"
" push-сповіщення на вашому сайті, перейдіть в Налаштування модуля Веб-сайт "
"та налаштуйте запит на дозвіл на сповіщення."
#: ../../social_marketing/social_marketing/social_marketing.rst:67
#: ../../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 ""
"Once it’s done, a popup will appear to your website’s visitors, asking them "
"to allow push notifications. As soon as they subscribe to it, you can start "
"sending them push notifications through the Visitors menu. You can either "
"send it individually or target a bigger segment by selecting multiple "
"visitors in the list view (e.g. all the visitors that visited your "
"Homepage)."
"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 ""
"Після того, як це буде виконано, сповіщення будуть з'являтися відвідувачам "
"вашого сайту, запитуючи їх про дозвіл на push-сповіщення. Як тільки вони "
"підпишуться на них, ви можете починати надсилати їм push-сповіщення через "
"меню Відвідувачів. Ви можете легко надсилати їх персонально або націлювати "
"їх на більший сегмент, обравши кілька відвідувачів у перегляді списку "
"(напр., усі відвідувачі, які відвідали Домашню сторінку)."
#: ../../social_marketing/social_marketing/social_marketing.rst:75
msgid "Interact with your online visitors"
msgstr "Взаємодійте з вашими відвідувачами онлайн"
#: ../../social_marketing/overview/push_notifications.rst:11
msgid "Ask users for permission"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:77
#: ../../social_marketing/overview/push_notifications.rst:13
msgid ""
"You can monitor your online visits via the Visitors menu. You’ll see every "
"visitors that landed on one of your tracked pages (you can configure your "
"tracked pages in the Website application), online or offline. Your online "
"visitors will be authenticated if they’re linked to a lead or an existing "
"partner. You will be able to contact them with an email, a message sms, a "
"push notification (if they have subscribed to it), or even send them a live "
"chat request that they will receive on their next move on one of your "
"tracked pages (if you installed the Live Chat application)."
"In the *Website* application go to :menuselection:`Website --> Configuration"
" --> Settings` and enable *Web Push Notifications*."
msgstr ""
"Ви можете моніторити ваші онлайн-відвідування через меню Відвідувачі. Ви "
"побачите кожного відвідувача, який зайшов на одну з ваших відслідковуваних "
"сторінок (ви можете налаштувати відслідковувані сторінки у модулі Веб-сайт),"
" онлайн або офлайн. Ваші онлайн-відвідувачі будуть автентифіковані, якщо "
"вони пов'язані з лідом або з існуючим партнером. Ви зможете зв'язатися з "
"ними через email, sms-повідомлення, push-сповіщення (якщо вони на них "
"підписані), або навіть надсилати їм запит на живий чат, який вони отримають "
"під час наступної дії на відслідковуваних сторінках (якщо ви встановили "
"модуль Живого чату)."
#: ../../social_marketing/social_marketing/social_marketing.rst:91
msgid "Configure your own Facebook and Twitter developer accounts"
msgstr "Налаштуйте ваші облікові записи розробника Facebook та Twitter"
#: ../../social_marketing/social_marketing/social_marketing.rst:93
#: ../../social_marketing/overview/push_notifications.rst:20
msgid ""
"By default, the Social application is already configured with a Facebook and"
" Twitter developer accounts but you can use your own if necessary. Activate "
"the developer mode, go to Configuration > Settings and enter your own API "
"keys."
"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 ""
"За замовчуванням модуль Соцмережі вже налаштовані з обліковим записом "
"розробника Facebook та Twitter, але ви можете використовувати власні, якщо "
"це необхідно. Активуйте режим розробника, перейдіть у Налаштування > "
"Налаштування та введіть ваші ключі API."
#: ../../social_marketing/social_marketing/social_marketing.rst:102
msgid "Configure your own Firebase API"
msgstr "Налаштуйте ваш власний API Firebase"
#: ../../social_marketing/overview/push_notifications.rst:28
msgid "Send notifications"
msgstr ""
#: ../../social_marketing/social_marketing/social_marketing.rst:104
#: ../../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 ""
"By default, a Firebase project is running on your database so there’s no "
"need to configure it. If you have multiple websites, every website will be "
"linked to a different Firebase project. If you need to configure your own "
"Firebase project, please go to :menuselection:`Website --> Configuration -->"
" Settings` Web Push Notifications section."
"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 ""
"За замовчуванням проект Firebase запускається на вашій базі даних, тому не "
"потрібно ніяких налаштувань. Якщо у вас кілька веб-сайтів, кожен веб-сайт "
"буде пов'язано з різними проектами Firebase. Якщо вам потрібно налаштувати "
"власний проект Firebase, перейдіть у :menuselection:`Веб-сайт --> "
"Налаштування --> Налаштування` секцію веб Push-сповіщення."
locale/uk/LC_MESSAGES/studio.po
+941
View File
@@ -0,0 +1,941 @@
# 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
# Alina Lisnenko <alinasemeniuk1@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: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/uk/LC_MESSAGES/support.po
+491
View File
@@ -0,0 +1,491 @@
# 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
# Alina Lisnenko <alinasemeniuk1@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: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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 ""
#: ../../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 ""
#: ../../support/supported_versions.rst:17
msgid "What's the support status of my Odoo?"
msgstr ""
#: ../../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 ""
#: ../../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 ""
#: ../../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 ""
#: ../../support/supported_versions.rst:30
msgid "Odoo 12.saas~3"
msgstr ""
#: ../../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 "Дані відсутні"
#: ../../support/supported_versions.rst:30
msgid "August 2019"
msgstr ""
#: ../../support/supported_versions.rst:32
msgid "**Odoo 12.0**"
msgstr ""
#: ../../support/supported_versions.rst:32
msgid "October 2018"
msgstr ""
#: ../../support/supported_versions.rst:34
msgid "Odoo 11.saas~3"
msgstr ""
#: ../../support/supported_versions.rst:34
msgid "April 2018"
msgstr ""
#: ../../support/supported_versions.rst:36
msgid "**Odoo 11.0**"
msgstr ""
#: ../../support/supported_versions.rst:36
msgid "October 2017"
msgstr ""
#: ../../support/supported_versions.rst:36
msgid "*End-of-support is planned for October 2020*"
msgstr ""
#: ../../support/supported_versions.rst:38
msgid "Odoo 10.saas~15"
msgstr ""
#: ../../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 ""
#: ../../support/supported_versions.rst:40
msgid "Odoo 10.saas~14"
msgstr ""
#: ../../support/supported_versions.rst:40
msgid "January 2017"
msgstr ""
#: ../../support/supported_versions.rst:42
msgid "**Odoo 10.0**"
msgstr ""
#: ../../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 ""
#: ../../support/supported_versions.rst:44
msgid "Odoo 9.saas~11"
msgstr ""
#: ../../support/supported_versions.rst:44
msgid "May 2016"
msgstr ""
#: ../../support/supported_versions.rst:46
msgid "**Odoo 9.0**"
msgstr ""
#: ../../support/supported_versions.rst:46
msgid "October 2015"
msgstr ""
#: ../../support/supported_versions.rst:48
msgid "Odoo 8.saas~6"
msgstr ""
#: ../../support/supported_versions.rst:48
msgid "February 2015"
msgstr ""
#: ../../support/supported_versions.rst:50
msgid "**Odoo 8.0**"
msgstr ""
#: ../../support/supported_versions.rst:50
msgid "September 2014"
msgstr ""
#: ../../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 ""
#: ../../support/supported_versions.rst:79
msgid ""
"OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform."
msgstr ""
#: ../../support/supported_versions.rst:81
msgid ""
"TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform."
msgstr ""
#: ../../support/supported_versions.rst:83
msgid ""
"You should consider `upgrading <https://upgrade.odoo.com/>`_ your database."
msgstr ""
#: ../../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 ""
"Ваша підписка на Odoo Online включає **необмежену підтримку 24 години на "
"добу без додаткових витрат з понеділка по п'ятницю**. Наші команди "
"розташовані по всьому світу, щоби забезпечити підтримку, незалежно від "
"вашого місцезнаходження. Ваш представник підтримки може зв'язатися з вами із"
" Сан-Франциско, Бельгії або Індії!"
#: ../../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 ""
"З нашою командою підтримки можна зв'язатися з нашою формою онлайн-підтримки "
"<https://www.odoo.com/help>`__."
#: ../../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 ""
"Відповіді на проблеми, які можуть виникнути у вашій стандартній базі даних "
"Odoo (наприклад, \"Я не можу закрити свою точку продажу\" або \"Я не можу "
"знайти мої KPI продажів?\")"
#: ../../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 ""
"Питання чи проблеми, пов'язані з конкретними розробками або налаштуваннями, "
"зробленими Odoo або третьою стороною (це стосується лише вашої бази даних "
"або включеного коду)"
#: ../../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 ""
"Ви можете отримати такий тип підтримки за допомогою `Пакету послуг "
"<https://www.odoo.com/pricing-packs>`__. Один із наших консультантів з таким"
" пакетом проаналізує, як працює ваш бізнес, і розповість вам, як ви можете "
"максимально використати свою базу даних Odoo. Ми будемо обробляти всі "
"налаштування та навчати вас, як користуватися Odoo."
#: ../../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/uk/LC_MESSAGES/survey.po
+240
View File
@@ -0,0 +1,240 @@
# 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
# Alina Lisnenko <alinasemeniuk1@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: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/uk/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
# Alina Lisnenko <alinasemeniuk1@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 15:13+0000\n"
"Last-Translator: Alina Lisnenko <alinasemeniuk1@gmail.com>, 2020\n"
"Language-Team: Ukrainian (https://www.transifex.com/odoo/teams/41243/uk/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: uk\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 != 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n % 100 > 14) ? 1 : n % 1 == 0 && (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/uk/LC_MESSAGES/website.po
+373 -165
View File
File diff suppressed because it is too large Load Diff