From 0b4980c0df0859b3072ca3c7381fa303cd40767e Mon Sep 17 00:00:00 2001 From: TarantoolBot Date: Mon, 23 Oct 2023 13:21:39 +0000 Subject: [PATCH 1/3] updated pot --- locale/en/book/connectors/community.pot | 6 +- locale/en/contributing/docs/build.pot | 238 +----- locale/en/index.pot | 6 +- locale/en/reference/reference_rock/index.pot | 6 +- .../luatest/luatest_overview.pot | 785 +----------------- locale/en/singlehtml.pot | 6 +- locale/en/toctree.pot | 6 +- 7 files changed, 7 insertions(+), 1046 deletions(-) diff --git a/locale/en/book/connectors/community.pot b/locale/en/book/connectors/community.pot index 229f995f81..2bbf780d03 100644 --- a/locale/en/book/connectors/community.pot +++ b/locale/en/book/connectors/community.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Tarantool 2.11\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-12 15:09+0000\n" +"POT-Creation-Date: 2023-10-23 13:20+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,10 +16,6 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../doc/book/connectors/community.rst:9 -msgid "C++" -msgstr "" - #: ../../doc/book/connectors/community.rst:4 msgid "Community-supported connectors" msgstr "" diff --git a/locale/en/contributing/docs/build.pot b/locale/en/contributing/docs/build.pot index 4bf01d8684..40eebad7d6 100644 --- a/locale/en/contributing/docs/build.pot +++ b/locale/en/contributing/docs/build.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Tarantool 2.11\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-12 15:09+0000\n" +"POT-Creation-Date: 2023-10-23 13:20+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -19,239 +19,3 @@ msgstr "" #: ../../doc/contributing/docs/build.rst:2 msgid "Building Tarantool Docs" msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:2 -msgid "How to build Tarantool documentation using Docker" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:4 -msgid "See `Docker `_" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:7 -msgid "Prepare for work" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:9 -msgid "First of all, pull the image for building the docs." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:11 -msgid "docker pull tarantool/doc-builder:fat-4.1" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:15 -msgid "Next, initialize a Makefile for your OS:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:17 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"cmake .\"" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:22 -msgid "Update submodules and generate documentation sources from code" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:24 -msgid "A big part of documentation sources comes from several other projects, connected as Git submodules. To include their latest contents in the docs, run these two steps." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:28 -msgid "Update the submodules:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:30 -msgid "git submodule update --init\n" -"git fetch --recurse-submodules\n" -"git submodule update --remote --checkout" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:36 -msgid "This will initialize Git submodules and update them to the top of the stable branch in each repository." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:39 -msgid "``git submodule update`` can sometimes fail, for example, when you have changes in submodules' files. You can reinitialize submodules to fix the problem." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:43 -msgid "**Caution:** all untracked changes in submodules will be lost!" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:45 -msgid "git submodule deinit -f .\n" -"git submodule update --init" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:51 -msgid "Note that there's an option to update submodule repositories with a ``make`` command. However, it's intended for use in a CI environment and not on a local machine." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:54 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make pull-modules\"" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:58 -msgid "Build the submodules content:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:60 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make build-modules\"" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:64 -msgid "This command will do two things:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:66 -msgid "Generate documentation source files from the source code" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:67 -msgid "Copy these files to the right places under the ``./doc/`` directory." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:69 -msgid "If you're editing submodules locally, repeat this step to view the updated results." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:72 -msgid "Now you're ready to build and preview the documentation locally." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:75 -msgid "Build and run the documentation on your machine" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:77 -msgid "When editing the documentation, you can set up a live-reload server. It will build your documentation and serve it on `127.0.0.1:8000 `_. Every time you make changes in the source files, it will rebuild the docs and refresh the browser page." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:82 -msgid "docker run --rm -it -p 8000:8000 -v $(pwd):/doc tarantool/doc-builder:fat-4.3 sh -c \"make autobuild\"" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:86 -msgid "First build will take some time. When it's done, open `127.0.0.1:8000 `_ in the browser. Now when you make changes, they will be rebuilt in a few seconds, and the browser tab with preview will reload automatically." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:91 -msgid "You can also build the docs manually with ``make html``, and then serve them using python3 built-in server:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:94 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make html\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make html-ru\"\n" -"python3 -m http.server --directory output/html" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:100 -msgid "or python2 built-in server:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:102 -msgid "cd output/html\n" -"python -m SimpleHTTPServer" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:107 -msgid "then go to `localhost:8000 `_ in your browser." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:109 -msgid "There are other commands which can run in the ``tarantool/doc-builder`` container:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:112 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make html\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make html-ru\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make singlehtml\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make singlehtml-ru\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make pdf\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make pdf-ru\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make json\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make json-ru\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make epub\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make epub-ru\"\n" -"docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make update-po\"" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:127 -msgid "Linkcheck" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:129 -msgid "There's a specific build mode which checks internal and external links instead of producing a document." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:131 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make linkcheck\"" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:135 -msgid "If you need to save the linkcheck's report in a file, you can use the following trick:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:137 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make linkcheck\" 2>&1 | tee linkcheck.log" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:141 -msgid "Here ``2>&1`` redirects the ``stderr`` output to ``stdout``, and then ``tee`` both shows in on screen and writes to a file." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:145 -msgid "Localization" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:147 -msgid "Terms:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:149 -msgid "**translation unit** (TU) is an atomic piece of text which can be translated. A paragraph, a list item, a heading, image's alt-text and so on." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:152 -msgid "**translation source files** are the files with translation units in English only. They're located in ``locale/en``." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:155 -msgid "**translation files** are the files which match original text to translated text. They're located in ``locale/ru``." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:158 -msgid "To update the translation files, run the `make update-po` task:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:160 -msgid "docker run --rm -it -v $(pwd):/doc tarantool/doc-builder:fat-4.1 sh -c \"make update-po\"" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:164 -msgid "Translate the strings in the updated files and then commit the changes." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:167 -msgid "How to contribute" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:169 -msgid "To contribute to documentation, use the `REST `_ format for drafting and submit your updates as a `pull request `_ via GitHub." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:175 -msgid "To comply with the writing and formatting style, use the `guidelines `_ provided in the documentation, common sense and existing documents." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:179 -msgid "Notes:" -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:181 -msgid "If you suggest creating a new documentation section (a whole new page), it has to be saved to the relevant section at GitHub." -msgstr "" - -#: ../../doc/contributing/docs/_includes/README.rst:184 -msgid "If you want to contribute to localizing this documentation (for example, into Russian), add your translation strings to ``.po`` files stored in the corresponding locale directory (for example, ``/locale/ru/LC_MESSAGES/`` for Russian). See more about localizing with Sphinx at http://www.sphinx-doc.org/en/stable/intl.html." -msgstr "" diff --git a/locale/en/index.pot b/locale/en/index.pot index 62b8d7c1b5..6864bb16f9 100644 --- a/locale/en/index.pot +++ b/locale/en/index.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Tarantool 2.11\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-12 15:09+0000\n" +"POT-Creation-Date: 2023-10-23 13:20+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -20,10 +20,6 @@ msgstr "" msgid "CRUD operations" msgstr "" -#: ../../doc/index.rst:50 -msgid "Cluster on Cartridge" -msgstr "" - #: ../../doc/index.rst:10 msgid "Tarantool -- Documentation" msgstr "" diff --git a/locale/en/reference/reference_rock/index.pot b/locale/en/reference/reference_rock/index.pot index d4735c0dc0..bcea5533b3 100644 --- a/locale/en/reference/reference_rock/index.pot +++ b/locale/en/reference/reference_rock/index.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Tarantool 2.11\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-12 15:09+0000\n" +"POT-Creation-Date: 2023-10-23 13:20+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -16,10 +16,6 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../doc/reference/reference_rock/index.rst:9 -msgid "Module metrics" -msgstr "" - #: ../../doc/reference/reference_rock/index.rst:9 msgid "Module luatest" msgstr "" diff --git a/locale/en/reference/reference_rock/luatest/luatest_overview.pot b/locale/en/reference/reference_rock/luatest/luatest_overview.pot index cd9bdebec7..5db1635481 100644 --- a/locale/en/reference/reference_rock/luatest/luatest_overview.pot +++ b/locale/en/reference/reference_rock/luatest/luatest_overview.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Tarantool 2.11\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-12 15:09+0000\n" +"POT-Creation-Date: 2023-10-23 13:20+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -23,786 +23,3 @@ msgstr "" #: ../../doc/reference/reference_rock/luatest/luatest_overview.rst:5 msgid "More about Luatest API see :ref:`below `." msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:3 -msgid "Overview" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:5 -msgid "Tool for testing tarantool applications." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:7 -msgid "Highlights:" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:9 -msgid "executable to run tests in directory or specific files," -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:10 -msgid "before/after suite hooks," -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:11 -msgid "before/after test group hooks," -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:12 -msgid "`output capturing `_," -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:13 -msgid "`helpers `_ for testing tarantool applications," -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:14 -msgid "`luacov integration `_." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:18 -msgid "Requirements" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:20 -msgid "Tarantool (it requires tarantool-specific ``fio`` module and ``ffi`` from LuaJIT)." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:24 -msgid "Installation" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:26 -msgid "tarantoolctl rocks install luatest\n" -".rocks/bin/luatest --help # list available options" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:33 -msgid "Usage" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:35 -msgid "Define tests." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:37 -msgid "-- test/feature_test.lua\n" -"local t = require('luatest')\n" -"local g = t.group('feature')\n" -"-- Default name is inferred from caller filename when possible.\n" -"-- For `test/a/b/c_d_test.lua` it will be `a.b.c_d`.\n" -"-- So `local g = t.group()` works the same way.\n" -"\n" -"-- Tests. All properties with name staring with `test` are treated as test cases.\n" -"g.test_example_1 = function() ... end\n" -"g.test_example_n = function() ... end\n" -"\n" -"-- Define suite hooks\n" -"t.before_suite(function() ... end)\n" -"t.before_suite(function() ... end)\n" -"\n" -"-- Hooks to run once for tests group\n" -"g.before_all(function() ... end)\n" -"g.after_all(function() ... end)\n" -"\n" -"-- Hooks to run for each test in group\n" -"g.before_each(function() ... end)\n" -"g.after_each(function() ... end)\n" -"\n" -"-- Hooks to run for a specified test in group\n" -"g.before_test('test_example_1', function() ... end)\n" -"g.after_test('test_example_2', function() ... end)\n" -"-- before_test runs after before_each\n" -"-- after_test runs before after_each\n" -"\n" -"-- test/other_test.lua\n" -"local t = require('luatest')\n" -"local g = t.group('other')\n" -"-- ...\n" -"g.test_example_2 = function() ... end\n" -"g.test_example_m = function() ... end\n" -"\n" -"-- Define parametrized groups\n" -"local pg = t.group('pgroup', {{engine = 'memtx'}, {engine = 'vinyl'}})\n" -"pg.test_example_3 = function(cg)\n" -" -- Use cg.params here\n" -" box.schema.space.create('test', {\n" -" engine = cg.params.engine,\n" -" })\n" -"end\n" -"\n" -"-- Hooks can be specified for one parameter\n" -"pg.before_all({engine = 'memtx'}, function() ... end)\n" -"pg.before_each({engine = 'memtx'}, function() ... end)\n" -"pg.before_test('test_example_3', {engine = 'vinyl'}, function() ... end)" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:89 -msgid "Run tests from a path." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:91 -msgid "luatest # run all tests from the ./test directory\n" -"luatest test/integration # run all tests from the specified directory\n" -"luatest test/feature_test.lua # run all tests from the specified file" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:97 -msgid "Run tests from a group." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:99 -msgid "luatest feature # run all tests from the specified group\n" -"luatest other.test_example_2 # run one test from the specified group\n" -"luatest feature other.test_example_2 # run tests by group and test name" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:105 -msgid "Note that luatest recognizes an input parameter as a path only if it contains ``/``, otherwise, it will be considered as a group name." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:108 -msgid "luatest feature # considered as a group name\n" -"luatest ./feature # considered as a path\n" -"luatest feature/ # considered as a path" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:114 -msgid "You can also use ``-p`` option in combination with the examples above for running tests matching to some name pattern." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:116 -msgid "luatest feature -p test_example # run all tests from the specified group matching to the specified pattern" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:120 -msgid "Luatest automatically requires ``test/helper.lua`` file if it's present. You can configure luatest or run any bootstrap code there." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:123 -msgid "See the `getting-started example `_ in cartridge-cli repo." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:128 -msgid "Tests order" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:130 -msgid "Use the ``--shuffle`` option to tell luatest how to order the tests. The available ordering schemes are ``group``, ``all`` and ``none``." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:133 -msgid "``group`` shuffles tests within the groups." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:135 -msgid "``all`` randomizes execution order across all available tests. Be careful: ``before_all/after_all`` hooks run always when test group is changed, so it may run multiple time." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:139 -msgid "``none`` is the default, which executes examples within the group in the order they are defined (eventually they are ordered by functions line numbers)." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:142 -msgid "With ``group`` and ``all`` you can also specify a ``seed`` to reproduce specific order." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:144 -msgid "--shuffle none\n" -"--shuffle group\n" -"--shuffle all --seed 123\n" -"--shuffle all:123 # same as above" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:151 -msgid "To change default order use:" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:153 -msgid "-- test/helper.lua\n" -"local t = require('luatest')\n" -"t.configure({shuffle = 'group'})" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:162 -msgid "List of luatest functions" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:165 -msgid "**Assertions**" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:167 -msgid "``assert (value[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:167 -msgid "Check that value is truthy." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:169 -msgid "``assert_almost_equals (actual, expected, margin[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:169 -msgid "Check that two floats are close by margin." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:171 -msgid "``assert_covers (actual, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:171 -msgid "Checks that actual map includes expected one." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:173 -msgid "``assert_lt (left, right[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:173 -msgid "Compare numbers." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:175 -msgid "``assert_le (left, right[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:177 -msgid "``assert_gt (left, right[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:179 -msgid "``assert_ge (left, right[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:181 -msgid "``assert_equals (actual, expected[, message[, deep_analysis]])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:181 -msgid "Check that two values are equal." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:183 -msgid "``assert_error (fn, ...)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:183 -msgid "Check that calling fn raises an error." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:185 -msgid "``assert_error_msg_contains (expected_partial, fn, ...)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:187 -msgid "``assert_error_msg_content_equals (expected, fn, ...)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:187 -msgid "Strips location info from message text." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:189 -msgid "``assert_error_msg_equals (expected, fn, ...)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:189 -msgid "Checks full error: location and text." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:191 -msgid "``assert_error_msg_matches (pattern, fn, ...)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:193 -msgid "``assert_eval_to_false (value[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:193 -msgid "Alias for assert_not." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:195 -msgid "``assert_eval_to_true (value[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:195 -msgid "Alias for assert." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:197 -msgid "``assert_items_include (actual, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:197 -msgid "Checks that one table includes all items of another, irrespective of their keys." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:200 -msgid "``assert_is (actual, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:200 -msgid "Check that values are the same." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:202 -msgid "``assert_is_not (actual, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:202 -msgid "Check that values are not the same." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:204 -msgid "``assert_items_equals (actual, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:204 -msgid "Checks that two tables contain the same items, irrespective of their keys." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:207 -msgid "``assert_nan (value[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:209 -msgid "``assert_not (value[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:209 -msgid "Check that value is falsy." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:211 -msgid "``assert_not_almost_equals (actual, expected, margin[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:211 -msgid "Check that two floats are not close by margin" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:213 -msgid "``assert_not_covers (actual, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:213 -msgid "Checks that map does not contain the other one." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:216 -msgid "``assert_not_equals (actual, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:216 -msgid "Check that two values are not equal." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:218 -msgid "``assert_not_nan (value[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:220 -msgid "``assert_not_str_contains (actual, expected[, is_pattern[, message]])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:220 -#: ../../doc/reference/reference_rock/luatest/README.rst:225 -msgid "Case-sensitive strings comparison." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:223 -msgid "``assert_not_str_icontains (value, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:223 -#: ../../doc/reference/reference_rock/luatest/README.rst:227 -msgid "Case-insensitive strings comparison." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:225 -msgid "``assert_str_contains (value, expected[, is_pattern[, message]])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:227 -msgid "``assert_str_icontains (value, expected[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:229 -msgid "``assert_str_matches (value, pattern[, start=1[, final=value:len() [, message]]])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:229 -msgid "Verify a full match for the string." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:232 -msgid "``assert_type (value, expected_type[, message])``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:232 -msgid "Check value's type." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:234 -msgid "**Flow control**" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:236 -msgid "``fail (message)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:236 -msgid "Stops a test due to a failure." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:238 -msgid "``fail_if (condition, message)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:238 -msgid "Stops a test due to a failure if condition is met." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:241 -msgid "``xfail (message)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:241 -msgid "Mark test as xfail." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:243 -msgid "``xfail_if (condition, message)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:243 -msgid "Mark test as xfail if condition is met." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:245 -msgid "``skip (message)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:245 -msgid "Skip a running test." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:247 -msgid "``skip_if (condition, message)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:247 -msgid "Skip a running test if condition is met." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:249 -msgid "``success ()``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:249 -msgid "Stops a test with a success." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:251 -msgid "``success_if (condition)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:251 -msgid "Stops a test with a success if condition is met." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:254 -msgid "**Suite and groups**" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:256 -msgid "``after_suite (fn)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:256 -msgid "Add after suite hook." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:258 -msgid "``before_suite (fn)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:258 -msgid "Add before suite hook." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:260 -msgid "``group (name)``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:260 -msgid "Create group of tests." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:267 -msgid "XFail" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:269 -msgid "The ``xfail`` mark makes test results to be interpreted vice versa: it's threated as passed when an assertion fails, and it fails if no errors are raised. It allows one to mark a test as temporarily broken due to a bug in some other component which can't be fixed immediately. It's also a good practice to keep xfail tests in sync with an issue tracker." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:275 -msgid "local g = t.group()\n" -"g.test_fail = function()\n" -" t.xfail('Must fail no matter what')\n" -" t.assert_equals(3, 4)\n" -"end" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:283 -msgid "XFail only applies to the errors raised by the luatest assertions. Regular Lua errors still cause the test failure." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:290 -msgid "Capturing output" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:292 -msgid "By default runner captures all stdout/stderr output and shows it only for failed tests. Capturing can be disabled with ``-c`` flag." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:299 -msgid "Tests repeating" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:301 -msgid "Runners can repeat tests with flags ``-r`` / ``--repeat`` (to repeat all the tests) or ``-R`` / ``--repeat-group`` (to repeat all the tests within the group)." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:308 -msgid "Parametrization" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:310 -msgid "Test group can be parametrized." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:312 -msgid "local g = t.group('pgroup', {{a = 1, b = 4}, {a = 2, b = 3}})\n" -"\n" -"g.test_params = function(cg)\n" -" ...\n" -" log.info('a = %s', cg.params.a)\n" -" log.info('b = %s', cg.params.b)\n" -" ...\n" -"end" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:323 -msgid "Group can be parametrized with a matrix of parameters using `luatest.helpers`:" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:325 -msgid "local g = t.group('pgroup', t.helpers.matrix({a = {1, 2}, b = {3, 4}}))\n" -"-- Will run:\n" -"-- * a = 1, b = 3\n" -"-- * a = 1, b = 4\n" -"-- * a = 2, b = 3\n" -"-- * a = 2, b = 4" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:334 -msgid "Each test will be performed for every params combination. Hooks will work as usual unless there are specified params. The order of execution in the hook group is determined by the order of declaration." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:338 -msgid "-- called before every test\n" -"g.before_each(function(cg) ... end)\n" -"\n" -"-- called before tests when a == 1\n" -"g.before_each({a = 1}, function(cg) ... end)\n" -"\n" -"-- called only before the test when a == 1 and b == 3\n" -"g.before_each({a = 1, b = 3}, function(cg) ... end)\n" -"\n" -"-- called before test named 'test_something' when a == 1\n" -"g.before_test('test_something', {a = 1}, function(cg) ... end)\n" -"\n" -"--etc" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:354 -msgid "Test from a parameterized group can be called from the command line in such a way:" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:356 -msgid "luatest pgroup.a:1.b:4.test_params\n" -"luatest pgroup.a:2.b:3.test_params" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:361 -msgid "Note that values for ``a`` and ``b`` have to match to defined group params. The command below will give you an error because such params are not defined for the group." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:364 -msgid "luatest pgroup.a:2.b:2.test_params # will raise an error" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:372 -msgid "Test helpers" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:374 -msgid "There are helpers to run tarantool applications and perform basic interaction with it. If application follows configuration conventions it is possible to use options to configure server instance and helpers at the same time. For example ``http_port`` is used to perform http request in tests and passed in ``TARANTOOL_HTTP_PORT`` to server process." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:380 -msgid "local server = luatest.Server:new({\n" -" command = '/path/to/executable.lua',\n" -" -- arguments for process\n" -" args = {'--no-bugs', '--fast'},\n" -" -- additional envars to pass to process\n" -" env = {SOME_FIELD = 'value'},\n" -" -- passed as TARANTOOL_WORKDIR\n" -" workdir = '/path/to/test/workdir',\n" -" -- passed as TARANTOOL_HTTP_PORT, used in http_request\n" -" http_port = 8080,\n" -" -- passed as TARANTOOL_LISTEN, used in connect_net_box\n" -" net_box_port = 3030,\n" -" -- passed to net_box.connect in connect_net_box\n" -" net_box_credentials = {user = 'username', password = 'secret'},\n" -"})\n" -"server:start()\n" -"-- Wait until server is ready to accept connections.\n" -"-- This may vary from app to app: for one server:connect_net_box() is enough,\n" -"-- for another more complex checks are required.\n" -"luatest.helpers.retrying({}, function() server:http_request('get', '/ping') end)\n" -"\n" -"-- http requests\n" -"server:http_request('get', '/path')\n" -"server:http_request('post', '/path', {body = 'text'})\n" -"server:http_request('post', '/path', {json = {field = value}, http = {\n" -" -- http client options\n" -" headers = {Authorization = 'Basic ' .. credentials},\n" -" timeout = 1,\n" -"}})\n" -"\n" -"-- This method throws error when response status is outside of then range 200..299.\n" -"-- To change this behaviour, path `raise = false`:\n" -"t.assert_equals(server:http_request('get', '/not_found', {raise = false}).status, 404)\n" -"t.assert_error(function() server:http_request('get', '/not_found') end)\n" -"\n" -"-- using net_box\n" -"server:connect_net_box()\n" -"server:eval('return do_something(...)', {arg1, arg2})\n" -"server:call('function_name', {arg1, arg2})\n" -"server:exec(function() return box.info() end)\n" -"server:stop()" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:424 -msgid "``luatest.Process:start(path, args, env)`` provides low-level interface to run any other application." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:426 -msgid "There are several small helpers for common actions:" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:428 -msgid "luatest.helpers.uuid('ab', 2, 1) == 'abababab-0002-0000-0000-000000000001'\n" -"\n" -"luatest.helpers.retrying({timeout = 1, delay = 0.1}, failing_function, arg1, arg2)\n" -"-- wait until server is up\n" -"luatest.helpers.retrying({}, function() server:http_request('get', '/status') end)" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:440 -msgid "luacov integration" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:442 -msgid "Install `luacov `_ with ``tarantoolctl rocks install luacov``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:443 -msgid "Configure it with ``.luacov`` file" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:444 -msgid "Clean old reports ``rm -f luacov.*.out*``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:445 -msgid "Run luatest with ``--coverage`` option" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:446 -msgid "Generate report with ``.rocks/bin/luacov .``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:447 -msgid "Show summary with ``grep -A999 '^Summary' luacov.report.out``" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:449 -msgid "When running integration tests with coverage collector enabled, luatest automatically starts new tarantool instances with luacov enabled. So coverage is collected from all the instances. However this has some limitations:" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:454 -msgid "It works only for instances started with ``Server`` helper." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:455 -msgid "Process command should be executable lua file or tarantool with script argument." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:456 -msgid "Instance must be stopped with ``server:stop()``, because this is the point where stats are saved." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:457 -msgid "Don't save stats concurrently to prevent corruption." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:461 -msgid "Development" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:463 -msgid "Check out the repo." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:464 -msgid "Prepare makefile with ``cmake .``." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:465 -msgid "Install dependencies with ``make bootstrap``." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:466 -msgid "Run it with ``make lint`` before committing changes." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:467 -msgid "Run tests with ``bin/luatest``." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:471 -msgid "Contributing" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:473 -msgid "Bug reports and pull requests are welcome on at https://github.com/tarantool/luatest." -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:478 -msgid "License" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/README.rst:480 -msgid "MIT" -msgstr "" - -#: ../../doc/reference/reference_rock/luatest/_includes/index.rst:3 -msgid "API" -msgstr "" diff --git a/locale/en/singlehtml.pot b/locale/en/singlehtml.pot index e117741563..d81a459f66 100644 --- a/locale/en/singlehtml.pot +++ b/locale/en/singlehtml.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Tarantool 2.11\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-12 15:09+0000\n" +"POT-Creation-Date: 2023-10-23 13:20+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -19,7 +19,3 @@ msgstr "" #: ../../doc/singlehtml.rst:9 msgid "CRUD operations" msgstr "" - -#: ../../doc/singlehtml.rst:9 -msgid "Cluster on Cartridge" -msgstr "" diff --git a/locale/en/toctree.pot b/locale/en/toctree.pot index 85dd3015e0..9d4f9dc580 100644 --- a/locale/en/toctree.pot +++ b/locale/en/toctree.pot @@ -8,7 +8,7 @@ msgid "" msgstr "" "Project-Id-Version: Tarantool 2.11\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-10-12 15:09+0000\n" +"POT-Creation-Date: 2023-10-23 13:20+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -19,7 +19,3 @@ msgstr "" #: ../../doc/toctree.rst:3 msgid "CRUD operations" msgstr "" - -#: ../../doc/toctree.rst:3 -msgid "Cluster on Cartridge" -msgstr "" From d1716899392a90be5d8a3facca5b0859590ca5c2 Mon Sep 17 00:00:00 2001 From: Weblate Admin Date: Tue, 24 Oct 2023 13:21:08 +0000 Subject: [PATCH 2/3] Translated using Weblate (Russian) Currently translated at 16.6% (5 of 30 strings) Translation: testing_project/Documentation: contributing/docs/style Translate-URL: http://weblate.tarantool.io/projects/testing_project/documentation-contributingdocsstyle/ru/ --- .../ru/LC_MESSAGES/contributing/docs/style.po | 422 ------------------ 1 file changed, 422 deletions(-) diff --git a/locale/ru/LC_MESSAGES/contributing/docs/style.po b/locale/ru/LC_MESSAGES/contributing/docs/style.po index 01763b5f29..e69de29bb2 100644 --- a/locale/ru/LC_MESSAGES/contributing/docs/style.po +++ b/locale/ru/LC_MESSAGES/contributing/docs/style.po @@ -1,422 +0,0 @@ - -msgid "Language and style" -msgstr "" - -msgid "General style" -msgstr "" - -msgid "Concise is good" -msgstr "" - -msgid "" -"People usually read technical documentation because they want something up " -"and running quickly. Write simpler, more concise sentences." -msgstr "" - -msgid "" -"Split the content into smaller paragraphs to improve readability. This will " -"also eliminate the need for using ``|br|`` and help us translate content " -"faster. Any paragraph over 6 sentences is large." -msgstr "" - -msgid "Keep your audience in mind" -msgstr "" - -msgid "" -"Consider your audience's level. A getting started guide should be written in" -" simpler terms than an advanced internals description." -msgstr "" - -msgid "" -"If you choose to use metaphors to clarify a concept, make sure they are " -"relatable for an international audience of IT professionals." -msgstr "" - -msgid "Don't say \"we\"" -msgstr "" - -msgid "" -"Only use the pronoun \"we\" in entry-level texts like getting started " -"guides. In other cases, avoid using \"we\", because it is unclear who that " -"is exactly. `Consider how Gentoo does it " -"`__." -msgstr "" - -msgid "Stick to the facts" -msgstr "" - -msgid "" -"Use measurable facts instead of personal judgments. Different users may have" -" different ideas of what \"often\", \"slow\", or \"small\" means." -msgstr "" - -msgid "**Bad example:** This parameter is rarely updated." -msgstr "" - -msgid "" -"**Good example:** This parameter is updated every two hours or more rarely." -msgstr "" - -msgid "Refer to absolute time" -msgstr "" - -msgid "" -"Temporal adverbs like \"today\", \"currently\", \"now\", \"in the future\", " -"etc. are relative -- that is, they are based on the time the documentation " -"is created." -msgstr "" - -msgid "" -"Instead of these words, use absolute terms like version numbers or years. " -"The meaning of those terms doesn't change over time." -msgstr "" - -msgid "" -"If technical documentation is tied semantically to the time it was created, " -"it increases the risk of the documentation becoming obsolete." -msgstr "" - -msgid "" -"**Bad example:** Previously, the functionality worked differently. " -"Currently, it supports SSL." -msgstr "" - -msgid "" -"**Good example:** Before version x.y.z, the functionality worked " -"differently. Since version x.y.z, it supports SSL." -msgstr "" - -msgid "Express one idea in a sentence" -msgstr "" - -msgid "" -"Say exactly one thing in a sentence. If you want to define or clarify " -"something, do it in a separate sentence. Simple sentences are easier to " -"read, understand and translate." -msgstr "" - -msgid "Don't" -msgstr "" - -msgid "Do" -msgstr "" - -msgid "" -"Dogs (I have three of them) are my favorite animals. Their names are Ace, " -"Bingo and Charm; Charm is the youngest one." -msgstr "" - -msgid "" -"Dogs are my favorite animals. I have three of them. Their names are Ace, " -"Bingo and Charm. Charm is the youngest one." -msgstr "" - -msgid "" -"memtx (the in-memory storage engine) is the default and was the first to " -"arrive." -msgstr "" -"memtx (in-memory движок базы данных) используется по умолчанию, который был " -"первым." - -msgid "" -"memtx is an in-memory storage engine. It is the default and was the first to" -" arrive." -msgstr "" - -msgid "" -"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 "" -"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 "Put examples next to theory" -msgstr "" - -msgid "" -"It's best if examples immediately follow the concept they illustrate. The " -"readers wouldn't want to look for the examples in a different part of the " -"article." -msgstr "" - -msgid "Specify link text" -msgstr "" - -msgid "" -"When you provide a :doc:`link `, clearly " -"specify where it leads. In this way, you will not mislead the reader." -msgstr "" - -msgid "Bad example:" -msgstr "" - -msgid "For more details, click :doc:`here `." -msgstr "" - -msgid "Use :doc:`this `." -msgstr "" - -msgid "Good example:" -msgstr "" - -msgid "" -"For more details, refer to the documentation on :doc:`making links " -"`." -msgstr "" - -msgid "Use full :doc:`link names `." -msgstr "" - -msgid "Formatting" -msgstr "" - -msgid "Use lists and tables" -msgstr "" - -msgid "Lists and tables help split heavy content into manageable chunks." -msgstr "" - -msgid "" -"To make tables maintainable and easy to translate, use the ``list-table`` " -"directive, as described in the Tarantool :doc:`table markup reference " -"`." -msgstr "" - -msgid "" -"Translators find it hard to work with content \"drawn\" with ASCII " -"characters, because it requires adjusting the number of spaces and manually " -"counting characters." -msgstr "" - -msgid "Don't \"draw\" tables with ASCII characters" -msgstr "" - -msgid "Use the \"list-table\" directive instead" -msgstr "" - -msgid "Format code as code" -msgstr "" - -msgid "" -"Format large code fragments using the ``code-block`` directive, indicating " -"the language. For ``shorter code snippets``, make sure that only code goes " -"in the backticks. Non-code shouldn't be formatted as code, because this " -"confuses users (and translators, too). Check our guidelines on :doc:`writing" -" about code `." -msgstr "" - -msgid "" -"For more about formatting, check out the Tarantool :doc:`markup reference " -"`." -msgstr "" - -msgid "Word choice" -msgstr "" - -msgid "Instance vs server" -msgstr "Экземпляр или сервер" - -msgid "" -"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 "" - -msgid "" -"Wrong usage: \"Replication allows multiple Tarantool *servers* to work with " -"copies of the same database.\"" -msgstr "" - -msgid "" -"Correct usage: \"Replication allows multiple Tarantool *instances* to work " -"with copies of the same database.\"" -msgstr "" - -msgid "Don't use i.e. and e.g." -msgstr "" - -msgid "Don't use the following contractions:" -msgstr "" - -msgid "" -"`\"i.e.\" `_---from the " -"Latin \"id est\". Use \"that is\" or \"which means\" instead." -msgstr "" - -msgid "" -"`\"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 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 "Spelling and punctuation" -msgstr "" - -msgid "Tarantool capitalization" -msgstr "" - -msgid "" -"The word \"Tarantool\" is capitalized because it's a product name. The only " -"context where it can start with a lowercase \"t\" is code. Learn more about " -":doc:`code formatting in Tarantool documentation " -"`." -msgstr "" - -msgid "US vs British spelling" -msgstr "Британский или американский вариант английского" - -#, fuzzy -msgid "Use the US English spelling." -msgstr "Британский или американский вариант английского" - -msgid "Check your spelling and punctuation" -msgstr "" - -msgid "" -"Consider checking spelling, grammar, and punctuation with special tools like" -" `LanguageTool `_ or `Grammarly " -"`_." -msgstr "" - -msgid "Dashes" -msgstr "" - -msgid "" -"Special symbols like dashes, quotation marks, and apostrophes look the same " -"across all Tarantool documentation in a single language. This is because the" -" documentation :doc:`builder ` renders specific " -"character sequences in the source into correct typographic characters." -msgstr "" - -msgid "" -"Tarantool documentarians are recommended to use the **en dash** (--) only. " -"Type two hyphens to insert it: ``--``. Add spaces on both sides of the dash." -" Don't use a single hyphen as a dash." -msgstr "" - -msgid "Use the dash for the following purposes:" -msgstr "" - -msgid "To separate extra information." -msgstr "" - -msgid "To mark a break in a sentence." -msgstr "" - -msgid "" -"To mark ranges like 4--16 GB (don't surround the dash with spaces in this " -"case)." -msgstr "" - -msgid "" -"When indicating a range like ``code element 1``\\--``code element 2``, " -"escape the series of hyphens using `character-level inline markup " -"`_. Otherwise, the RST interpreter will perceive the " -"dash as part of the RST syntax:" -msgstr "" - -msgid "``box.begin()``\\--``box.commit()``" -msgstr "" - -msgid "Ending punctuation in lists and tables" -msgstr "" - -msgid "" -"The following recommendations are *for the English language only.* You can " -"find similar guidelines for the Russian language in the `external reference " -"for Russian proofreaders " -"`__." -msgstr "" - -msgid "Lists" -msgstr "" - -msgid "There are two kinds of lists:" -msgstr "" - -msgid "Where each item forms a complete sentence." -msgstr "" - -msgid "Where each item is a phrase of three or less words or a term." -msgstr "" - -msgid "" -"In the former case, start each item with a capital letter and end with a " -"period. In the latter case, start it with a lowercase letter and add no " -"ending punctuation (no period, no comma, no semicolon)." -msgstr "" - -msgid "" -"A list should be formatted uniformly: choose the first or second rule for " -"all items in a list." -msgstr "" - -msgid "" -"The above rules are adapted from the `Microsoft style guide " -"`__." -msgstr "" - -msgid "" -"The sentence preceding a list can end either with a semicolon or a period." -msgstr "" - -msgid "" -"Don't add redundant conjunctions like \"and\"/\"or\" before the last list " -"item." -msgstr "" - -msgid "General English punctuation rules still apply for text in lists." -msgstr "" - -msgid "Tables" -msgstr "" - -msgid "" -"For the text in cells, use periods or other end punctuation only if the " -"cells contain complete sentences or a mixture of fragments and sentences. " -"(This is also a `Microsoft guideline `__ for the English " -"language.)" -msgstr "" - -msgid "" -"Besides, make sure that your table punctuation is consistent -- either all " -"similar list/table items end with a period or they all don't. In the example" -" below, *all* items in the second column don't have ending punctuation. " -"Meanwhile, *all* items in the fourth column end with a period, because they " -"are a mix of fragments and sentences:" -msgstr "" - -msgid "Items in one column have similar ending punctuation" -msgstr "" - -msgid "" -"To learn more about table formatting, check the :doc:`table markup reference" -" `." -msgstr "" - -#~ msgid "We use the US English spelling." -#~ msgstr "" - -#~ msgid "" -#~ "Dogs (I have three of them) are my favourite animals. Their names are Ace, " -#~ "Bingo and Charm; Charm is the youngest one." -#~ msgstr "" - -#~ msgid "" -#~ "Dogs are my favourite animals. I have three of them. Their names are Ace, " -#~ "Bingo and Charm. Charm is the youngest one." -#~ msgstr "" From 0a0ca4387f6c42383f4b4b22680c11a3e218cfc9 Mon Sep 17 00:00:00 2001 From: Weblate Admin Date: Tue, 24 Oct 2023 10:09:00 +0000 Subject: [PATCH 3/3] Translated using Weblate (Russian) Currently translated at 100.0% (12 of 12 strings) Translation: testing_project/Documentation: book/admin/logs Translate-URL: http://weblate.tarantool.io/projects/testing_project/documentation-bookadminlogs/ru/ --- locale/ru/LC_MESSAGES/book/admin/logs.po | 234 ----------------------- 1 file changed, 234 deletions(-) diff --git a/locale/ru/LC_MESSAGES/book/admin/logs.po b/locale/ru/LC_MESSAGES/book/admin/logs.po index 03b24f345f..e69de29bb2 100644 --- a/locale/ru/LC_MESSAGES/book/admin/logs.po +++ b/locale/ru/LC_MESSAGES/book/admin/logs.po @@ -1,234 +0,0 @@ - -msgid "Logs" -msgstr "Журналирование" - -msgid "" -"Each Tarantool instance logs important events to its own log file " -"``.log``. For instances started with :ref:`tt `, the " -"log location is defined by the ``log_dir`` parameter in the :ref:`tt " -"configuration `. By default, it's ``/var/log/tarantool`` in the " -"``tt`` :ref:`system mode `, and the ``var/log/`` " -"subdirectory of the ``tt`` working directory in the :ref:`local mode `. In the specified location, ``tt`` creates separate " -"directories for each instance's logs." -msgstr "" - -msgid "" -"To check how logging works, write something to the log using the :ref:`log " -"` module:" -msgstr "" - -#, fuzzy -msgid "" -"$ tt connect my_app\n" -" • Connecting to the instance...\n" -" • Connected to /var/run/tarantool/my_app.control\n" -"\n" -"/var/run/tarantool/my_app.control> require('log').info(\"Hello for the manual readers\")" -msgstr "" -"$ tarantoolctl enter my_app\n" -"/bin/tarantoolctl: connected to unix/:/var/run/tarantool/my_app.control\n" -"unix/:/var/run/tarantool/my_app.control> require('log').info(\"Hello for the manual readers\")\n" -"---\n" -"..." - -msgid "Then check the logs:" -msgstr "Затем проверим содержимое журнала:" - -msgid "" -"$ tail /var/log/tarantool/my_app.log\n" -"2023-09-12 18:13:00.396 [67173] main/111/guard of feedback_daemon/box.feedback_daemon V> metrics_collector restarted\n" -"2023-09-12 18:13:00.396 [67173] main/103/-/box.feedback_daemon V> feedback_daemon started\n" -"2023-09-12 18:13:00.396 [67173] main/103/- D> memtx_tuple_new_raw_impl(14) = 0x1090077b4\n" -"2023-09-12 18:13:00.396 [67173] main/103/- D> memtx_tuple_new_raw_impl(26) = 0x1090077ec\n" -"2023-09-12 18:13:00.396 [67173] main/103/- D> memtx_tuple_new_raw_impl(39) = 0x109007824\n" -"2023-09-12 18:13:00.396 [67173] main/103/- D> memtx_tuple_new_raw_impl(24) = 0x10900785c\n" -"2023-09-12 18:13:00.396 [67173] main/103/- D> memtx_tuple_new_raw_impl(39) = 0x109007894\n" -"2023-09-12 18:13:00.396 [67173] main/106/checkpoint_daemon I> scheduled next checkpoint for Tue Sep 12 19:44:34 2023\n" -"2023-09-12 18:13:00.396 [67173] main I> entering the event loop\n" -"2023-09-12 18:13:11.656 [67173] main/114/console/unix/:/tarantool I> Hello for the manual readers" -msgstr "" - -msgid "Log rotation" -msgstr "" - -msgid "" -"When :ref:`logging to a file `, the system administrator " -"must ensure logs are rotated timely and do not take up all the available " -"disk space. To prevent log files from growing infinitely, ``tt`` " -"automatically rotates instance logs. The following ``tt`` configuration " -"parameters define the log rotation: ``log_maxsize`` (in megabytes) and " -"``log_maxage`` (in days). When any of these limits is reached, the log is " -"rotated. Additionally, there is the ``log_maxbackups`` parameter (the number" -" of stored log files for an instance), which enables automatic removal of " -"old log files." -msgstr "" - -msgid "" -"# tt.yaml\n" -"tt:\n" -" app:\n" -" log_maxsize: 100\n" -" log_maxage: 3\n" -" log_maxbackups: 50\n" -" # ..." -msgstr "" - -msgid "" -"There is also the :ref:`tt logrotate ` command that performs " -"log rotation on demand." -msgstr "" - -msgid "tt logrotate my_app" -msgstr "" - -msgid "" -"To learn about log rotation in the deprecated ``tarantoolctl`` utility, " -"check its :ref:`documentation `." -msgstr "" - -msgid "Log formats" -msgstr "" - -#, fuzzy -msgid "" -"Tarantool can write its logs to a log file, to ``syslog``, or to a specified" -" program through a pipe." -msgstr "" -"Tarantool может писать события в файл журнала, ``syslog`` или программу, " -"указанную в конфигурационном файле (см. параметр :ref:`log `)." - -msgid "" -"File is the default log format for ``tt``. To send logs to a pipe or " -"``syslog``, specify the :ref:`box.cfg.log ` parameter, for " -"example:" -msgstr "" - -msgid "" -"box.cfg{log = '| cronolog tarantool.log'}\n" -"-- or\n" -"box.cfg{log = 'syslog:identity=tarantool,facility=user'}" -msgstr "" - -msgid "" -"In such configurations, log rotation is usually handled by the external " -"program used for logging." -msgstr "" - -#~ msgid "" -#~ "Tarantool logs important events to a file, e.g. " -#~ "``/var/log/tarantool/my_app.log``. To build the log file path, " -#~ "``tarantoolctl`` takes the instance name, prepends the instance directory " -#~ "and appends “.log” extension." -#~ msgstr "" -#~ "Все важные события Tarantool записывает в файл журнала -- например, в " -#~ "``/var/log/tarantool/my_app.log``. ``tarantoolctl`` строит путь до файла " -#~ "журнала следующим образом: \"путь до директории с экземплярами\" + \"имя " -#~ "экземпляра\" + \".lua\"." - -#~ msgid "Let’s write something to the log file:" -#~ msgstr "Запишем что-нибудь в файл журнала:" - -#~ msgid "" -#~ "$ tail /var/log/tarantool/my_app.log\n" -#~ "2017-04-04 15:54:04.977 [29255] main/101/tarantoolctl C> version 1.7.3-382-g68ef3f6a9\n" -#~ "2017-04-04 15:54:04.977 [29255] main/101/tarantoolctl C> log level 5\n" -#~ "2017-04-04 15:54:04.978 [29255] main/101/tarantoolctl I> mapping 134217728 bytes for tuple arena...\n" -#~ "2017-04-04 15:54:04.985 [29255] iproto/101/main I> binary: bound to [::1]:3301\n" -#~ "2017-04-04 15:54:04.986 [29255] main/101/tarantoolctl I> recovery start\n" -#~ "2017-04-04 15:54:04.986 [29255] main/101/tarantoolctl I> recovering from `/var/lib/tarantool/my_app/00000000000000000000.snap'\n" -#~ "2017-04-04 15:54:04.988 [29255] main/101/tarantoolctl I> ready to accept requests\n" -#~ "2017-04-04 15:54:04.988 [29255] main/101/tarantoolctl I> set 'checkpoint_interval' configuration option to 3600\n" -#~ "2017-04-04 15:54:04.988 [29255] main/101/my_app I> Run console at unix/:/var/run/tarantool/my_app.control\n" -#~ "2017-04-04 15:54:04.989 [29255] main/106/console/unix/:/var/ I> started\n" -#~ "2017-04-04 15:54:04.989 [29255] main C> entering the event loop\n" -#~ "2017-04-04 15:54:47.147 [29255] main/107/console/unix/: I> Hello for the manual readers" -#~ msgstr "" -#~ "$ tail /var/log/tarantool/my_app.log\n" -#~ "2017-04-04 15:54:04.977 [29255] main/101/tarantoolctl C> version 1.7.3-382-g68ef3f6a9\n" -#~ "2017-04-04 15:54:04.977 [29255] main/101/tarantoolctl C> log level 5\n" -#~ "2017-04-04 15:54:04.978 [29255] main/101/tarantoolctl I> mapping 134217728 bytes for tuple arena...\n" -#~ "2017-04-04 15:54:04.985 [29255] iproto/101/main I> binary: bound to [::1]:3301\n" -#~ "2017-04-04 15:54:04.986 [29255] main/101/tarantoolctl I> recovery start\n" -#~ "2017-04-04 15:54:04.986 [29255] main/101/tarantoolctl I> recovering from `/var/lib/tarantool/my_app/00000000000000000000.snap'\n" -#~ "2017-04-04 15:54:04.988 [29255] main/101/tarantoolctl I> ready to accept requests\n" -#~ "2017-04-04 15:54:04.988 [29255] main/101/tarantoolctl I> set 'checkpoint_interval' configuration option to 3600\n" -#~ "2017-04-04 15:54:04.988 [29255] main/101/my_app I> Run console at unix/:/var/run/tarantool/my_app.control\n" -#~ "2017-04-04 15:54:04.989 [29255] main/106/console/unix/:/var/ I> started\n" -#~ "2017-04-04 15:54:04.989 [29255] main C> entering the event loop\n" -#~ "2017-04-04 15:54:47.147 [29255] main/107/console/unix/: I> Hello for the manual readers" - -#~ msgid "" -#~ "When logging to a file, the system administrator must ensure logs are " -#~ "rotated timely and do not take up all the available disk space. With " -#~ "``tarantoolctl``, log rotation is pre-configured to use ``logrotate`` " -#~ "program, which you must have installed." -#~ msgstr "" -#~ "При включенном журналировании системный администратор должен обеспечивать " -#~ "своевременную ротацию журналов, чтобы избежать переполнения дискового " -#~ "пространства. Ротация журналов в ``tarantoolctl`` производится с помощью " -#~ "программы ``logrotate``, которую необходимо установить заранее." - -#~ msgid "" -#~ "File ``/etc/logrotate.d/tarantool`` is part of the standard Tarantool " -#~ "distribution, and you can modify it to change the default behavior. This is " -#~ "what this file is usually like:" -#~ msgstr "" -#~ "Файл ``/etc/logrotate.d/tarantool`` поставляется со стандартным " -#~ "дистрибутивом Tarantool. Его можно редактировать для изменения поведения по " -#~ "умолчанию. Содержимое файла обычно выглядит так:" - -#~ msgid "" -#~ "/var/log/tarantool/*.log {\n" -#~ " daily\n" -#~ " size 512k\n" -#~ " missingok\n" -#~ " rotate 10\n" -#~ " compress\n" -#~ " delaycompress\n" -#~ " create 0640 tarantool adm\n" -#~ " postrotate\n" -#~ " /usr/bin/tarantoolctl logrotate `basename ${1%%.*}`\n" -#~ " endscript\n" -#~ "}" -#~ msgstr "" -#~ "/var/log/tarantool/*.log {\n" -#~ " daily\n" -#~ " size 512k\n" -#~ " missingok\n" -#~ " rotate 10\n" -#~ " compress\n" -#~ " delaycompress\n" -#~ " create 0640 tarantool adm\n" -#~ " postrotate\n" -#~ " /usr/bin/tarantoolctl logrotate `basename ${1%%.*}`\n" -#~ " endscript\n" -#~ "}" - -#~ msgid "" -#~ "If you use a different log rotation program, you can invoke ``tarantoolctl " -#~ "logrotate`` command to request instances to reopen their log files after " -#~ "they were moved by the program of your choice." -#~ msgstr "" -#~ "Если вы используете другую программу для ротации журналов, можно вызвать " -#~ "команду ``tarantoolctl logrotate``, чтобы экземпляры переоткрыли свои файлы " -#~ "журнала после того, как выбранная вами программа переместила их." - -#~ msgid "" -#~ "By default, logs are written to a file as defined in ``tarantoolctl`` " -#~ "defaults. ``tarantoolctl`` automatically detects if an instance is using " -#~ "``syslog`` or an external program for logging, and does not override the log" -#~ " destination in this case. In such configurations, log rotation is usually " -#~ "handled by the external program used for logging. So, ``tarantoolctl " -#~ "logrotate`` command works only if logging-into-file is enabled in the " -#~ "instance file." -#~ msgstr "" -#~ "По умолчанию запись производится в файл журнала, как указано в исходных " -#~ "настройках ``tarantoolctl``. Скрипт ``tarantoolctl`` автоматически " -#~ "определяет, когда экземпляр использует для журналирования ``syslog`` или " -#~ "внешнюю программу, и не изменяет то, куда ведется запись. В таких случаях " -#~ "ротацию журналов обычно выполняет та же программа, которая используется для " -#~ "журналирования. Именно поэтому команда ``tarantoolctl logrotate`` сработает " -#~ "только в том случае, если в файле экземпляра включена возможность вести " -#~ "запись в файл."