Skip to content

Commit

Permalink
Update tutorial with translations
Browse files Browse the repository at this point in the history
  • Loading branch information
@OHelesh @VDigitall
OHelesh authored and VDigitall committed Oct 30, 2020
1 parent 07442a4 commit af5fa22
Show file tree
Hide file tree
Showing 2 changed files with 37 additions and 23 deletions.
45 changes: 27 additions & 18 deletions docs/source/locale/uk/LC_MESSAGES/tendering/tutorial.po
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@ msgid ""
msgstr ""
"Project-Id-Version: openprocurement.api 0.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-10-07 20:36+0300\n"
"PO-Revision-Date: 2020-10-07 20:39+0200\n"
"POT-Creation-Date: 2020-10-12 19:16+0300\n"
"PO-Revision-Date: 2020-10-12 19:24+0200\n"
"Last-Translator: Oleh Helesh <[email protected]>\n"
"Language: uk\n"
"Language-Team: Ukrainian <[email protected]>\n"
Expand Down Expand Up @@ -390,30 +390,33 @@ msgstr ""
msgid "Let's see the list of all added contract documents:"
msgstr "Тепер переглянемо знову усі документи пов’язані із укладанням угоди:"

#, fuzzy
msgid "Contract signing tutorial"
msgstr "Встановити дату підписання угоди"
msgid "Contract signing flow"
msgstr "Процес підписання договору"

msgid "Checking if contract has the `pending` status:"
msgstr ""
msgstr "Перевіримо чи договір у статусі `pending`:"

msgid ""
"To identify a winner supplier we need to find a bid which owner won an"
" auction. Bid and award should be in the status `active`."
msgstr ""
"Для визначення постачальника-переможця нам потрібно знайти **bid**, власник"
" якого виграв аукціон. **Bid** та **Award** повинні мати статус `active`."

msgid ""
"Changing a contract status to `pending.winner-signing` by the tender owner:"
msgstr ""
"Змінимо статус договору на `pending.winner-signing` власником закупівлі."

msgid "Uploading a sign document to the contract document by supplier:"
msgstr ""
msgstr "Завантажимо підписаний документ у документ договору постачальником:"

msgid "Changing a contract status to `pending` by supplier:"
msgstr ""
msgstr "Змінимо статус контракту на `pending` постачальником:"

msgid "Uploading a sign document to the contract document by tender owner:"
msgstr ""
"Завантажимо підписаний документ у документ договору власником закупівлі:"

msgid "Set contract signature date"
msgstr "Встановити дату підписання угоди"
Expand Down Expand Up @@ -529,13 +532,13 @@ msgid "`contractForm` - document with recommended JSON form."
msgstr "`contractForm` - документ з рекомендовною JSON формою;"

msgid ""
"**! Note:** Documents are linked with `contractProforma` by new reference"
" type ``documentOf`` attribute equal to ``document`` and ``relatedItem``"
" equal to corresponding `contractProforma` document ``id``."
"Documents are linked with `contractProforma` by new reference type"
" ``documentOf`` attribute equal to ``document`` and ``relatedItem`` equal to"
" corresponding `contractProforma` document ``id``."
msgstr ""
"**! Примітка:** Ці документи пов'язані з `contractProforma` новим типом"
" зв'язку: атрибутом ``documentOf``, рівним ``document`` та ``relatedItem``,"
" рівним відповідному ``id`` документу `contractProforma`."
"Ці документи пов'язані з `contractProforma` новим типом зв'язку: атрибутом"
" ``documentOf``, рівним ``document`` та ``relatedItem``, рівним відповідному"
" ``id`` документу `contractProforma`."

msgid "Let's review above mentioned documents in tender:"
msgstr "Давайте переглянемо вищезгадані документи у закупівлі:"
Expand Down Expand Up @@ -645,11 +648,11 @@ msgstr ""
" та формує PDF/A версію договору на основі цього файлу."

msgid ""
"**! Note:** Process data related to **Plan, Tender, Award** and **Bid** at"
" the time of contract generation are complete and can not be modified."
"Process data related to **Plan, Tender, Award** and **Bid** at the time of"
" contract generation are complete and can not be modified."
msgstr ""
"**! Примітка:** Дані процесу, пов’язані з **Plan, Tender, Award** та **Bid**"
" на момент формування контракту, є кінцевими та не можуть бути змінені."
"Дані процесу, пов’язані з **Plan, Tender, Award** та **Bid** на момент"
" формування контракту, є кінцевими та не можуть бути змінені."

msgid ""
"In case of errors in aggregated `contractData` (from tender announcement or"
Expand All @@ -672,9 +675,15 @@ msgstr ""
"Здобуває оновлення даних про Замовника та/або Постачальника згідно"
" `contractSchema` з ``role``, рівною ``buyerCorrigenda``;"

msgid "Let's review updated document in tender:"
msgstr "Давайте переглянемо оновлений документ у закупівлі:"

#~ msgid "Tender announcment stage"
#~ msgstr ""

#~ msgid "Uploads `contractData` with information about Contracting Authority with ``role`` equal to ``buyer``;"
#~ msgstr "Завантажує `contractData` з інформацією про Замовника з ``role``, рівною ``buyer``;"

#~ msgid "Contract signing tutorial"
#~ msgstr "Встановити дату підписання угоди"

15 changes: 10 additions & 5 deletions docs/source/tendering/tutorial.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -340,8 +340,8 @@ Let's see the list of all added contract documents:
.. include:: http/tutorial/tender-contract-get-documents-again.http
:code:

Contract signing tutorial
--------------------------------
Contract signing flow
---------------------

Checking if contract has the `pending` status:

Expand Down Expand Up @@ -460,7 +460,7 @@ Afterwards system automatically (with the help of auxiliary component tempalte r
* `contractForm` - document with recommended JSON form.


**! Note:** Documents are linked with `contractProforma` by new reference type ``documentOf`` attribute equal to ``document`` and ``relatedItem`` equal to corresponding `contractProforma` document ``id``.
.. note:: Documents are linked with `contractProforma` by new reference type ``documentOf`` attribute equal to ``document`` and ``relatedItem`` equal to corresponding `contractProforma` document ``id``.


Let's review above mentioned documents in tender:
Expand Down Expand Up @@ -508,10 +508,10 @@ Contract signing stage

At the beginning of the contracting process auxiliary component rBot (renderer) generates a JSON `contractData` document based on aggregated data from various procedure objects, such as: **Plan, Tender, Bid, Award** and **Contract** and forms **PDF/A** version of contract based on this file.

.. include:: http/tutorial/tender-contract-get-documents.http
.. include:: http/tutorial/tender-contract-with-generated-documents.http
:code:

**! Note:** Process data related to **Plan, Tender, Award** and **Bid** at the time of contract generation are complete and can not be modified.
.. note:: Process data related to **Plan, Tender, Award** and **Bid** at the time of contract generation are complete and can not be modified.

In case of errors in aggregated `contractData` (from tender announcement or bid submission stages), Procuring Entity can upload updates for `contractData` to `contract` document until activation of the contract.

Expand All @@ -523,3 +523,8 @@ To do this marketplace of Contracting Authority performs following steps:

.. include:: http/tutorial/tender-contract-fix-contract-data-document.http
:code:

Let's review updated document in tender:

.. include:: http/tutorial/tender-contract-get-documents.http
:code:

0 comments on commit af5fa22

Please sign in to comment.