From 7073e3294915d2f33efe41a15cdab17608be8835 Mon Sep 17 00:00:00 2001 From: Nick Volynkin Date: Wed, 6 Oct 2021 19:01:15 +0700 Subject: [PATCH] Fix text formatting and code examples according to Lua style guide (#2249) * Fix text formatting and code examples according to Lua style guide Translated by ainoneko, translation reviewed by Patience Daur and Alexander Turenko Co-authored-by: ainoneko Co-authored-by: Patience Daur Alexander Turenko --- doc/reference/reference_lua/key_def.rst | 68 ++-- .../ru/LC_MESSAGES/book/connectors/index.po | 16 +- .../LC_MESSAGES/contributing/contributing.po | 378 +++++++++--------- .../LC_MESSAGES/contributing/docs/examples.po | 29 +- .../ru/LC_MESSAGES/contributing/docs/infra.po | 84 ++-- .../LC_MESSAGES/contributing/docs/markup.po | 7 +- .../contributing/docs/markup/admonitions.po | 17 + .../contributing/docs/markup/links.po | 25 +- .../contributing/docs/sphinx-warnings.po | 70 ++-- .../ru/LC_MESSAGES/contributing/docs/style.po | 59 ++- .../ru/LC_MESSAGES/contributing/docs/terms.po | 83 ++-- .../reference/reference_lua/key_def.po | 203 +++++++--- .../ru/LC_MESSAGES/release/major-features.po | 4 +- 13 files changed, 572 insertions(+), 471 deletions(-) diff --git a/doc/reference/reference_lua/key_def.rst b/doc/reference/reference_lua/key_def.rst index 0328d56b2..a4d60f830 100644 --- a/doc/reference/reference_lua/key_def.rst +++ b/doc/reference/reference_lua/key_def.rst @@ -18,8 +18,9 @@ to extract or compare the index key values. Create a new key_def instance. :param table parts: field numbers and types. - There must be at least one part and it - must have at least fieldno and type. + There must be at least one part. + Every part must have the attributes ``type`` and ``fieldno``/``field``. + Other attributes are optional. :returns: key_def-object :ref:`a key_def object ` @@ -27,9 +28,10 @@ to extract or compare the index key values. the ``parts`` option in :ref:`Options for space_object:create_index() `. - fieldno (integer) for example fieldno = 1. It is legal to say field instead of fieldno. + ``fieldno`` (integer) for example ``fieldno = 1``. + It is legal to use ``field`` instead of ``fieldno``. - type (string) for example type = 'string'. + ``type`` (string) for example ``type = 'string'``. Other components are optional. @@ -54,15 +56,15 @@ to extract or compare the index key values. .. method:: extract_key(tuple) - Return a tuple containing only the fields of the key_def object. + Return a tuple containing only the fields of the ``key_def`` object. :param table tuple: tuple or Lua table with field contents - :return: the fields that were defined for the key_def object + :return: the fields that were defined for the ``key_def`` object **Example #1:** - .. code-block:: none + .. code-block:: tarantoolsession -- Suppose that an item has five fields -- 1, 99.5, 'X', nil, 99.5 @@ -76,7 +78,7 @@ to extract or compare the index key values. ... tarantool> k = key_def.new({{type = 'string', fieldno = 3}, - > {type = 'unsigned', fieldno =1 }}) + > {type = 'unsigned', fieldno = 1}}) --- ... @@ -87,7 +89,7 @@ to extract or compare the index key values. **Example #2** - .. code-block:: none + .. code-block:: lua -- Now suppose that the item is a tuple in a space which -- has an index on field #3 plus field #1. @@ -96,14 +98,14 @@ to extract or compare the index key values. -- The result will be the same. key_def = require('key_def') box.schema.space.create('T') - i = box.space.T:create_index('I',{parts={3,'string',1,'unsigned'}}) + i = box.space.T:create_index('I', {parts={3, 'string', 1, 'unsigned'}}) box.space.T:insert{1, 99.5, 'X', nil, 99.5} k = key_def.new(i.parts) k:extract_key(box.space.T:get({'X', 1})) **Example #3** - .. code-block:: none + .. code-block:: lua -- Iterate through the tuples in a secondary non-unique index. -- extracting the tuples' primary-key values so they can be deleted @@ -125,11 +127,11 @@ to extract or compare the index key values. .. method:: compare(tuple_1, tuple_2) - Compare the key fields of tuple_1 to the key fields of tuple_2. + Compare the key fields of ``tuple_1`` to the key fields of ``tuple_2``. This is a tuple-by-tuple comparison so users do not have to write code which compares a field at a time. Each field's type and collation will be taken into account. - In effect it is a comparison of extract_key(tuple_1) with extract_key(tuple_2). + In effect it is a comparison of ``extract_key(tuple_1)`` with ``extract_key(tuple_2)``. :param table tuple1: tuple or Lua table with field contents :param table tuple2: tuple or Lua table with field contents @@ -140,22 +142,22 @@ to extract or compare the index key values. **Example:** - .. code-block:: none + .. code-block:: lua -- This will return 0 key_def = require('key_def') - k = key_def.new({{type='string',fieldno=3,collation='unicode_ci'}, - {type='unsigned',fieldno=1}}) + k = key_def.new({{type = 'string', fieldno = 3, collation = 'unicode_ci'}, + {type = 'unsigned', fieldno = 1}}) k:compare({1, 99.5, 'X', nil, 99.5}, {1, 99.5, 'x', nil, 99.5}) .. _key_def-compare_with_key: .. method:: compare_with_key(tuple_1, tuple_2) - Compare the key fields of tuple_1 to all the fields of tuple_2. + Compare the key fields of ``tuple_1`` to all the fields of ``tuple_2``. This is the same as :ref:`key_def_object:compare() ` - except that tuple_2 contains only the key fields. - In effect it is a comparison of extract_key(tuple_1) with tuple_2. + except that ``tuple_2`` contains only the key fields. + In effect it is a comparison of ``extract_key(tuple_1)`` with ``tuple_2``. :param table tuple1: tuple or Lua table with field contents :param table tuple2: tuple or Lua table with field contents @@ -166,22 +168,22 @@ to extract or compare the index key values. **Example:** - .. code-block:: none + .. code-block:: lua -- This will return 0 key_def = require('key_def') - k = key_def.new({{type='string',fieldno=3,collation='unicode_ci'}, - {type='unsigned',fieldno=1}}) + k = key_def.new({{type = 'string', fieldno = 3, collation = 'unicode_ci'}, + {type = 'unsigned', fieldno = 1}}) k:compare_with_key({1, 99.5, 'X', nil, 99.5}, {'x', 1}) .. _key_def-merge: .. method:: merge (other_key_def_object) - Combine the main key_def_object with other_key_def_object. - The return value is a new key_def_object containing all the fields of - the main key_def_object, then all the fields of other_key_def_object which - are not in the main key_def_object. + Combine the main ``key_def_object`` with ``other_key_def_object``. + The return value is a new ``key_def_object`` containing all the fields of + the main ``key_def_object``, then all the fields of ``other_key_def_object`` which + are not in the main ``key_def_object``. :param key_def_object other_key_def_object: definition of fields to add @@ -189,9 +191,9 @@ to extract or compare the index key values. **Example:** - .. code-block:: none + .. code-block:: lua - -- This will return a key definition with fieldno=3 and fieldno=1. + -- This will return a key definition with fieldno = 3 and fieldno = 1. key_def = require('key_def') k = key_def.new({{type = 'string', fieldno = 3}}) k2= key_def.new({{type = 'unsigned', fieldno = 1}, @@ -202,11 +204,11 @@ to extract or compare the index key values. .. method:: totable() - Return a table containing what is in the key_def_object. + Return a table containing what is in the ``key_def_object``. This is the reverse of ``key_def.new()``: - * ``key_def.new()`` takes a table and returns a key_def object, - * ``key_def_object:totable()`` takes a key_def object and returns a table. + * ``key_def.new()`` takes a table and returns a ``key_def`` object, + * ``key_def_object:totable()`` takes a ``key_def`` object and returns a table. This is useful for input to ``_serialize`` methods. @@ -214,9 +216,9 @@ to extract or compare the index key values. **Example:** - .. code-block:: none + .. code-block:: lua - -- This will return a table with type='string', fieldno=3 + -- This will return a table with type = 'string', fieldno = 3 key_def = require('key_def') k = key_def.new({{type = 'string', fieldno = 3}}) k:totable() diff --git a/locale/ru/LC_MESSAGES/book/connectors/index.po b/locale/ru/LC_MESSAGES/book/connectors/index.po index b1c7674bf..adb1f6f79 100644 --- a/locale/ru/LC_MESSAGES/book/connectors/index.po +++ b/locale/ru/LC_MESSAGES/book/connectors/index.po @@ -257,7 +257,7 @@ msgstr "" "поддерживает как отдельные узлы и кластеры Tarantool, так и приложения, " "созданные с использованием :doc:`фреймворка Cartridge ` и " "его модулей. Команда Tarantool активно добавляет в этот модуль новейшие " -"функциональные возможности Tarantool." +"функциональные возможности платформы." msgid "" "`tarantool-java `__ works with " @@ -268,11 +268,13 @@ msgstr "" "`tarantool-java `__ " "предназначен для ранних версий Tarantool (1.6 и выше) и предоставляет " "интерфейс JDBC для одиночных узлов Tarantool. Этот модуль *в настоящее время" -" не поддерживается* и не работает с новейшими функциональными возможностями " -"Tarantool 2.x и с кластерами Tarantool." +" не поддерживается* и не работает ни с новейшими функциональными " +"возможностями Tarantool 2.x, ни с кластерами Tarantool." msgid "The following modules support Java libraries and frameworks:" -msgstr "Следующие модули поддерживают библиотеки и фреймворки Java:" +msgstr "" +"Для работы с библиотеками и фреймворками Java в Tarantool существуют " +"следующие модули:" msgid "" "`TestContainers Tarantool module `__ to get familiar" " with using this module in real applications." msgstr "" -"`Проект Spring Pet Clinic `__, показывает, как использовать этот модуль в реальных " -"приложениях." +"Чтобы узнать, как использовать этот модуль в реальных приложениях, " +"ознакомьтесь с `проектом Spring Pet Clinic " +"`__." msgid "Go" msgstr "Go" diff --git a/locale/ru/LC_MESSAGES/contributing/contributing.po b/locale/ru/LC_MESSAGES/contributing/contributing.po index 0d89738a9..a5b10ade9 100644 --- a/locale/ru/LC_MESSAGES/contributing/contributing.po +++ b/locale/ru/LC_MESSAGES/contributing/contributing.po @@ -1,5 +1,5 @@ -msgid "How to be involved in Tarantool" +msgid "How to get involved in Tarantool" msgstr "" msgid "What is Tarantool?" @@ -8,8 +8,8 @@ msgstr "" msgid "" "Tarantool is an open source database that can store everything in RAM. Use " "Tarantool as a cache with the ability to save data to disk. Tarantool serves" -" up to a million requests per second, secondary index searches, and SQL " -"support." +" up to a million requests per second, allows for secondary index searches, " +"and has SQL support." msgstr "" msgid "" @@ -31,39 +31,39 @@ msgstr "" msgid "" "This is the easiest way to get your questions answered. Many people are " -"afraid to ask questions because they think they are \"wasting the experts' " -"time,\" but no one really thinks so. Contributors are important to us." +"afraid to ask questions because they believe they are \"wasting the experts'" +" time,\" but we don't really think so. Contributors are important to us." msgstr "" msgid "" -"Also we have a `Stack Overflow tag " +"We also have a `Stack Overflow tag " "`_." msgstr "" msgid "Join the chat and ask questions." msgstr "" -msgid "How to leave feedback, ideas or suggestions?" +msgid "How to leave feedback, ideas, or suggestions?" msgstr "" msgid "You can leave your feedback or share ideas in different ways:" msgstr "" msgid "" -"**The simplest way** is to write `here " +"**The simplest way** is to fill `the feedback form " "`__. All you need to do " -"is fill in one product comment field and send it to us. If you don't mind --" -" leave your email address. If you wish, we can involve you in the product " +"is fill in one product comment field and click \"Send.\" You can optionally " +"provide your email address. If you wish, we can involve you in the product " "development process." msgstr "" msgid "" "**A more technical way** is to create a ticket on GitHub. If you have a " -"suggestion for a new feature or information about a bug, `follow the link " -"`_ and leave a ticket. " -"The link leads to the ``tarantool/tarantool`` repository. For any other " -"projects on GitHub select \"Issues\" - \"New issue\"." +"suggestion for a new feature or information about a bug, `create a new " +"GitHub issue `_. The link" +" leads to the ``tarantool/tarantool`` repository. To leave feedback for our " +"other projects on GitHub, select \"Issues\" > \"New issue.\"" msgstr "" msgid "" @@ -71,9 +71,7 @@ msgid "" "`_." msgstr "" -msgid "" -"You can chat with the team in the general product chat. They are divided by " -"language:" +msgid "To talk to our team about a product, go to one of our chats:" msgstr "" msgid "`Russian-speaking `_" @@ -83,46 +81,44 @@ msgid "`English-speaking `_" msgstr "" msgid "" -"If this communication channel is inconvenient for you or there is simply no " -"Telegram, you can leave your comment on `tarantool.io " -"`_. Fill out the form at the bottom of the site and" -" leave your email. We read each request and respond to them usually within 2" -" days." +"If Telegram is inconvenient for you or simply isn't working, you can leave " +"your comment on `tarantool.io `_. Fill out the form" +" at the bottom of the site and leave your email. We read every request and " +"respond to them usually within 2 days." msgstr "" -msgid "How to contribute?" +msgid "How to contribute" msgstr "" msgid "There are many ways to contribute to Tarantool:" msgstr "" msgid "" -"Code -- Contribute to the code. We have components written in C, Lua, " -"Python, Go, and other languages." +"Code: Contribute to the code. We have components written in C, Lua, Python, " +"Go, and other languages." msgstr "" msgid "" -"Write -- Improve documentation, write blog posts, create tutorials or " -"solution pages." +"Write: Improve documentation, write blog posts, create tutorials or solution" +" pages." msgstr "" msgid "" -"Q&A -- Share your acknowledgments at Stack Overflow with tag `#tarantool " -"`_." +"Q&A: Share your experience on Stack Overflow with the `#tarantool " +"`_ tag." msgstr "" msgid "" -"Spread the word -- Share your accomplishments in social media using the " -"``#tarantool`` hashtags (or CC ``@tarantooldb`` in Twitter)." -msgstr "" - -msgid "Tarantool Ecosystem" +"Spread the word: Share your accomplishments on social media using the " +"``#tarantool`` hashtag (or CC ``@tarantooldb`` on Twitter)." msgstr "" -msgid "Tarantool has a large ecosystem of tools around the product itself." +msgid "Tarantool ecosystem" msgstr "" -msgid "We divide the Tarantool ecosystem into 4 types:" +msgid "" +"Tarantool has a large ecosystem of tools. We divide the ecosystem into four " +"large blocks:" msgstr "" msgid "Tarantool itself." @@ -135,14 +131,15 @@ msgid "Connectors for programming languages." msgstr "" msgid "" -"Applied tools. See a selection including external tools in the `\"awesome " -"Tarantool\" list `_." +"Applied tools. See the curated `Awesome Tarantool list " +"`_, which also includes " +"external tools." msgstr "" msgid "" -"First-time tasks can be easily found in the issues section of any repository" -" by the \"good first issue\" tag. These are beginner to intermediate tasks " -"that will help you get comfortable with the tool." +"To start contributing, check the \"good first issue\" tag in the issues " +"section of any of our repositories. These are beginner to intermediate tasks" +" that will help you get comfortable with the tool." msgstr "" msgid "" @@ -152,8 +149,8 @@ msgid "" msgstr "" msgid "" -"For each repository we have a queue for reviewing, and reviewing your " -"changes can be delayed. We try to give the first answer within two days. " +"There is a review queue in each of our repositories, so your changes may not" +" be reviewed immediately. We usually give the first answer within two days. " "Depending on the ticket and its complexity, the review time may take a week " "or more." msgstr "" @@ -161,11 +158,10 @@ msgstr "" msgid "Please do not hesitate to tag the maintainer in your GitHub ticket." msgstr "" -msgid "Read further about the contribution to each of the blocks." +msgid "Read on to learn about contributing to different ecosystem blocks." msgstr "" -msgid "" -"You have a problem in documentation. How to tell about it and how to fix it?" +msgid "Documentation: How to report and fix problems" msgstr "" msgid "There are several ways to improve the documentation:" @@ -173,196 +169,199 @@ msgstr "" msgid "" "**The easiest one** is to leave your comment on the web documentation page. " -"All you need to do is click on the red button in the bottom right corner of " -"the page and fill in the comment field. You can point out an error, provide " -"feedback on the current article, or suggest changes. We review each comment " -"and take it to work. This form is built into the documentation on the " -"Tarantool website." +"To use the built-in feedback form, just click the red button in the bottom " +"right corner of the page and fill in the comment field. You can point out an" +" error, provide feedback on the current article, or suggest changes. We " +"review each comment and work with it." msgstr "" msgid "" -"**Advanced** -- All Tarantool documentation tasks are `in the repository " -"`_. Here you can take any tasks and" -" suggest your changes. Our documentation is written in the `reStructuredText" -" markup " +"**Advanced**: All Tarantool documentation tasks can be found in the " +"`repository `_. Go to any task and " +"suggest your changes. We write our documentation using `reStructuredText " +"markup " "`_, and " -"we have a :doc:`writing style guide `. After making the change, you " -"need to build the documentation locally and see how it was laid out. This is" -" done automatically in Docker. `Read more in the README of the tarantool/doc" -" repository `_." +"we have a :doc:`writing style guide `. After you make the change, " +"build the documentation locally and see how it works. This can be done " +"automatically in Docker. To learn more, check the `README of the " +"tarantool/doc repository `_." msgstr "" msgid "" -"Some projects have their documentation in the code repository. For example, " -"`Tarantool Cartridge `_. This is " -"done on purpose, so the developers themselves can update it faster. " -"Instructions for building such documentation sets are in the code " -"repository." +"Some projects, like `Tarantool Cartridge " +"`_, have their documentation in the" +" code repository. This is done on purpose, so the developers themselves can " +"update it faster. You can find instructions for building such documentation " +"in the code repository." msgstr "" msgid "" -"If you find that the documentation in the README of a module or, for " -"example, a connector is incomplete or wrong, the best way to influence this " -"is to fix it yourself. Clone the repository, fix the bug, and suggest " -"changes as a PR (pull request). It will take you 5 minutes and will help the" -" whole community." +"If you find that the documentation provided in the README of a module or a " +"connector is incomplete or wrong, the best way to influence this is to fix " +"it yourself. Clone the repository, fix the bug, and suggest changes in a " +"pull request. It will take you five minutes but it will help the whole " +"community." msgstr "" msgid "" -"If for some reason you cannot fix it, create a ticket in this repository and" -" report the error. Such errors are fixed quickly." +"If you cannot fix it for any reason, create a ticket in the repository and " +"report the error. It will be fixed promptly." msgstr "" msgid "How to contribute to modules" msgstr "" msgid "" -"Tarantool is a database with an embedded application server. You can write " -"any code in C and Lua and pack it in distributable modules." +"Tarantool is a database with an embedded application server. This means you " +"can write any code in C or Lua and pack it in distributable modules." msgstr "" -msgid "Here are examples of official modules:" +msgid "" +"We have official and unofficial modules. Here are some of our official " +"modules:" msgstr "" msgid "" -"`HTTP server `_ -- HTTP server " +"`HTTP server `_: HTTP server " "implementation with middleware support." msgstr "" msgid "" -"`queue `_ - Tarantool implementation of " -"a persistent message queue." +"`queue `_: Tarantool implementation of " +"the persistent message queue." msgstr "" msgid "" -"`metrics `_ - ready-to-use solution " -"for collecting metrics." +"`metrics `_: Ready-to-use solution for" +" collecting metrics." msgstr "" msgid "" -"`cartridge `_ - framework for " -"writing distributed applications." +"`cartridge `_: Framework for writing" +" distributed applications." +msgstr "" + +msgid "Official modules are provided in our organization on GitHub." msgstr "" msgid "" -"Modules are distributed through our package manager, which is already " -"preinstalled with Tarantool." +"All modules are distributed through our package manager, which is pre-" +"installed with Tarantool. That also applies to unofficial modules, which " +"means that other users can get your module easily." msgstr "" msgid "" -"We have official modules and unofficial ones. The official ones are those " -"that are in our organization on GitHub. But we distribute unofficial ones " -"via our package manager too so that other users can get your module easily. " -"If you want to add your module to our GitHub organization -- `text us here " -"`_." +"If you want to add your module to our GitHub organization, `send us a " +"message on Telegram `_." msgstr "" -msgid "Want to contribute to an existing module" +msgid "Contributing to an existing module" msgstr "" msgid "" -"Tasks for contributors can be easily found in the issues section of any " -"repository by the \"good first issue\" tag. These are tasks of an initial or" -" intermediate level of difficulty that will help you get comfortable in the " -"module of interest." +"Tasks for contributors can be found in the issues section of any repository " +"under the \"good first issue\" tag. These tasks are beginner or intermediate" +" in terms of difficulty level, so you can comfortably get used to the module" +" of your interest." msgstr "" msgid "" -"Look at the `currently open tasks " +"Check the `currently open tasks " "`_" " for the HTTP Server module." msgstr "" -msgid "" -"The style guide for the Lua code we are following is :ref:`here " -"`." +msgid "Please see our :doc:`Lua style guide `." msgstr "" msgid "" -"You can contact the current maintainer through MAINTAINERS, which is located" -" in the root of the repository. If there is not such a file -- `let us know " -"`_. We will respond within one to two days." +"You can find the contact of the current maintainer in the MAINTAINERS file, " +"located in the root of the repository. If there is no such file, please `let" +" us know `_. We will respond within two days." msgstr "" msgid "" "If you see that the project does not have a maintainer or is inactive, you " -"can become one yourself. See the section :ref:`How to become a maintainer " -"`." +"can become its maintainer yourself. See the :ref:`How to become a maintainer" +" ` section." msgstr "" -msgid "Want to create a new module" +msgid "Creating a new module" msgstr "" msgid "" -"You can also create any custom modules and share them with the community. " -"`Look at the module template `_ and " -"write your own." +"You can also create custom modules and share them with the community. `Look " +"at the module template `_ and write " +"your own." msgstr "" msgid "How to contribute to Tarantool Core" msgstr "" msgid "" -"Tarantool is written mostly in C. Some parts are written in C++ and Lua. " -"Review can take longer because we want it to be reliable." +"Tarantool is written mostly in C. Some parts are in C++ and Lua. Your " +"contributions to Tarantool Core may take longer to review because we want " +"the code to be reliable." msgstr "" msgid "To start:" msgstr "" -msgid ":ref:`learn how to build Tarantool `" +msgid ":doc:`Learn how to build Tarantool `." msgstr "" msgid "" -"read about Tarantool architecture and main modules (`here " -"`__ and `here " -"`__)" +"Read about Tarantool architecture and main modules on the `developer site " +"`__ and on `GitHub " +"`__." msgstr "" msgid "" -"We have standards that we try to adhere to when developing in Tarantool. " -"These are the Style Guide and Contribution Guide :ref:`links " -"`. They tell you how to format your code, how to " -"format your commits, and how to write your test and make sure you don't " -"break anything." +"In Tarantool development, we strive to follow the standards laid out in our " +":doc:`style and contribution guides `. " +"These documents explain how to format your code and commits as well as how " +"to write tests without breaking anything accidentally." msgstr "" msgid "" -"They will also help you make a patch that is easier to check, which will " -"allow you to quickly push changes to master." +"The guidelines also help you create patches that are easy to check, which " +"allows quickly pushing changes to master." msgstr "" msgid "" -"Before your first commit, read `this article " +"Please read about `our code review procedure " "`_!" +"coding-points-to-check>`_ before making your first commit." msgstr "" -msgid "A patch can be offered in two ways:" +msgid "Here are two ways to suggest a patch:" msgstr "" msgid "" -"(preferred) Using a fork and pull mechanism on GitHub: make changes to your " -"copy of the repository and submit to us for review. See details `here " -"`__." +"(preferred) Using the fork and pull mechanism on GitHub: Make changes to " +"your copy of the repository and submit it to us for review. Check the " +"`GitHub documentation `__ to learn " +"how to do it." msgstr "" msgid "" -"Suggest a patch via the mailing list. Our developers are discussing most of " -"the features there. See details :ref:`here `." +"Suggest a patch via the mailing list. This is where our developers discuss " +"most features. Learn more in :ref:`the article on submitting patches " +"`." msgstr "" -msgid "How to write a test" +msgid "How to write tests" msgstr "" msgid "" -"The database is a product that is expected to be as reliable as possible. We" -" at Tarantool have developed a dedicated test framework for developing test " -"scripts that test Tarantool itself. The framework is called ``test-run``." +"A database is a product that is expected to be as reliable as possible. We " +"at Tarantool created ``test-run``, a dedicated test framework for developing" +" scripts that test Tarantool itself." msgstr "" -msgid "Writing your own test is not difficult. See test examples here:" +msgid "" +"Writing your own test is not difficult. Check out the following examples:" msgstr "" msgid "" @@ -376,45 +375,40 @@ msgid "" msgstr "" msgid "" -"We also have a CI that automatically checks build and test coverage for new " -"changes on all supported operating systems. This happens after any commit to" -" the repository." +"We also have a CI workflow that automatically checks build and test coverage" +" for new changes on all supported operating systems. The workflow is " +"launched after every commit to the repository." msgstr "" msgid "" -"The QA team has many tasks for specialists who are involved in checking the " -"quality of the product and tools. They provide test coverage for products, " -"help develop the test framework, and introduce and maintain new tools to " -"test the stability of releases." +"We have many tasks for QA specialists. Our QA team provides test coverage " +"for our products, helps develop the test framework, and introduces and " +"maintains new tools to test the stability of our releases." msgstr "" msgid "" -"We test modules differently: for modules, we use the `luatest " -"`_ framework. This is a fork of the " -"popular framework in the Lua community, which we have enhanced and optimized" -" for our tasks. See `examples " +"For modules, we use `luatest `_--- our" +" fork of a framework popular in the Lua community, enhanced and optimized " +"for our tasks. See `examples " "`_. of writing tests " "for a module." msgstr "" -msgid "Read: writing tests in Tarantool, writing unit tests. ???" -msgstr "" - msgid "How to contribute to language connectors" msgstr "" msgid "" -"A connector is a library that provides an API for accessing Tarantool from a" -" programming language. Tarantool uses its own binary protocol for access, " -"and the connector's task is to transfer user requests to the database and " +"A connector is a library that provides an API to access Tarantool from a " +"programming language. Tarantool uses its own binary protocol for access, and" +" the connector's task is to transfer user requests to the database and " "application server in the required format." msgstr "" msgid "" "Data access connectors have already been implemented for all major " "languages. If you want to write your own connector, you first need to " -"familiarize yourself with the Tarantool binary protocol. Its current " -"description can be found :ref:`here `." +"familiarize yourself with the Tarantool binary protocol. Read :doc:`the " +"protocol description ` to learn more." msgstr "" msgid "We consider the following connectors as references:" @@ -426,70 +420,69 @@ msgstr "" msgid "" "`net.box " "`_" -" — binary protocol client in Tarantool" +"---Tarantool binary protocol client" msgstr "" msgid "You can look at them to understand how to do it right." msgstr "" msgid "" -"The Tarantool ecosystem has connectors that are supported by the Tarantool " -"team itself, and there are connectors that are developed and supported " -"exclusively by the community. All of them have their pros and cons. See a " -"`complete list of connectors and their recommended versions " +"Some connectors in the Tarantool ecosystem are supported by the Tarantool " +"team. Others are developed and supported exclusively by the community. All " +"of them have their pros and cons. See the `complete list of connectors and " +"their recommended versions " "`_." msgstr "" msgid "" -"If you are using an existing connector from the community and want to " -"implement new features or fix a bug, then send your PRs via GitHub to the " -"desired repository." +"If you are using a community connector and want to implement new features " +"for it or fix a bug, send your PRs via GitHub to the connector repository." msgstr "" msgid "" -"To contact the author of the connector in case of questions, look in the " -"MAINTAINERS file: there will be contacts of the repository maintainer. If " -"there is no such file -- `text us here `_. We will " -"help you figure it out. We usually answer within one day." +"If you have questions for the author of the connector, check the MAINTAINERS" +" file for the repository maintainer's contact. If there is no such file, " +"`send us a message on Telegram `_. We will help you " +"figure it out. We usually answer within one day." msgstr "" msgid "How to contribute to tools" msgstr "" msgid "" -"The Tarantool ecosystem has tools that help in operation, deploy " -"applications, or allow working with Kubernetes." +"The Tarantool ecosystem has tools that facilitate the workflow, help with " +"application deployment, or allow working with Kubernetes." msgstr "" -msgid "Examples of tools from the Tarantool team:" +msgid "Here are some of the tools created by the Tarantool team:" msgstr "" msgid "" -"`ansible-cartridge `_: " -"Ansible role for deploying an application on Cartridge" +"`ansible-cartridge `_: an " +"Ansible role to deploy Cartridge applications." msgstr "" msgid "" -"`cartridge-cli `_: CLI utility " -"for creating applications, launching clusters locally on Cartridge and " -"solving operational problems" +"`cartridge-cli `_: a CLI utility" +" for creating applications, launching clusters locally on Cartridge, and " +"solving operation problems." msgstr "" msgid "" -"`tarantool-operator `_: " -"Kubernetes operator for cluster orchestration" +"`tarantool-operator `_: a " +"Kubernetes operator for cluster orchestration." msgstr "" msgid "" "These tools can be installed via standard package managers: ``ansible " -"galaxy``, ``yum``, ``apt-get``, respectively." +"galaxy``, ``yum``, or ``apt-get``." msgstr "" msgid "" -"If you have a tool that might go well in our curated `\"awesome Tarantool\" " -"list `_ you can read the " -"`guide for contributors `_ there and submit a pull request." +"If you have a tool that might go well in our curated `Awesome Tarantool list" +" `_, read the `guide for " +"contributors `_ and submit a pull request." msgstr "" msgid "How to become a maintainer" @@ -497,29 +490,30 @@ msgstr "" msgid "" "Maintainers are people who can merge PRs or commit to master. We expect " -"maintainers to answer questions and tickets in time, and do code reviews." +"maintainers to answer questions and tickets on time as well as do code " +"reviews." msgstr "" msgid "" -"If you need to get a review but no one responds for a week, take a look at " -"the Maintainers section of the ``README.md`` in the repository. Write to the" -" person listed there. If you have not received an answer in 3-4 days, you " -"can escalate the question `here `__." +"If you need to get a review but no one responds within a week, take a look " +"at the Maintainers section of the repository's ``README.md``. Write to the " +"person listed there. If you have not received an answer within 3--4 days, " +"you can escalate the question `on Telegram `__." msgstr "" msgid "" -"A repository may have no maintainers (the Maintainers list in ``README.md`` " -"is empty), or existing maintainers may be inactive. Then you can become a " -"maintainer yourself. We think it's better if the repository is maintained by" -" a newbie than if the repository is dead. So don't be shy: we love " -"maintainers and help them figure it out." +"A repository may have no maintainers (empty Maintainers list in " +"``README.md``), or the existing maintainers may be inactive. In this case, " +"you can become a maintainer yourself. We think it's better if the repository" +" is maintained by a newbie than if the repository is dead. So don't be shy: " +"we love maintainers and help them figure it all out." msgstr "" msgid "" "All you need to do is fill out `this form " "`_." -" Indicate which repository you want to access, the reason (inactivity, the " -"maintainer is not responding), and how to contact you. We will consider the " -"application in 1 day and either give you the rights or tell you what else " +" Tell us what repository you want to access, the reason (inactivity, the " +"maintainer is not responding), and how to contact you. We will consider your" +" application in 1 day and either give you the rights or tell you what else " "needs to be done." msgstr "" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/examples.po b/locale/ru/LC_MESSAGES/contributing/docs/examples.po index 7fb458358..538a00f42 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/examples.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/examples.po @@ -3,8 +3,8 @@ msgid "Examples and templates" msgstr "Примеры и шаблоны" msgid "" -"In this document, we explain general guidelines for describing Tarantool API" -" and give some examples and templates." +"This document contains general guidelines for describing the Tarantool API, " +"as well as examples and templates." msgstr "" msgid "Use this checklist for documenting a function or a method:" @@ -28,7 +28,7 @@ msgstr "" msgid "Complexity factors (if exist)" msgstr "" -msgid "Note re storage engine (if exists)" +msgid "Usage with memtx and vinyl (if differs)" msgstr "" msgid "Example(s)" @@ -37,12 +37,12 @@ msgstr "" msgid "Extra information (if needed)" msgstr "" -msgid "Documenting a function" +msgid "Documenting functions" msgstr "" msgid "" -"We describe functions of Tarantool modules via Sphinx directives ``.. " -"module::`` and ``.. function::``:" +"We use the Sphinx directives ``.. module::`` and ``.. function::`` to " +"describe functions of Tarantool modules:" msgstr "" msgid "" @@ -77,7 +77,7 @@ msgid "" " ...\n" msgstr "" -msgid "And the resulting output looks like this:" +msgid "The resulting output looks like this:" msgstr "" msgid "" @@ -137,22 +137,22 @@ msgstr "" "---\n" "..." -msgid "Documenting class method and data" +msgid "Documenting class methods and data" msgstr "" msgid "" -"Description of a method is similar to a function, but the ``.. class::`` " +"Methods are described similarly to functions, but the ``.. class::`` " "directive, unlike ``.. module::``, requires nesting." msgstr "" msgid "" -"As for documenting data, it will be enough to write a description, a return " -"type, and an example." +"As for data, it's enough to write the description, the return type, and an " +"example." msgstr "" msgid "" -"Here is an example of documenting a method and data of a class " -"``index_object``:" +"Here is the example documentation describing the method and data of the " +"``index_object`` class:" msgstr "" msgid "" @@ -201,6 +201,9 @@ msgid "" " ...\n" msgstr "" +msgid "And the resulting output looks like this:" +msgstr "" + msgid "Search for a tuple :ref:`via the given index `." msgstr "" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/infra.po b/locale/ru/LC_MESSAGES/contributing/docs/infra.po index 35bfb59f4..323a0cfa1 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/infra.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/infra.po @@ -3,40 +3,40 @@ msgid "Documentation infrastructure" msgstr "" msgid "" -"In this section of the :doc:`documentation guidelines `," -" we deal with some support activities to ensure the correct building of " -"documentation." +"This section of the :doc:`documentation guidelines ` " +"discusses some of the support activities that ensure the correct building of" +" documentation." msgstr "" msgid "Adding submodules" msgstr "" msgid "" -"The source files with the documentation content are mainly stored in the " -"`documentation repository `_. However, in " -"some of the cases the content source files are stored in repositories of " -"other Tarantool-related products and modules, for example, `Cartridge " -"`_, `Monitoring " -"`__, and " -"some others." +"The documentation source files are mainly stored in the `documentation " +"repository `_. However, in some cases, " +"they are stored in the repositories of other Tarantool-related products or " +"modules---`Cartridge `_, `Monitoring" +" `__, and " +"others." msgstr "" msgid "" -"In this case, we need to add such a repository containing the source files " -"as a submodule to the `documentation repository " -"`_ and set up other necessary settings to " -"ensure the proper building of the entire body of Tarantool documentation " -"presented at the `official web-site `_." +"If you are working with source files from a product or module repository, " +"add that repository as a submodule to the `documentation repository " +"`_ and configure other necessary settings." +" This will ensure that the entire body of Tarantool documentation, presented" +" on the `official website `_, is built " +"properly." msgstr "" -msgid "The steps to do that are the following:" +msgid "Here is how to do that:" msgstr "" msgid "1. Add a submodule" msgstr "" msgid "" -"First, we need to add a repository containing the content source files as a " +"First, we need to add the repository with content source files as a " "submodule." msgstr "" @@ -54,8 +54,7 @@ msgid "" msgstr "" msgid "" -"Check that the new submodule appears in the ``.gitmodules`` file, for " -"example:" +"Check that the new submodule is in the ``.gitmodules`` file, for example:" msgstr "" msgid "" @@ -68,42 +67,39 @@ msgid "2. Update build_submodules.sh" msgstr "" msgid "" -"Next, we should define what directories and files are to be copied from the " -"submodule repository into the documentation one before building " -"documentation. These settings are defined in the ``build_submodules.sh`` " -"file which is in the root directory of the documentation repository." +"Now define what directories and files are to be copied from the submodule " +"repository to the documentation repository before building documentation. " +"These settings are defined in the ``build_submodules.sh`` file in the root " +"directory of the documentation repository." msgstr "" msgid "" -"We can take examples of the already existing submodules to show the logic of" -" the settings." +"Here are some real submodule examples that show the logic of the settings." msgstr "" msgid "metrics" msgstr "" msgid "" -"In case of the ``metrics`` submodule, the content source files are in the " +"The content source files for the ``metrics`` submodule are in the " "``./doc/monitoring`` directory of the submodule repository. In the final " "documentation view, the content should appear in the `Monitoring " "`__ chapter " "(``https://www.tarantool.io/en/doc/latest/book/monitoring/``)." msgstr "" -msgid "So, we need to:" +msgid "To make this work:" msgstr "" -msgid "create a directory at ``./doc/book/monitoring/``." +msgid "Create a directory at ``./doc/book/monitoring/``." msgstr "" msgid "" -"copy the entire content of the ``./modules/metrics/doc/monitoring/`` " +"Copy the entire content of the ``./modules/metrics/doc/monitoring/`` " "directory to ``./doc/book/monitoring/``." msgstr "" -msgid "" -"The corresponding lines in the ``build_submodules.sh`` file are the " -"following:" +msgid "Here are the corresponding lines in ``build_submodules.sh``:" msgstr "" msgid "" @@ -115,33 +111,30 @@ msgid "" msgstr "" msgid "" -"The ``${project_root}`` variable is defined earlier as " -"``project_root=$(pwd)``. We should start the documentation build from the " -"documentation repository root directory so that will be the value of the " -"variable." +"The ``${project_root}`` variable is defined earlier in the file as " +"``project_root=$(pwd)``. This is because the documentation build has to " +"start from the documentation repository root directory." msgstr "" msgid "cartridge_cli" msgstr "" msgid "" -"In case of the ``cartridge_cli`` submodule, the content source is in the " -"``README.rst`` file located in the directory of the submodule repository. In" -" the final documentation view, the content should appear here: " +"The content source file for the ``cartridge_cli`` submodule is " +"``README.rst``, located in the directory of the submodule repository. In the" +" final documentation view, the content should appear here: " "``https://www.tarantool.io/en/doc/latest/book/cartridge/cartridge_cli/``." msgstr "" -msgid "create a directory at ``./doc/book/cartridge/cartridge_cli``" +msgid "Create a directory at ``./doc/book/cartridge/cartridge_cli``." msgstr "" msgid "" -"copy ``./modules/cartridge_cli/README.rst`` to " +"Copy ``./modules/cartridge_cli/README.rst`` to " "``./doc/book/cartridge/cartridge_cli/index.rst``." msgstr "" -msgid "" -"The corresponding settings in the ``build_submodules.st`` file are the " -"following:" +msgid "Here ar the corresponding settings in ``build_submodules.sh``:" msgstr "" msgid "" @@ -158,6 +151,5 @@ msgid "3. Update .gitignore" msgstr "" msgid "" -"Finaly, we should add paths to the copied directories and files to the " -"``.gitignore`` file." +"Finally, add paths to the copied directories and files to ``.gitignore``." msgstr "" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/markup.po b/locale/ru/LC_MESSAGES/contributing/docs/markup.po index 2eaecb7c2..ffd802fc9 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/markup.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/markup.po @@ -3,11 +3,10 @@ msgid "Markup reference" msgstr "" msgid "" -"Tarantool documentation is built via `Sphinx `_ engine and is written in `reStructuredText " -"`_ " -"markup. This section will guide you through our typical cases while writing " -"the docs." +"`_. This" +" section will guide you through our typical documentation formatting cases." msgstr "" msgid "Contents:" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/markup/admonitions.po b/locale/ru/LC_MESSAGES/contributing/docs/markup/admonitions.po index bea97522e..6133b9e78 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/markup/admonitions.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/markup/admonitions.po @@ -43,6 +43,23 @@ msgid "" "user about some consequences of his actions." msgstr "" +msgid "Important:" +msgstr "" + +msgid ".. important::" +msgstr "" + +msgid "" +"This block contains essential information that the user should know while " +"doing something." +msgstr "" + +msgid "" +"For example, the block :doc:`in Getting Started with Docker " +"` is used to warn the user against " +"closing the terminal window." +msgstr "" + msgid "Custom admonition:" msgstr "" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/markup/links.po b/locale/ru/LC_MESSAGES/contributing/docs/markup/links.po index 706a73876..58ca7876e 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/markup/links.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/markup/links.po @@ -43,11 +43,11 @@ msgstr "" msgid "Our naming convention is as follows:" msgstr "Соглашение об именовании заключается в следующем:" -msgid "Character set: a through z, 0 through 9, dash, underscore." -msgstr "Набор символов: от a до z, от 0 до 9, дефис, подчеркивание." +msgid "Character set: a through z, 0 through 9, hyphen, underscore." +msgstr "" -msgid "Format: ``path dash filename dash tag``" -msgstr "Формат: ``путь дефис имя файла дефис тег``" +msgid "Format: ``path hyphen filename hyphen tag``" +msgstr "" msgid "**Example:**" msgstr "**Пример:**" @@ -68,24 +68,17 @@ msgid "``iterator_type`` is the tag." msgstr "" msgid "" -"Use a dash \"-\" to delimit the path and the file name. In the documentation" -" source, we use only underscores \"_\" in paths and file names, reserving " -"dash \"-\" as the delimiter for local links." +"Use a hyphen \"-\" to delimit the path and the file name. In the " +"documentation source, we use only underscores \"_\" in paths and file names," +" reserving the hyphen \"-\" as the delimiter for local links." msgstr "" -"Используйте дефис \"-\", чтобы разграничить путь и имя файла. В исходном " -"коде документации мы пользуемся только символами подчеркивания \"_\" при " -"указании пути и имени файла, оставляя дефисы \"-\" для разграничения в " -"локальных ссылках." msgid "" "The tag can be anything meaningful. The only guideline is for Tarantool " "syntax items (such as members), where the preferred tag syntax is " -"``module_or_object_name dash member_name``. For example, ``box_space-drop``." +"``module_or_object_name hyphen member_name``. For example, ``box_space-" +"drop``." msgstr "" -"Тег может содержать любую значимую информацию. Единственная рекомендация " -"дается для элементов синтаксиса Tarantool'а, где предпочтительно " -"использовать следующий синтаксис в тегах: ``имя_объекта_или_модуля дефис " -"имя_элемента``. Например, ``box_space-drop``." msgid "To add a link to an anchor, use the following syntax:" msgstr "" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/sphinx-warnings.po b/locale/ru/LC_MESSAGES/contributing/docs/sphinx-warnings.po index 571a81b04..e4616dc99 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/sphinx-warnings.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/sphinx-warnings.po @@ -3,13 +3,11 @@ msgid "Sphinx-build warnings reference" msgstr "" msgid "" -"This document will guide you through the possible warnings raised by Sphinx " -"engine while building the docs." +"This document will guide you through the warnings that can be raised by " +"Sphinx while building the docs." msgstr "" -msgid "" -"Below we cite a list with the most frequent warnings and the ways of " -"solutions." +msgid "Below are the most frequent warnings and the ways to solve them." msgstr "" msgid "Bullet list ends without a blank line; unexpected unindent" @@ -59,8 +57,8 @@ msgid "" msgstr "" msgid "" -"Sometimes, however, there's no appropriate lexer, or the code snippet can't " -"be lexed properly. In such case, use ``code-block:: text``." +"However, sometimes there's no appropriate lexer or the code snippet can't be" +" lexed properly. In that case, use ``code-block:: text``." msgstr "" msgid "Duplicate explicit target name: \"...\"" @@ -68,22 +66,22 @@ msgstr "" msgid "" "* `Install `_\n" -" ``git``, a version control system.\n" +" ``git``, the version control system.\n" "\n" "* `Install `_\n" " the ``unzip`` utility." msgstr "" msgid "" -"Sphinx-builder raises warnings when we call different targets the same " -"names. Sphinx developers `recommend `_ using double underlines ``__`` in such cases to " "avoid this." msgstr "" msgid "" "* `Install `__\n" -" ``git``, a version control system.\n" +" ``git``, the version control system.\n" "\n" "* `Install `__\n" " the ``unzip`` utility." @@ -97,23 +95,25 @@ msgid "" msgstr "" msgid "" -"If you don't need it there, place ``:orphan:`` directive at the top of the " -"file. Or, if this file is included somewhere or reused, add it to the " -"_includes directory. These directories are ignored by Sphinx because we put " -"them in ``exclude_patterns`` in ``conf.py`` file." +"If you don't want to include the document in a toctree, place the " +"``:orphan:`` directive at the top of the file. If this file is already " +"included somewhere or reused, add it to the _includes directory. Sphinx " +"ignores everything in this directory because we list it among " +"``exclude_patterns`` in ``conf.py``." msgstr "" msgid "Duplicate label \"...\", other instance in \".../.../...\"" msgstr "" msgid "" -"This happens if you include the contents of one file with tags in another. " -"Then Sphinx thinks the tags are repeated." +"This happens if you include the contents of a file into another file, when " +"the included file has tags in it. In this, Sphinx thinks the tags are " +"repeated." msgstr "" msgid "" -"As in previous case, don't forget to add such file in _includes or avoid " -"using tags within it." +"As in the previous case, add the file to _includes or avoid using tags in " +"it." msgstr "" msgid "Malformed hyperlink target" @@ -122,7 +122,7 @@ msgstr "" msgid "**Similar warning:** Unknown target name: \"...\"" msgstr "" -msgid "Check the spelling of the target or the accuracy of the tag." +msgid "Check the target spelling and the tag syntax." msgstr "" msgid ".. _box_space-index_func" @@ -132,7 +132,7 @@ msgid "" "See the :ref:`Creating a functional index ` section." msgstr "" -msgid "Semicolon is missing in tag definition:" +msgid "A semicolon is missing in the tag definition:" msgstr "" msgid ".. _box_space-index_func:" @@ -141,16 +141,14 @@ msgstr "" msgid "Toctree contains reference to nonexisting document '...'" msgstr "" -msgid "" -"This may happen when you, for example, refer to the wrong path to a " -"document." +msgid "This may happen when you refer to a wrong path to a document." msgstr "" msgid "Check the path." msgstr "" msgid "" -"If the path is in ``cartridge`` or another submodule, check that you've " +"If the path points to ``cartridge`` or another submodule, check that you've " ":doc:`built the submodules content ` before " "building docs." msgstr "" @@ -172,37 +170,37 @@ msgstr "" msgid "**See also:**" msgstr "**См. также:**" -msgid ":doc:`/contributing/docs/markup/links`" +msgid ":doc:`Links and references `" msgstr "" msgid "Unexpected indentation" msgstr "" msgid "" -"The reStructuredText syntax is based on indentation, much like in Python. In" -" a block of content, all lines should be equally indented. An increase or " -"decrease in indentation means the end of the current block and the beginning" -" of a new one." +"The reStructuredText syntax is based on indentation, much like in Python. " +"All lines in a block of content must be equally indented. An increase or " +"decrease in indentation denotes the end of the current block and the " +"beginning of a new one." msgstr "" msgid "" -"Note: dots show indentation spaces in these examples. For example, ``|..|`` " -"means a two-space indentation." +"Note: In the following examples, dots stand for indentation spaces. For " +"example, ``|..|`` denotes a two-space indentation." msgstr "" msgid "" "|..|* (Engines) Improve dump start/stop logging. When initiating memory dump, print\n" -"how much memory is going to be dumped, expected dump rate, ETA, and the recent\n" +"how much memory is going to be dumped, the expected dump rate, ETA, and the recent\n" "write rate." msgstr "" msgid "" "*|...|(Engines) Improve dump start/stop logging. When initiating memory dump, print\n" -"|....|how much memory is going to be dumped, expected dump rate, ETA, and the recent\n" +"|....|how much memory is going to be dumped, the expected dump rate, ETA, and the recent\n" "|....|write rate." msgstr "" -msgid ":doc:`/contributing/docs/markup/intro`" +msgid ":doc:`General syntax guidelines `" msgstr "" msgid "Unknown document" @@ -212,7 +210,7 @@ msgid ":doc:`reference/reference_lua/box_space/update`" msgstr "" msgid "" -"Sphinx did not recognise the file path correctly due to a missing slash at " +"Sphinx did not recognize the file path correctly due to a missing slash at " "the beginning, so let's just put it there:" msgstr "" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/style.po b/locale/ru/LC_MESSAGES/contributing/docs/style.po index 4c560dac5..9e9466694 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/style.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/style.po @@ -5,37 +5,27 @@ msgstr "" msgid "US vs British spelling" msgstr "Британский или американский вариант английского" -msgid "We use English US spelling." +msgid "We use the US English spelling." msgstr "" -"В английской версии документации мы придерживаемся американского варианта " -"английского языка." msgid "Instance vs server" msgstr "Экземпляр или сервер" msgid "" -"We say \"instance\" rather than \"server\" to refer to an instance of " -"Tarantool server. This keeps the manual terminology consistent with names " -"like ``/etc/tarantool/instances.enabled`` in the Tarantool environment." +"We say \"instance\" rather than \"server\" to refer to a Tarantool server " +"instance. This keeps the manual terminology consistent with names like " +"``/etc/tarantool/instances.enabled`` in the Tarantool environment." msgstr "" -"Ссылаясь на экземпляр Tarantool-сервера, мы говорим \"экземпляр\", а не " -"\"сервер\". Это обеспечивает однородность терминологии в руководстве и " -"именами в окружении Tarantool'а (например, " -"``/etc/tarantool/instances.enabled`` -- активные экземпляры)." msgid "" -"Wrong usage: \"Replication allows multiple Tarantool *servers* to work on " -"copies of the same databases.\"" +"Wrong usage: \"Replication allows multiple Tarantool *servers* to work with " +"copies of the same database.\"" msgstr "" -"Неправильно: \"С помощью репликации несколько *серверов* Tarantool’а могут " -"работать на копиях одинаковых баз данных.\"" msgid "" "Correct usage: \"Replication allows multiple Tarantool *instances* to work " -"on copies of the same databases.\"" +"with copies of the same database.\"" msgstr "" -"Правильно: \"С помощью репликации несколько *экземпляров* Tarantool’а могут " -"работать на копиях одинаковых баз данных.\"" msgid "Express one idea in a sentence" msgstr "" @@ -75,15 +65,15 @@ msgid "" msgstr "" msgid "" -"A replica set from which the bucket is being migrated is called a source; a " -"target replica set to which the bucket is being migrated is called a " -"destination." +"The replica set from where the bucket is being migrated is called the " +"source; the target replica set where the bucket is being migrated to is " +"called the destination." msgstr "" msgid "" -"A replica set from which the bucket is being migrated is called a source. A " -"target replica set to which the bucket is being migrated is called a " -"destination." +"The replica set from where the bucket is being migrated is called the " +"source. The target replica set where the bucket is being migrated to is " +"called the destination." msgstr "" msgid "Don't use i.e. and e.g." @@ -93,28 +83,29 @@ msgid "Don't use the following contractions:" msgstr "" msgid "" -"`\"i.e.\" `_ —from Latin " -"\"id est\". Use \"that is\" or \"which means\" instead." +"`\"i.e.\" `_---from the " +"Latin \"id est\". Use \"that is\" or \"which means\" instead." msgstr "" msgid "" -"`\"e.g.\" `_ —from Latin " -"\"exempli gratia\". Use \"for example\" or \"such as\" instead." +"`\"e.g.\" `_---from the " +"Latin \"exempli gratia\". Use \"for example\" or \"such as\" instead." msgstr "" msgid "" -"Many people, especially non-native English speakers, aren't familiar or " -"don't know the difference between `\"i.e.\" and \"e.g.\" contractions " -"`_. So it's best to avoid using them." +"Many people, especially non-native English speakers, aren't familiar with " +"the `\"i.e.\" and \"e.g.\" contractions `_ " +"or don't know the difference between them. For this reason, it's best to " +"avoid using them." msgstr "" -msgid "Specify a link text" +msgid "Specify link text" msgstr "" msgid "" -"While giving a :doc:`link `, specify " -"clearly where this link leads. Thus, you will not mislead a reader." +"When you provide a :doc:`link `, clearly " +"specify where it leads. In this way, you will not mislead the reader." msgstr "" msgid "Bad example:" diff --git a/locale/ru/LC_MESSAGES/contributing/docs/terms.po b/locale/ru/LC_MESSAGES/contributing/docs/terms.po index 484d0753c..1b1b99db2 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/terms.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/terms.po @@ -6,83 +6,82 @@ msgid "What are concepts and terms" msgstr "" msgid "" -"To write well about some subject matter, one needs to know the objects of " -"this subject matter and use the right, carefully selected words for them. " -"Such objects are called concepts, and the words for them are called terms." +"To write well about a certain subject matter, one needs to know its details " +"and use the right, carefully selected words for them. These details are " +"called concepts, and the words for them are called terms." msgstr "" msgid "concept" msgstr "" msgid "" -"The concept is the idea of some object, attribute, or action. It is " -"independent of languages, audience, and products. It just exists." +"A concept is the idea of an object, attribute, or action. It is independent " +"of languages, audience, and products. It just exists." msgstr "" msgid "" -"For example, a large database can be partitioned into smaller instances, " -"which are easier to operate and can exceed the throughput of a single large " -"database instance. Such instances can exchange data for keeping it " -"consistent between them." +"For example, a large database can be partitioned into smaller instances. " +"Those instances are easier to operate, and their throughput often exceeds " +"the throughput of a single large database instance. The instances can " +"exchange data to keep it consistent between them." msgstr "" msgid "term" msgstr "" msgid "" -"The term is a word, which authors or a particular book, article, or " -"documentation set have explicitly selected to denote a :term:`concept` in a " -"particular language and for a particular audience." +"A term is a word explicitly selected by the authors of a particular text to " +"denote a :term:`concept` in a particular language for a particular audience." msgstr "" msgid "" "For example, in Tarantool, we use the term \"[database] sharding\" to denote" -" the concept mentioned in the previous example." +" the concept described in the previous example." msgstr "" msgid "Use preferred terms" msgstr "" msgid "" -"The purpose of using terms is to write concisely and unambiguously, which is" -" good for readers. But selecting terms is hard. Often there are two or more " -"terms for one concept popular with the community, so there's no obvious " -"choice. Indeed, selecting and consistently using any of them is much better " -"than not selecting and just using random terms each time. This is why it's " -"also helpful to restrict the usage of some terms explicitly." +"The purpose of using terms is writing concisely and unambiguously, which is " +"good for the readers. But selecting terms is hard. Often, the community " +"favors two or more terms for one concept, so there's no obvious choice. " +"Selecting and consistently using any of them is much better than not making " +"a choice and using a random term every time. This is why it's also helpful " +"to restrict the usage of some terms explicitly." msgstr "" msgid "restricted term" msgstr "" msgid "" -"A restricted term is a word that authors have explicitly forbidden to use " +"A restricted term is a word that the authors explicitly prohibited to use " "for denoting a :term:`concept`. Such a word is sometimes used as a " -":term:`term` for the same :term:`concept` elsewhere: in the community, in " -"other books, or other products' documentation. Sometimes, this word is used " -"to denote a similar but different concept. In this case, the right choice of" -" terms helps us differentiate between concepts." +":term:`term` for the same :term:`concept` elsewhere---in the community, in " +"books, or in other product documentation. Sometimes this word is used to " +"denote a similar but different concept. In this case, the right choice of " +"terms helps us differentiate between concepts." msgstr "" msgid "" "For example, in Tarantool, we don't use the term \"[database] segmentation\"" -" to denote what we call \"database sharding.\" Although, other authors could" -" do so. Also, there is the term \"[database] partitioning\" that we use to " -"denote a wider concept, which includes sharding and other things." +" to denote what we call \"database sharding.\" Nevertheless, other authors " +"might do so. We also use the term \"[database] partitioning\" to denote a " +"wider concept, which includes sharding among other things." msgstr "" msgid "Define terms by explaining concepts" msgstr "" msgid "" -"Define the term by explaining the concept. For the most important concepts " -"and the ones unique to Tarantool, the definition should always be in our " -"documentation." +"We always want to document definitions for the most important concepts, as " +"well as for concepts unique to Tarantool." msgstr "" msgid "" -"Define each term in the document which is most relevant to it. There's no " -"need to gather all definitions on a particular \"Glossary\" page." +"Define every term in the document that you find most appropriate for it. You" +" don't have to create a dedicated glossary page containing all the " +"definitions." msgstr "" msgid "To define a term, use the ``glossary`` directive in the following way:" @@ -106,17 +105,17 @@ msgstr "" msgid "" "The `Sphinx documentation `_ has an extensive glossary, which " -"we can use as a reference." +"doc/sphinx/blob/master/doc/glossary.rst>`_ has an extensive glossary that " +"can be used as a reference." msgstr "" msgid "Introduce terms on first entry" msgstr "" msgid "" -"When you use a term for the first time in a document, introduce it by giving" -" a definition, synonyms, translation, examples, and links. It will help " -"readers learn the term and understand the concept behind it." +"When you use a term in a document for the first time, define it and provide " +"synonyms, a translation, examples, and/or links. It will help readers learn " +"the term and understand the concept behind it." msgstr "" msgid "Define the term or give a link to the definition." @@ -130,15 +129,15 @@ msgstr "" msgid "" "For example, this is a link to the definition of :term:`concept`.\n" -"As with any rST role, it can have :term:`custom text `." +"Like any rST role, it can have :term:`custom text `." msgstr "" msgid "The resulting output will look like this:" msgstr "" msgid "" -"For example, this is a link to the definition of :term:`concept`. As with " -"any rST role, it can have :term:`custom text `." +"For example, this is a link to the definition of :term:`concept`. Like any " +"rST role, it can have :term:`custom text `." msgstr "" msgid "With acronyms, you can also use the `abbr` role:" @@ -160,10 +159,10 @@ msgstr "" msgid "" "When writing in Russian, it's good to add the corresponding English term. " -"Readers may be more familiar with it or can use it in search." +"Readers may be more familiar with it or can search it online." msgstr "" -msgid "Шардирование (сегментирование, sharding) — это..." +msgid "Шардирование (сегментирование, sharding) --- это..." msgstr "" msgid "Give examples or links to extra reading where you can." diff --git a/locale/ru/LC_MESSAGES/reference/reference_lua/key_def.po b/locale/ru/LC_MESSAGES/reference/reference_lua/key_def.po index c3e6e8131..e6829186c 100644 --- a/locale/ru/LC_MESSAGES/reference/reference_lua/key_def.po +++ b/locale/ru/LC_MESSAGES/reference/reference_lua/key_def.po @@ -1,54 +1,69 @@ msgid "Module `key_def`" -msgstr "" +msgstr "Модуль `key_def`" msgid "" "The `key_def` module has a function for making a definition of the field " "numbers and types of a tuple. The definition is usually used in conjunction " "with an index definition to extract or compare the index key values." msgstr "" +"В модуле `key_def` есть функция, позволяющая создавать определение номеров и" +" типов полей кортежа. Это определение обычно используется вместе с " +"определением индекса, чтобы извлекать или сравнивать значения ключей " +"индекса." msgid "Create a new key_def instance." -msgstr "" +msgstr "Создание нового экземпляра key_def." msgid "Parameters" msgstr "Параметры" msgid "" -"field numbers and types. There must be at least one part and it must have at" -" least fieldno and type." +"field numbers and types. There must be at least one part. Every part must " +"have the attributes ``type`` and ``fieldno``/``field``. Other attributes are" +" optional." msgstr "" +"типы и номера полей. В таблице ``parts`` должен быть хотя бы один элемент. " +"Для каждого элемента обязательны только атрибуты ``type`` и " +"``fieldno``/``field``." msgid "returns" msgstr "возвращает" msgid "key_def-object :ref:`a key_def object `" -msgstr "" +msgstr ":ref:`объект key_def `" msgid "" "The parts table has components which are the same as the ``parts`` option in" " :ref:`Options for space_object:create_index() `." msgstr "" +"Таблица parts содержит компоненты, аналогичные тем, что указываются в " +"параметре ``parts`` :ref:`при создании объекта space_object:create_index() " +"`:" msgid "" -"fieldno (integer) for example fieldno = 1. It is legal to say field instead " -"of fieldno." +"``fieldno`` (integer) for example ``fieldno = 1``. It is legal to use " +"``field`` instead of ``fieldno``." msgstr "" +"``fieldno`` (целое число), например ``fieldno = 1``. Вместо ``fieldno`` " +"можно использовать ``field``." -msgid "type (string) for example type = 'string'." -msgstr "" +msgid "``type`` (string) for example ``type = 'string'``." +msgstr "``type`` (строка), например ``type = 'string'``." msgid "Other components are optional." -msgstr "" +msgstr "Остальные компоненты необязательны." msgid "Example: ``key_def.new({{type = 'unsigned', fieldno = 1}})``" -msgstr "" +msgstr "Пример №1: ``key_def.new({{type = 'unsigned', fieldno = 1}})``" msgid "" "Example: ``key_def.new({{type = 'string', collation = 'unicode', field = " "2}})``" msgstr "" +"Пример №2: ``key_def.new({{type = 'string', collation = 'unicode', field = " +"2}})``" msgid "" "A key_def object is an object returned by :ref:`key_def.new() `, :ref:`merge() `, :ref:`totable() " "`." msgstr "" +"Объект key_def возвращается функцией :ref:`key_def.new() `. У " +"него есть следующие методы: :ref:`extract_key() `, " +":ref:`compare() `, :ref:`compare_with_key() `, :ref:`merge() `, :ref:`totable() " +"`." -msgid "Return a tuple containing only the fields of the key_def object." -msgstr "" +msgid "Return a tuple containing only the fields of the ``key_def`` object." +msgstr "Получение кортежа, содержащего только поля объекта ``key_def``." msgid "tuple or Lua table with field contents" -msgstr "" +msgstr "кортеж или Lua-таблица с содержимым поля" msgid "return" msgstr "возвращает" -msgid "the fields that were defined for the key_def object" -msgstr "" +msgid "the fields that were defined for the ``key_def`` object" +msgstr "поля, определенные для объекта ``key_def``," msgid "**Example #1:**" msgstr "**Пример №1:**" @@ -86,7 +106,7 @@ msgid "" "...\n" "\n" "tarantool> k = key_def.new({{type = 'string', fieldno = 3},\n" -"> {type = 'unsigned', fieldno =1 }})\n" +"> {type = 'unsigned', fieldno = 1}})\n" "---\n" "...\n" "\n" @@ -95,6 +115,26 @@ msgid "" "- ['X', 1]\n" "..." msgstr "" +"-- Предположим, что у некоторого элемента пять полей:\n" +"-- 1, 99.5, 'X', nil, 99.5\n" +"-- и нас интересуют только два из них:\n" +"-- третье (строка) и первое (целое число).\n" +"-- Мы можем определить эти поля инструкцией k = key_def.new\n" +"-- и извлечь значения командой k:extract_key.\n" +"\n" +"tarantool> key_def = require('key_def')\n" +"---\n" +"...\n" +"\n" +"tarantool> k = key_def.new({{type = 'string', fieldno = 3},\n" +"> {type = 'unsigned', fieldno = 1}})\n" +"---\n" +"...\n" +"\n" +"tarantool> k:extract_key({1, 99.5, 'X', nil, 99.5})\n" +"---\n" +"- ['X', 1]\n" +"..." msgid "**Example #2**" msgstr "**Пример №2**" @@ -107,11 +147,22 @@ msgid "" "-- The result will be the same.\n" "key_def = require('key_def')\n" "box.schema.space.create('T')\n" -"i = box.space.T:create_index('I',{parts={3,'string',1,'unsigned'}})\n" +"i = box.space.T:create_index('I', {parts={3, 'string', 1, 'unsigned'}})\n" "box.space.T:insert{1, 99.5, 'X', nil, 99.5}\n" "k = key_def.new(i.parts)\n" "k:extract_key(box.space.T:get({'X', 1}))" msgstr "" +"-- Теперь предположим, что элемент является кортежем в спейсе.\n" +"-- У спейса есть составной индекс, построенный по полям 3 и 1.\n" +"-- Мы можем передать определение индекса в качестве аргумента функции key_def.new,\n" +"-- а не заполнять определение, как в примере №1.\n" +"-- Результат будет тот же.\n" +"key_def = require('key_def')\n" +"box.schema.space.create('T')\n" +"i = box.space.T:create_index('I', {parts={3, 'string', 1, 'unsigned'}})\n" +"box.space.T:insert{1, 99.5, 'X', nil, 99.5}\n" +"k = key_def.new(i.parts)\n" +"k:extract_key(box.space.T:get({'X', 1}))" msgid "**Example #3**" msgstr "**Пример №3**" @@ -133,19 +184,42 @@ msgid "" " pk:delete(key)\n" "end" msgstr "" +"-- Проходим по всем кортежам во вторичном неуникальном индексе\n" +"-- и извлекаем из них значения по первичному ключу.\n" +"-- Затем удаляем значения, используя уникальный индекс.\n" +"-- Этот код должен входить в Lua-функцию.\n" +"local key_def_lib = require('key_def')\n" +"local s = box.schema.space.create('test')\n" +"local pk = s:create_index('pk')\n" +"local sk = s:create_index('test', {unique = false, parts = {\n" +" {2, 'number', path = 'a'}, {2, 'number', path = 'b'}}})\n" +"s:insert{1, {a = 1, b = 1}}\n" +"s:insert{2, {a = 1, b = 2}}\n" +"local key_def = key_def_lib.new(pk.parts)\n" +"for _, tuple in sk:pairs({1})) do\n" +" local key = key_def:extract_key(tuple)\n" +" pk:delete(key)\n" +"end" msgid "" -"Compare the key fields of tuple_1 to the key fields of tuple_2. This is a " -"tuple-by-tuple comparison so users do not have to write code which compares " -"a field at a time. Each field's type and collation will be taken into " -"account. In effect it is a comparison of extract_key(tuple_1) with " -"extract_key(tuple_2)." +"Compare the key fields of ``tuple_1`` to the key fields of ``tuple_2``. This" +" is a tuple-by-tuple comparison so users do not have to write code which " +"compares a field at a time. Each field's type and collation will be taken " +"into account. In effect it is a comparison of ``extract_key(tuple_1)`` with " +"``extract_key(tuple_2)``." msgstr "" +"Сравнение полей кортежей ``tuple_1`` и ``tuple_2`` по определённому ключу. " +"Пользователю не нужно писать код для сравнения отдельных полей. Учитываются " +"типы полей и параметры сортировки. Фактически сравниваются значения " +"``extract_key(tuple_1)`` и ``extract_key(tuple_2)``." msgid "" "> 0 if tuple_1 key fields > tuple_2 key fields, = 0 if tuple_1 key fields = " "tuple_2 key fields, < 0 if tuple_1 key fields < tuple_2 key fields" msgstr "" +"положительное число, если значения полей tuple_1 больше значений полей " +"tuple_2 по ключу; 0, если они равны; отрицательное число, если значения " +"полей tuple_1 меньше значений полей tuple_2 по ключу" msgid "**Example:**" msgstr "**Пример:**" @@ -153,74 +227,113 @@ msgstr "**Пример:**" msgid "" "-- This will return 0\n" "key_def = require('key_def')\n" -"k = key_def.new({{type='string',fieldno=3,collation='unicode_ci'},\n" -" {type='unsigned',fieldno=1}})\n" +"k = key_def.new({{type = 'string', fieldno = 3, collation = 'unicode_ci'},\n" +" {type = 'unsigned', fieldno = 1}})\n" "k:compare({1, 99.5, 'X', nil, 99.5}, {1, 99.5, 'x', nil, 99.5})" msgstr "" +"-- Результат этого кода будет 0\n" +"key_def = require('key_def')\n" +"k = key_def.new({{type = 'string', fieldno = 3, collation = 'unicode_ci'},\n" +" {type = 'unsigned', fieldno = 1}})\n" +"k:compare({1, 99.5, 'X', nil, 99.5}, {1, 99.5, 'x', nil, 99.5})" msgid "" -"Compare the key fields of tuple_1 to all the fields of tuple_2. This is the " -"same as :ref:`key_def_object:compare() ` except that " -"tuple_2 contains only the key fields. In effect it is a comparison of " -"extract_key(tuple_1) with tuple_2." +"Compare the key fields of ``tuple_1`` to all the fields of ``tuple_2``. This" +" is the same as :ref:`key_def_object:compare() ` except " +"that ``tuple_2`` contains only the key fields. In effect it is a comparison " +"of ``extract_key(tuple_1)`` with ``tuple_2``." msgstr "" +"Сравнение полей кортежей ``tuple_1`` с полями кортежа ``tuple_2`` по " +"заданному ключу. Аналогично :ref:`key_def_object:compare() `, за исключением того, что ``tuple_2`` содержит только поля ключа. " +"Фактически это сравнение ``extract_key(tuple_1)`` с ``tuple_2``." msgid "" "> 0 if tuple_1 key fields > tuple_2 fields, = 0 if tuple_1 key fields = " "tuple_2 fields, < 0 if tuple_1 key fields < tuple_2 fields" msgstr "" +"положительное число, если значения полей tuple_1 больше значений полей " +"tuple_2 по ключу; 0, если они равны; отрицательное число, если значения " +"полей tuple_1 меньше значений полей tuple_2 по ключу" msgid "" "-- This will return 0\n" "key_def = require('key_def')\n" -"k = key_def.new({{type='string',fieldno=3,collation='unicode_ci'},\n" -" {type='unsigned',fieldno=1}})\n" +"k = key_def.new({{type = 'string', fieldno = 3, collation = 'unicode_ci'},\n" +" {type = 'unsigned', fieldno = 1}})\n" "k:compare_with_key({1, 99.5, 'X', nil, 99.5}, {'x', 1})" msgstr "" +"-- Результат этого кода будет 0\n" +"key_def = require('key_def')\n" +"k = key_def.new({{type = 'string', fieldno = 3, collation = 'unicode_ci'},\n" +" {type = 'unsigned', fieldno = 1}})\n" +"k:compare_with_key({1, 99.5, 'X', nil, 99.5}, {'x', 1})" msgid "" -"Combine the main key_def_object with other_key_def_object. The return value " -"is a new key_def_object containing all the fields of the main " -"key_def_object, then all the fields of other_key_def_object which are not in" -" the main key_def_object." +"Combine the main ``key_def_object`` with ``other_key_def_object``. The " +"return value is a new ``key_def_object`` containing all the fields of the " +"main ``key_def_object``, then all the fields of ``other_key_def_object`` " +"which are not in the main ``key_def_object``." msgstr "" +"Объединение основного объекта ``key_def_object`` с другим объектом " +"``other_key_def_object``. Возвращает новый объект ``key_def_object``, " +"содержащий сначала все поля основного объекта ``key_def_object``, а потом те" +" поля объекта ``other_key_def_object``, которых не было в основном объекте " +"``key_def_object``." msgid "definition of fields to add" -msgstr "" +msgstr "определение полей, которые нужно добавить" msgid "key_def_object" -msgstr "" +msgstr "key_def_object" msgid "" -"-- This will return a key definition with fieldno=3 and fieldno=1.\n" +"-- This will return a key definition with fieldno = 3 and fieldno = 1.\n" "key_def = require('key_def')\n" "k = key_def.new({{type = 'string', fieldno = 3}})\n" "k2= key_def.new({{type = 'unsigned', fieldno = 1},\n" " {type = 'string', fieldno = 3}})\n" "k:merge(k2)" msgstr "" +"-- Результатом этого кода будет определение ключа\n" +"-- по полям с fieldno = 3 и fieldno = 1\n" +"key_def = require('key_def')\n" +"k = key_def.new({{type = 'string', fieldno = 3}})\n" +"k2= key_def.new({{type = 'unsigned', fieldno = 1},\n" +" {type = 'string', fieldno = 3}})\n" +"k:merge(k2)" msgid "" -"Return a table containing what is in the key_def_object. This is the reverse" -" of ``key_def.new()``:" +"Return a table containing what is in the ``key_def_object``. This is the " +"reverse of ``key_def.new()``:" msgstr "" +"Возвращает таблицу с содержимым ``key_def_object``. Функция противоположна " +"функции ``key_def.new()``:" -msgid "``key_def.new()`` takes a table and returns a key_def object," -msgstr "" +msgid "``key_def.new()`` takes a table and returns a ``key_def`` object," +msgstr "``key_def.new()`` принимает таблицу, а возвращает объект ``key_def``." msgid "" -"``key_def_object:totable()`` takes a key_def object and returns a table." +"``key_def_object:totable()`` takes a ``key_def`` object and returns a table." msgstr "" +"``key_def_object:totable()`` принимает объект ``key_def``, а возвращает " +"таблицу." msgid "This is useful for input to ``_serialize`` methods." msgstr "" +"Это удобно при подготовке входных данных для методов сериализации " +"(``_serialize``)." msgid "table" -msgstr "таблица" +msgstr "таблицу" msgid "" -"-- This will return a table with type='string', fieldno=3\n" +"-- This will return a table with type = 'string', fieldno = 3\n" "key_def = require('key_def')\n" "k = key_def.new({{type = 'string', fieldno = 3}})\n" "k:totable()" msgstr "" +"-- Результатом этого кода будет таблица с type = 'string', fieldno = 3\n" +"key_def = require('key_def')\n" +"k = key_def.new({{type = 'string', fieldno = 3}})\n" +"k:totable()" diff --git a/locale/ru/LC_MESSAGES/release/major-features.po b/locale/ru/LC_MESSAGES/release/major-features.po index 179a1d927..29acb75ee 100644 --- a/locale/ru/LC_MESSAGES/release/major-features.po +++ b/locale/ru/LC_MESSAGES/release/major-features.po @@ -153,11 +153,9 @@ msgid "2.4.1" msgstr "2.4.1" msgid "" -":ref:`UUID type for field and index <_index-box_uuid>` (:tarantool-" +":ref:`UUID type for field and index ` (:tarantool-" "issue:`4268`, :tarantool-issue:`2916`)" msgstr "" -":ref:`Поддержка UUID для полей и индексов<_index-box_uuid>` (:tarantool-" -"issue:`4268`, :tarantool-issue:`2916`)" msgid "" ":doc:`popen ` built-in module (:tarantool-"