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/hu.po

397 lines
15 KiB
Plaintext
Raw 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
# Hungarian translation for gimp-windows-installer.
Update Hungarian translation
2024-02-20 03:41:03 +08:00
# Copyright (C) 2017, 2018, 2021, 2022, 2024 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 Hungarian translation
2024-02-20 03:41:03 +08:00
# Balázs Úr <ur.balazs at fsf dot hu>, 2017, 2018, 2021, 2022, 2024.
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"
Update Hungarian translation
2018-06-29 03:55:58 +08:00
"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\n"
Update Hungarian translation
2024-02-20 03:41:03 +08:00
"POT-Creation-Date: 2024-02-15 20:23+0000\n"
"PO-Revision-Date: 2024-02-19 20:39+0100\n"
Update Hungarian translation
2021-09-11 04:17:14 +08:00
"Last-Translator: Balázs Úr <ur.balazs at fsf dot hu>\n"
Update Hungarian translation
2024-02-20 03:41:03 +08:00
"Language-Team: Hungarian <openscope at fsf dot hu>\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: hu\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
Update Hungarian translation
2024-02-20 03:41:03 +08:00
"X-Generator: Lokalize 23.08.4\n"
Update Hungarian translation
2018-02-26 01:01:35 +08:00
"Plural-Forms: nplurals=2; plural=(n != 1);\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 "Licencmegállapodás"
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 Hungarian, Latvian translations ender's name can't be encoded in the target encoding -> use ASCII.
2018-03-11 07:19:38 +08:00
msgstr "A beállítást összeállította: Jernej Simoncic, 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 Hungarian translation
2024-02-20 03:41:03 +08:00
#| msgid ""
#| "This version of GIMP requires Windows 7, or a newer version of Windows."
msgid ""
"This version of GIMP requires Windows 10, or a newer version of Windows."
msgstr ""
"A GIMP ezen verziója Windows 10-et, vagy újabb Windows verziót igényel."
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 "Fejlesztői verzió"
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 Hungarian translation
2018-02-26 01:01:35 +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 Hungarian translation
2018-10-06 05:51:30 +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 Hungarian translation
2018-02-26 01:01:35 +08:00
"Ez a GIMP fejlesztői verziója, amelyben néhány funkció még nem készült el, "
"vagy instabil lehet.%nA GIMP ezen verziója nem ajánlott a mindennapi "
Update Hungarian translation
2018-05-05 19:31:26 +08:00
"munkavégzéshez, mivel instabil lehet, és a munkája elvesztését okozhatja."
"%nHa bármilyen problémával találkozik, akkor először ellenőrizze, hogy nem "
"javították-e még ki a GIT-en, mielőtt kapcsolatba lépne a fejlesztőkkel, "
Update Hungarian translation
2018-10-06 05:51:30 +08:00
"vagy a GIMP bugzilla oldalán jelentené:%n_https://gitlab.gnome.org/GNOME/"
"gimp/issues%n%nMindenképp folytatni szeretné a telepítést?"
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: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 "&Folytatás"
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 "Kilépés"
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 "A GIMP ezen verziója az SSE utasításokat támogató processzort igényel."
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 "Probléma a kijelzőbeállításokkal"
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 ""
"A telepítő azt észlelte, hogy a Windows nem 32 bites színmélységű módban "
"fut. Ez a GIMP-nek stabilitási problémákat okoz, így javasoljuk, hogy a "
"folytatás előtt állítsa a színmélységet 32 bitesre."
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 "&Kilépés"
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 ""
"A GIMP immár kész a telepítésre. Kattintson a Telepítés gombra az "
"alapértelmezett beállításokkal való telepítéshez, vagy a Személyre szabás "
"gombra, ha módosítani szeretné a telepítendő összetevők listáját."
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"
msgstr "&Telepítés"
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 "&Személyre szabás"
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 "Kompakt telepítés"
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 "Egyéni telepítés"
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 "Teljes telepítés"
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 "Leírás"
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 "A GIMP és minden alap bővítménye"
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 "Futásidejű programkönyvtárak"
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
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 ""
Update Hungarian translation
2024-02-20 03:41:03 +08:00
"A GIMP által használt futásidejű programkönyvtárak, beleértve a GTK "
"futtatókörnyezetet is"
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 Hungarian translation
2018-05-05 19:31:26 +08:00
msgid "Debug symbols"
msgstr "Hibakeresési szimbólumok"
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 Hungarian translation
2018-05-05 19:31:26 +08:00
msgid "Include information to help with debugging GIMP"
msgstr "Olyan információk hozzáadása, amelyek segítenek a GIMP hibakeresésében"
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
msgid "MS-Windows engine for GTK"
Update Hungarian translation
2022-09-02 07:15:06 +08:00
msgstr "MS-Windows motor a GTK-hoz"
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 "Natív Windows megjelenés a GIMP-hez"
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 "Régi bővítmények támogatása"
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 "Régi külső bővítményekhez szükséges programkönyvtárak telepítése"
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"
msgstr "Fordítások"
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 "Python parancsfájlok"
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."
msgstr "Lehetővé teszi Python nyelven írt GIMP bővítmények használatát."
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 Hungarian translation
2021-09-11 04:17:14 +08:00
msgid "Lua scripting"
msgstr "Lua parancsfájlok"
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 Hungarian translation
2021-09-11 04:17:14 +08:00
msgid "Allows you to use GIMP plugins written in Lua scripting language."
msgstr "Lehetővé teszi a Lua nyelven írt GIMP bővítmények használatát."
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 Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "MyPaint ecsetek"
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: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 Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "MyPaint ecsetek alapértelmezett készletének telepítése"
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 "PostScript támogatás"
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 "A GIMP betöltheti a PostScript fájlokat"
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 "32 bites bővítmények támogatása"
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 ""
"A 32 bites bővítmények támogatásához szükséges fájlok.%nSzükséges a Python "
"támogatáshoz."
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 "További ikonok:"
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"
msgstr "&Asztali ikon létrehozása"
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"
msgstr "&Gyorsindító ikon létrehozása"
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 "Korábbi GIMP verzió eltávolítása"
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 ""
"Hiba történt a GIMP környezetének frissítésekor ebben: %1. Ha hibaüzeneteket "
"kap a bővítmények betöltésekor, akkor próbálja meg eltávolítani és "
"újratelepíteni a GIMP-et."
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."
msgstr "Hiba az ideiglenes adatok kibontásakor."
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 "Hiba a Python értelmező információinak frissítésekor."
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 Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "Hiba a MyPaint ecsetek információinak frissítésekor."
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 "Hiba történt a következő frissítésekor: %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."
msgstr "Hiba történt a GIMP beállítófájljának frissítésekor: %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: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 "Szerkesztés a GIMP-pel"
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 "Válasszon fájltársításokat"
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 "Kiterjesztések:"
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 "Válassza ki a GIMP-hez társítandó fájltípusokat"
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 ""
"Ennek hatására a kijelölt típusú fájlok a GIMP-ben nyílnak meg, amikor "
"duplán kattint rájuk az Intézőben."
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 "Összes &kijelölése"
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 "Kijelölés &törlése"
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 "Tö&bbi kijelölése"
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 "A GIMP-hez társítandó fájltípusok:"
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 "A GIMP korábbi verziójának eltávolítása:"
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 ""
"A GIMP %1 nem telepíthető a jelenlegi GIMP verzió fölé, és a régi verzió "
"automatikus eltávolítása meghiúsult.%n%nTávolítsa el a GIMP korábbi "
"verzióját, mielőtt ezt a verziót ide telepíti: %2, vagy válassza az Egyéni "
"telepítést és válasszon másik telepítési mappát.%n%nA telepítő most kilép."
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: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 "
Update Hungarian translation
2024-02-20 03:41:03 +08:00
"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."
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgstr ""
"A GIMP %1 nem telepíthető a jelenlegi GIMP verzió fölé, és a telepítő nem "
Update Hungarian translation
2024-02-20 03:41:03 +08:00
"tudta megállapítani, hogyan távolítható el a régi verzió automatikusan."
"%n%nTávolítsa el a GIMP korábbi verzióját és a bővítményeket, mielőtt ezt a "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"verziót ide telepíti: %2, vagy válassza az Egyéni telepítést és válasszon "
"másik telepítési mappát.%n%nA telepítő most kilép."
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 ""
"A GIMP korábbi verziója sikeresen eltávolítva, de a Windowst újra kell "
"indítani, mielőtt a telepítés folytatódhatna.%n%nA számítógép újraindítása "
"és egy adminisztrátor bejelentkezése után a telepítő futása folytatódik."
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 "Hiba történt a Telepítő újraindításakor. (%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 Hungarian translation
2018-06-29 03:55:58 +08:00
msgid "Cleaning up old files..."
msgstr "Régi fájlok eltakarítása…"
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"
msgstr "Ne feledje: A GIMP szabad szoftver.%n%nFrissítésekért keresse fel a"
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."
msgstr "oldalt."
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..."
Update Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "Fájltársítások beállítása…"
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: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..."
Update Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "Környezet beállítása a GIMP Python kiterjesztéséhez…"
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: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 Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "MyPaint ecsetek beállítása…"
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..."
Update Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "A GIMP környezetének beállítása…"
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: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..."
Update Hungarian translation
2018-02-26 01:01:35 +08:00
msgstr "A GIMP beállítása a 32-bites bővítmények támogatásához…"
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 "A GIMP indítása"
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 "Bővítmény eltávolítása"
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 "Belső hiba (%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?"
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 "A GIMP nem található a kijelölt könyvtárban. Mindenképp folytatja?"