isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-27 02:20:43 -05:00
Code Issues Packages Projects Releases Wiki Activity
77ec8774a0
mutter/po/ru.po

2790 lines
95 KiB
Plaintext
Raw Normal View History

Added Russian translation
2011-09-11 03:27:00 -04:00
# Russian translation for clutter.
# Copyright (C) 2011 clutter's COPYRIGHT HOLDER
# This file is distributed under the same license as the clutter package.
Updated Russian translation
2012-09-06 14:41:33 -04:00
# Yuri Myasoedov <omerta13@yandex.ru>, 2011, 2012.
Added Russian translation
2011-09-11 03:27:00 -04:00
#
msgid ""
msgstr ""
"Project-Id-Version: clutter master\n"
Updated Russian translation
2014-03-11 08:20:07 -04:00
"Report-Msgid-Bugs-To: http://bugzilla.gnome.org/enter_bug.cgi?"
"product=clutter&keywords=I18N+L10N&component=general\n"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
"POT-Creation-Date: 2012-12-18 02:00+0000\n"
"PO-Revision-Date: 2012-12-18 09:50+0400\n"
"Last-Translator: Aleksej Kabanov <ak099@mail.ru>\n"
Updated Russian translation
2012-09-06 14:41:33 -04:00
"Language-Team: русский <gnome-cyr@gnome.org>\n"
"Language: ru\n"
Added Russian translation
2011-09-11 03:27:00 -04:00
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
Updated Russian translation
2014-03-11 08:20:07 -04:00
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
Updated Russian translation
2012-12-19 02:39:46 -05:00
"X-Generator: Poedit 1.5.4\n"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6144
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "X coordinate"
msgstr "Координата по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6145
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "X coordinate of the actor"
msgstr "Координата актора по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6163
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Y coordinate"
msgstr "Координата по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6164
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Y coordinate of the actor"
msgstr "Координата актора по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6186
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Position"
msgstr "Положение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6187
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The position of the origin of the actor"
msgstr "Исходное положение актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6204 ../clutter/clutter-canvas.c:215
#: ../clutter/clutter-grid-layout.c:1238
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:481
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Width"
msgstr "Ширина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6205
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Width of the actor"
msgstr "Ширина актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6223 ../clutter/clutter-canvas.c:231
#: ../clutter/clutter-grid-layout.c:1245
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:497
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Height"
msgstr "Высота"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6224
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Height of the actor"
msgstr "Высота актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6245
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Size"
msgstr "Размер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6246
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The size of the actor"
msgstr "Размер актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6264
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Fixed X"
msgstr "Фиксировано по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6265
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Forced X position of the actor"
msgstr "Принудительное положение размещения актора по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6282
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Fixed Y"
msgstr "Фиксировано по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6283
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Forced Y position of the actor"
msgstr "Принудительное положение размещения актора по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6298
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Fixed position set"
msgstr "Фиксированное положение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6299
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to use fixed positioning for the actor"
msgstr "Использовать ли фиксированное позиционирование актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6317
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Min Width"
msgstr "Мин. ширина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6318
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Forced minimum width request for the actor"
msgstr "Запрос принудительной минимальной ширины актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6336
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Min Height"
msgstr "Мин. высота"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6337
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Forced minimum height request for the actor"
msgstr "Запрос принудительной минимальной высоты актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6355
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Natural Width"
msgstr "Естественная ширина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6356
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Forced natural width request for the actor"
msgstr "Запрос принудительной естественной ширины актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6374
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Natural Height"
msgstr "Естественная высота"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6375
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Forced natural height request for the actor"
msgstr "Запрос принудительной естественной высоты актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6390
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Minimum width set"
msgstr "Минимальная ширина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6391
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to use the min-width property"
msgstr "Использовать ли свойство min-width"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6405
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Minimum height set"
msgstr "Минимальная высота"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6406
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to use the min-height property"
msgstr "Использовать ли свойство min-height"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6420
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Natural width set"
msgstr "Естественная ширина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6421
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to use the natural-width property"
msgstr "Использовать ли свойство natural-width"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6435
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Natural height set"
msgstr "Естественная высота"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6436
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to use the natural-height property"
msgstr "Использовать ли свойство natural-height"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6452
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Allocation"
msgstr "Размещение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6453
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The actor's allocation"
msgstr "Размещение актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6510
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Request Mode"
msgstr "Режим запроса"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6511
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The actor's request mode"
msgstr "Режим запроса актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6535
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Depth"
msgstr "Глубина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6536
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Position on the Z axis"
msgstr "Положение по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6563
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Z Position"
msgstr "Положение по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6564
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The actor's position on the Z axis"
msgstr "Положение актора по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6581
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Opacity"
msgstr "Непрозрачность"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6582
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Opacity of an actor"
msgstr "Непрозрачность актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6602
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Offscreen redirect"
msgstr "Закадровое перенаправление"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6603
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Flags controlling when to flatten the actor into a single image"
msgstr "Флаги, контролирующие перевод актора в одиночное изображение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6617
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Visible"
msgstr "Видимость"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6618
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the actor is visible or not"
msgstr "Является ли актор видимым"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6632
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Mapped"
msgstr "Отображён"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6633
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the actor will be painted"
msgstr "Будет ли отрисовываться актор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6646
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Realized"
msgstr "Реализован"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6647
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the actor has been realized"
msgstr "Нужно ли реализовывать актор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6662
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Reactive"
msgstr "Реактивный"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6663
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the actor is reactive to events"
msgstr "Реагирует ли актор на события"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6674
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Has Clip"
msgstr "Есть кадр"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6675
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the actor has a clip set"
msgstr "Имеется ли у актора кадр"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6688
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Clip"
msgstr "Кадрирование"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6689
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The clip region for the actor"
msgstr "Область кадирорования для актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6708
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Clip Rectangle"
msgstr "Прямоугольник кадрирования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6709
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The visible region of the actor"
msgstr "Видимая область актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6723 ../clutter/clutter-actor-meta.c:207
#: ../clutter/clutter-binding-pool.c:319 ../clutter/clutter-input-device.c:258
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Name"
msgstr "Имя"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6724
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Name of the actor"
msgstr "Имя актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6745
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Pivot Point"
msgstr "Точка вращения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6746
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The point around which the scaling and rotation occur"
msgstr "Точка, вокруг которой выполняется масштабирование и вращение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6764
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Pivot Point Z"
msgstr "Точка вращения Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6765
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Z component of the pivot point"
msgstr "Компонента Z точки вращения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6783
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Scale X"
msgstr "Масштаб по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6784
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Scale factor on the X axis"
msgstr "Масштабный коэффициент по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6802
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Scale Y"
msgstr "Масштаб по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6803
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Scale factor on the Y axis"
msgstr "Масштабный коэффициент по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6821
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Scale Z"
msgstr "Масштаб по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6822
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Scale factor on the Z axis"
msgstr "Масштабный коэффициент по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6840
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Scale Center X"
msgstr "Центр масштабирования по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6841
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Horizontal scale center"
msgstr "Центр масштабирования по горизонтали"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6859
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Scale Center Y"
msgstr "Центр масштабирования по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6860
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical scale center"
msgstr "Центр масштабирования по вертикали"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6878
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Scale Gravity"
msgstr "Притяжение масштабирования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6879
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The center of scaling"
msgstr "Центр масштабирования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6897
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Rotation Angle X"
msgstr "Угол поворота на оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6898
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The rotation angle on the X axis"
msgstr "Угол поворота на оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6916
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Rotation Angle Y"
msgstr "Угол поворота на оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6917
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The rotation angle on the Y axis"
msgstr "Угол поворота на оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6935
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Rotation Angle Z"
msgstr "Угол поворота на оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6936
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The rotation angle on the Z axis"
msgstr "Угол поворота на оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6954
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Rotation Center X"
msgstr "Центр поворота на оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6955
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The rotation center on the X axis"
msgstr "Центр поворота на оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6972
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Rotation Center Y"
msgstr "Центр поворота на оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6973
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The rotation center on the Y axis"
msgstr "Центр поворота на оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6990
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Rotation Center Z"
msgstr "Центр поворота на оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:6991
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The rotation center on the Z axis"
msgstr "Центр поворота на оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7008
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Rotation Center Z Gravity"
msgstr "Притяжение центра поворота по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7009
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Center point for rotation around the Z axis"
msgstr "Центральная точка поворота вокруг оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7037
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Anchor X"
msgstr "Привязка по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7038
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "X coordinate of the anchor point"
msgstr "Координата точки привязки по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7066
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Anchor Y"
msgstr "Привязка по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7067
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Y coordinate of the anchor point"
msgstr "Координата точки привязки по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7094
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Anchor Gravity"
msgstr "Притяжение привязки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7095
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The anchor point as a ClutterGravity"
msgstr "Точка привязки как ClutterGravity"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7114
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Translation X"
msgstr "Переход по X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7115
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Translation along the X axis"
msgstr "Переход по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7134
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Translation Y"
msgstr "Переход по Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7135
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Translation along the Y axis"
msgstr "Переход по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7154
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Translation Z"
msgstr "Переход по Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7155
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Translation along the Z axis"
msgstr "Переход по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7185
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Transform"
msgstr "Преобразование"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7186
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Transformation matrix"
msgstr "Матрица преобразования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7201
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Transform Set"
msgstr "Установить преобразование"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7202
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether the transform property is set"
msgstr "Установлено ли свойство преобразования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7223
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Child Transform"
msgstr "Дочернее преобразование"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7224
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Children transformation matrix"
msgstr "Матрица дочернего преобразования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7239
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Child Transform Set"
msgstr "Установить дочернее преобразование"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7240
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether the child-transform property is set"
msgstr "Установлено ли свойство дочернего преобразования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7257
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Show on set parent"
msgstr "Показывать на установленном родителе"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7258
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the actor is shown when parented"
msgstr "Показывать ли актор при наличии у него родителя"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7275
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Clip to Allocation"
msgstr "Кадрировать по размещению"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7276
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Sets the clip region to track the actor's allocation"
msgstr "Устанавливает область кадрирования для слежения за размещением актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7289
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Text Direction"
msgstr "Направление текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7290
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Direction of the text"
msgstr "Направление текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7305
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Has Pointer"
msgstr "Указатель"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7306
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the actor contains the pointer of an input device"
msgstr "Содержит ли актор указатель устройства ввода"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7319
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Actions"
msgstr "Действия"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7320
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Adds an action to the actor"
msgstr "Добавляет актору действие"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7333
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Constraints"
msgstr "Ограничители"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7334
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Adds a constraint to the actor"
msgstr "Добавляет актору ограничители"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7347
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Effect"
msgstr "Эффект"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7348
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Add an effect to be applied on the actor"
msgstr "Добавить эффект, применяемый эффект к актору"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7362
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Layout Manager"
msgstr "Менеджер компоновки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7363
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The object controlling the layout of an actor's children"
msgstr "Объект, управляющий размещением потомков актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7377
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "X Expand"
msgstr "Растяжение по X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7378
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether extra horizontal space should be assigned to the actor"
msgstr "Нужна ли дополнительная область по горизонтали для актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7393
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Y Expand"
msgstr "Растяжение по Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7394
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether extra vertical space should be assigned to the actor"
msgstr "Нужна ли дополнительная область по вертикали для актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7410
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "X Alignment"
msgstr "Выравнивание по X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7411
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The alignment of the actor on the X axis within its allocation"
msgstr "Выравнивание актора по оси X вместе с его размещением"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7426
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Y Alignment"
msgstr "Выравнивание по Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7427
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The alignment of the actor on the Y axis within its allocation"
msgstr "Выравнивание актора по оси Y вместе с его размещением"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7446
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Margin Top"
msgstr "Поле сверху"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7447
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Extra space at the top"
msgstr "Дополнительное место сверху"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7468
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Margin Bottom"
msgstr "Поле снизу"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7469
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Extra space at the bottom"
msgstr "Дополнительное место снизу"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7490
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Margin Left"
msgstr "Поле слева"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7491
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Extra space at the left"
msgstr "Дополнительное место слева"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7512
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Margin Right"
msgstr "Поле справа"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7513
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Extra space at the right"
msgstr "Дополнительное место справа"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7529
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Background Color Set"
msgstr "Цвет фона"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7530 ../clutter/deprecated/clutter-box.c:275
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Whether the background color is set"
msgstr "Установлен ли цвет фона"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7546
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Background color"
msgstr "Цвет фона"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7547
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The actor's background color"
msgstr "Цвет фона актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7562
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "First Child"
msgstr "Первый потомок"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7563
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The actor's first child"
msgstr "Первый потомок актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7576
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Last Child"
msgstr "Последний потомок"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7577
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The actor's last child"
msgstr "Последний потомок актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7591
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Content"
msgstr "Содержимое"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7592
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Delegate object for painting the actor's content"
msgstr "Делегировать объект для отрисовки содержимого актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7617
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Content Gravity"
msgstr "Притяжение содержимого"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7618
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Alignment of the actor's content"
msgstr "Выравнивание содержимого актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7638
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Content Box"
msgstr "Контейнер содержимого"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7639
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The bounding box of the actor's content"
msgstr "Контейнер содержимого актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7647
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Minification Filter"
msgstr "Уменьшающий фильтр"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7648
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The filter used when reducing the size of the content"
msgstr "Фильтр, используемый для уменьшения размеров содержимого"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7655
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Magnification Filter"
msgstr "Увеличивающий фильтр"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7656
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The filter used when increasing the size of the content"
msgstr "Фильтр, используемый для увеличения размеров содержимого"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7670
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Content Repeat"
msgstr "Повторение содержимого"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor.c:7671
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The repeat policy for the actor's content"
msgstr "Политика повторения содержимого актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor-meta.c:193 ../clutter/clutter-child-meta.c:142
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Actor"
msgstr "Актор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor-meta.c:194
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The actor attached to the meta"
msgstr "Актор, прикреплённый к метаактору"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor-meta.c:208
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The name of the meta"
msgstr "Имя метаактора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor-meta.c:221 ../clutter/clutter-input-device.c:337
#: ../clutter/deprecated/clutter-shader.c:313
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Enabled"
msgstr "Включён"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-actor-meta.c:222
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the meta is enabled"
msgstr "Включён ли метаактор"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-align-constraint.c:279
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-bind-constraint.c:358 ../clutter/clutter-clone.c:345
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-snap-constraint.c:321
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Source"
msgstr "Источник"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-align-constraint.c:280
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The source of the alignment"
msgstr "Источник выравнивания"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-align-constraint.c:293
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Align Axis"
msgstr "Ось выравнивания"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-align-constraint.c:294
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The axis to align the position to"
msgstr "Выравнивать по оси"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-align-constraint.c:313
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-desaturate-effect.c:270
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Factor"
msgstr "Коэффициент"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-align-constraint.c:314
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The alignment factor, between 0.0 and 1.0"
msgstr "Коэффициент выравнивания, между 0.0 и 1.0"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-backend.c:379
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Unable to initialize the Clutter backend"
msgstr "Не удалось инициализировать драйвер Clutter"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-backend.c:453
Updated Russian translation
2012-03-11 15:36:53 -04:00
#, c-format
msgid "The backend of type '%s' does not support creating multiple stages"
msgstr "Драйвер типа «%s» не поддерживает создание нескольких сцен"
Added Russian translation
2011-09-11 03:27:00 -04:00
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-bind-constraint.c:359
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The source of the binding"
msgstr "Источник привязки"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-bind-constraint.c:372
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Coordinate"
msgstr "Координата"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-bind-constraint.c:373
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The coordinate to bind"
msgstr "Координата привязки"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-bind-constraint.c:387
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-path-constraint.c:226
#: ../clutter/clutter-snap-constraint.c:366
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Offset"
msgstr "Отступ"
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/clutter-bind-constraint.c:388
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The offset in pixels to apply to the binding"
msgstr "Отступ в пикселах для применения привязки"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-binding-pool.c:320
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The unique name of the binding pool"
msgstr "Уникальное имя пула привязки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-bin-layout.c:240 ../clutter/clutter-bin-layout.c:655
#: ../clutter/clutter-box-layout.c:390 ../clutter/clutter-table-layout.c:610
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Horizontal Alignment"
msgstr "Горизонтальное выравнивание"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-bin-layout.c:241
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Horizontal alignment for the actor inside the layout manager"
msgstr "Горизонтальное выравнивание актора внутри менеджера компоновки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-bin-layout.c:249 ../clutter/clutter-bin-layout.c:675
#: ../clutter/clutter-box-layout.c:399 ../clutter/clutter-table-layout.c:625
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical Alignment"
msgstr "Вертикальное выравнивание"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-bin-layout.c:250
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical alignment for the actor inside the layout manager"
msgstr "Вертикальное выравнивание актора внутри менеджера компоновки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-bin-layout.c:656
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Default horizontal alignment for the actors inside the layout manager"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Горизонтальное выравнивание по умолчанию для акторов внутри менеджера "
"компоновки"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-bin-layout.c:676
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Default vertical alignment for the actors inside the layout manager"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Вертикальное выравнивание по умолчанию для акторов внутри менеджера "
"компоновки"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:365
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Expand"
msgstr "Растягивать"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:366
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Allocate extra space for the child"
msgstr "Занимать дополнительное место для дочернего элемента"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:372 ../clutter/clutter-table-layout.c:589
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Horizontal Fill"
msgstr "Горизонтальное заполнение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:373 ../clutter/clutter-table-layout.c:590
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Whether the child should receive priority when the container is allocating "
"spare space on the horizontal axis"
msgstr ""
"Должен ли дочерний элемент получать приоритет, когда контейнер размещается в "
"пустом пространстве по горизонтальной оси"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:381 ../clutter/clutter-table-layout.c:596
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical Fill"
msgstr "Вертикальное заполнение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:382 ../clutter/clutter-table-layout.c:597
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Whether the child should receive priority when the container is allocating "
"spare space on the vertical axis"
msgstr ""
"Должен ли дочерний элемент получать приоритет, когда контейнер размещается в "
"пустом пространстве по вертикальной оси"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:391 ../clutter/clutter-table-layout.c:611
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Horizontal alignment of the actor within the cell"
msgstr "Горизонтальное выравнивание актора вместе с ячейкой"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:400 ../clutter/clutter-table-layout.c:626
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical alignment of the actor within the cell"
msgstr "Вертикальное выравнивание актора вместе с ячейкой"
# Компоновка
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1365
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical"
msgstr "Вертикальная"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1366
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the layout should be vertical, rather than horizontal"
msgstr "Приоритет вертикальной компоновки над горизонтальной"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1383 ../clutter/clutter-flow-layout.c:890
#: ../clutter/clutter-grid-layout.c:1550
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Orientation"
msgstr "Ориентация"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1384 ../clutter/clutter-flow-layout.c:891
#: ../clutter/clutter-grid-layout.c:1551
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The orientation of the layout"
msgstr "Ориентация компоновки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1400 ../clutter/clutter-flow-layout.c:906
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Homogeneous"
msgstr "Однородный"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1401
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Whether the layout should be homogeneous, i.e. all childs get the same size"
msgstr ""
"Должна ли компоновка быть однородной, т. е. все дочерние элементы имеют "
"одинаковые размеры"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1416
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Pack Start"
msgstr "Упаковывать с начала"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1417
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to pack items at the start of the box"
msgstr "Упаковывать ли элементы, начиная с начала контейнера"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1430
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Spacing"
msgstr "Расстояние"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1431
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Spacing between children"
msgstr "Расстояние между дочерними элементами"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1448 ../clutter/clutter-table-layout.c:1675
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Use Animations"
msgstr "Использовать анимацию"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1449 ../clutter/clutter-table-layout.c:1676
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether layout changes should be animated"
msgstr "Анимировать ли изменения в компоновке"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1473 ../clutter/clutter-table-layout.c:1700
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Easing Mode"
msgstr "Режим анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1474 ../clutter/clutter-table-layout.c:1701
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The easing mode of the animations"
msgstr "Режим анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1494 ../clutter/clutter-table-layout.c:1721
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Easing Duration"
msgstr "Продолжительность анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-box-layout.c:1495 ../clutter/clutter-table-layout.c:1722
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The duration of the animations"
msgstr "Продолжительность анимации"
Updated Russian translation
2012-09-17 07:55:50 -04:00
#: ../clutter/clutter-brightness-contrast-effect.c:321
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Brightness"
msgstr "Яркость"
Updated Russian translation
2012-09-17 07:55:50 -04:00
#: ../clutter/clutter-brightness-contrast-effect.c:322
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The brightness change to apply"
msgstr "Изменение яркости"
Updated Russian translation
2012-09-17 07:55:50 -04:00
#: ../clutter/clutter-brightness-contrast-effect.c:341
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Contrast"
msgstr "Контрастность"
Updated Russian translation
2012-09-17 07:55:50 -04:00
#: ../clutter/clutter-brightness-contrast-effect.c:342
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The contrast change to apply"
msgstr "Изменение контрастности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-canvas.c:216
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The width of the canvas"
msgstr "Ширина канвы"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-canvas.c:232
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The height of the canvas"
msgstr "Высота канвы"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-child-meta.c:127
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Container"
msgstr "Контейнер"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-child-meta.c:128
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The container that created this data"
msgstr "Контейнер, создавший эти данные"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-child-meta.c:143
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The actor wrapped by this data"
msgstr "Актор, описанный этими данными"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:559
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Pressed"
msgstr "Актор нажат"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:560
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the clickable should be in pressed state"
msgstr "Должен ли актор, реагирующий на щелчки мыши, быть в нажатом состоянии"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:573
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Held"
msgstr "Удержание"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:574
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the clickable has a grab"
msgstr "Должен ли актор, реагирующий на щелчки мыши, захватывать курсор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:591 ../clutter/clutter-settings.c:599
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Long Press Duration"
msgstr "Время длительного нажатия"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:592
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The minimum duration of a long press to recognize the gesture"
msgstr "Минимальное время длительного нажатия для распознавания жеста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:610
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Long Press Threshold"
msgstr "Порог длительного нажатия"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-click-action.c:611
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The maximum threshold before a long press is cancelled"
msgstr "Максимальный порог перед отменой длительного нажатия"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-clone.c:346
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Specifies the actor to be cloned"
msgstr "Определяет актора для клонирования"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-colorize-effect.c:251
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Tint"
msgstr "Окраска"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-colorize-effect.c:252
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The tint to apply"
msgstr "Применить окраску"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-deform-effect.c:588
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Horizontal Tiles"
msgstr "Горизонтальные элементы"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-deform-effect.c:589
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The number of horizontal tiles"
msgstr "Количество горизонтальных элементов"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-deform-effect.c:604
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical Tiles"
msgstr "Вертикальные элементы"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-deform-effect.c:605
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The number of vertical tiles"
msgstr "Количество вертикальных элементов"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-deform-effect.c:622
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Back Material"
msgstr "Материал заднего плана"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-deform-effect.c:623
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The material to be used when painting the back of the actor"
msgstr "Материал, используемый при отрисовке заднего плана актора"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-desaturate-effect.c:271
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The desaturation factor"
msgstr "Коэффициент разбавления"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-device-manager.c:131
#: ../clutter/clutter-input-device.c:366
#: ../clutter/x11/clutter-keymap-x11.c:316
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Backend"
msgstr "Драйвер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-device-manager.c:132
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The ClutterBackend of the device manager"
msgstr "ClutterBackend диспетчера устройств"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:742
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Horizontal Drag Threshold"
msgstr "Порог горизонтального перетаскивания"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:743
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The horizontal amount of pixels required to start dragging"
msgstr "Количество пикселов по горизонтали для начала перетаскивания"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:770
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Vertical Drag Threshold"
msgstr "Порог вертикального перетаскивания"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:771
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The vertical amount of pixels required to start dragging"
msgstr "Количество пикселов по вертикали для начала перетаскивания"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:792
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Drag Handle"
msgstr "Область захвата"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:793
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The actor that is being dragged"
msgstr "Перетаскиваемый актор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:806
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Drag Axis"
msgstr "Ось перетаскивания"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:807
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Constraints the dragging to an axis"
msgstr "Ограничивает перетаскивание по оси"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:823
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Drag Area"
msgstr "Область перетаскивания"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:824
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Constrains the dragging to a rectangle"
msgstr "Ограничить перетаскивание прямоугольником"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:837
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Drag Area Set"
msgstr "Установить область перетаскивания"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-drag-action.c:838
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether the drag area is set"
msgstr "Установлена ли область перетаскивания"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:907
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether each item should receive the same allocation"
msgstr "Должен ли каждый элемент получать тоже самое размещение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:922 ../clutter/clutter-table-layout.c:1637
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Column Spacing"
msgstr "Расстояние между столбцами"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:923
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The spacing between columns"
msgstr "Расстояние между столбцами"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:939 ../clutter/clutter-table-layout.c:1651
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Row Spacing"
msgstr "Расстояние между строками"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:940
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The spacing between rows"
msgstr "Расстояние между строками"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:954
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Minimum Column Width"
msgstr "Минимальная ширина столбца"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:955
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Minimum width for each column"
msgstr "Минимальная ширина для каждого столбца"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:970
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Maximum Column Width"
msgstr "Максимальная ширина столбца"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:971
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Maximum width for each column"
msgstr "Максимальная ширина для каждого столбца"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:985
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Minimum Row Height"
msgstr "Минимальная высота строки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:986
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Minimum height for each row"
msgstr "Минимальная ширина для каждой строки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:1001
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Maximum Row Height"
msgstr "Максимальная высота строки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-flow-layout.c:1002
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Maximum height for each row"
msgstr "Максимальная ширина для каждой строки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1222
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Left attachment"
msgstr "Вложение слева"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1223
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The column number to attach the left side of the child to"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Номер столбца, к которому нужно прикрепить левую границу дочернего виджета"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1230
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Top attachment"
msgstr "Вложение сверху"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1231
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The row number to attach the top side of a child widget to"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Номер строки, к которой нужно прикрепить верхнюю границу дочернего виджета"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1239
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The number of columns that a child spans"
msgstr "Количество столбцов, занимаемых дочерним виджетом"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1246
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The number of rows that a child spans"
msgstr "Количество строк, занимаемых дочерним виджетом"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1565
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Row spacing"
msgstr "Расстояние между строками"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1566
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The amount of space between two consecutive rows"
msgstr "Свободное место между двумя соседними строками"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1579
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Column spacing"
msgstr "Расстояние между столбцами"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1580
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The amount of space between two consecutive columns"
msgstr "Свободное место между двумя соседними столбцами"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1594
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Row Homogeneous"
msgstr "Однородные строки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1595
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "If TRUE, the rows are all the same height"
msgstr "Если установлено, то строки будут иметь одинаковую высоту"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1608
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Column Homogeneous"
msgstr "Однородные столбцы"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-grid-layout.c:1609
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "If TRUE, the columns are all the same width"
msgstr "Если установлено, то столбцы будут иметь одинаковую ширину"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-image.c:248 ../clutter/clutter-image.c:311
#: ../clutter/clutter-image.c:399
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Unable to load image data"
msgstr "Не удалось загрузить данные изображения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:242
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Id"
msgstr "ID"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:243
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Unique identifier of the device"
msgstr "Уникальный идентификатор устройства"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:259
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The name of the device"
msgstr "Название устройства"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:273
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Device Type"
msgstr "Тип устройства"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:274
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The type of the device"
msgstr "Тип устройства"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:289
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Device Manager"
msgstr "Диспетчер устройств"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:290
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The device manager instance"
msgstr "Экземпляр диспетчера устройств"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:303
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Device Mode"
msgstr "Режим устройства"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:304
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The mode of the device"
msgstr "Режим устройства"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:318
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Has Cursor"
msgstr "Есть курсор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:319
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the device has a cursor"
msgstr "Есть ли у устройства курсор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:338
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the device is enabled"
msgstr "Включено ли устройство"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:351
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Number of Axes"
msgstr "Количество осей"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:352
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The number of axes on the device"
msgstr "Количество осей в устройстве"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-input-device.c:367
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The backend instance"
msgstr "Экземпляр драйвера"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-interval.c:506
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Value Type"
msgstr "Тип значения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-interval.c:507
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The type of the values in the interval"
msgstr "Тип значений в интервале"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-interval.c:522
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Initial Value"
msgstr "Исходное значение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-interval.c:523
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Initial value of the interval"
msgstr "Исходное значение интервала"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-interval.c:537
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Final Value"
msgstr "Конечное значение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-interval.c:538
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Final value of the interval"
msgstr "Конечное значение интервала"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-layout-meta.c:117
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Manager"
msgstr "Менеджер"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-layout-meta.c:118
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The manager that created this data"
msgstr "Менеджер, создавший эти данные"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#. Translators: Leave this UNTRANSLATED if your language is
#. * left-to-right. If your language is right-to-left
#. * (e.g. Hebrew, Arabic), translate it to "default:RTL".
#. *
#. * Do NOT translate it to non-English e.g. "predefinito:LTR"! If
#. * it isn't default:LTR or default:RTL it will not work.
#.
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:772
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "default:LTR"
msgstr "default:LTR"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1646
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Show frames per second"
msgstr "Показывать частоту смены кадров"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1648
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Default frame rate"
msgstr "Частота смены кадров по умолчанию"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1650
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Make all warnings fatal"
msgstr "Сделать все предупреждения фатальными"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1653
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Direction for the text"
msgstr "Направление текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1656
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Disable mipmapping on text"
msgstr "Отключить MIP-текстурирование текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1659
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Use 'fuzzy' picking"
msgstr "Использовать «нечёткий» отбор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1662
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Clutter debugging flags to set"
msgstr "Установить отладочные флаги Clutter"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1664
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Clutter debugging flags to unset"
msgstr "Сбросить отладочные флаги Clutter"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1668
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Clutter profiling flags to set"
msgstr "Установить профилировочные флаги Clutter"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1670
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Clutter profiling flags to unset"
msgstr "Сбросить профилировочные флаги Clutter"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1673
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Enable accessibility"
msgstr "Включить специальные возможности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1865
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Clutter Options"
msgstr "Параметры Clutter"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-main.c:1866
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Show Clutter Options"
msgstr "Показать параметры Clutter"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:448
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Pan Axis"
msgstr "Ось панорамирования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:449
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Constraints the panning to an axis"
msgstr "Привязать панорамирование к оси"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:463
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Interpolate"
msgstr "Интерполировать"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:464
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether interpolated events emission is enabled."
msgstr "Включена ли отправка событий интерполяции."
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:480
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Deceleration"
Updated Russian translation
2012-09-17 07:55:50 -04:00
msgstr "Торможение"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:481
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Rate at which the interpolated panning will decelerate in"
Updated Russian translation
2012-09-17 07:55:50 -04:00
msgstr "Скорость, к которой стремится интерполированное панорамирование"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:498
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Initial acceleration factor"
msgstr "Исходный коэффициент ускорения"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-pan-action.c:499
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Factor applied to the momentum when starting the interpolated phase"
Updated Russian translation
2012-09-17 07:55:50 -04:00
msgstr "Коэффициент, применяемый в момент запуска этапа интерполяции"
Added Russian translation
2011-09-11 03:27:00 -04:00
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-path-constraint.c:212
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-path.c:225
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Path"
msgstr "Траектория"
#: ../clutter/clutter-path-constraint.c:213
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The path used to constrain an actor"
msgstr "Траектория используемая для ограничения актора"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-path-constraint.c:227
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The offset along the path, between -1.0 and 2.0"
msgstr "Смещение вдоль траектории, между -1.0 и 2.0"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-property-transition.c:271
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Property Name"
msgstr "Имя свойства"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-property-transition.c:272
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The name of the property to animate"
msgstr "Имя свойства для анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-script.c:466
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Filename Set"
msgstr "Имя файла"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-script.c:467
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the :filename property is set"
msgstr "Установлено ли свойство :filename"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-script.c:481
#: ../clutter/deprecated/clutter-texture.c:1082
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Filename"
msgstr "Имя файла"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-script.c:482
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The path of the currently parsed file"
msgstr "Путь к текущему разбираемому файлу"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-script.c:499
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Translation Domain"
msgstr "Домен переводов"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-script.c:500
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The translation domain used to localize string"
msgstr "Домен переводов, используемый для локализации строк"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-scroll-actor.c:263
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Scroll Mode"
msgstr "Режим прокрутки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-scroll-actor.c:264
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The scrolling direction"
msgstr "Направление прокрутки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:440
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Double Click Time"
msgstr "Время двойного щелчка"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:441
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The time between clicks necessary to detect a multiple click"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Время между щелчками, необходимое для обнаружения множественного щелчка"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:456
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Double Click Distance"
msgstr "Интервал двойного щелчка"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:457
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The distance between clicks necessary to detect a multiple click"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Интервал между щелчками, необходимый для обнаружения множественного щелчка"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:472
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Drag Threshold"
msgstr "Порог перетаскивания"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:473
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The distance the cursor should travel before starting to drag"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Расстояние, на которое нужно передвинуть курсор, чтобы начать перетаскивание"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:488 ../clutter/clutter-text.c:3369
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font Name"
msgstr "Название шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:489
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"The description of the default font, as one that could be parsed by Pango"
Added Russian translation
2011-09-11 03:27:00 -04:00
msgstr "Описание шрифта по умолчанию, которое может разобрать Pango"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:504
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font Antialias"
msgstr "Сглаживание шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:505
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Whether to use antialiasing (1 to enable, 0 to disable, and -1 to use the "
"default)"
msgstr ""
"Использовать ли сглаживание (1 — использовать; 0 — не использовать; -1 — "
"использовать настройки по умолчанию)"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:521
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font DPI"
msgstr "Разрешение шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:522
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"The resolution of the font, in 1024 * dots/inch, or -1 to use the default"
msgstr ""
"Разрешение шрифта, в 1024 * точек/дюйм, или -1, чтобы использовать "
"разрешение по умолчанию"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:538
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font Hinting"
msgstr "Хинтинг шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:539
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Whether to use hinting (1 to enable, 0 to disable and -1 to use the default)"
msgstr ""
"Использовать ли хинтинг (1 — использовать; 0 — не использовать; -1 — "
"использовать настройки по умолчанию)"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:560
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font Hint Style"
msgstr "Стиль хинтинга шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:561
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The style of hinting (hintnone, hintslight, hintmedium, hintfull)"
msgstr "Стиль хинтинга (hintnone, hintslight, hintmedium, hintfull)"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:582
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font Subpixel Order"
msgstr "Порядок субпиксельной обработки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:583
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The type of subpixel antialiasing (none, rgb, bgr, vrgb, vbgr)"
msgstr "Тип субпиксельного сглаживания (none, rgb, bgr, vrgb, vbgr)"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:600
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The minimum duration for a long press gesture to be recognized"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Минимальная продолжительность, необходимая для распознавания жеста "
"длительного нажатия"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:607
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Fontconfig configuration timestamp"
msgstr "Метка времени настройки шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:608
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Timestamp of the current fontconfig configuration"
msgstr "Метка времени текущей настройки fontconfig"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:625
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Password Hint Time"
msgstr "Время отображения пароля"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-settings.c:626
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "How long to show the last input character in hidden entries"
msgstr "Как долго показывать последний введённый символ в скрытых полях"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-shader-effect.c:486
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Shader Type"
msgstr "Тип шейдера"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-shader-effect.c:487
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The type of shader used"
msgstr "Тип используемого шейдера"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-snap-constraint.c:322
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The source of the constraint"
msgstr "Источник ограничения"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-snap-constraint.c:335
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "From Edge"
msgstr "От края"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-snap-constraint.c:336
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The edge of the actor that should be snapped"
msgstr "Край актора, который должен быть скреплён"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-snap-constraint.c:350
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "To Edge"
msgstr "К краю"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-snap-constraint.c:351
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The edge of the source that should be snapped"
msgstr "Край источника, который должен быть скреплён"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#: ../clutter/clutter-snap-constraint.c:367
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The offset in pixels to apply to the constraint"
msgstr "Смещение в пикселах для применения к ограничению"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1895
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Fullscreen Set"
msgstr "На полный экран"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1896
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the main stage is fullscreen"
msgstr "Должна ли главная сцена занимать весь экран"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1910
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Offscreen"
msgstr "За кадром"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1911
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the main stage should be rendered offscreen"
msgstr "Должна ли главная сцена отрисовываться за кадром"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1923 ../clutter/clutter-text.c:3483
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Cursor Visible"
msgstr "Видимый курсор"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1924
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the mouse pointer is visible on the main stage"
msgstr "Виден ли указатель мыши на главной сцене"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1938
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "User Resizable"
msgstr "Пользователь может менять размер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1939
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the stage is able to be resized via user interaction"
msgstr "Может ли сцена изменять размер в зависимости от действий пользователя"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1954 ../clutter/deprecated/clutter-box.c:260
#: ../clutter/deprecated/clutter-rectangle.c:273
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Color"
msgstr "Цвет"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1955
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The color of the stage"
msgstr "Цвет сцены"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1970
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Perspective"
msgstr "Перспектива"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1971
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Perspective projection parameters"
msgstr "Параметры проекции перспективы"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1986
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Title"
msgstr "Заголовок"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:1987
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Stage Title"
msgstr "Заголовок сцены"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2004
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Use Fog"
msgstr "Использовать туман"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2005
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to enable depth cueing"
msgstr "Включить ли эффект тумана"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2021
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Fog"
msgstr "Туман"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2022
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Settings for the depth cueing"
msgstr "Параметры эффекта тумана"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2038
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Use Alpha"
msgstr "Использовать полупрозрачность"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2039
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether to honour the alpha component of the stage color"
msgstr "Учитывать ли альфа-слой цвета сцены"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2055
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Key Focus"
msgstr "Клавишный фокус"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2056
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The currently key focused actor"
msgstr "Актор, у которого в настоящий момент есть фокус"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2072
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "No Clear Hint"
msgstr "Не очищать"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2073
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the stage should clear its contents"
msgstr "Должно ли сцена очищать своё содержимое"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2086
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Accept Focus"
msgstr "Принимать фокус"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-stage.c:2087
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the stage should accept focus on show"
msgstr "Должна ли сцена принимать фокус"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-table-layout.c:543
msgid "Column Number"
msgstr "Номер столбца"
#: ../clutter/clutter-table-layout.c:544
msgid "The column the widget resides in"
msgstr "Столбец, в котором находится виджет"
#: ../clutter/clutter-table-layout.c:551
msgid "Row Number"
msgstr "Номер строки"
#: ../clutter/clutter-table-layout.c:552
msgid "The row the widget resides in"
msgstr "Строка, в которой находится виджет"
#: ../clutter/clutter-table-layout.c:559
msgid "Column Span"
msgstr "Диапазон столбцов"
#: ../clutter/clutter-table-layout.c:560
msgid "The number of columns the widget should span"
msgstr "Количество столбцов, занимаемых виджетом"
#: ../clutter/clutter-table-layout.c:567
msgid "Row Span"
msgstr "Диапазон строк"
#: ../clutter/clutter-table-layout.c:568
msgid "The number of rows the widget should span"
msgstr "Количество строк, занимаемых виджетом"
#: ../clutter/clutter-table-layout.c:575
msgid "Horizontal Expand"
msgstr "Горизонтальное растяжение"
#: ../clutter/clutter-table-layout.c:576
msgid "Allocate extra space for the child in horizontal axis"
msgstr "Выделить дополнительное место по горизонтали для дочернего элемента "
#: ../clutter/clutter-table-layout.c:582
msgid "Vertical Expand"
msgstr "Вертикальное растяжение"
#: ../clutter/clutter-table-layout.c:583
msgid "Allocate extra space for the child in vertical axis"
msgstr "Выделить дополнительное место по вертикали для дочернего элемента "
#: ../clutter/clutter-table-layout.c:1638
msgid "Spacing between columns"
msgstr "Расстояние между столбцами"
#: ../clutter/clutter-table-layout.c:1652
msgid "Spacing between rows"
msgstr "Расстояние между строками"
#: ../clutter/clutter-text-buffer.c:351 ../clutter/clutter-text.c:3404
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Text"
msgstr "Текст"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text-buffer.c:352
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The contents of the buffer"
msgstr "Содержимое буфера"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text-buffer.c:365
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Text length"
msgstr "Длина текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text-buffer.c:366
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Length of the text currently in the buffer"
msgstr "Длина текста, находящегося в буфере"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text-buffer.c:379
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Maximum length"
msgstr "Максимальная длина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text-buffer.c:380
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Maximum number of characters for this entry. Zero if no maximum"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Максимальное количество символов для этого поля. Ноль, если максимум не "
"указан."
Updated Russian translation
2012-03-11 15:36:53 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3351
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Buffer"
msgstr "Буфер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3352
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The buffer for the text"
msgstr "Буфер для текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3370
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The font to be used by the text"
msgstr "Шрифт, используемый для текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3387
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font Description"
msgstr "Описание шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3388
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The font description to be used"
msgstr "Описание используемого шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3405
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The text to render"
msgstr "Текст для отрисовки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3419
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Font Color"
msgstr "Цвет шрифта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3420
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Color of the font used by the text"
msgstr "Цвет шрифта, используемого для текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3435
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Editable"
msgstr "Редактирование"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3436
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the text is editable"
msgstr "Можно ли изменить текст"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3451
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Selectable"
msgstr "Выделение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3452
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the text is selectable"
msgstr "Можно ли выделять текст"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3466
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Activatable"
msgstr "Активация"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3467
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether pressing return causes the activate signal to be emitted"
msgstr "Высылает ли нажатие return сигнал активации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3484
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the input cursor is visible"
msgstr "Является ли курсор ввода видимым"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3498 ../clutter/clutter-text.c:3499
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Cursor Color"
msgstr "Цвет курсора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3514
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Cursor Color Set"
msgstr "Цвет курсора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3515
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the cursor color has been set"
msgstr "Установлен ли цвет курсора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3530
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Cursor Size"
msgstr "Размер курсора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3531
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The width of the cursor, in pixels"
msgstr "Ширина курсора в пикселах"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3547 ../clutter/clutter-text.c:3565
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Cursor Position"
msgstr "Положение курсора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3548 ../clutter/clutter-text.c:3566
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The cursor position"
msgstr "Положение курсора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3581
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Selection-bound"
msgstr "Граница выделения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3582
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The cursor position of the other end of the selection"
msgstr "Положение курсора другого конца выделения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3597 ../clutter/clutter-text.c:3598
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Selection Color"
msgstr "Цвет выделения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3613
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Selection Color Set"
msgstr "Цвет выделения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3614
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the selection color has been set"
msgstr "Установлен ли цвет выделения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3629
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Attributes"
msgstr "Атрибуты"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3630
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "A list of style attributes to apply to the contents of the actor"
msgstr "Список стилевых атрибутов, применяемых к содержимому актору"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3652
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Use markup"
msgstr "Использовать разметку"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3653
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether or not the text includes Pango markup"
msgstr "Включает ли текст разметку Pango"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3669
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Line wrap"
msgstr "Перенос строк"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3670
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "If set, wrap the lines if the text becomes too wide"
msgstr "Если установлено, то будет включён перенос текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3685
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Line wrap mode"
msgstr "Режим переноса строк"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3686
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Control how line-wrapping is done"
msgstr "Управление переносом строк"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3701
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Ellipsize"
msgstr "Усечь"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3702
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The preferred place to ellipsize the string"
msgstr "Предпочтительное место для усечения строки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3718
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Line Alignment"
msgstr "Выравнивание строк"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3719
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The preferred alignment for the string, for multi-line text"
msgstr "Предпочтительное выравнивание строки, многострочного текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3735
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Justify"
msgstr "По ширине"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3736
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the text should be justified"
msgstr "Должен ли текст растягиваться по ширине"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3751
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Password Character"
msgstr "Парольный символ"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3752
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "If non-zero, use this character to display the actor's contents"
msgstr "Использовать этот символ для отображения содержимого актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3766
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Max Length"
msgstr "Макс. длина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3767
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Maximum length of the text inside the actor"
msgstr "Максимальная длина текста внутри актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3790
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Single Line Mode"
msgstr "Режим одиночной строки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3791
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the text should be a single line"
msgstr "Должен ли текст записывать в одну строку"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3805 ../clutter/clutter-text.c:3806
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Selected Text Color"
msgstr "Цвет выделенного текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3821
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Selected Text Color Set"
msgstr "Цвет выделенного текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-text.c:3822
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the selected text color has been set"
msgstr "Установлен ли цвет для выделенного текста"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:561
#: ../clutter/deprecated/clutter-animation.c:560
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Loop"
msgstr "Зациклить"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:562
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Should the timeline automatically restart"
msgstr "Должна ли временная шкала автоматически перезапускаться"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:576
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Delay"
msgstr "Задержка"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:577
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Delay before start"
msgstr "Задержка перед запуском"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:592
#: ../clutter/deprecated/clutter-animation.c:544
#: ../clutter/deprecated/clutter-animator.c:1804
Updated Russian translation
2012-09-06 14:41:33 -04:00
#: ../clutter/deprecated/clutter-media.c:224
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-state.c:1523
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Duration"
msgstr "Длительность"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:593
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Duration of the timeline in milliseconds"
msgstr "Длина временной шкалы в миллисекундах"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:608
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:528
#: ../clutter/deprecated/clutter-behaviour-rotate.c:337
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Direction"
msgstr "Направление"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:609
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Direction of the timeline"
msgstr "Направление временной шкалы"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:624
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Auto Reverse"
msgstr "Автоматический переворот"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:625
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Whether the direction should be reversed when reaching the end"
msgstr "Менять ли направление на обратное при достижении конца"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:643
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Repeat Count"
msgstr "Количество повторов"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:644
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "How many times the timeline should repeat"
msgstr "Сколько раз должна повторяться временная шкала"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:658
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Progress Mode"
msgstr "Режим выполнения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-timeline.c:659
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "How the timeline should compute the progress"
msgstr "Как временная шкала вычисляет выполнение"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-transition.c:246
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Interval"
msgstr "Интервал"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-transition.c:247
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The interval of values to transition"
msgstr "Интервал значений для перехода"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-transition.c:261
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Animatable"
msgstr "Анимационный"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-transition.c:262
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "The animatable object"
msgstr "Анимационный объект"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-transition.c:283
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Remove on Complete"
msgstr "Убрать после завершения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-transition.c:284
Updated Russian translation
2012-03-21 14:47:04 -04:00
msgid "Detach the transition when completed"
msgstr "Отсоединить переход после завершения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-zoom-action.c:354
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Zoom Axis"
msgstr "Ось масштабирования"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/clutter-zoom-action.c:355
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Constraints the zoom to an axis"
msgstr "Привязать масштабирование к оси"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-alpha.c:355
#: ../clutter/deprecated/clutter-animation.c:575
#: ../clutter/deprecated/clutter-animator.c:1821
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Timeline"
msgstr "Временная шкала"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-alpha.c:356
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Timeline used by the alpha"
msgstr "Временная шкала, используемая альфа-функцией"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-alpha.c:372
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Alpha value"
msgstr "Значение альфа-функции"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-alpha.c:373
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Alpha value as computed by the alpha"
msgstr "Значение, вычисленное альфа-функцией"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-alpha.c:394
#: ../clutter/deprecated/clutter-animation.c:528
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Mode"
msgstr "Режим"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-alpha.c:395
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Progress mode"
msgstr "Режим выполнения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:511
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Object"
msgstr "Объект"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:512
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Object to which the animation applies"
msgstr "Объект, к которому применяется анимация"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:529
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The mode of the animation"
msgstr "Режим анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:545
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Duration of the animation, in milliseconds"
msgstr "Длительность анимации, в миллисекундах"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:561
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether the animation should loop"
msgstr "Зациклить ли анимацию"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:576
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The timeline used by the animation"
msgstr "Временная шкала, используемая для анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:592
#: ../clutter/deprecated/clutter-behaviour.c:241
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Alpha"
msgstr "Альфа-функция"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animation.c:593
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The alpha used by the animation"
msgstr "Альфа-функция, используемая анимацией"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animator.c:1805
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The duration of the animation"
msgstr "Продолжительность анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-animator.c:1822
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The timeline of the animation"
msgstr "Временная шкала анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour.c:242
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Alpha Object to drive the behaviour"
msgstr "Объект альфа-функции для управления поведением"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-depth.c:182
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Start Depth"
msgstr "Начальная глубина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-depth.c:183
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Initial depth to apply"
msgstr "Начальная глубина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-depth.c:198
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "End Depth"
msgstr "Конечная глубина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-depth.c:199
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Final depth to apply"
msgstr "Конечная глубина"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:401
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Start Angle"
msgstr "Начальный угол"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:402
#: ../clutter/deprecated/clutter-behaviour-rotate.c:284
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Initial angle"
msgstr "Начальный угол"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:417
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "End Angle"
msgstr "Конечный угол"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:418
#: ../clutter/deprecated/clutter-behaviour-rotate.c:302
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Final angle"
msgstr "Конечный угол"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:433
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Angle x tilt"
msgstr "Угол наклона вокруг оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:434
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Tilt of the ellipse around x axis"
msgstr "Наклон эллипса вокруг оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:449
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Angle y tilt"
msgstr "Угол наклона вокруг оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:450
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Tilt of the ellipse around y axis"
msgstr "Наклон эллипса вокруг оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:465
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Angle z tilt"
msgstr "Угол наклона вокруг оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:466
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Tilt of the ellipse around z axis"
msgstr "Наклон эллипса вокруг оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:482
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Width of the ellipse"
msgstr "Ширина эллипса"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:498
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Height of ellipse"
msgstr "Высота эллипса"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:513
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Center"
msgstr "Центр"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:514
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Center of ellipse"
msgstr "Центр эллипса"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-ellipse.c:529
#: ../clutter/deprecated/clutter-behaviour-rotate.c:338
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Direction of rotation"
msgstr "Направление вращения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-opacity.c:184
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Opacity Start"
msgstr "Начальная непрозрачность"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-opacity.c:185
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Initial opacity level"
msgstr "Начальный уровень непрозрачности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-opacity.c:202
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Opacity End"
msgstr "Конечная непрозрачность"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-opacity.c:203
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Final opacity level"
msgstr "Конечный уровень непрозрачности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-path.c:226
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The ClutterPath object representing the path to animate along"
msgstr "Объект ClutterPath, представляющий траекторию для анимации"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:283
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Angle Begin"
msgstr "Начальный угол"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:301
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Angle End"
msgstr "Конечный угол"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:319
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Axis"
msgstr "Ось"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:320
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Axis of rotation"
msgstr "Ось вращения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:355
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Center X"
msgstr "Центр по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:356
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "X coordinate of the center of rotation"
msgstr "Координата центра вращения по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:373
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Center Y"
msgstr "Центр по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:374
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Y coordinate of the center of rotation"
msgstr "Координата центра вращения по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:391
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Center Z"
msgstr "Центр по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-rotate.c:392
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Z coordinate of the center of rotation"
msgstr "Координата центра вращения по оси Z"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:226
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "X Start Scale"
msgstr "Начальный масштаб по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:227
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Initial scale on the X axis"
msgstr "Начальный масштаб по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:245
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "X End Scale"
msgstr "Конечный масштаб по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:246
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Final scale on the X axis"
msgstr "Конечный масштаб по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:264
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Y Start Scale"
msgstr "Начальный масштаб по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:265
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Initial scale on the Y axis"
msgstr "Начальный масштаб по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:283
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Y End Scale"
msgstr "Конечный масштаб по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-behaviour-scale.c:284
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Final scale on the Y axis"
msgstr "Конечный масштаб по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-box.c:261
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The background color of the box"
msgstr "Цвет фона ящика"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-box.c:274
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Color Set"
msgstr "Цвет"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-cairo-texture.c:597
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Surface Width"
msgstr "Ширина поверхности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-cairo-texture.c:598
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The width of the Cairo surface"
msgstr "Ширина поверхности Cairo"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-cairo-texture.c:615
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Surface Height"
msgstr "Высота поверхности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-cairo-texture.c:616
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The height of the Cairo surface"
msgstr "Высота поверхности Cairo"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-cairo-texture.c:636
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Auto Resize"
msgstr "Автоматически изменять размер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-cairo-texture.c:637
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Whether the surface should match the allocation"
msgstr "Должна ли поверхность совпадать с размещением"
#: ../clutter/deprecated/clutter-media.c:83
msgid "URI"
msgstr "URI"
#: ../clutter/deprecated/clutter-media.c:84
msgid "URI of a media file"
msgstr "URI медиа-файла"
#: ../clutter/deprecated/clutter-media.c:100
msgid "Playing"
msgstr "Воспроизведение"
#: ../clutter/deprecated/clutter-media.c:101
msgid "Whether the actor is playing"
msgstr "Воспроизводится ли актор"
#: ../clutter/deprecated/clutter-media.c:118
msgid "Progress"
msgstr "Ход воспроизведения"
#: ../clutter/deprecated/clutter-media.c:119
msgid "Current progress of the playback"
msgstr "Текущий ход воспроизведения"
#: ../clutter/deprecated/clutter-media.c:135
msgid "Subtitle URI"
msgstr "URI субтитров"
#: ../clutter/deprecated/clutter-media.c:136
msgid "URI of a subtitle file"
msgstr "URI файла с субтитрами"
#: ../clutter/deprecated/clutter-media.c:154
msgid "Subtitle Font Name"
msgstr "Шрифт для субтитров"
#: ../clutter/deprecated/clutter-media.c:155
msgid "The font used to display subtitles"
msgstr "Шрифт, используемый для субтитров"
#: ../clutter/deprecated/clutter-media.c:172
msgid "Audio Volume"
msgstr "Громкость звука"
#: ../clutter/deprecated/clutter-media.c:173
msgid "The volume of the audio"
msgstr "Громкость звука"
#: ../clutter/deprecated/clutter-media.c:189
msgid "Can Seek"
msgstr "Можно перемещаться"
#: ../clutter/deprecated/clutter-media.c:190
msgid "Whether the current stream is seekable"
msgstr "Можно ли перемещаться по текущему потоку"
#: ../clutter/deprecated/clutter-media.c:207
msgid "Buffer Fill"
msgstr "Заполнение буфера"
#: ../clutter/deprecated/clutter-media.c:208
msgid "The fill level of the buffer"
msgstr "Уровень заполнения буфера"
#: ../clutter/deprecated/clutter-media.c:225
msgid "The duration of the stream, in seconds"
msgstr "Продолжительность потока в секундах"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-rectangle.c:274
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The color of the rectangle"
msgstr "Цвет прямоугольника"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-rectangle.c:287
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Border Color"
msgstr "Цвет рамки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-rectangle.c:288
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The color of the border of the rectangle"
msgstr "Цвет рамки прямоугольника"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-rectangle.c:303
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Border Width"
msgstr "Ширина рамки"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-rectangle.c:304
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The width of the border of the rectangle"
msgstr "Ширина рамки прямоугольника"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-rectangle.c:318
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Has Border"
msgstr "Есть рамка"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-rectangle.c:319
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Whether the rectangle should have a border"
msgstr "Есть ли у прямоугольника рамка"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:261
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Vertex Source"
msgstr "Источник вершины"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:262
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Source of vertex shader"
msgstr "Источник вершинного шейдера"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:278
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Fragment Source"
msgstr "Источник фрагмента"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:279
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Source of fragment shader"
msgstr "Источник фрагментного шейдера"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:296
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Compiled"
msgstr "Скомпилированный"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:297
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Whether the shader is compiled and linked"
msgstr "Скомпилирован и скомпонован ли шейдер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:314
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Whether the shader is enabled"
msgstr "Включён ли шейдер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:525
Updated Russian translation
2012-03-11 15:36:53 -04:00
#, c-format
msgid "%s compilation failed: %s"
msgstr "Сбой при компиляции %s: %s"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:526
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Vertex shader"
msgstr "Вершинный шейдер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-shader.c:527
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Fragment shader"
msgstr "Фрагментный шейдер"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-state.c:1505
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "State"
msgstr "Состояние"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-state.c:1506
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Currently set state, (transition to this state might not be complete)"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Текущее установленное состояние (переход к этому состоянию может быть "
"неплоным)"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-state.c:1524
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Default transition duration"
msgstr "Продолжительность перехода по умолчанию"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:994
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Sync size of actor"
msgstr "Синхронизировать размер актора"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:995
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Auto sync size of actor to underlying pixbuf dimensions"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Автоматически синхронизировать размер актора под расположенный за ним "
"пиксельный буфер"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1002
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Disable Slicing"
msgstr "Отключить расщепление"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1003
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Forces the underlying texture to be singular and not made of smaller space "
"saving individual textures"
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgstr "Запрещает разбиение текстуры на отдельные более мелкие текстуры"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1012
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Tile Waste"
msgstr "Остаток черепицы"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1013
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Maximum waste area of a sliced texture"
msgstr "Максимальная бесполезная область расщеплённой текстуры"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1021
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Horizontal repeat"
msgstr "Повторять по горизонтали"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1022
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Repeat the contents rather than scaling them horizontally"
msgstr "Повторять содержимое вместо масштабирования по горизонтали"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1029
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Vertical repeat"
msgstr "Повторять по вертикали"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1030
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Repeat the contents rather than scaling them vertically"
msgstr "Повторять содержимое вместо масштабирования по вертикали"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1037
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Filter Quality"
msgstr "Качество фильтра"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1038
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Rendering quality used when drawing the texture"
msgstr "Качество отрисовки, используемое для рисования текстур"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1046
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Pixel Format"
msgstr "Пиксельный формат"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1047
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The Cogl pixel format to use"
msgstr "Используемый пиксельный формат Cogl"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1055
#: ../clutter/wayland/clutter-wayland-surface.c:449
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Cogl Texture"
msgstr "Текстура Cogl"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1056
#: ../clutter/wayland/clutter-wayland-surface.c:450
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The underlying Cogl texture handle used to draw this actor"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Дескриптор нижележащей текстуры Cogl, используемой для отрисовки этого актора"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1063
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Cogl Material"
msgstr "Материал Cogl"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1064
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The underlying Cogl material handle used to draw this actor"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Дескриптор нижележащего материала Cogl, используемого для отрисовки этого "
"актора"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1083
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "The path of the file containing the image data"
msgstr "Путь к файлу, содержащему данные изображения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1090
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Keep Aspect Ratio"
msgstr "Сохранять соотношение сторон"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1091
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Keep the aspect ratio of the texture when requesting the preferred width or "
"height"
msgstr ""
"Сохранять соотношение сторон текстуры, при запросе предпочтительной ширины и "
"высоты"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1119
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Load asynchronously"
msgstr "Загружать асинхронно"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1120
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Load files inside a thread to avoid blocking when loading images from disk"
msgstr ""
"Загружать файлы в потоке, чтобы избежать блокирования при загрузке "
"изображений с диска"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1138
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Load data asynchronously"
msgstr "Загружать данные асинхронно"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1139
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgid ""
"Decode image data files inside a thread to reduce blocking when loading "
"images from disk"
msgstr ""
"Декодировать данные файлов в потоке, чтобы сократить блокирование при "
"загрузке изображения с диска"
Updated Russian translation
2012-09-06 14:41:33 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1165
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Pick With Alpha"
msgstr "Выбирать с прозрачностью"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1166
Updated Russian translation
2012-09-06 14:41:33 -04:00
msgid "Shape actor with alpha channel when picking"
msgstr "Выбирать актор вместе с каналом прозрачности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1599
#: ../clutter/deprecated/clutter-texture.c:1994
#: ../clutter/deprecated/clutter-texture.c:2090
#: ../clutter/deprecated/clutter-texture.c:2388
Updated Russian translation
2012-09-06 14:41:33 -04:00
#, c-format
msgid "Failed to load the image data"
msgstr "Сбой при загрузке данных изображения"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1758
Updated Russian translation
2012-09-06 14:41:33 -04:00
#, c-format
msgid "YUV textures are not supported"
msgstr "Текстуры YUV не поддерживаются"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/deprecated/clutter-texture.c:1767
Updated Russian translation
2012-09-06 14:41:33 -04:00
#, c-format
msgid "YUV2 textues are not supported"
msgstr "Текстуры YUV2 не поддерживаются"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/evdev/clutter-input-device-evdev.c:159
msgid "sysfs Path"
msgstr "Путь sysfs"
#: ../clutter/evdev/clutter-input-device-evdev.c:160
msgid "Path of the device in sysfs"
msgstr "Путь к устройству в sysfs"
#: ../clutter/evdev/clutter-input-device-evdev.c:175
msgid "Device Path"
msgstr "Путь к устройству"
#: ../clutter/evdev/clutter-input-device-evdev.c:176
msgid "Path of the device node"
msgstr "Путь к узлу устройства"
#: ../clutter/gdk/clutter-backend-gdk.c:296
Updated Russian translation
2012-03-11 15:36:53 -04:00
#, c-format
msgid "Could not find a suitable CoglWinsys for a GdkDisplay of type %s"
msgstr "Не удалось найти подходящий CoglWinsys для GdkDisplay типа %s"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/wayland/clutter-wayland-surface.c:423
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Surface"
msgstr "Поверхность"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/wayland/clutter-wayland-surface.c:424
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The underlying wayland surface"
msgstr "Подложка wayland"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/wayland/clutter-wayland-surface.c:431
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Surface width"
msgstr "Ширина поверхности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/wayland/clutter-wayland-surface.c:432
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The width of the underlying wayland surface"
msgstr "Ширина подложки wayland"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/wayland/clutter-wayland-surface.c:440
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "Surface height"
msgstr "Высота поверхности"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/wayland/clutter-wayland-surface.c:441
Updated Russian translation
2012-03-11 15:36:53 -04:00
msgid "The height of the underlying wayland surface"
msgstr "Высота подложки wayland"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-backend-x11.c:516
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "X display to use"
msgstr "Использовать дисплей X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-backend-x11.c:522
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "X screen to use"
msgstr "Использовать экран X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-backend-x11.c:527
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Make X calls synchronous"
msgstr "Делать вызовы X синхронно"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-backend-x11.c:534
Updated Russian translation
2012-12-19 02:39:46 -05:00
msgid "Disable XInput support"
msgstr "Отключить поддержку XInput"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-keymap-x11.c:317
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The Clutter backend"
msgstr "Драйвер Clutter"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:539
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Pixmap"
msgstr "Пиксельная карта"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:540
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The X11 Pixmap to be bound"
msgstr "Ограниченная пиксельная карта X11"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:548
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Pixmap width"
msgstr "Ширина пиксельной карты"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:549
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The width of the pixmap bound to this texture"
msgstr "Ширина пиксельной карты, ограниченная этой текстурой"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:557
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Pixmap height"
msgstr "Высота пиксельной карты"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:558
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The height of the pixmap bound to this texture"
msgstr "Высота пиксельной карты, ограниченная этой текстурой"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:566
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Pixmap Depth"
msgstr "Глубина пиксельной карты"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:567
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The depth (in number of bits) of the pixmap bound to this texture"
msgstr "Глубина (количество бит) пиксельной карты, ограниченная этой текстурой"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:575
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Automatic Updates"
msgstr "Автоматические обновления"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:576
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "If the texture should be kept in sync with any pixmap changes."
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Если текстура должна синхронизироваться с любыми изменениями пиксельной "
"карты."
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:584
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Window"
msgstr "Окно"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:585
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "The X11 Window to be bound"
msgstr "Ограниченное окно X11"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:593
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Window Redirect Automatic"
msgstr "Автоматическое перенаправление окон"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:594
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "If composite window redirects are set to Automatic (or Manual if false)"
Updated Russian translation
2014-03-11 08:20:07 -04:00
msgstr ""
"Если перенаправления композитных окон установлены в автоматический режим "
"(или в ручной, если не установлено)"
Added Russian translation
2011-09-11 03:27:00 -04:00
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:604
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Window Mapped"
msgstr "Отображённое (mapped) окно"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:605
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "If window is mapped"
msgstr "Если окно отображено (mapped)"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:614
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Destroyed"
msgstr "Уничтожено"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:615
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "If window has been destroyed"
msgstr "Если окно было разрушено"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:623
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Window X"
msgstr "Окно по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:624
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "X position of window on screen according to X11"
msgstr "Положение окна на экране в соответствии с X11 по оси X"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:632
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Window Y"
msgstr "Окно по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:633
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Y position of window on screen according to X11"
msgstr "Положение окна на экране в соответствии с X11 по оси Y"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:640
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "Window Override Redirect"
msgstr "Переопределять перенаправление окна"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 15:34:20 -05:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:641
Added Russian translation
2011-09-11 03:27:00 -04:00
msgid "If this is an override-redirect window"
msgstr "Если является окном переопределения перенаправления"
Updated Russian translation
2012-03-11 15:36:53 -04:00
#~ msgid "The layout manager used by the box"
#~ msgstr "Менеджер компоновки, используемый ящиком"
Reference in New Issue Copy Permalink