This piece of code in capplets/theme-switcher/control/control.c:19 is
problematic with regard to gettext translation:

  /* just 8 short names that will serve as samples for titles in demo */
  char *column1[4] = { N_("Eenie"),  N_("Mynie"), N_("Catcha"), N_("By Its") };
  char *column2[4] = { N_("Meenie"), N_("Moe"),   N_("Tiger"),  N_("Toe") };


This ends up in the po file as:

#. just 8 short names that will serve as samples for titles in demo
#: capplets/theme-switcher/control/control.c:19
msgid "Eenie"
msgstr ""

#: capplets/theme-switcher/control/control.c:19
msgid "Mynie"
msgstr ""

#: capplets/theme-switcher/control/control.c:19
msgid "Catcha"
msgstr ""

#: capplets/theme-switcher/control/control.c:19
msgid "By Its"
msgstr ""

#: capplets/theme-switcher/control/control.c:20
msgid "Meenie"
msgstr ""

#: capplets/theme-switcher/control/control.c:20
msgid "Moe"
msgstr ""

#: capplets/theme-switcher/control/control.c:20
msgid "Tiger"
msgstr ""

#: capplets/theme-switcher/control/control.c:20
msgid "Toe"
msgstr ""

Obviously, the chances that the translation will be in the correct order is
pretty slim with this design.
A better solution would be to allow the translation of this whole rhyme in
one single message, where the order is preserved and the connection is obvious.