documentation/locale/uk/LC_MESSAGES/events.po

# 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: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"
"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 ""