brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
05a7419e11
mutter/po/clutter-1.0.pot

2100 lines
45 KiB
Plaintext
Raw Normal View History

po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
# SOME DESCRIPTIVE TITLE.
Updated Galician translations
2011-05-12 07:18:02 -04:00
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
"Project-Id-Version: PACKAGE VERSION\n"
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
"Report-Msgid-Bugs-To: http://bugzilla.clutter-project.org/enter_bug.cgi?"
"product=clutter\n"
Updated Galician translations
2011-05-12 07:18:02 -04:00
"POT-Creation-Date: 2011-05-12 13:17+0200\n"
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3617
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X coordinate"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3618
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X coordinate of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3633
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Y coordinate"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3634
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Y coordinate of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3649 ../clutter/clutter-behaviour-ellipse.c:474
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3650
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Width of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3664 ../clutter/clutter-behaviour-ellipse.c:490
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3665
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Height of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3683
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Fixed X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3684
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Forced X position of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3702
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Fixed Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3703
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Forced Y position of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3719
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Fixed position set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3720
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to use fixed positioning for the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3742
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Min Width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3743
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Forced minimum width request for the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3762
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Min Height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3763
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Forced minimum height request for the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3782
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Natural Width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3783
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Forced natural width request for the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3802
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Natural Height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3803
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Forced natural height request for the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3819
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Minimum width set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3820
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to use the min-width property"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3835
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Minimum height set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3836
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to use the min-height property"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3851
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Natural width set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3852
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to use the natural-width property"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3869
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Natural height set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3870
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to use the natural-height property"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3889
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Allocation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3890
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The actor's allocation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3946
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Request Mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3947
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The actor's request mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3962
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Depth"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3963
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Position on the Z axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3977
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Opacity"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3978
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Opacity of an actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3993
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Visible"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:3994
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the actor is visible or not"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4009
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Mapped"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4010
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the actor will be painted"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4024
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Realized"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4025
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the actor has been realized"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4041
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Reactive"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4042
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the actor is reactive to events"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4054
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Has Clip"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4055
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the actor has a clip set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4070
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Clip"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4071
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The clip region for the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4085 ../clutter/clutter-actor-meta.c:205
#: ../clutter/clutter-binding-pool.c:319 ../clutter/clutter-input-device.c:236
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Name"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4086
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Name of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4100
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Scale X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4101
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Scale factor on the X axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4116
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Scale Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4117
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Scale factor on the Y axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4132
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Scale Center X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4133
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal scale center"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4148
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Scale Center Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4149
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical scale center"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4164
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Scale Gravity"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4165
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The center of scaling"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4182
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rotation Angle X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4183
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The rotation angle on the X axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4198
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rotation Angle Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4199
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The rotation angle on the Y axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4214
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rotation Angle Z"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4215
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The rotation angle on the Z axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4230
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rotation Center X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4231
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The rotation center on the X axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4247
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rotation Center Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4248
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The rotation center on the Y axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4264
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rotation Center Z"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4265
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The rotation center on the Z axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4281
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rotation Center Z Gravity"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4282
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Center point for rotation around the Z axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4300
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Anchor X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4301
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X coordinate of the anchor point"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4317
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Anchor Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4318
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Y coordinate of the anchor point"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4333
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Anchor Gravity"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4334
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The anchor point as a ClutterGravity"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4353
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Show on set parent"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4354
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the actor is shown when parented"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4374
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Clip to Allocation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4375
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Sets the clip region to track the actor's allocation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4385
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Text Direction"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4386
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Direction of the text"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4404
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Has Pointer"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4405
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the actor contains the pointer of an input device"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4422
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Actions"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4423
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Adds an action to the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4437
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Constraints"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor.c:4438
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Adds a constraint to the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor-meta.c:191 ../clutter/clutter-child-meta.c:142
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor-meta.c:192
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The actor attached to the meta"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor-meta.c:206
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The name of the meta"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor-meta.c:219 ../clutter/clutter-input-device.c:315
#: ../clutter/clutter-shader.c:295
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Enabled"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-actor-meta.c:220
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the meta is enabled"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-align-constraint.c:252
#: ../clutter/clutter-bind-constraint.c:316 ../clutter/clutter-clone.c:326
#: ../clutter/clutter-snap-constraint.c:321
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Source"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-align-constraint.c:253
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The source of the alignment"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-align-constraint.c:266
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Align Axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-align-constraint.c:267
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The axis to align the position to"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-align-constraint.c:286
#: ../clutter/clutter-desaturate-effect.c:304
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Factor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-align-constraint.c:287
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The alignment factor, between 0.0 and 1.0"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-alpha.c:339 ../clutter/clutter-animation.c:528
#: ../clutter/clutter-animator.c:1802
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Timeline"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-alpha.c:340
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Timeline used by the alpha"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-alpha.c:355
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Alpha value"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-alpha.c:356
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Alpha value as computed by the alpha"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-alpha.c:376 ../clutter/clutter-animation.c:484
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-alpha.c:377
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Progress mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:468
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Object"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:469
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Object to which the animation applies"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:485
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The mode of the animation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:499 ../clutter/clutter-animator.c:1786
#: ../clutter/clutter-media.c:194 ../clutter/clutter-state.c:1422
#: ../clutter/clutter-timeline.c:294
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Duration"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:500
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Duration of the animation, in milliseconds"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:514 ../clutter/clutter-timeline.c:263
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Loop"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:515
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the animation should loop"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:529
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The timeline used by the animation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:542 ../clutter/clutter-behaviour.c:298
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Alpha"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animation.c:543
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The alpha used by the animation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animator.c:1787
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The duration of the animation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-animator.c:1803
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The timeline of the animation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour.c:299
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Alpha Object to drive the behaviour"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-depth.c:174
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Start Depth"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-depth.c:175
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Initial depth to apply"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-depth.c:190
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "End Depth"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-depth.c:191
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Final depth to apply"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:394
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Start Angle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:395
#: ../clutter/clutter-behaviour-rotate.c:276
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Initial angle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:410
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "End Angle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:411
#: ../clutter/clutter-behaviour-rotate.c:294
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Final angle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:426
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Angle x tilt"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:427
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Tilt of the ellipse around x axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:442
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Angle y tilt"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:443
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Tilt of the ellipse around y axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:458
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Angle z tilt"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:459
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Tilt of the ellipse around z axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:475
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Width of the ellipse"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:491
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Height of ellipse"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:506
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Center"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:507
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Center of ellipse"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:521
#: ../clutter/clutter-behaviour-rotate.c:329 ../clutter/clutter-timeline.c:310
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Direction"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-ellipse.c:522
#: ../clutter/clutter-behaviour-rotate.c:330
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Direction of rotation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-opacity.c:177
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Opacity Start"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-opacity.c:178
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Initial opacity level"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-opacity.c:195
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Opacity End"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-opacity.c:196
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Final opacity level"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-path.c:219
#: ../clutter/clutter-path-constraint.c:212
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Path"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-path.c:220
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The ClutterPath object representing the path to animate along"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:275
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Angle Begin"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:293
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Angle End"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:311
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:312
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Axis of rotation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:347
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Center X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:348
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X coordinate of the center of rotation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:365
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Center Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:366
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Y coordinate of the center of rotation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:383
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Center Z"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-rotate.c:384
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Z coordinate of the center of rotation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:218
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X Start Scale"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:219
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Initial scale on the X axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:237
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X End Scale"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:238
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Final scale on the X axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:256
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Y Start Scale"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:257
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Initial scale on the Y axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:275
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Y End Scale"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-behaviour-scale.c:276
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Final scale on the Y axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bind-constraint.c:317
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The source of the binding"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bind-constraint.c:330
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Coordinate"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bind-constraint.c:331
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The coordinate to bind"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bind-constraint.c:345
#: ../clutter/clutter-path-constraint.c:226
#: ../clutter/clutter-snap-constraint.c:366
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Offset"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bind-constraint.c:346
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The offset in pixels to apply to the binding"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-binding-pool.c:320
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The unique name of the binding pool"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bin-layout.c:261 ../clutter/clutter-bin-layout.c:580
#: ../clutter/clutter-box-layout.c:395 ../clutter/clutter-table-layout.c:652
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal Alignment"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bin-layout.c:262
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal alignment for the actor inside the layout manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bin-layout.c:270 ../clutter/clutter-bin-layout.c:597
#: ../clutter/clutter-box-layout.c:404 ../clutter/clutter-table-layout.c:667
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical Alignment"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bin-layout.c:271
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical alignment for the actor inside the layout manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bin-layout.c:581
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Default horizontal alignment for the actors inside the layout manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-bin-layout.c:598
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Default vertical alignment for the actors inside the layout manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box.c:537
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Layout Manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box.c:538
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The layout manager used by the box"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box.c:557 ../clutter/clutter-rectangle.c:258
#: ../clutter/clutter-stage.c:1710
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Color"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box.c:558
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The background color of the box"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box.c:572
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Color Set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box.c:573
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the background color is set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:370
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Expand"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:371
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Allocate extra space for the child"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:377 ../clutter/clutter-table-layout.c:631
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal Fill"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:378 ../clutter/clutter-table-layout.c:632
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Whether the child should receive priority when the container is allocating "
"spare space on the horizontal axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:386 ../clutter/clutter-table-layout.c:638
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical Fill"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:387 ../clutter/clutter-table-layout.c:639
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Whether the child should receive priority when the container is allocating "
"spare space on the vertical axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:396 ../clutter/clutter-table-layout.c:653
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal alignment of the actor within the cell"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:405 ../clutter/clutter-table-layout.c:668
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical alignment of the actor within the cell"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1077
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1078
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the layout should be vertical, rather than horizontal"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1093 ../clutter/clutter-flow-layout.c:898
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Homogeneous"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1094
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Whether the layout should be homogeneous, i.e. all childs get the same size"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1109
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pack Start"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1110
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to pack items at the start of the box"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1123
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Spacing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1124
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Spacing between children"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1138 ../clutter/clutter-table-layout.c:1740
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Use Animations"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1139 ../clutter/clutter-table-layout.c:1741
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether layout changes should be animated"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1160 ../clutter/clutter-table-layout.c:1762
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Easing Mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1161 ../clutter/clutter-table-layout.c:1763
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The easing mode of the animations"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1178 ../clutter/clutter-table-layout.c:1780
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Easing Duration"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-box-layout.c:1179 ../clutter/clutter-table-layout.c:1781
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The duration of the animations"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-cairo-texture.c:404
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Surface Width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-cairo-texture.c:405
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The width of the Cairo surface"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-cairo-texture.c:419
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Surface Height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-cairo-texture.c:420
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The height of the Cairo surface"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-child-meta.c:127
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Container"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-child-meta.c:128
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The container that created this data"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-child-meta.c:143
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The actor wrapped by this data"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-click-action.c:302
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pressed"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-click-action.c:303
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the clickable should be in pressed state"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-click-action.c:316
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Held"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-click-action.c:317
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the clickable has a grab"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-clone.c:327
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Specifies the actor to be cloned"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-colorize-effect.c:307
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Tint"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-colorize-effect.c:308
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The tint to apply"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-deform-effect.c:527
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal Tiles"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-deform-effect.c:528
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The number of horizontal tiles"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-deform-effect.c:543
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical Tiles"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-deform-effect.c:544
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The number of vertical tiles"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-deform-effect.c:561
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Back Material"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-deform-effect.c:562
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The material to be used when painting the back of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-desaturate-effect.c:305
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The desaturation factor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-device-manager.c:131
#: ../clutter/clutter-input-device.c:344
#: ../clutter/x11/clutter-keymap-x11.c:316
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Backend"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-device-manager.c:132
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The ClutterBackend of the device manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:547
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal Drag Threshold"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:548
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The horizontal amount of pixels required to start dragging"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:575
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical Drag Threshold"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:576
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The vertical amount of pixels required to start dragging"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:597
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Drag Handle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:598
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The actor that is being dragged"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:611
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Drag Axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-drag-action.c:612
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Constraints the dragging to an axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:882
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Orientation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:883
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The orientation of the layout"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:899
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether each item should receive the same allocation"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:914 ../clutter/clutter-table-layout.c:1711
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Column Spacing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:915
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The spacing between columns"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:931 ../clutter/clutter-table-layout.c:1725
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Row Spacing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:932
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The spacing between rows"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:946
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Minimum Column Width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:947
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Minimum width for each column"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:962
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Maximum Column Width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:963
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Maximum width for each column"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:977
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Minimum Row Height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:978
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Minimum height for each row"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:993
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Maximum Row Height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-flow-layout.c:994
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Maximum height for each row"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:220
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Id"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:221
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Unique identifier of the device"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:237
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The name of the device"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:251
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Device Type"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:252
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The type of the device"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:267
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Device Manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:268
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The device manager instance"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:281
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Device Mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:282
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The mode of the device"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:296
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Has Cursor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:297
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the device has a cursor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:316
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the device is enabled"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:329
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Number of Axes"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:330
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The number of axes on the device"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-input-device.c:345
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The backend instance"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-interval.c:397
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Value Type"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-interval.c:398
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The type of the values in the interval"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-layout-meta.c:117
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Manager"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-layout-meta.c:118
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The manager that created this data"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#. Translate to default:RTL if you want your widgets
#. * to be RTL, otherwise translate to default:LTR.
#. *
#. * Do *not* translate it to "predefinito:LTR": if it
#. * it isn't default:LTR or default:RTL it will not work
#.
#: ../clutter/clutter-main.c:486
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "default:LTR"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1282
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Show frames per second"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1284
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Default frame rate"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1286
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Make all warnings fatal"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1289
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Direction for the text"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1292
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Disable mipmapping on text"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1295
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Use 'fuzzy' picking"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1298
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Clutter debugging flags to set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1300
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Clutter debugging flags to unset"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1304
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Clutter profiling flags to set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1306
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Clutter profiling flags to unset"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1309
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Enable accessibility"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1491
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Clutter Options"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-main.c:1492
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Show Clutter Options"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:77
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "URI"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:78
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "URI of a media file"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:91
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Playing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:92
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Wheter the actor is playing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:106
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Progress"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:107
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Current progress of the playback"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:120
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Subtitle URI"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:121
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "URI of a subtitle file"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:136
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Subtitle Font Name"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:137
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The font used to display subtitles"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:151
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Audio Volume"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:152
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The volume of the audio"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:165
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Can Seek"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:166
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the current stream is seekable"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:180
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Buffer Fill"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:181
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The fill level of the buffer"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-media.c:195
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The duration of the stream, in seconds"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-path-constraint.c:213
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The path used to constrain an actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-path-constraint.c:227
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The offset along the path, between -1.0 and 2.0"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-rectangle.c:259
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The color of the rectangle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-rectangle.c:272
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Border Color"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-rectangle.c:273
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The color of the border of the rectangle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-rectangle.c:288
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Border Width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-rectangle.c:289
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The width of the border of the rectangle"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-rectangle.c:303
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Has Border"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-rectangle.c:304
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the rectangle should have a border"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-script.c:385
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Filename Set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-script.c:386
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the :filename property is set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-script.c:400 ../clutter/clutter-texture.c:1080
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Filename"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-script.c:401
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The path of the currently parsed file"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:350
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Double Click Time"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:351
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The time between clicks necessary to detect a multiple click"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:366
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Double Click Distance"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:367
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The distance between clicks necessary to detect a multiple click"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:382
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Drag Threshold"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:383
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The distance the cursor should travel before starting to drag"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:398 ../clutter/clutter-text.c:2554
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font Name"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:399
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"The description of the default font, as one that could be parsed by Pango"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:414
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font Antialias"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:415
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Whether to use antialiasing (1 to enable, 0 to disable, and -1 to use the "
"default)"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:431
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font DPI"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:432
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"The resolution of the font, in 1024 * dots/inch, or -1 to use the default"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:448
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font Hinting"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:449
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Whether to use hinting (1 to enable, 0 to disable and -1 to use the default)"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:470
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font Hint Style"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:471
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The style of hinting (hintnone, hintslight, hintmedium, hintfull)"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:492
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font Subpixel Order"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-settings.c:493
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The type of subpixel antialiasing (none, rgb, bgr, vrgb, vbgr)"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:249
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertex Source"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:250
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Source of vertex shader"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:264
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Fragment Source"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:265
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Source of fragment shader"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:280
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Compiled"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:281
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the shader is compiled and linked"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:296
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the shader is enabled"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:501
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
#, c-format
msgid "%s compilation failed: %s"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:502
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertex shader"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader.c:503
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Fragment shader"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader-effect.c:415
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Shader Type"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-shader-effect.c:416
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The type of shader used"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-snap-constraint.c:322
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The source of the constraint"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-snap-constraint.c:335
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "From Edge"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-snap-constraint.c:336
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The edge of the actor that should be snapped"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-snap-constraint.c:350
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "To Edge"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-snap-constraint.c:351
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The edge of the source that should be snapped"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-snap-constraint.c:367
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The offset in pixels to apply to the constraint"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1652
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Fullscreen Set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1653
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the main stage is fullscreen"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1669
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Offscreen"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1670
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the main stage should be rendered offscreen"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1682 ../clutter/clutter-text.c:2667
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Cursor Visible"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1683
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the mouse pointer is visible on the main stage"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1697
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "User Resizable"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1698
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the stage is able to be resized via user interaction"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1711
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The color of the stage"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1725
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Perspective"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1726
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Perspective projection parameters"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1741
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Title"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1742
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Stage Title"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1757
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Use Fog"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1758
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to enable depth cueing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1772
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Fog"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1773
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Settings for the depth cueing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1789
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Use Alpha"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1790
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether to honour the alpha component of the stage color"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1806
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Key Focus"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1807
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The currently key focused actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1823
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "No Clear Hint"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1824
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the stage should clear its contents"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1837
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Accept Focus"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-stage.c:1838
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the stage should accept focus on show"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-state.c:1408
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "State"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-state.c:1409
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Currently set state, (transition to this state might not be complete)"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-state.c:1423
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Default transition duration"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:585
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Column Number"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:586
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The column the widget resides in"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:593
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Row Number"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:594
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The row the widget resides in"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:601
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Column Span"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:602
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The number of columns the widget should span"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:609
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Row Span"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:610
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The number of rows the widget should span"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:617
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal Expand"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:618
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Allocate extra space for the child in horizontal axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:624
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical Expand"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:625
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Allocate extra space for the child in vertical axis"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:1712
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Spacing between columns"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-table-layout.c:1726
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Spacing between rows"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2555
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The font to be used by the text"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2572
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font Description"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2573
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The font description to be used"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2589
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Text"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2590
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The text to render"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2604
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Font Color"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2605
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Color of the font used by the text"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2619
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Editable"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2620
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the text is editable"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2635
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Selectable"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2636
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the text is selectable"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2650
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Activatable"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2651
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether pressing return causes the activate signal to be emitted"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2668
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the input cursor is visible"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2682 ../clutter/clutter-text.c:2683
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Cursor Color"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2697
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Cursor Color Set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2698
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the cursor color has been set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2713
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Cursor Size"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2714
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The width of the cursor, in pixels"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2728
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Cursor Position"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2729
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The cursor position"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2744
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Selection-bound"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2745
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The cursor position of the other end of the selection"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2760 ../clutter/clutter-text.c:2761
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Selection Color"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2775
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Selection Color Set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2776
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the selection color has been set"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2791
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Attributes"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2792
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "A list of style attributes to apply to the contents of the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2814
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Use markup"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2815
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether or not the text includes Pango markup"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2831
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Line wrap"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2832
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "If set, wrap the lines if the text becomes too wide"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2847
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Line wrap mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2848
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Control how line-wrapping is done"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2863
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Ellipsize"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2864
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The preferred place to ellipsize the string"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2880
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Line Alignment"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2881
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The preferred alignment for the string, for multi-line text"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2897
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Justify"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2898
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the text should be justified"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2913
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Password Character"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2914
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "If non-zero, use this character to display the actor's contents"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2928
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Max Length"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2929
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Maximum length of the text inside the actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2952
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Single Line Mode"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-text.c:2953
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the text should be a single line"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:994
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Sync size of actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:995
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Auto sync size of actor to underlying pixbuf dimensions"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1002
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Disable Slicing"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1003
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Forces the underlying texture to be singular and not made of smaller space "
"saving individual textures"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1012
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Tile Waste"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1013
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Maximum waste area of a sliced texture"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1021
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Horizontal repeat"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1022
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Repeat the contents rather than scaling them horizontally"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1029
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Vertical repeat"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1030
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Repeat the contents rather than scaling them vertically"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1037
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Filter Quality"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1038
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Rendering quality used when drawing the texture"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1046
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pixel Format"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1047
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The Cogl pixel format to use"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1055
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Cogl Texture"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1056
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The underlying Cogl texture handle used to draw this actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1063
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Cogl Material"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1064
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The underlying Cogl material handle used to draw this actor"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1081
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The path of the file containing the image data"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1088
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Keep Aspect Ratio"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1089
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Keep the aspect ratio of the texture when requesting the preferred width or "
"height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1115
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Load asynchronously"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1116
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Load files inside a thread to avoid blocking when loading images from disk"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1132
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Load data asynchronously"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1133
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid ""
"Decode image data files inside a thread to reduce blocking when loading "
"images from disk"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1157
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pick With Alpha"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-texture.c:1158
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Shape actor with alpha channel when picking"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-timeline.c:264
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Should the timeline automatically restart"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-timeline.c:278
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Delay"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-timeline.c:279
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Delay before start"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-timeline.c:295
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Duration of the timeline in milliseconds"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-timeline.c:311
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Direction of the timeline"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-timeline.c:326
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Auto Reverse"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/clutter-timeline.c:327
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Whether the direction should be reversed when reaching the end"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/evdev/clutter-input-device-evdev.c:147
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "sysfs Path"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/evdev/clutter-input-device-evdev.c:148
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Path of the device in sysfs"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/evdev/clutter-input-device-evdev.c:163
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Device Path"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/evdev/clutter-input-device-evdev.c:164
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Path of the device node"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/glx/clutter-backend-glx.c:107
msgid "Set to 'none' or '0' to disable throttling framerate to vblank"
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-backend-x11.c:483
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X display to use"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-backend-x11.c:489
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X screen to use"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-backend-x11.c:494
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Make X calls synchronous"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-backend-x11.c:501
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Enable XInput support"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-keymap-x11.c:317
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The Clutter backend"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:545
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pixmap"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:546
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The X11 Pixmap to be bound"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:554
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pixmap width"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:555
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The width of the pixmap bound to this texture"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:563
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pixmap height"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:564
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The height of the pixmap bound to this texture"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:572
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Pixmap Depth"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:573
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The depth (in number of bits) of the pixmap bound to this texture"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:581
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Automatic Updates"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:582
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "If the texture should be kept in sync with any pixmap changes."
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:590
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Window"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:591
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "The X11 Window to be bound"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:599
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Window Redirect Automatic"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:600
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "If composite window redirects are set to Automatic (or Manual if false)"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:610
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Window Mapped"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:611
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "If window is mapped"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:620
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Destroyed"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:621
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "If window has been destroyed"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:629
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Window X"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:630
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "X position of window on screen according to X11"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:638
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Window Y"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:639
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Y position of window on screen according to X11"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:646
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "Window Override Redirect"
msgstr ""
Updated Galician translations
2011-05-12 07:18:02 -04:00
#: ../clutter/x11/clutter-x11-texture-pixmap.c:647
po: Track Clutter's POT file in Git If no POT file is found, gettext will automatically create it; this, in turn, will cause msgmerge to be run, and that will cause the PO files to be touched and changed at the very first call for `make`. Having the PO files with unstaged changes will ultimately lead to merge issues will pulling from the remote repository between releases - unless `git checkout -f` is called prior to `git pull -r`. I think intltool only has some rule to avoid that from happening unless on dist, but I have no intention of dragging intltool into the build of a library that barely has localized messages.
2011-03-31 12:07:08 -04:00
msgid "If this is an override-redirect window"
msgstr ""
Reference in New Issue Copy Permalink