isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-12-26 12:52:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
1227f7c489
mutter/po/tr.po

2164 lines
55 KiB
Plaintext
Raw Normal View History

[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
# Turkish translation for clutter.
# Copyright (C) 2011 clutter's COPYRIGHT HOLDER
# This file is distributed under the same license as the clutter package.
#
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
# Muhammet Kara <muhammet.k@gmail.com>, 2011.
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid ""
msgstr ""
"Project-Id-Version: clutter master\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 20:34:20 +00:00
"Report-Msgid-Bugs-To: http://bugzilla.clutter-project.org/enter_bug.cgi?"
"product=clutter\n"
"POT-Creation-Date: 2011-09-12 13:51+0100\n"
"PO-Revision-Date: 2011-09-11 22:10+0300\n"
"Last-Translator: Muhammet Kara <muhammet.k@gmail.com>\n"
"Language-Team: Turkish <gnome-turk@gnome.org>\n"
Post-release version bump to 1.7.91
2011-09-12 12:59:30 +00:00
"Language: tr\n"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\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 20:34:20 +00:00
"X-Generator: Lokalize 1.2\n"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:3852
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "X coordinate"
msgstr "X koordinatı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3853
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "X coordinate of the actor"
msgstr "Aktörün X koordinatı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3868
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Y coordinate"
msgstr "Y koordinatı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3869
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Y coordinate of the actor"
msgstr "Aktörün Y koordinatı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3884 clutter/clutter-behaviour-ellipse.c:477
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Width"
msgstr "Genişlik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3885
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Width of the actor"
msgstr "Aktörün genişliği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3899 clutter/clutter-behaviour-ellipse.c:493
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Height"
msgstr "Yükseklik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3900
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Height of the actor"
msgstr "Aktörün yüksekliği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3918
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Fixed X"
msgstr "Sabit 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 20:34:20 +00:00
#: clutter/clutter-actor.c:3919
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Forced X position of the actor"
msgstr "Aktörün zorunlu X konumu"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3937
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Fixed Y"
msgstr "Sabit 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 20:34:20 +00:00
#: clutter/clutter-actor.c:3938
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Forced Y position of the actor"
msgstr "Aktörün zorunlu Y konumu"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3954
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Fixed position set"
msgstr "Ayarlanan sabit konum"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3955
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether to use fixed positioning for the actor"
msgstr "Aktör için sabit konumlandırma kullanılıp kullanılmayacağı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3977
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Min Width"
msgstr "En Küçük Genişlik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3978
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Forced minimum width request for the actor"
msgstr "Aktörün zorunlu en küçük genişlik isteği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3997
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Min Height"
msgstr "En Küçük Yükseklik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:3998
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Forced minimum height request for the actor"
msgstr "Aktörün zorunlu en küçük yükseklik isteği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4017
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Natural Width"
msgstr "Doğal Genişlik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4018
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Forced natural width request for the actor"
msgstr "Aktörün zorunlu doğal genişlik isteği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4037
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Natural Height"
msgstr "Doğal Yükseklik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4038
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Forced natural height request for the actor"
msgstr "Aktörün zorunlu doğal yükseklik isteği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4054
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Minimum width set"
msgstr "Ayarlanan en küçük genişlik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4055
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether to use the min-width property"
msgstr "En küçük genişlik özelliğinin kullanımı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4070
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Minimum height set"
msgstr "Ayarlanan en küçük yükseklik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4071
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether to use the min-height property"
msgstr "En küçük yükseklik özelliğinin kullanımı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4086
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Natural width set"
msgstr "Ayarlanan doğal genişlik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4087
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether to use the natural-width property"
msgstr "Doğal genişlik özelliğinin kullanımı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4104
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Natural height set"
msgstr "Ayarlanan doğal yükseklik"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4105
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether to use the natural-height property"
msgstr "Doğal yükseklik özelliğinin kullanımı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4124
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Allocation"
msgstr "Yer Ayırma"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4125
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The actor's allocation"
msgstr "Aktör için yer tahsisi"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4181
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Request Mode"
msgstr "İstek Kipi"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4182
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The actor's request mode"
msgstr "Aktörün istek kipi"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4197
msgid "Depth"
msgstr "Derinlik"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4198
msgid "Position on the Z axis"
msgstr "Z eksenindeki konum"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4212
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Opacity"
msgstr "Matlık"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4213
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Opacity of an actor"
msgstr "Bir aktörün matlığı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4232
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Offscreen redirect"
msgstr "Ekran dışı yönlendirme"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4233
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Flags controlling when to flatten the actor into a single image"
msgstr ""
"Aktörün ne zaman tekil bir görüntüye dönüştürüleceğini (düzleştirileceğini) "
"denetleyen imler"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4251
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Visible"
msgstr "Görünür"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4252
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the actor is visible or not"
msgstr "Aktörün görünürlüğü"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4267
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Mapped"
msgstr "Eşleştirilmiş"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4268
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the actor will be painted"
msgstr "Aktörün boyanması"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4282
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Realized"
msgstr "Gerçeklendi"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4283
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the actor has been realized"
msgstr "Aktörün gerçeklenme durumu"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4299
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Reactive"
msgstr "Duyarlı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4300
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the actor is reactive to events"
msgstr "Aktörün olaylara duyarlılığı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4312
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Has Clip"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4313
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the actor has a clip set"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4328
msgid "Clip"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4329
msgid "The clip region for the actor"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4343 clutter/clutter-actor-meta.c:207
#: clutter/clutter-binding-pool.c:319 clutter/clutter-input-device.c:236
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Name"
msgstr "Ad"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4344
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Name of the actor"
msgstr "Aktörün adı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4358
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Scale X"
msgstr "X Ölçeği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4359
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Scale factor on the X axis"
msgstr "X eksenindeki ölçekleme çarpanı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4374
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Scale Y"
msgstr "Y Ölçeği"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4375
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Scale factor on the Y axis"
msgstr "Y eksenindeki ölçekleme çarpanı"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-actor.c:4390
msgid "Scale Center X"
msgstr "X Ölçeği Merkezi"
#: clutter/clutter-actor.c:4391
msgid "Horizontal scale center"
msgstr "Yatay ölçek merkezi"
#: clutter/clutter-actor.c:4406
msgid "Scale Center Y"
msgstr "Y Ölçeği Merkezi"
#: clutter/clutter-actor.c:4407
msgid "Vertical scale center"
msgstr "Dikey ölçek merkezi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4422
msgid "Scale Gravity"
msgstr "Ölçek Ağırlık Merkezi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4423
msgid "The center of scaling"
msgstr "Ölçekleme merkezi"
#: clutter/clutter-actor.c:4440
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Rotation Angle X"
msgstr "X Dönme Açı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 20:34:20 +00:00
#: clutter/clutter-actor.c:4441
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The rotation angle on the X axis"
msgstr "X ekseni üzerindeki dönme açı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 20:34:20 +00:00
#: clutter/clutter-actor.c:4456
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Rotation Angle Y"
msgstr "Y Dönme Açı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 20:34:20 +00:00
#: clutter/clutter-actor.c:4457
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The rotation angle on the Y axis"
msgstr "Y ekseni üzerindeki dönme açı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 20:34:20 +00:00
#: clutter/clutter-actor.c:4472
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Rotation Angle Z"
msgstr "Z Dönme Açı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 20:34:20 +00:00
#: clutter/clutter-actor.c:4473
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The rotation angle on the Z axis"
msgstr "Z ekseni üzerindeki dönme açı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 20:34:20 +00:00
#: clutter/clutter-actor.c:4488
msgid "Rotation Center X"
msgstr "X Dönme Merkezi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4489
msgid "The rotation center on the X axis"
msgstr "X ekseni üzerindeki dönme merkezi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4505
msgid "Rotation Center Y"
msgstr "Y Dönme Merkezi"
#: clutter/clutter-actor.c:4506
msgid "The rotation center on the Y axis"
msgstr "Y ekseni üzerindeki dönme merkezi"
#: clutter/clutter-actor.c:4522
msgid "Rotation Center Z"
msgstr "Z Dönme Merkezi"
#: clutter/clutter-actor.c:4523
msgid "The rotation center on the Z axis"
msgstr "Z ekseni üzerindeki dönme merkezi"
#: clutter/clutter-actor.c:4539
msgid "Rotation Center Z Gravity"
msgstr "Z Dönme Merkezi Yerçekimi"
#: clutter/clutter-actor.c:4540
msgid "Center point for rotation around the Z axis"
msgstr ""
#: clutter/clutter-actor.c:4558
msgid "Anchor X"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4559
msgid "X coordinate of the anchor point"
msgstr ""
#: clutter/clutter-actor.c:4575
msgid "Anchor Y"
msgstr ""
#: clutter/clutter-actor.c:4576
msgid "Y coordinate of the anchor point"
msgstr ""
#: clutter/clutter-actor.c:4591
msgid "Anchor Gravity"
msgstr ""
#: clutter/clutter-actor.c:4592
msgid "The anchor point as a ClutterGravity"
msgstr ""
#: clutter/clutter-actor.c:4611
msgid "Show on set parent"
msgstr ""
#: clutter/clutter-actor.c:4612
msgid "Whether the actor is shown when parented"
msgstr ""
#: clutter/clutter-actor.c:4632
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Clip to Allocation"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4633
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4643
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Text Direction"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Metin Yönü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4644
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Direction of the text"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Metnin yönü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4662
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Has Pointer"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "İşaretçisi Var"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4663
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the actor contains the pointer of an input device"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Aktörün, bir giriş aygıtının işaretçisini içerip içermemesi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4680
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Actions"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Eylemler"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4681
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Adds an action to the actor"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Aktöre bir eylem ekler"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4695
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Constraints"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Kısıtlar"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor.c:4696
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Adds a constraint to the actor"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Aktöre bir kısıt ekler"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor-meta.c:193 clutter/clutter-child-meta.c:142
msgid "Actor"
msgstr "Aktör"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor-meta.c:194
msgid "The actor attached to the meta"
msgstr "Meta'ya ekli aktör"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor-meta.c:208
msgid "The name of the meta"
msgstr "Meta'nın adı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor-meta.c:221 clutter/clutter-input-device.c:315
#: clutter/clutter-shader.c:307
msgid "Enabled"
msgstr "Etkinleştirildi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-actor-meta.c:222
msgid "Whether the meta is enabled"
msgstr "Meta'nın etkin olup olmaması"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-align-constraint.c:270
#: clutter/clutter-bind-constraint.c:349 clutter/clutter-clone.c:340
#: clutter/clutter-snap-constraint.c:321
msgid "Source"
msgstr "Kaynak"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-align-constraint.c:271
msgid "The source of the alignment"
msgstr "Hizalama kaynağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-align-constraint.c:284
msgid "Align Axis"
msgstr "Hizalama Ekseni"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-align-constraint.c:285
msgid "The axis to align the position to"
msgstr "Konumun hizalanacağı eksen"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-align-constraint.c:304
#: clutter/clutter-desaturate-effect.c:304
msgid "Factor"
msgstr "Çarpan"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-align-constraint.c:305
msgid "The alignment factor, between 0.0 and 1.0"
msgstr "Hizalama çarpanı, 0.0 ile 1.0 arasında"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-alpha.c:345 clutter/clutter-animation.c:538
#: clutter/clutter-animator.c:1802
msgid "Timeline"
msgstr "Zaman Çizgisi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-alpha.c:346
msgid "Timeline used by the alpha"
msgstr "Alfa tarafından kullanılan zaman çizgisi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-alpha.c:361
msgid "Alpha value"
msgstr "Alfa değeri"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-alpha.c:362
msgid "Alpha value as computed by the alpha"
msgstr "Alfa tarafından hesaplandığı haliyle alfa değeri"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-alpha.c:382 clutter/clutter-animation.c:494
msgid "Mode"
msgstr "Kip"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-alpha.c:383
msgid "Progress mode"
msgstr "İlerleme kipi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-animation.c:478
msgid "Object"
msgstr "Nesne"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-animation.c:479
msgid "Object to which the animation applies"
msgstr "Canlandırmanın uygulanacağı nesne"
#: clutter/clutter-animation.c:495
msgid "The mode of the animation"
msgstr "Canlandırma kipi"
#: clutter/clutter-animation.c:509 clutter/clutter-animator.c:1786
#: clutter/clutter-media.c:194 clutter/clutter-state.c:1486
#: clutter/clutter-timeline.c:294
msgid "Duration"
msgstr "Süre"
#: clutter/clutter-animation.c:510
msgid "Duration of the animation, in milliseconds"
msgstr "Milisaniye cinsinden canlandırma süresi"
#: clutter/clutter-animation.c:524 clutter/clutter-timeline.c:263
msgid "Loop"
msgstr "Döngü"
#: clutter/clutter-animation.c:525
msgid "Whether the animation should loop"
msgstr "Canlandırmanın tekrarlanıp tekrarlanmayacağı"
#: clutter/clutter-animation.c:539
msgid "The timeline used by the animation"
msgstr "Canlandırma tarafından kullanılan zaman çizgisi"
#: clutter/clutter-animation.c:552 clutter/clutter-behaviour.c:304
msgid "Alpha"
msgstr "Alfa"
#: clutter/clutter-animation.c:553
msgid "The alpha used by the animation"
msgstr "Canlandırma tarafından kullanılan alfa"
#: clutter/clutter-animator.c:1787
msgid "The duration of the animation"
msgstr "Canlandırma süresi"
#: clutter/clutter-animator.c:1803
msgid "The timeline of the animation"
msgstr "Canlandırma zaman çizgisi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour.c:305
msgid "Alpha Object to drive the behaviour"
msgstr "Davranışı kontrol eden Alfa Nesnesi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-depth.c:178
msgid "Start Depth"
msgstr "Başlangıç Derinliği"
#: clutter/clutter-behaviour-depth.c:179
msgid "Initial depth to apply"
msgstr "Uygulanacak ilk derinlik"
#: clutter/clutter-behaviour-depth.c:194
msgid "End Depth"
msgstr "Bitiş Derinliği"
#: clutter/clutter-behaviour-depth.c:195
msgid "Final depth to apply"
msgstr "Uygulanacak son derinlik"
#: clutter/clutter-behaviour-ellipse.c:397
msgid "Start Angle"
msgstr "Başlangıç Açısı"
#: clutter/clutter-behaviour-ellipse.c:398
#: clutter/clutter-behaviour-rotate.c:280
msgid "Initial angle"
msgstr "İlk açı"
#: clutter/clutter-behaviour-ellipse.c:413
msgid "End Angle"
msgstr "Bitiş Açısı"
#: clutter/clutter-behaviour-ellipse.c:414
#: clutter/clutter-behaviour-rotate.c:298
msgid "Final angle"
msgstr "Son açı"
#: clutter/clutter-behaviour-ellipse.c:429
msgid "Angle x tilt"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:430
msgid "Tilt of the ellipse around x axis"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:445
msgid "Angle y tilt"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:446
msgid "Tilt of the ellipse around y axis"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:461
msgid "Angle z tilt"
Updated Turkish translation
2014-12-09 20:37:12 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:462
msgid "Tilt of the ellipse around z axis"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:478
msgid "Width of the ellipse"
msgstr "Elipsin genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:494
msgid "Height of ellipse"
msgstr "Elips yüksekliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:509
msgid "Center"
msgstr "Merkez"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:510
msgid "Center of ellipse"
msgstr "Elips merkezi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:524
#: clutter/clutter-behaviour-rotate.c:333 clutter/clutter-timeline.c:310
msgid "Direction"
msgstr "Yön"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-ellipse.c:525
#: clutter/clutter-behaviour-rotate.c:334
msgid "Direction of rotation"
msgstr "Dönme yönü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-opacity.c:181
msgid "Opacity Start"
msgstr "Matlık Başlangıcı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-opacity.c:182
msgid "Initial opacity level"
msgstr "İlk matlık düzeyi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-opacity.c:199
msgid "Opacity End"
msgstr "Matlık Bitişi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-opacity.c:200
msgid "Final opacity level"
msgstr "Son matlık düzeyi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-path.c:222 clutter/clutter-path-constraint.c:212
msgid "Path"
msgstr "Yol"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-path.c:223
msgid "The ClutterPath object representing the path to animate along"
msgstr "Üzerinde canlandırma yapılacak yolu ifade eden ClutterPath nesnesi"
#: clutter/clutter-behaviour-rotate.c:279
msgid "Angle Begin"
msgstr "Açı Başlangıcı"
#: clutter/clutter-behaviour-rotate.c:297
msgid "Angle End"
msgstr "Açı Sonu"
#: clutter/clutter-behaviour-rotate.c:315
msgid "Axis"
msgstr "Eksen"
#: clutter/clutter-behaviour-rotate.c:316
msgid "Axis of rotation"
msgstr "Dönme ekseni"
#: clutter/clutter-behaviour-rotate.c:351
msgid "Center X"
msgstr "Merkez X"
#: clutter/clutter-behaviour-rotate.c:352
msgid "X coordinate of the center of rotation"
msgstr "Dönme merkezinin X koordinatı"
#: clutter/clutter-behaviour-rotate.c:369
msgid "Center Y"
msgstr "Merkez Y"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-behaviour-rotate.c:370
msgid "Y coordinate of the center of rotation"
msgstr "Dönme merkezinin Y koordinatı"
#: clutter/clutter-behaviour-rotate.c:387
msgid "Center Z"
msgstr "Merkez Z"
#: clutter/clutter-behaviour-rotate.c:388
msgid "Z coordinate of the center of rotation"
msgstr "Dönme merkezinin Z koordinatı"
#: clutter/clutter-behaviour-scale.c:222
msgid "X Start Scale"
msgstr "X Başlangıç Ölçeği"
#: clutter/clutter-behaviour-scale.c:223
msgid "Initial scale on the X axis"
msgstr "X eksenindeki ilk ölçek"
#: clutter/clutter-behaviour-scale.c:241
msgid "X End Scale"
msgstr "X Bitiş Ölçeği"
#: clutter/clutter-behaviour-scale.c:242
msgid "Final scale on the X axis"
msgstr "X eksenindeki son ölçek"
#: clutter/clutter-behaviour-scale.c:260
msgid "Y Start Scale"
msgstr "Y Başlangıç Ölçeği"
#: clutter/clutter-behaviour-scale.c:261
msgid "Initial scale on the Y axis"
msgstr "Y eksenindeki ilk ölçek"
#: clutter/clutter-behaviour-scale.c:279
msgid "Y End Scale"
msgstr "Y Bitiş Ölçeği"
#: clutter/clutter-behaviour-scale.c:280
msgid "Final scale on the Y axis"
msgstr "Y eksenindeki son ölçek"
#: clutter/clutter-bind-constraint.c:350
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The source of the binding"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Bağlama kaynağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-bind-constraint.c:363
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Coordinate"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Koordinat"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-bind-constraint.c:364
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The coordinate to bind"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Bağlanacak koordinat"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-bind-constraint.c:378 clutter/clutter-path-constraint.c:226
#: clutter/clutter-snap-constraint.c:366
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Offset"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Denkleştirme"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-bind-constraint.c:379
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The offset in pixels to apply to the binding"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Bağlamaya uygulanacak piksel cinsinden denkleştirme"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-binding-pool.c:320
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The unique name of the binding pool"
[l10n]Updated Turkish translation
2011-09-11 06:00:52 +00:00
msgstr "Bağlama havuzunun özgün adı."
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-bin-layout.c:261 clutter/clutter-bin-layout.c:585
#: clutter/clutter-box-layout.c:395 clutter/clutter-table-layout.c:652
msgid "Horizontal Alignment"
msgstr "Yatay Hizalama"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-bin-layout.c:262
msgid "Horizontal alignment for the actor inside the layout manager"
msgstr "Yerleşim yöneticisi içindeki aktörün yatay hizalaması"
#: clutter/clutter-bin-layout.c:270 clutter/clutter-bin-layout.c:602
#: clutter/clutter-box-layout.c:404 clutter/clutter-table-layout.c:667
msgid "Vertical Alignment"
msgstr "Dikey Hizalama"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-bin-layout.c:271
msgid "Vertical alignment for the actor inside the layout manager"
msgstr "Yerleşim yöneticisi içindeki aktörün dikey hizalaması"
#: clutter/clutter-bin-layout.c:586
msgid "Default horizontal alignment for the actors inside the layout manager"
msgstr "Yerleşim yöneticisi içindeki aktörlerin öntanımlı yatay hizalaması"
#: clutter/clutter-bin-layout.c:603
msgid "Default vertical alignment for the actors inside the layout manager"
msgstr "Yerleşim yöneticisi içindeki aktörlerin öntanımlı dikey hizalaması"
#: clutter/clutter-box.c:544
msgid "Layout Manager"
msgstr "Yerleşim Yöneticisi"
#: clutter/clutter-box.c:545
msgid "The layout manager used by the box"
msgstr "Kutu tarafından kullanılan yerleşim yöneticisi"
#: clutter/clutter-box.c:564 clutter/clutter-rectangle.c:267
#: clutter/clutter-stage.c:1765
msgid "Color"
msgstr "Renk"
#: clutter/clutter-box.c:565
msgid "The background color of the box"
msgstr "Kutunun arkaplan rengi"
#: clutter/clutter-box.c:579
msgid "Color Set"
msgstr "Renk Ayarı"
#: clutter/clutter-box.c:580
msgid "Whether the background color is set"
msgstr "Arkaplan renginin atanmış olması"
#: clutter/clutter-box-layout.c:370
msgid "Expand"
msgstr "Genişlet"
#: clutter/clutter-box-layout.c:371
msgid "Allocate extra space for the child"
msgstr "Çocuk için fazladan yer ayır"
#: clutter/clutter-box-layout.c:377 clutter/clutter-table-layout.c:631
msgid "Horizontal Fill"
msgstr "Yatay Doldur"
#: clutter/clutter-box-layout.c:378 clutter/clutter-table-layout.c:632
msgid ""
"Whether the child should receive priority when the container is allocating "
"spare space on the horizontal axis"
msgstr ""
#: clutter/clutter-box-layout.c:386 clutter/clutter-table-layout.c:638
msgid "Vertical Fill"
msgstr "Dikey Doldur"
#: clutter/clutter-box-layout.c:387 clutter/clutter-table-layout.c:639
msgid ""
"Whether the child should receive priority when the container is allocating "
"spare space on the vertical axis"
msgstr ""
#: clutter/clutter-box-layout.c:396 clutter/clutter-table-layout.c:653
msgid "Horizontal alignment of the actor within the cell"
msgstr "Aktörün hücre içindeki yatay hizalaması"
#: clutter/clutter-box-layout.c:405 clutter/clutter-table-layout.c:668
msgid "Vertical alignment of the actor within the cell"
msgstr "Aktörün hücre içindeki dikey hizalaması"
#: clutter/clutter-box-layout.c:1305
msgid "Vertical"
msgstr "Dikey"
#: clutter/clutter-box-layout.c:1306
msgid "Whether the layout should be vertical, rather than horizontal"
msgstr "Yerleşimin yatay değil de dikey olup olmaması"
#: clutter/clutter-box-layout.c:1321 clutter/clutter-flow-layout.c:901
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Homogeneous"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Homojen"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-box-layout.c:1322
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid ""
"Whether the layout should be homogeneous, i.e. all childs get the same size"
msgstr ""
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
"Yerleşimin homojen olup olmayacağı; bu durumda tüm çocuklar aynı boyutu alır"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-box-layout.c:1337
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Pack Start"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-box-layout.c:1338
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-box-layout.c:1351
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Spacing"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aralık"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-box-layout.c:1352
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Spacing between children"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Çocuklar arasındaki boşluk"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-box-layout.c:1366 clutter/clutter-table-layout.c:1742
msgid "Use Animations"
msgstr "Canlandırmaları Kullan"
#: clutter/clutter-box-layout.c:1367 clutter/clutter-table-layout.c:1743
msgid "Whether layout changes should be animated"
msgstr "Yerleşim değişikliklerinin canlandırılması"
#: clutter/clutter-box-layout.c:1388 clutter/clutter-table-layout.c:1764
msgid "Easing Mode"
msgstr "Hafifletme Kipi"
#: clutter/clutter-box-layout.c:1389 clutter/clutter-table-layout.c:1765
msgid "The easing mode of the animations"
msgstr "Canlandırmaları hafifletme kipi"
#: clutter/clutter-box-layout.c:1406 clutter/clutter-table-layout.c:1782
msgid "Easing Duration"
msgstr "Hafifletme Süresi"
#: clutter/clutter-box-layout.c:1407 clutter/clutter-table-layout.c:1783
msgid "The duration of the animations"
msgstr "Canlandırmaların süresi"
#: clutter/clutter-cairo-texture.c:582
msgid "Surface Width"
msgstr "Yüzey Genişliği"
#: clutter/clutter-cairo-texture.c:583
msgid "The width of the Cairo surface"
msgstr "Cairo yüzey genişliği"
#: clutter/clutter-cairo-texture.c:597
msgid "Surface Height"
msgstr "Yüzey Yüksekliği"
#: clutter/clutter-cairo-texture.c:598
msgid "The height of the Cairo surface"
msgstr "Cairo yüzey yüksekliği"
#: clutter/clutter-cairo-texture.c:615
msgid "Auto Resize"
msgstr "Otomatik Yeniden Boyutlandır"
#: clutter/clutter-cairo-texture.c:616
msgid "Whether the surface should match the allocation"
msgstr "Yüzeyin yer ayrımına uyumu"
#: clutter/clutter-child-meta.c:127
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Container"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Kap"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-child-meta.c:128
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The container that created this data"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Bu veriyi oluşturan kap"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-child-meta.c:143
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The actor wrapped by this data"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Bu veri tarafından sarılan aktör"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:542
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Pressed"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Basıldı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:543
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the clickable should be in pressed state"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Tıklanabilirin basılmış durumda olup olmayacağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:556
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Held"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Basılı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:557
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the clickable has a grab"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Tıklanabilirin basılı halde beklemesi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:574 clutter/clutter-settings.c:573
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Long Press Duration"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Uzun Basma Süresi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:575
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The minimum duration of a long press to recognize the gesture"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Hareketin algılanacağı en küçük uzun basma süresi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:593
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Long Press Threshold"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Uzun Basma Eşiği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-click-action.c:594
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The maximum threshold before a long press is cancelled"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Uzun basma iptal edilmeden önceki en büyük eşik"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-clone.c:341
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Specifies the actor to be cloned"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Birebir kopyalanacak aktörü belirtir"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-colorize-effect.c:307
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Tint"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-colorize-effect.c:308
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The tint to apply"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-deform-effect.c:527
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Horizontal Tiles"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Yatay Döşemeler"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-deform-effect.c:528
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The number of horizontal tiles"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Yatay döşeme sayısı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-deform-effect.c:543
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Vertical Tiles"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Dikey Döşemeler"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-deform-effect.c:544
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The number of vertical tiles"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Dikey döşeme sayısı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-deform-effect.c:561
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Back Material"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-deform-effect.c:562
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The material to be used when painting the back 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 20:34:20 +00:00
#: clutter/clutter-desaturate-effect.c:305
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The desaturation factor"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Desatürasyon çarpanı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-device-manager.c:131 clutter/clutter-input-device.c:344
#: clutter/x11/clutter-keymap-x11.c:316
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Backend"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Arka Uç"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-device-manager.c:132
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The ClutterBackend of the device manager"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıt yöneticisindeki ClutterBackend"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:596
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Horizontal Drag Threshold"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Yatay Sürükleme Eşiği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:597
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The horizontal amount of pixels required to start dragging"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sürüklemeyi başlatmak için gereken yatay piksel miktarı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:624
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Vertical Drag Threshold"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Dikey Sürükleme Eşiği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:625
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The vertical amount of pixels required to start dragging"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sürüklemeyi başlatmak için gereken dikey piksel miktarı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:646
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Drag Handle"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sürükleme Kulpu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:647
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The actor that is being dragged"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sürüklenmekte olan aktör"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:660
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Drag Axis"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sürükleme Ekseni"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-drag-action.c:661
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Constraints the dragging to an axis"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sürüklemeyi bir eksenle kısıtlar"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:885
msgid "Orientation"
msgstr "Yönelim"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:886
msgid "The orientation of the layout"
msgstr "Yerleşim yönelimi"
Updated Turkish translation
2014-12-09 20:37:12 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:902
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether each item should receive the same allocation"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Her ögeye aynı miktarda yer ayrılması"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:917 clutter/clutter-table-layout.c:1713
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Column Spacing"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sütun Aralığı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:918
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The spacing between columns"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Sütunlar arasındaki boşluk"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:934 clutter/clutter-table-layout.c:1727
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Row Spacing"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Satır Aralığı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:935
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The spacing between rows"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Satırlar arasındaki boşluk"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:949
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Minimum Column Width"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "En Küçük Sütun Genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:950
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Minimum width for each column"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Her sütunun en küçük genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:965
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Maximum Column Width"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "En Büyük Sütun Genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:966
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Maximum width for each column"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Her sütunun en büyük genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:980
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Minimum Row Height"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "En Küçük Satır Yüksekliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:981
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Minimum height for each row"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Her satırın en küçük yüksekliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:996
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Maximum Row Height"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "En Büyük Satır Yüksekliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-flow-layout.c:997
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Maximum height for each row"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Her satırın en büyük yüksekliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:220
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Id"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Id"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:221
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Unique identifier of the device"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıtın özgün tanımlayıcısı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:237
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The name of the device"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıtın adı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:251
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Device Type"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıt Türü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:252
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The type of the device"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıtın türü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:267
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Device Manager"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıt Yöneticisi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:268
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The device manager instance"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıt yöneticisi örneği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:281
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Device Mode"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıt Kipi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:282
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The mode of the device"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıtın kipi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:296
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Has Cursor"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "İmleci Var"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:297
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the device has a cursor"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıtın bir imlecinin olup olmaması"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:316
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the device is enabled"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aygıtın etkin olup olmaması"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:329
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Number of Axes"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:330
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The number of axes on the device"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-input-device.c:345
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The backend instance"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Arka uç örneği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-interval.c:397
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Value Type"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Değer Türü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-interval.c:398
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The type of the values in the interval"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aralıktaki değerlerin türü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-layout-meta.c:117
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Manager"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Yönetici"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-layout-meta.c:118
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The manager that created this data"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Bu veriyi oluşturan yönetici"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:490
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "default:LTR"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "default:LTR"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1321
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Show frames per second"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Saniye başına düşen çerçeveleri göster"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1323
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Default frame rate"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Öntanımlı çerçeve hızı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1325
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Make all warnings fatal"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Tüm uyarıları ölümcül yap"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1328
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Direction for the text"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Metin yönü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1331
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Disable mipmapping on text"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Metinde haritalamayı devre dışı bırak"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1334
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Use 'fuzzy' picking"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1337
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Clutter debugging flags to set"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Ayarlanacak Clutter hata ayıklama bayrakları"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1339
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Clutter debugging flags to unset"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Kaldırılacak Clutter hata ayıklama bayrakları"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1343
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Clutter profiling flags to set"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Ayarlanacak Clutter profilleme bayrakları"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1345
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Clutter profiling flags to unset"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Kaldırılacak Clutter profilleme bayrakları"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1348
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Enable accessibility"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Erişilebilirliği etkinleştir"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1530
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Clutter Options"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Clutter Seçenekleri"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-main.c:1531
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Show Clutter Options"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Clutter Seçeneklerini Göster"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:77
msgid "URI"
msgstr "URI"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:78
msgid "URI of a media file"
msgstr "Bir ortam dosyasının URI'si"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:91
msgid "Playing"
msgstr "Oynuyor"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:92
msgid "Whether the actor is playing"
msgstr "Aktörün oynamakta olup olmadığı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:106
msgid "Progress"
msgstr "İlerleme"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:107
msgid "Current progress of the playback"
msgstr "Oynatmanın şu anki ilerleme durumu"
#: clutter/clutter-media.c:120
msgid "Subtitle URI"
msgstr "Altyazı URI"
#: clutter/clutter-media.c:121
msgid "URI of a subtitle file"
msgstr "Bir altyazı dosyasının URI adresi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:136
msgid "Subtitle Font Name"
msgstr "Altyazı Yazıtipi Adı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:137
msgid "The font used to display subtitles"
msgstr "Altyazıları göstermek için kullanılan yazıtipi"
#: clutter/clutter-media.c:151
msgid "Audio Volume"
msgstr "Ses Düzeyi"
#: clutter/clutter-media.c:152
msgid "The volume of the audio"
msgstr "Ses düzeyi"
#: clutter/clutter-media.c:165
msgid "Can Seek"
Updated Turkish translation
2014-12-09 20:37:12 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:166
msgid "Whether the current stream is seekable"
msgstr ""
#: clutter/clutter-media.c:180
msgid "Buffer Fill"
msgstr "Tampon Doldurma"
#: clutter/clutter-media.c:181
msgid "The fill level of the buffer"
msgstr "Tamponun doldurma düzeyi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-media.c:195
msgid "The duration of the stream, in seconds"
msgstr "Akışın saniye cinsinden süresi"
#: clutter/clutter-path-constraint.c:213
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The path used to constrain an actor"
[l10n]Updated Turkish translation
2011-09-11 08:28:56 +00:00
msgstr "Aktörü kısıtlamak için kullanılan yol"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-path-constraint.c:227
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The offset along the path, between -1.0 and 2.0"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-rectangle.c:268
msgid "The color of the rectangle"
msgstr "Dikdörtgenin rengi"
#: clutter/clutter-rectangle.c:281
msgid "Border Color"
msgstr "Kenarlık Rengi"
#: clutter/clutter-rectangle.c:282
msgid "The color of the border of the rectangle"
msgstr "Dikdörtgen kenarlığının rengi"
#: clutter/clutter-rectangle.c:297
msgid "Border Width"
msgstr "Kenarlık Genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-rectangle.c:298
msgid "The width of the border of the rectangle"
msgstr "Dikdörtgen kenarlığının genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-rectangle.c:312
msgid "Has Border"
msgstr "Kenarlığı Var"
#: clutter/clutter-rectangle.c:313
msgid "Whether the rectangle should have a border"
msgstr "Dikdörtgenin kenarlığının olup olmayacağı"
#: clutter/clutter-script.c:434
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Filename Set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Dosya Adı Ayarlandı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-script.c:435
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the :filename property is set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr ":filename özelliğinin ayarlanmış olup olmaması"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-script.c:449 clutter/clutter-texture.c:1081
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Filename"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Dosya adı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-script.c:450
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The path of the currently parsed file"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Şu anda ayrıştırılan dosyanın yolu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:414
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Double Click Time"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Çift Tıklama Zamanı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:415
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The time between clicks necessary to detect a multiple click"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Çoklu tıklamanın algılanması için gereken iki tık arası zaman"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:430
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Double Click Distance"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Çift Tıklama Mesafesi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:431
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The distance between clicks necessary to detect a multiple click"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Çoklu tıklamanın algılanması için gereken iki tık arası mesafe"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:446
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Drag Threshold"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Sürükleme Eşiği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:447
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The distance the cursor should travel before starting to drag"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Sürüklemeye başlamadan önce imlecin katetmesi gereken mesafe"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:462 clutter/clutter-text.c:2939
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font Name"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Yazıtipi Adı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:463
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid ""
"The description of the default font, as one that could be parsed by Pango"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Öntanımlı yazıtipinin Pango tarafından ayrıştırılabilecek tanımı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:478
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font Antialias"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Yazıtipi Yumuşatma"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:479
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid ""
"Whether to use antialiasing (1 to enable, 0 to disable, and -1 to use the "
"default)"
msgstr ""
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
"Yumuşatma kullanılıp kullanılmayacağı (etkinleştirmek için 1, devre dışı "
Post-release version bump to 1.7.91
2011-09-12 12:59:30 +00:00
"bırakmak için 0, öntanımlı ayarı kullanmak için -1)"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:495
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font DPI"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Yazıtipi DPI"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:496
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid ""
"The resolution of the font, in 1024 * dots/inch, or -1 to use the default"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-settings.c:512
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font Hinting"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:513
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid ""
"Whether to use hinting (1 to enable, 0 to disable and -1 to use the default)"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-settings.c:534
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font Hint Style"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:535
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The style of hinting (hintnone, hintslight, hintmedium, hintfull)"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-settings.c:556
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font Subpixel Order"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:557
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The type of subpixel antialiasing (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 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:574
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The minimum duration for a long press gesture to be recognized"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Hareketin algılanacağı en küçük uzun basma süresi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:581
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Fontconfig configuration timestamp"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Fontconfig yapılandırması zaman damgası"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-settings.c:582
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Timestamp of the current fontconfig configuration"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Mevcut fontconfig yapılandırmasının zaman damgası"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-shader.c:255
msgid "Vertex Source"
msgstr "Tepe Kaynağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-shader.c:256
msgid "Source of vertex shader"
msgstr "Tepe gölgelendiricisi kaynağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-shader.c:272
msgid "Fragment Source"
msgstr "Parça Kaynağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-shader.c:273
msgid "Source of fragment shader"
msgstr "Parça gölgelendiricisi kaynağı"
#: clutter/clutter-shader.c:290
msgid "Compiled"
msgstr "Derlendi"
#: clutter/clutter-shader.c:291
msgid "Whether the shader is compiled and linked"
msgstr "Gölgelendiricinin derlenmiş ve bağlanmış olup olmadığı"
#: clutter/clutter-shader.c:308
msgid "Whether the shader is enabled"
msgstr "Gölgelendiricinin etkin olup olmadığı"
#: clutter/clutter-shader.c:519
#, c-format
msgid "%s compilation failed: %s"
msgstr "%s derlemesi başarısız: %s"
#: clutter/clutter-shader.c:520
msgid "Vertex shader"
msgstr "Tepe gölgelendiricisi"
#: clutter/clutter-shader.c:521
msgid "Fragment shader"
msgstr "Parça gölgelendiricisi"
#: clutter/clutter-shader-effect.c:415
msgid "Shader Type"
msgstr "Gölgelendirici Türü"
#: clutter/clutter-shader-effect.c:416
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The type of shader used"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kullanılan gölgelendirici türü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-snap-constraint.c:322
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The source of the constraint"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kısıt kaynağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-snap-constraint.c:335
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "From Edge"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kenardan"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-snap-constraint.c:336
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The edge of the actor that should be snapped"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-snap-constraint.c:350
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "To Edge"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kenara"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-snap-constraint.c:351
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The edge of the source that should be snapped"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-snap-constraint.c:367
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The offset in pixels to apply to the constraint"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1707
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Fullscreen Set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Tam Ekran Ayarlandı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1708
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the main stage is fullscreen"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Ana sahnenin tam ekran olup olmayışı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1724
msgid "Offscreen"
msgstr "Ekran Dışı"
#: clutter/clutter-stage.c:1725
msgid "Whether the main stage should be rendered offscreen"
msgstr ""
#: clutter/clutter-stage.c:1737 clutter/clutter-text.c:3052
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Cursor Visible"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Görünür İmleç"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1738
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the mouse pointer is visible on the main stage"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Ana sahnede fare imlecinin görünürlüğü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1752
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "User Resizable"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kullanıcı Yeniden Boyutlandırabilir"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1753
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the stage is able to be resized via user interaction"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Sahnenin kullanıcı etkileşimi ile yeniden boyutlandırılabilirliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1766
msgid "The color of the stage"
msgstr "Sahne rengi"
#: clutter/clutter-stage.c:1780
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Perspective"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Bakış Açısı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1781
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Perspective projection parameters"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1796
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Title"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Başlık"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1797
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Stage Title"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Sahne Başlığı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1812
msgid "Use Fog"
msgstr "Sis Kullan"
#: clutter/clutter-stage.c:1813
msgid "Whether to enable depth cueing"
msgstr ""
#: clutter/clutter-stage.c:1827
msgid "Fog"
msgstr "Sis"
#: clutter/clutter-stage.c:1828
msgid "Settings for the depth cueing"
msgstr ""
#: clutter/clutter-stage.c:1844
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Use Alpha"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Alfa Kullan"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1845
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1861
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Key Focus"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1862
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1878
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "No Clear Hint"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1879
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1892
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Accept Focus"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-stage.c:1893
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-state.c:1472
msgid "State"
msgstr "Durum"
#: clutter/clutter-state.c:1473
msgid "Currently set state, (transition to this state might not be complete)"
msgstr ""
#: clutter/clutter-state.c:1487
msgid "Default transition duration"
msgstr "Öntanımlı geçiş süresi"
#: clutter/clutter-table-layout.c:585
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Column Number"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Sütun Numarası"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-table-layout.c:586
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The column the widget resides in"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-table-layout.c:593
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Row Number"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Satır Numarası"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-table-layout.c:594
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The row the widget resides in"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-table-layout.c:601
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Column Span"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-table-layout.c:602
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The number of columns the widget should span"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-table-layout.c:609
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Row Span"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-table-layout.c:610
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The number of rows the widget should span"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/clutter-table-layout.c:617
msgid "Horizontal Expand"
msgstr ""
#: clutter/clutter-table-layout.c:618
msgid "Allocate extra space for the child in horizontal axis"
msgstr ""
#: clutter/clutter-table-layout.c:624
msgid "Vertical Expand"
msgstr ""
#: clutter/clutter-table-layout.c:625
msgid "Allocate extra space for the child in vertical axis"
msgstr ""
#: clutter/clutter-table-layout.c:1714
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Spacing between columns"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Sütunlar arasındaki boşluk"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-table-layout.c:1728
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Spacing between rows"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Satırlar arasındaki boşluk"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:2940
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The font to be used by the text"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Metinde kullanılacak yazıtipi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:2957
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font Description"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Yazıtipi Tanımı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:2958
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The font description to be used"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kullanılacak yazıtipi tanımı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:2974
msgid "Text"
msgstr "Metin"
#: clutter/clutter-text.c:2975
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The text to render"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:2989
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Font Color"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Yazıtipi Rengi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:2990
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Color of the font used by the text"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Metinde kullanılan yazıtipinin rengi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3004
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Editable"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Düzenlenebilir"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3005
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the text is editable"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Metnin düzenlenebilirliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3020
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Selectable"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Seçilebilir"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3021
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the text is selectable"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Metnin seçilebilirliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3035
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Activatable"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Aktifleştirilebilir"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3036
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether pressing return causes the activate signal to be emitted"
msgstr ""
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
"Enter tuşuna basılmasının aktifleştirme sinyalinin gönderilmesine sebep olup "
"olmayacağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3053
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the input cursor is visible"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Giriş imlecinin görünürlüğü"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3067 clutter/clutter-text.c:3068
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Cursor Color"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İmleç Rengi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3082
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Cursor Color Set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İmleç Rengi Ayarlandı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3083
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the cursor color has been set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İmleç renginin ayarlanmış olup olmadığı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3098
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Cursor Size"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İmleç Boyutu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3099
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The width of the cursor, in pixels"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İmlecin piksel cinsinden genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3113
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Cursor Position"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İmleç Konumu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3114
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The cursor position"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İmlecin konumu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3129
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Selection-bound"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3130
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3145 clutter/clutter-text.c:3146
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Selection Color"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Seçim Rengi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3160
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Selection Color Set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Seçim Rengi Ayarlandı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3161
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the selection color has been set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Seçim renginin ayarlanmış olup olmadığı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3176
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Attributes"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Öznitelikler"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3177
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "A list of style attributes to apply to the contents of the actor"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3199
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Use markup"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3200
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether or not the text includes Pango 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 20:34:20 +00:00
#: clutter/clutter-text.c:3216
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Line wrap"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Satır kaydırma"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3217
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "If set, wrap the lines if the text becomes too wide"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Eğer atanmışsa, satırlar çok geniş olduğunda bölünür"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3232
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Line wrap mode"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Satır kaydırma kipi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3233
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Control how line-wrapping is done"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Satır kaydırmanın nasıl yapıldığını denetle"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3248
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Ellipsize"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3249
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3265
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Line Alignment"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Satır Hizalama"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3266
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The preferred alignment for the string, for multi-line text"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Çok satırlı metinde dizge için tercih edilen hizalama"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3282
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Justify"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "İki yana yasla"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3283
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the text should be justified"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Metnin iki yana yaslanıp yaslanmayacağı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3298
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Password Character"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Parola Karakteri"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3299
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3313
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Max Length"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "En Büyük Uzunluk"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3314
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Maximum length of the text inside the actor"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Aktör içindeki metnin en büyük uzunluğu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3337
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Single Line Mode"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Tek Satır Kipi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3338
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3352 clutter/clutter-text.c:3353
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Selected Text Color"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Seçili Metin Rengi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3367
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Selected Text Color Set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Seçili Metin Rengi Ayarlandı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-text.c:3368
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Whether the selected text color has been set"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Seçili metin renginin ayarlanıp ayarlanmadığı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:995
msgid "Sync size of actor"
msgstr "Aktörün boyutunu eşle"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:996
msgid "Auto sync size of actor to underlying pixbuf dimensions"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1003
msgid "Disable Slicing"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1004
msgid ""
"Forces the underlying texture to be singular and not made of smaller space "
"saving individual textures"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1013
msgid "Tile Waste"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1014
msgid "Maximum waste area of a sliced texture"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1022
msgid "Horizontal repeat"
msgstr "Yatay tekrarla"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1023
msgid "Repeat the contents rather than scaling them horizontally"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1030
msgid "Vertical repeat"
msgstr "Dikey tekrarla"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1031
msgid "Repeat the contents rather than scaling them vertically"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1038
msgid "Filter Quality"
msgstr "Filtre Kalitesi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1039
msgid "Rendering quality used when drawing the texture"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1047
msgid "Pixel Format"
msgstr "Piksel Biçimi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1048
msgid "The Cogl pixel format to use"
msgstr "Kullanılacak Cogl piksel biçimi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1056
msgid "Cogl Texture"
msgstr "Cogl Kaplaması"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1057
msgid "The underlying Cogl texture handle used to draw this actor"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1064
msgid "Cogl Material"
msgstr "Cogl Malzemesi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1065
msgid "The underlying Cogl material handle used to draw this actor"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1082
msgid "The path of the file containing the image data"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1089
msgid "Keep Aspect Ratio"
msgstr "En-Boy Oranını Koru"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1090
msgid ""
"Keep the aspect ratio of the texture when requesting the preferred width or "
"height"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1116
msgid "Load asynchronously"
msgstr "Eşzamansız yükle"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1117
msgid ""
"Load files inside a thread to avoid blocking when loading images from disk"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1133
msgid "Load data asynchronously"
msgstr "Veriyi eşzamansız yükle"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1134
msgid ""
"Decode image data files inside a thread to reduce blocking when loading "
"images from disk"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1158
msgid "Pick With Alpha"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1159
msgid "Shape actor with alpha channel when picking"
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1557 clutter/clutter-texture.c:1967
#: clutter/clutter-texture.c:2062 clutter/clutter-texture.c:2343
msgid "Failed to load the image data"
msgstr "Resim verisinin yüklenmesi başarısız oldu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1703
msgid "YUV textures are not supported"
msgstr "YUV kaplamaları desteklenmiyor"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-texture.c:1712
msgid "YUV2 textues are not supported"
msgstr "YUV2 kaplamaları desteklenmiyor"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-timeline.c:264
msgid "Should the timeline automatically restart"
msgstr "Zaman çizgisi otomatik olarak yeniden başlamalı mı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-timeline.c:278
msgid "Delay"
msgstr "Gecikme"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/clutter-timeline.c:279
msgid "Delay before start"
msgstr "Başlamadan önceki gecikme"
#: clutter/clutter-timeline.c:295
msgid "Duration of the timeline in milliseconds"
msgstr "Milisaniye cinsinden zaman çizgisi süresi"
#: clutter/clutter-timeline.c:311
msgid "Direction of the timeline"
msgstr "Zaman çizgisi yönü"
#: clutter/clutter-timeline.c:326
msgid "Auto Reverse"
msgstr "Otomatik Tersine Çevir"
#: clutter/clutter-timeline.c:327
msgid "Whether the direction should be reversed when reaching the end"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/evdev/clutter-input-device-evdev.c:147
msgid "sysfs Path"
msgstr "sysfs Yolu"
#: clutter/evdev/clutter-input-device-evdev.c:148
msgid "Path of the device in sysfs"
msgstr "sysfs'deki aygıt yolu"
#: clutter/evdev/clutter-input-device-evdev.c:163
msgid "Device Path"
msgstr "Aygıt Yolu"
#: clutter/evdev/clutter-input-device-evdev.c:164
msgid "Path of the device node"
msgstr "Aygıt düğümü yolu"
#: clutter/x11/clutter-backend-x11.c:483
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "X display to use"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kullanılacak X göstericisi"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-backend-x11.c:489
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "X screen to use"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Kullanılacak X ekranı"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-backend-x11.c:494
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Make X calls synchronous"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "X çağrılarını eşazamanlı yap"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-backend-x11.c:501
msgid "Enable XInput support"
msgstr "XInput desteğini etkinleştir"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-keymap-x11.c:317
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The Clutter backend"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Clutter arka ucu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:545
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Pixmap"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Pixmap"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:546
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The X11 Pixmap to be 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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:554
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Pixmap width"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Pixmap genişliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:555
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:563
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Pixmap height"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Pixmap yüksekliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:564
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:572
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Pixmap Depth"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Pixmap Derinliği"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:573
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:581
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Automatic Updates"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Otomatik Güncellemeler"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:582
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "If the texture should be kept in sync with any pixmap changes."
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:590
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Window"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Pencere"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:591
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "The X11 Window to be bound"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:599
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Window Redirect Automatic"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:600
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "If composite window redirects are set to Automatic (or Manual if false)"
msgstr ""
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:610
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Window 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 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:611
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "If window is 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 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:620
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Destroyed"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:621
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:629
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Window X"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Pencere X"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:630
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "X position of window on screen according to X11"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "X11'e göre ekranda pencere X konumu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:638
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Window Y"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "Pencere Y"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:639
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Y position of window on screen according to X11"
[l10n]Updated Turkish translation
2011-09-11 19:13:31 +00:00
msgstr "X11'e göre ekranda pencere Y konumu"
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:646
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "Window Override Redirect"
WARNING: Massive revert commit Revert all the work that happened on the master branch. Sadly, this is the only way to merge the current development branch back into master. It is now abundantly clear that I merged the 1.99 branch far too soon, and that Clutter 2.0 won't happen any time soon, if at all. Since having the development happen on a separate branch throws a lot of people into confusion, let's undo the clutter-1.99 → master merge, and move back the development of Clutter to the master branch. In order to do so, we need to do some surgery to the Git repository. First, we do a massive revert in a single commit of all that happened since the switch to 1.99 and the API version bump done with the 89a2862b057423c3c1fc666e6fa776ccacf377dd commit. The history is too long to be reverted commit by commit without being extremely messy.
2015-01-03 20:34:20 +00:00
msgstr ""
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00: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 20:34:20 +00:00
#: clutter/x11/clutter-x11-texture-pixmap.c:647
[l10n]Added Turkish translation
2011-09-10 18:05:30 +00:00
msgid "If this is an override-redirect window"
msgstr ""
Reference in New Issue Copy Permalink