diff --git a/core/common/overlays/src/main/res/values-ru/strings.xml b/core/common/overlays/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..c1b977439 --- /dev/null +++ b/core/common/overlays/src/main/res/values-ru/strings.xml @@ -0,0 +1,24 @@ + + + + Перемещение + Индекс + Идёт запись жеста… + + %1$d/%2$d + \ No newline at end of file diff --git a/core/common/quality/src/main/res/values-ru/strings.xml b/core/common/quality/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..b442c9f0c --- /dev/null +++ b/core/common/quality/src/main/res/values-ru/strings.xml @@ -0,0 +1,26 @@ + + + + + Устранение неполадок + Похоже, что разрешение на доступ к Спец. возможностям было снято неоднократно. Если вы не делали этого сами, значит это было сделано вашим + устройством автоматически.\n\nНекоторые производители систем Android не дают нормально функционировать фоновым приложениям, и в зависимости от бренда устройства может + потребоваться дополнительная настройка.\n\nБолее подробную информацию об этом вопросе и о том, как можно повысить стабильность разрешений, можно найти на следующем сайте. + Ясно + + \ No newline at end of file diff --git a/core/common/ui/src/main/res/values-ru/strings.xml b/core/common/ui/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..bf42c26a8 --- /dev/null +++ b/core/common/ui/src/main/res/values-ru/strings.xml @@ -0,0 +1,107 @@ + + + + + Предупреждение + Копирование + Руководство + + + Позиция нажатия + Позиции смахивания + Опробовать %1$s + Данное действие недопустимо + + + Копировать нечего + + + Если действия в вашем сценарии выполняются + слишком быстро, то они могут попрепятствовать остановке Klick\'r через плавающее + меню.\n\nВ данном случае остановить выполнение можно нажав на физическую кнопку + уменьшения громкости. + + + Предотвращение обнаружения + Длительность нажатий (в мс) + Название + Длительность бездействия + Название сценария + Длительность смахивания (в мс) + Обязательное поле + + + + + Включено + Отключено + Позиции и продолжительность нажатий, смахиваний и бездействий будут выполняться с небольшим беспорядочным смещением + Все действия будут выполняться как требуется + + мс + с + мин + ч + Единица времени + + + Коснитесь там, где нужно расположить нажатие + Коснитесь там, откуда должно начаться смахивание + Коснитесь там, где смахивание должно окончиться + + + Значок, показывающий тип действия + Кнопка создания элемента + Кнопка создания копии из существующего элемента + Перетащить элемент, чтобы изменить порядок + Переместить плавающее меню + Запустить или приостановить сценарий + Остановить Klick\'r + Подтвердить + Вернуться + \ No newline at end of file diff --git a/feature/backup/src/main/res/values-ru/strings.xml b/feature/backup/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..925937c2d --- /dev/null +++ b/feature/backup/src/main/res/values-ru/strings.xml @@ -0,0 +1,63 @@ + + + + + + Создание копии + Удаление сценария + Загрузка копии + + + + Выбрать место сохрания + Выбрать резервную копию + + + + Создание резервной копии: %1$d/%2$d + Резервное копирование завершилось успешно + Произошла ошибка, резервное копирование было отменено + Импорт резервной копии: %1$d + Проверка данных + Импорт завершился успешно\nСценариев загружено: %1$d\nОшибок возникло: %2$d + Импорт завершился успешно\nСценариев загружено: %1$d\nОшибок возникло: %2$d + Произошла ошибка, загрузка резервной копии была отменена + Некоторые из загруженных сценариев были созданы на устройстве с другими характеристиками + экрана, и это может вызвать проблемы с обнаружениями и координатами действия.\n\nЧтобы избежать этих проблем, вам нужно сделать новые + скриншоты для ваших условий и подправить позиции нажатий и смахиваний. + На устройстве не было найдено приложения для управления сохранением/загрузкой ZIP-файлов. + + + + Состояние резервной копии + + \ No newline at end of file diff --git a/feature/dumb-config/src/main/res/values-ru/strings.xml b/feature/dumb-config/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..af89d355e --- /dev/null +++ b/feature/dumb-config/src/main/res/values-ru/strings.xml @@ -0,0 +1,103 @@ + + + + + + Тип действия + Сценарий + + + Действия + Параметры + + + Длительность: %1$s + Нажимать на любою точку на экране + Нажимает %1$s на точку [%2$d, %3$d] + Нажимать на точку [%1$d\; %2$d] + Приостановить выполнение + Длительность: %1$s + Всего повторений: %1$d + Повторяется бесконечно + Смахивать с одной позиции на экране до другой + Движется %1$s из точки [%2$d, %3$d] + в точку [%4$d, %5$d] + Смахивает с точки [%1$d, %2$d] + до точки [%3$d, %4$d] + Нажатие + Бездействие + Смахивание + Действий нет + + + Созданных действий нет! + Чтобы запустить сценарий требуется + хотя бы одно действие + + + Чтобы использовать сценарий требуется + хотя бы одно действие + + + Действия из текущего сценария + Действия из всех сценариев + + + Поиск по названиям + + + + Максимальная длительность (в минутах) + Количество повторений + Задержка между повторениями (в мс) + + + Добавить новое действие в текущий сценарий + Показать или скрыть созданные действия + Открыть список действий + + \ No newline at end of file diff --git a/feature/permissions/src/main/res/values-ru/strings.xml b/feature/permissions/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..e72355326 --- /dev/null +++ b/feature/permissions/src/main/res/values-ru/strings.xml @@ -0,0 +1,52 @@ + + + + + + Специальные возможности + Уведомления + Разрешение не выдано + Поверх других приложений + + + Данное разрешение требуется для + отображения интерфейса Klick\'r поверх приложений, на которых вы хотите использовать + его. Это позволит вам настраивать выбранный сценарий не выходя из другого приложения. + Служба спец. возможностей позволит Klick\'r + выполнять жесты на экране вашего устройства. Она необходима для выполнения заданных вами в + сценарии нажатий и смахиваний.\n\nKlick\'r не будет собирать никаких данных.\n\nЧтобы активировать + эту службу, нажмите на кнопку ниже. + (необязательно) При работе приложения будет + показываться уведомление для быстрого возврата на экран выбора сценария. + Данное разрешение необходимо для + работы Klick\'r. + + + Запросить разрешение + Отклонить + + \ No newline at end of file diff --git a/feature/quick-settings-tile/src/main/res/values-ru/strings.xml b/feature/quick-settings-tile/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..0619405c5 --- /dev/null +++ b/feature/quick-settings-tile/src/main/res/values-ru/strings.xml @@ -0,0 +1,22 @@ + + + + Запустить Klick\'r + Остановить Klick\'r + Сценарий не был определён + \ No newline at end of file diff --git a/feature/revenue/src/playStore/res/values-ru/strings.xml b/feature/revenue/src/playStore/res/values-ru/strings.xml new file mode 100644 index 000000000..d12200b6d --- /dev/null +++ b/feature/revenue/src/playStore/res/values-ru/strings.xml @@ -0,0 +1,34 @@ + + + + Начинается обнаружение + + У этого приложения открытый исходный код и оно с любовью создаётся людьми в их + свободное время.\n\nПоддержите разработку просмотром рекламы или купите Klick\'r Pro, чтобы убрать её навсегда! + Спасибо Вам за покупку\nKlick\'r Pro ! + + Посмотреть рекламу + Просмотр недоступен + Купить Pro (%1$s) + Понятно + Покупка недоступна + Репозиторий на GitHub + %1$d-минутный пробный период + Операция производится + + \ No newline at end of file diff --git a/feature/smart-config/src/main/res/values-ru/event_default_config.xml b/feature/smart-config/src/main/res/values-ru/event_default_config.xml new file mode 100644 index 000000000..bf8013408 --- /dev/null +++ b/feature/smart-config/src/main/res/values-ru/event_default_config.xml @@ -0,0 +1,41 @@ + + + + 1200 + + Стандартное событие + + Нажатие + 1 + + Смахивание + 500 + + Бездействие + 50 + + Намерение + false + + Переключающее событие + + Условие + 4 + + Счётчик изменений + \ No newline at end of file diff --git a/feature/smart-config/src/main/res/values-ru/strings.xml b/feature/smart-config/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..84447f592 --- /dev/null +++ b/feature/smart-config/src/main/res/values-ru/strings.xml @@ -0,0 +1,355 @@ + + + + + + + Название + Задайте позицию + Параметры + Счётчики + Modify + + + + + Enabled + Disabled + + %1$d%% + Difference: %1$d%% + + Visible + Not visible + + On counter reached + Verify the value of a counter modified by an Action + %1$s %2$s %3$d + + On timer reached + Fulfilled after a defined time from this trigger activation + %1$s after event is enabled + + On Broadcast received + Fulfilled when a Broadcast is received + %1$s received + + Copy + Copy an existing Action from any Scenarios + + Click + Click somewhere on the screen + During %1$s on %2$s + During %1$s + + Swipe + Swipe from a position on the screen to another + During %1$s + + Wait + Pause the detection execution + During %1$s + + Change counter + Change a value to verify it later + %1$s %2$s %3$d + Counter is invalid + + Change event state + Change the enabled state of an event + Enable all + Disable all + Invert all + Change %1$d events + Target event not found + + Intent + Interact with another application + Send %1$s + Send %1$s to %2$s + Start %1$s + + + + + + Search by event name + Search by action name + Search by condition name + + Conditions from this event + Conditions from all events + + Actions from this event + Actions from other events + + Events from this scenario + Events from all scenarios + + + + + Сценарий + + Экранных событий нет! + Экранное событие содержит набор действий, выполняемых при обнаружении на экране определённого условия.\nДля выполнения сценария требуется по крайней мере одно экранное или исполняющее событие. + Исполняющих событий нет! + Исполняющее событие содержит набор действий, выполняемых при соблюдении набора пользовательских условий.\nДля выполнения сценария требуется по крайней мере одно экранное или исполняющее событие. + + Screen + Triggers + More + + Detection quality + Speed + Precision + + Show debug view + Generate a report + + Show report + Debug report is available + No debug report available + + Tutorial + Learn how to use Klick\'r + + Legacy UI + Change the action display by a list. Useful for complex scenarios. + + + + + Screen Event + Trigger + Action type + Trigger type + + %1$d conditions + No screen conditions ! + A screen condition is a part of a screenshot that will be searched on each frames displayed by your phone screen. + No conditions ! + A condition is a custom criteria for starting an action. + No actions ! + An action is an interaction (click, swipe…) with your phone triggered when the created conditions are fulfilled. + + Conditions + Actions + + State + This event will be interpreted normally when playing the scenario + This event needs to be enabled by an action to be interpreted when playing the scenario + + Operator + AND + "OR " + Only one condition must be fulfilled to trigger the actions + All conditions must be fulfilled to trigger the actions + + + + + No Actions. You need at least one Action to create a valid Event + No Screen Condition. You need at least one Condition to create a valid Event + + + + + Condition + + Visibility + The condition must be detected + The condition must not be detected + + Detection type + Detection at the captured position + Detection on the whole screen + Detection on a selected area + + Detection Area + In [%1$d, %2$d, %3$d, %4$d] + + Tolerated difference + + + + + Counter value + + Counter name + + Value + + Operator + + ]]> + = + + + + + + + Timer reached + + After + + Restart when reached + Once reached, the timer will restart, allowing this condition to be fulfilled again + Once reached, the timer will not be restarted, meaning that this condition can be fulfilled only once + + + + + Broadcast received + + + + + Click + Select a condition + + Click on + Click on the detected condition + Click on the selected position + + Click on a condition + %1$s + No condition selected + + Click on the first detected condition + Event is set to "One Condition", you can\'t select a specific one + + Click on %1$d, %2$d + + + + + Swipe + + Swipe positions + Swipe from %1$d, %2$d to %3$d, %4$d + + + + + Wait + + + + + Intent + Flags + Intent Actions + Component name + Select an application + + Advanced + Simple + + Select an application + Start an application when this action is executed + + Type + Start Activity + Send Broadcast + + Action + Broadcast Action + Flags + Component name + + Extras + + + + + Extra + + Key + Value + + Value type + Boolean + Byte + Char + Double + Integer + Float + Short + String + + True + False + + + + + Change counter + + No counter defined + Counters are created with a Change Counter Action or a Counter Reached Condition + + Value + + Operation + + + = + - + + + + + Event state + Events toggles + + Screen Events + Trigger Events + + Change all + Define the events to change manually + Enable all events in this scenario + Invert the state of all events in this scenario + Disable all events in this scenario. When all events are disabled, the scenario is stopped automatically. + + %1$d changes + No changes + Select at least one event to change to state of + + + + + This event have one or more toggle event actions referencing an event from another scenario.\nYou will have to update their target events before saving your scenario. + This event have one or more actions referencing it. Deleting this event will delete the associated actions as well.\nAre you sure ? + This condition have one or more actions referencing it. Deleting this condition will delete the associated actions as well.\nAre you sure ? + + Your scenario can\'t be saved due to an internal error.\nDo you want to modify it or cancel all your modifications ? + Klick\'r is incorrectly installed and can\'t start the detection.\n\nIf you have installed it from a legitimate application store, please contact us on GitHub, as it will help us fix this issue. + + + + + + The state of the event + The number of conditions in this event + The number of actions in this event + The image to be detected + Open the event list + The icon of the application to start. + + \ No newline at end of file diff --git a/feature/smart-debugging/src/main/res/values-ru/strings.xml b/feature/smart-debugging/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..43d4f8672 --- /dev/null +++ b/feature/smart-debugging/src/main/res/values-ru/strings.xml @@ -0,0 +1,57 @@ + + + + + Отладочный отчёт + + + Общая длительность + Изображений обработано + Средняя длительность обработки + Событий вызвано + Условий обнаружено + + + Минимальная + Максимальная + Средняя + Вызвано + Обработано + Обнаружено + Обработано + Длительность обработки + Степень достоверности обнаружений + + + %1$s / %2$s + + \ No newline at end of file diff --git a/feature/tutorial/src/main/res/values-ru/strings.xml b/feature/tutorial/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..4571c4ab5 --- /dev/null +++ b/feature/tutorial/src/main/res/values-ru/strings.xml @@ -0,0 +1,283 @@ + + + + Руководство + + Игрок: %1$d + Рекорд: %1$d + Осталось времени: %1$d + + Начать игру + Дальше + + + + + Нажимать на неподвижную цель + Создайте своё первое событие для нажатий на статичные цели + Нажимайте на синюю кнопку как можно быстрее + + Welcome to your first tutorial!\n\nHere, you will try to beat the high score + of a game with the help of Klick\'r.\n\nFirst, start the game and try to win by yourself. + + Difficult, isn\'t it?\nLet\'s use Klick\'r to beat it !\n\n + Click on the scenario configuration icon to start editing your new scenario. + + A Scenario is the root structure of Klick\'r automation.\n\n + It contains the general detection settings and a list of Events describing what will be executed when running + your Scenario. \n\nClick on the create event button to create your first event. + + An Event describe what Actions (click, swipe…) to execute when certain + Conditions are met.\n\nYou must create at least one Condition and one Action in order to create a valid Event + and use it in your scenario\n\nClick on the Conditions field to display the Conditions list. + + A Condition is a part of a screenshot that will be compared to each screen + frame of your device.\n\nTo beat the game, we want to click on the blue character when it\'s visible, so we need + a Condition that is fulfilled when the character is shown on your device screen.\n\nClick on the create + Condition button to create your first Condition. + + The first step of a Condition creation is to take a screenshot for it.\n\n + As we want to click when the blue character is visible, the screenshot must contains it. Start the game again in + order to display it, and then take the screenshot. + Use the capture button in the floating menu to take the screenshot. + + Once the screenshot is taken, you can crop it in order to only get the part + that is interesting for the detection. + If your screenshot does not contains the blue character, you can + press this button to take a new one. + + For this game, the interesting part is the blue character, so crop your + screenshot to only get him.\n\nYou can pinch on the screenshot to zoom on it and get a better accuracy for the + crop selector. + Ensure the character is complete in the selector. Also try to + crop it as close as possible to him in order to ease the image detection. + + Your Condition image is now recorded!\n\nThere is now several adjustments + that can be made to it, but the default settings suits our basic use case. As our target is not moving, it will + only detect at the capture position, which is faster than detecting on the whole screen.\n\nClick on the save + button to register it and return to the Conditions list. + + Close the Conditions list to return to the Event configuration. + + With this Condition, the scenario knows when to trigger the Actions.\n\n + You now need to define what Actions to trigger, so for this game, a click on the blue character.\n\nClick on the + Actions field to display the Actions list. + + An Action is something that is executed once the Conditions of its Event + are fulfilled.\n\nIt can be a click, a swipe, a pause, an Intent (an interaction with another application) or a + change in the Scenario execution, and multiple Actions can be defined for the same Event.\n\nClick on the create + Action button to create your first Action. + + First, we need to pick a type for your Action.\n\nFor this game, we simply + need to click on the blue character, so choose Click to create a new Click Action. + + A Click Action is defined by a position and a press duration.\n\nAs we + want to click as quickly as possible, we can keep the default press duration of 1ms, which is the lowest + possible value. So we only need to define a position.\n\nClick on the position picker button to select the Click + Action position. + + You need to select the exact position to be clicked, so you need to start + the game again to display the blue character, and then select its position.\n\nOnce the position is correct, + click on the validate button to save it. + You can\'t interact with the game while the position selector is + visible, but you can use this button to show and hide it, allowing you to remove that restriction at will. + + The click is now correctly configured!\n\nClick on the save button to + register it and return to the Actions list. + + Close the Actions list to return to the Event configuration. + + Your Event now have a Condition and an Action, which means it knows what + to execute and when to execute it.\n\nClick on the save button to register it and return to the Scenario dialog. + + The only requirement for a Scenario is to have at least one Event.\n + As our Event already cover how to win the game, we don\'t need anything else.\n\nClick on the save button the + save the Scenario in database and close the configuration dialogs. + + As you can see, the play button is now available, meaning that your + Scenario is valid and can be used for detection\n\nClick on it to start the detection. + + It\'s playing but nothing happens?\n\nThat\'s normal, it will click only + when the blue character is visible, remember? While keeping the scenario running, press the start game button + and just watch as Klick\'r will beat it for you! + + Congratulations!\n\nYou now know the basics of Klick\'r, but not + all use cases will be as simple as this game.\nTake a look at the next tutorial to learn how to track a moving + target + + + + Press a moving target + Change your event to click on a randomly moving target + Click on the moving blue button as fast as possible + + Let\'s complicate the game a little bit more. Now, the target is randomly + moving.\n\nFirst, start the game and check if you can win by yourself. + + Once again, it seems impossible to win manually, so let\'s use Smart + AutoClicker.\n\nYour scenario for the previous tutorial have been kept and load for this tutorial, but we will + need to change a few parameters in order to win this new game.\n\nClick on the Scenario configuration icon to + start updating your new scenario. + + We still want to click on the blue character, meaning that we still only + need one Condition and one Action, so only one Event.\n\nAs the use case is pretty similar to the previous game, + we will keep our Event and simply update it.\n\nClick on your previously created event to edit it. + + In a first time, we will update the Condition that detect the blue + character.\n\nClick on the Conditions field to display the Conditions list. + + As in the previous tutorial, we need to detect the blue character, but now + it is moving.\n\nOur previous Condition is already detecting the blue character, but only at one position. So you + don\'t need to take a new screenshot, as your previous Condition already has it, we just need to change its + parameters.\n\nClick on your Condition to start editing it. + + Currently, the Condition detection type is set to \"Exact\", meaning it + will only be verified at its capture position.\n\nTo win this game, we need verify the same Condition, but on + the whole screen.\n\nSelect the \"Whole screen\" type to detect the blue character anywhere on + the screen. + Detecting on the whole screen takes more time that the exact + position, keep that in mind when your Scenario execution timing is important. + + That\'s it!\nWe only needed to change the detection type in order for + your Condition to suits our needs.\n\nClick on the save button to register it and return to the Conditions list. + + Close the Conditions list to return to the Event configuration. + + Your Condition image is now updated!\n\nIn this state, the scenario will + now execute a click every time the blue character is visible anywhere on the screen, but this click will be at + the same position, the one selected during the previous tutorial. So, we need to update our Action.\n\n + Click on the Actions field to display the Actions list. + + We still want to execute a single click, but this time, we want to click + on the Condition and not a fixed position.\n\nAs this is still one click, we still need only one Action, so + let\'s edit your previous click.\n\nClick on your Action to start editing it. + + Currently, the Click Action \"Click on\" is set to \"Selected position\", + meaning you have to manually set the position to be clicked. The other choice is \"Condition\", meaning the Action will click on a + detected Condition coordinates.\n\nThat`s exactly what we need to beat the game. Every time the blue character + will be detected, this Action will click on it.\n\nSelect it to use it in your Action. + + Click on the Condition selector option to select which detected condition + to click on.\nWe need to specify it because we can have multiple Conditions in our Event. + + For our use case it is easy, we only have one condition, the blue character.\n\n + Select it to click on this Condition when it is detected on your screen. + + That\'s it!\nYour Click Action is now correctly configured to beat the + game.\n\nClick on the save button to register it and return to the Actions list. + + Close the Actions list to return to the Event configuration. + + You have updated the Condition and your Action, there is nothing more to + do.\n\nClick on the save button to register it and return to the Scenario dialog. + + One last save to register your new changes in the database and close the + configuration dialogs. + + Your Scenario is now configured to beat this new tutorial.\n\nStart the + detection with the floating menu play button and then, start the game. + + Congratulations!\n\nYou now know how to track a still or moving single + target, but there is a lot more to learn!. + + + + Combine multiple conditions + Create and combine multiple conditions for your event + Click on the blue button only when the red button is visible + + Let\'s change the rules of the game again. The blue target has stopped moving, + but now it should only be clicked when the red target is visible.\n\nFirst, start the game and check if you can win + by yourself. + + Once again, it seems impossible to win manually, so let\'s use Smart + AutoClicker.\n\nYour scenario for the previous tutorial have been kept and load for this tutorial, but we will + need to change a few parameters in order to win this new game.\n\nClick on the Scenario configuration icon to + start updating your new scenario. + + We still want to click on the blue target, but only when red on is visible.\n + So we need to add a condition for this red target in our Event.\n\nClick on your previously created event to edit it. + + We will combine several conditions, so we need to check the Condition operator + for this event.\n\nThe Condition operator indicates how multiples conditions will be interpreted together.\n + \'One\' means only one of the Conditions for this Event must be fulfilled in order + to execute the Actions.\n\n\'All\' means all Conditions for this Event must be fulfilled in order to execute the Actions. + \n\nAs we want to detect if two things are displayed together, we will use \'All\' + + Now we need to update our Conditions.\n\nClick on the Conditions field to display + the Conditions list. + + The previous Condition of detecting the blue target is still correct, but we need + a new one for the red target.\n\nClick on the create Condition button to create a new Condition for it. + + Just like for the blue target, start the game in order to show the red target. + Once it is visible, take a screenshot of it! + Use the capture button in the floating menu to take the screenshot. + + Is your screenshot containing the red target? You can crop it in order to only + get the part that is interesting for the detection, the red target. + If your screenshot does not contains the red target, you can + press this button to take a new one. + + Your Condition image is now recorded!\n\nAs the red target isn\'t moving, we + can keep the default configuration.\nClick on the save button to register it and return to the Conditions list. + + Close the Conditions list to return to the Event configuration. + + We now have two Conditions, one for each targets, and the Actions will be executed + only if both are detected.\n\nClick on the Actions field to display the Action list for our Event. + + The action is already set to click on the blue character, and it will only be + executed when the blue and the red characters are visible together.\n\nThis is exactly the behaviour we need to beat the + game, so no need to edit our click Action.\n\nClose the Actions list to return to the Event configuration. + + Click on the save button to save your Event. + + All changes must be saved in your scenario in order to be registered.\n\Click + on the save button to save your changes. + + We are ready to win this game!\n\nClick on the start button to start the + detection and then, start the game. + + Congratulations!\n\nYou now know how to combine multiple Conditions for an Event, + but there is a lot more to learn! + + + Negative conditions + Verify that something is not displayed before executing an action + + + + Multiple events scenario + Learn how to combine multiple events to achieve complex automation + + \ No newline at end of file diff --git a/smartautoclicker/src/main/res/values-ru/strings.xml b/smartautoclicker/src/main/res/values-ru/strings.xml new file mode 100644 index 000000000..a04781509 --- /dev/null +++ b/smartautoclicker/src/main/res/values-ru/strings.xml @@ -0,0 +1,117 @@ + + + + + Klick\'r + Klick\'r + + + Сценарий: %1$s + Нажмите, чтобы поменять сценарий + Запустить и скрыть + Приостановить и показать + Скрыть/Показать + Остановить + + + Сценарии + Данному приложению требуется эта служба для + выполнения созданных вами нажатий в других приложениях при исполнении требуемых условий.\n\nНикакие + данные с этих приложений собраны не будут. Исходный код открытый, не стесняйтесь посетить его на GitHub! + + + Новый сценарий + + + Экспортировать + Импортировать + Выбрать все + Конфиденциальность + Убрать рекламу + Устранение неполадок + Отмена + Найти + + + Классический автокликер.\nПросто разместите на экране нажатия и смахивания. + Остановиться после %1$s + Неограниченная длительность + Повторить %1$d раз + Повторять бесконечно + Используется обнаружение изображений для создания сложных ситуаций.\nНекоторые функции платные. + Используется обнаружение изображений для создания сложных ситуаций. + Простой + Умный + + + Создайте свой первый сценарий и начните автоматизацию задач на своём устройстве. + + + Сценарий %1$s будет удалён. Продолжить? + Ваша система не отправляет + стандартный в Android запрос на трансляцию экрана. Klick\'r не сможет работать на ней. + + + Тип сценария + + + + Разрешение на трансляцию экрана отклонено пользователем + Разрешение на работу в фоновом режиме отклонено пользователем + + + Создать сценарий + + + Создать новый сценарий + + + + Стандартное название + Снимковых событий нет + + \ No newline at end of file