glib/gio/tests/de.po

msgid ""
msgstr ""
"Project-Id-Version: \n"
"PO-Revision-Date: \n"
"Last-Translator: \n"
"Language-Team: \n"
"MIME-Version: \n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"

msgid "\"Unnamed\""
msgstr "\"Unbenannt\""

msgctxt "keyboard label"
msgid "\"BackSpace\""
msgstr "\"Löschen\""

msgid "\"12:00 AM\""
msgstr "\"00:00\""
Merge GSettings tests 2010-04-17 07:43:58 +02:00			`msgid ""`
			`msgstr ""`
			`"Project-Id-Version: \n"`
			`"PO-Revision-Date: \n"`
			`"Last-Translator: \n"`
			`"Language-Team: \n"`
			`"MIME-Version: \n"`
			`"Content-Type: text/plain; charset=UTF-8\n"`
			`"Content-Transfer-Encoding: 8bit\n"`
			`"Plural-Forms: nplurals=2; plural=(n != 1)\n"`

			`msgid "\"Unnamed\""`
			`msgstr "\"Unbenannt\""`

			`msgctxt "keyboard label"`
			`msgid "\"BackSpace\""`
			`msgstr "\"Löschen\""`
Add test for l10n="time" gschema attribute This is a copy of the existing test_l10n, modified to use LC_TIME instead of LC_MESSAGES. It's not safe as each call to g_setenv() or setlocale() could cause the test to crash; there is no safe way to change a threaded process's environment, and a threaded process's locale can only be safely changed using uselocale(), not with setlocale(). The calls to g_setenv() are definitely not needed on Linux. I wonder whether removing these will break the test on other platforms? The calls to setlocale() should be replaced by a dance of uselocale() -> duplocale() -> newlocale() -> uselocale() on Linux. But this is not portable and this is a cross-platform test. We would have to make the test platform-specific to do this. macOS and at least FreeBSD provide these functions via xlocale.h, but this isn't portable. 2023-07-21 20:48:34 +02:00
			`msgid "\"12:00 AM\""`
			`msgstr "\"00:00\""`