dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
gimp/po-windows-installer/pl.po

409 lines
15 KiB
Plaintext
Raw Permalink Normal View History

build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
# Polish translation for gimp-windows-installer.
Update Polish translation
2020-11-01 17:42:26 +08:00
# Copyright © 2012, 2017-2020 the gimp authors.
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
# This file is distributed under the same license as the gimp package.
Update Polish translation
2020-11-01 17:42:26 +08:00
# Piotr Drąg <piotrdrag@gmail.com>, 2012, 2017-2020.
# Aviary.pl <community-poland@mozilla.org>, 2012, 2017-2020.
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
#
msgid ""
msgstr ""
"Project-Id-Version: gimp-windows-installer\n"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\n"
"POT-Creation-Date: 2022-08-22 21:28+0200\n"
Update Polish translation
2020-11-01 17:42:26 +08:00
"PO-Revision-Date: 2020-11-01 10:42+0100\n"
Update Polish translation
2018-01-01 06:54:35 +08:00
"Last-Translator: Piotr Drąg <piotrdrag@gmail.com>\n"
"Language-Team: Polish <community-poland@mozilla.org>\n"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
"Language: pl\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
Update Polish translation
2018-01-01 06:54:35 +08:00
"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 "
"|| n%100>=20) ? 1 : 2);\n"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:7
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "License Agreement"
msgstr "Umowa licencyjna"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:10
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid "Setup built by Jernej Simonèiè, jernej-gimp@ena.si"
po-windows-installer: technical fix to the Polish translation Looks like ender's name can't be used verbatim in the encoding used for the Polish translation. Use his name as previously appeared in the Polish translation.
2018-01-07 01:05:55 +08:00
msgstr "Instalator utworzony przez Jerneja Simončiča, jernej-gimp@ena.si"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:13
#: build/windows/installer/lang/setup.isl.xml.in:16
Update Polish translation
2018-05-07 01:33:18 +08:00
msgid "This version of GIMP requires Windows 7, or a newer version of Windows."
msgstr "Ta wersja programu GIMP wymaga systemu Windows 7 lub nowszego."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:23
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Development version"
msgstr "Wersja rozwojowa"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:28
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
Update Polish translation
2018-01-08 22:30:21 +08:00
"This is a development version of GIMP where some features may not be "
"finished, or it may be unstable.%nThis version of GIMP is not intended for "
"day-to-day work as it may be unstable, and you could lose your work.%nIf you "
"encounter any problems, first verify that they haven't already been fixed in "
Update Polish translation
2018-08-06 01:10:57 +08:00
"GIT before you contact the developers or report it in GIMP gitlab:%n_https://"
"gitlab.gnome.org/GNOME/gimp/issues%n%nDo you wish to continue with "
"installation anyway?"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgstr ""
Update Polish translation
2018-01-08 22:30:21 +08:00
"To jest rozwojowa wersja programu GIMP, w której niektóre funkcje mogą nie "
"być ukończone lub program może być niestabilny.%nTa wersja programu GIMP nie "
"jest przeznaczona do codziennego użytku, ponieważ może być niestabilna, co "
"może doprowadzić do utraty danych.%nJeśli wystąpił problem, to prosimy "
"najpierw sprawdzić, czy nie został on już naprawiony w repozytorium git. "
Update Polish translation
2018-07-16 01:58:18 +08:00
"Jeśli nie, to prosimy zgłosić go w serwisie GitLab programu GIMP (w języku "
"angielskim):%n_https://gitlab.gnome.org/GNOME/gimp/issues%n%nKontynuować "
"instalację mimo to?"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:31
#: build/windows/installer/lang/setup.isl.xml.in:54
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "&Continue"
msgstr "&Kontynuuj"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:34
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Exit"
msgstr "Zakończ"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:44
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"This version of GIMP requires a processor that supports SSE instructions."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgstr "Ta wersja programu GIMP wymaga procesora obsługującego instrukcje SSE."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:48
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Display settings problem"
msgstr "Problem ustawień ekranu"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:51
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"Setup has detected that your Windows is not running in 32 bits-per-pixel "
"display mode. This has been known to cause stability problems with GIMP, so "
"it's recommended to change the display colour depth to 32BPP before "
"continuing."
msgstr ""
"Instalator wykrył, że system Windows nie działa w trybie wyświetlania 32 "
Update Polish translation
2018-01-01 06:54:35 +08:00
"bitów głębi kolorów. Powoduje to problemy ze stabilnością programu GIMP. "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"Zalecana jest zmiana głębi kolorów ekranu na 32 bity na piksel przed "
"kontynuowaniem."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:57
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "E&xit"
msgstr "Za&kończ"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:61
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"GIMP is now ready to be installed. Click the Install now button to install "
"using the default settings, or click the Customize button if you'd like to "
"have more control over what gets installed."
msgstr ""
"Program GIMP jest gotowy do instalacji. Kliknięcie przycisku Zainstaluj "
Update Polish translation
2018-01-01 06:54:35 +08:00
"spowoduje instalację za pomocą domyślnych ustawień, a kliknięcie przycisku "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"Dostosuj udostępnia więcej możliwości kontroli nad procesem instalacji."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:64
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "&Install"
Update Polish translation
2018-01-01 06:54:35 +08:00
msgstr "&Zainstaluj"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:67
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "&Customize"
msgstr "&Dostosuj"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:72
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Compact installation"
msgstr "Instalacja podstawowa"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:76
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Custom installation"
msgstr "Instalacja użytkownika"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:80
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Full installation"
msgstr "Pełna instalacja"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:85
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Description"
msgstr "Opis"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:89
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "GIMP"
msgstr "GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:93
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "GIMP and all default plug-ins"
msgstr "GIMP i wszystkie domyślne wtyczki"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:97
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Run-time libraries"
msgstr "Biblioteki wykonawcze"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:101
#, fuzzy
msgid "Run-time libraries used by GIMP, including GTK Run-time Environment"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgstr ""
"Biblioteki wykonawcze używane przez program GIMP, w tym środowisko "
Update Polish translation
2019-02-22 00:35:00 +08:00
"wykonawcze GTK"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:105
Update Polish translation
2018-05-07 01:33:18 +08:00
msgid "Debug symbols"
msgstr "Symbole debugowania"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:109
Update Polish translation
2018-05-07 01:33:18 +08:00
msgid "Include information to help with debugging GIMP"
msgstr "Informacje pomagające debugować program GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:113
#, fuzzy
msgid "MS-Windows engine for GTK"
Update Polish translation
2019-02-22 00:35:00 +08:00
msgstr "Mechanizm Windows dla biblioteki GTK"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:117
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Native Windows look for GIMP"
msgstr "Natywny wygląd programu GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:121
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Support for old plug-ins"
msgstr "Obsługa starszych wtyczek"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:125
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Install libraries needed by old third-party plug-ins"
msgstr "Instaluje biblioteki wymagane przez starsze wtyczki firm trzecich"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:129
#: build/windows/installer/lang/setup.isl.xml.in:133
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Translations"
Update Polish translation
2019-05-28 00:18:35 +08:00
msgstr "Tłumaczenia, w tym na język polski"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:137
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Python scripting"
msgstr "Język skryptowy Python"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:141
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Allows you to use GIMP plugins written in Python scripting language."
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgstr ""
"Umożliwia używanie wtyczek programu GIMP napisanych w języku skryptowym "
"Python."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:145
Update Polish translation
2020-11-01 17:42:26 +08:00
msgid "Lua scripting"
msgstr "Język skryptowy Lua"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:149
Update Polish translation
2020-11-01 17:42:26 +08:00
msgid "Allows you to use GIMP plugins written in Lua scripting language."
msgstr ""
"Umożliwia używanie wtyczek programu GIMP napisanych w języku skryptowym Lua."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:153
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid "MyPaint brushes"
Update Polish translation
2018-01-01 06:54:35 +08:00
msgstr "Pędzle programu MyPaint"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:157
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid "Install the default set of MyPaint brushes"
Update Polish translation
2018-01-01 06:54:35 +08:00
msgstr "Instaluje domyślny zestaw pędzli programu MyPaint"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:161
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "PostScript support"
msgstr "Obsługa plików PostScript"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:165
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Allow GIMP to load PostScript files"
msgstr "Umożliwia programowi GIMP wczytywanie plików w formacie PostScript"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:169
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Support for 32-bit plug-ins"
msgstr "Obsługa wtyczek 32-bitowych"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:173
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"Include files necessary for using 32-bit plug-ins.%nRequired for Python "
"support."
msgstr ""
Update Polish translation
2018-01-01 06:54:35 +08:00
"Dołącza pliki wymagane do obsługi wtyczek 32-bitowych.%nWymagane do obsługi "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"języka Python."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:178
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Additional icons:"
msgstr "Dodatkowe ikony:"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:182
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Create a &desktop icon"
Update Polish translation
2018-05-07 01:33:18 +08:00
msgstr "&Na pulpicie"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:186
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Create a &Quick Launch icon"
Update Polish translation
2018-05-07 01:33:18 +08:00
msgstr "Na pasku &szybkiego uruchamiania"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:190
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Remove previous GIMP version"
msgstr "Usunięcie poprzedniej wersji programu GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:195
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"There was a problem updating GIMP's environment in %1. If you get any errors "
"loading the plug-ins, try uninstalling and re-installing GIMP."
msgstr ""
"Wystąpił problem podczas aktualizowania środowiska programu GIMP w %1. Jeśli "
"wystąpią błędy podczas wczytywania wtyczek, to należy odinstalować i "
"ponownie zainstalować program GIMP."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:199
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Error extracting temporary data."
Update Polish translation
2018-01-01 06:54:35 +08:00
msgstr "Błąd podczas rozpakowywania plików tymczasowych."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:203
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Error updating Python interpreter info."
msgstr "Błąd podczas aktualizowania informacji o interpreterze języka Python."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:207
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid "Error updating MyPaint brushes info."
Update Polish translation
2018-01-01 06:54:35 +08:00
msgstr "Błąd podczas aktualizowania informacji o pędzlach programu MyPaint."
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:211
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "There was an error updating %1."
msgstr "Wystąpił błąd podczas aktualizowania %1."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:215
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "There was an error updating GIMP's configuration file %1."
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgstr ""
"Wystąpił błąd podczas aktualizowania pliku konfiguracji %1 programu GIMP."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:220
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Edit with GIMP"
msgstr "Edytuj za pomocą GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:225
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Select file associations"
msgstr "Wybór powiązań plików"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:229
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Extensions:"
msgstr "Rozszerzenia:"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:233
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Select the file types you wish to associate with GIMP"
msgstr "Proszę wybrać typy plików do powiązania z programem GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:237
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"This will make selected files open in GIMP when you double-click them in "
"Explorer."
msgstr ""
"Spowoduje to otwieranie wybranych plików w programie GIMP po podwójnym "
"kliknięciu ich w Eksploratorze."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:241
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Select &All"
msgstr "Zaznacz &wszystkie"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:245
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Unselect &All"
msgstr "Odznacz w&szystkie"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:249
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Select &Unused"
msgstr "Zaznacz &nieużywane"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:254
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "File types to associate with GIMP:"
msgstr "Typy plików do powiązania z programem GIMP:"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:258
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Removing previous version of GIMP:"
msgstr "Usuwanie poprzedniej wersji programu GIMP:"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:262
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"GIMP %1 cannot be installed over your currently installed GIMP version, and "
"the automatic uninstall of old version has failed.%n%nPlease remove the "
"previous version of GIMP yourself before installing this version in %2, or "
"choose a Custom install, and select a different installation folder.%n%nThe "
"Setup will now exit."
msgstr ""
"GIMP %1 nie może zostać zainstalowany w miejscu obecnie zainstalowanej "
"wersji, a automatyczne odinstalowanie poprzedniej wersji się nie powiodło.%n"
"%nProszę samodzielnie usunąć poprzednią wersję programu GIMP przed "
"zainstalowaniem tej wersji w katalogu %2 lub wybrać instalację użytkownika i "
"podać inny katalog instalacji.%n%nInstalator zostanie zakończony."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:266
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"GIMP %1 cannot be installed over your currently installed GIMP version, and "
"Setup couldn't determine how to remove the old version automatically.%n"
"%nPlease remove the previous version of GIMP and any add-ons yourself before "
"installing this version in %2, or choose a Custom install, and select a "
"different installation folder.%n%nThe Setup will now exit."
msgstr ""
"GIMP %1 nie może zostać zainstalowany w miejscu obecnie zainstalowanej "
"wersji, a instalator nie może ustalić sposobu automatycznego usunięcia "
"poprzedniej wersji.%n%nPrzed zainstalowaniem tej wersji w katalogu %2 proszę "
"usunąć poprzednią wersję programu GIMP i wszystkie dodatki zainstalowane "
"przez użytkownika lub wybrać instalację użytkownika i podać inny katalog "
"instalacji.%n%nInstalator zostanie zakończony."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:270
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"Previous GIMP version was removed successfully, but Windows has to be "
"restarted before the Setup can continue.%n%nAfter restarting your computer, "
"Setup will continue next time an administrator logs in."
msgstr ""
"Pomyślnie usunięto poprzednią wersję programu GIMP, ale system Windows musi "
"zostać ponownie uruchomiony przed kontynuowaniem instalacji.%n%nPo ponownym "
"uruchomieniu komputera instalator zostanie kontynuowany, kiedy administrator "
"się zaloguje."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:275
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "There was an error restarting the Setup. (%1)"
msgstr "Wystąpił błąd podczas ponownego uruchamiania instalatora. (%1)"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:279
Update Polish translation
2018-05-16 02:50:14 +08:00
msgid "Cleaning up old files..."
msgstr "Usuwanie nieużywanych starych plików..."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:284
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Remember: GIMP is Free Software.%n%nPlease visit"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgstr ""
"Prosimy pamiętać: program GIMP jest wolnym oprogramowaniem.%n%nZapraszamy do "
"odwiedzenia witryny"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:288
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "for free updates."
Update Polish translation
2018-01-01 06:54:35 +08:00
msgstr "zawierającej bezpłatne aktualizacje."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:292
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Setting up file associations..."
msgstr "Ustawianie powiązań plików..."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:295
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Setting up environment for GIMP Python extension..."
msgstr "Ustawianie środowiska dla rozszerzenia języka Python programu GIMP..."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:298
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid "Setting up MyPaint brushes..."
Update Polish translation
2018-01-01 06:54:35 +08:00
msgstr "Ustawianie pędzli programu MyPaint..."
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:301
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Setting up GIMP environment..."
msgstr "Ustawianie środowiska programu GIMP..."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:304
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Setting up GIMP configuration for 32-bit plug-in support..."
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgstr ""
Update Polish translation
2018-01-01 06:54:35 +08:00
"Ustawianie konfiguracji programu GIMP do obsługi wtyczek 32-bitowych..."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:309
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Launch GIMP"
msgstr "Uruchomienie programu GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:314
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Removing add-on"
msgstr "Usuwanie dodatku"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:318
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Internal error (%1)."
msgstr "Wewnętrzny błąd (%1)."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:323
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"GIMP does not appear to be installed in the selected directory. Continue "
"anyway?"
msgstr ""
"Program GIMP nie jest zainstalowany w wybranym katalogu. Kontynuować mimo to?"