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

413 lines
16 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
# French translation for gimp-windows-installer.
Updated French translations
2018-04-03 16:57:46 +08:00
# Copyright (C) 2017-2018 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 French translation (cherry picked from commit 1c7e0733796de7c5804e4f216112c881c9380b4b)
2022-04-02 18:17:35 +08:00
# Julien Hardelin <jhardlin@orange.fr>, 2018-2020.
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
#
msgid ""
msgstr ""
"Project-Id-Version: gimp-windows-installer\n"
po*: change Report-Msgid-Bugs-To URL to gitlab.gnome.org
2018-07-12 03:56:14 +08:00
"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\n"
Update French translation
2023-06-26 16:56:03 +08:00
"POT-Creation-Date: 2023-03-21 07:27+0000\n"
"PO-Revision-Date: 2023-06-26 10:35+0200\n"
Updated French translations
2018-04-03 16:57:46 +08:00
"Last-Translator: Julien Hardelin <jhardlin@orange.fr>\n"
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
"Language-Team: French <gnomefr@traduc.org>\n"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
Updated French translations
2018-04-03 16:57:46 +08:00
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
Update French translation
2023-06-26 16:56:03 +08:00
"X-Generator: Poedit 3.2.2\n"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:7
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "License Agreement"
msgstr "Contrat de licence utilisateur final"
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"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Création de Jernej Simonèiè, 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
Updated French translations
2018-05-18 00:28:14 +08:00
msgid "This version of GIMP requires Windows 7, or a newer version of Windows."
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
msgstr "Cette version de GIMP requiert Windows 7 ou plus récent."
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 "Version de développement"
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 ""
Updated French translations
2018-04-03 16:57:46 +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 French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +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 French translation
2023-06-26 16:56:03 +08:00
"Ceci est une version de développement de GIMP et certaines fonctions peuvent "
"ne pas être au point, ou être instables.%nCette version de GIMP n’est pas "
"destinée au travail de tous les jours, car elle est instable et vous courez "
"le risque de perdre votre travail.%nSi vous rencontrez des problèmes, "
"assurez-vous d’abord qu’ils n’ont pas déjà été réglés dans GIT avant de "
"contacter les développeurs ou de les rapporter dans le gitlab GIMP :"
"%n_https://gitlab.gnome.org/GNOME/gimp/issues%n%nSouhaitez-vous tout de même "
"poursuivre l’installation ?"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:31
#: build/windows/installer/lang/setup.isl.xml.in:54
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "&Continue"
msgstr "&Continuer"
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 "Quitter"
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."
msgstr ""
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
"Cette version de GIMP requiert un processeur prenant en charge les "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"instructions SSE."
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: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"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Problème de paramètres d’affichage"
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: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 ""
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
"L’installateur a détecté que Windows ne s’exécute pas en affichage 32 bits "
Updated French translations
2018-04-03 16:57:46 +08:00
"par pixel. C’est une cause connue d’instabilité de GIMP, nous vous "
"recommandons de changer la profondeur d’affichage de couleurs en 32BPP avant "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"de poursuivre."
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 "&Quitter"
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 ""
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
"GIMP est prêt à être installé. Cliquez sur le bouton « Installer » pour "
"utiliser les paramètres par défaut, ou sur « Personnaliser » pour choisir "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"plus finement ce qui sera installé."
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 "&Installer"
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 "&Personnaliser"
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 "Installation compacte"
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 "Installation personnalisée"
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 "Installation complète"
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 "Description"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:89
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "GIMP"
msgstr "GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:93
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "GIMP and all default plug-ins"
msgstr "GIMP et tous les greffons par défaut"
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"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Bibliothèques d’exécution"
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: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 ""
Updated French translations
2018-04-03 16:57:46 +08:00
"Bibliothèques d’exécution utilisées par GIMP, y compris l’environnement "
Update French translation
2023-06-26 16:56:03 +08:00
"d’exécution GTK"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:105
Updated French translations
2018-05-18 00:28:14 +08:00
msgid "Debug symbols"
msgstr "Symboles de débogage"
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
Updated French translations
2018-05-18 00:28:14 +08:00
msgid "Include information to help with debugging GIMP"
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Inclut des informations aidant à déboguer GIMP"
Updated French translations
2018-05-18 00:28:14 +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:113
msgid "MS-Windows engine for GTK"
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Moteur GTK pour Windows"
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 "Apparence native pour Windows"
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 "Prise en charge des anciens greffons"
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"
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Installe les bibliothèques requises par d’anciens greffons tiers"
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: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 "Traductions"
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 "Prise en charge des scripts Python"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:141
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Allows you to use GIMP plugins written in Python scripting language."
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Permet la prise en charge des greffons GIMP écrits en langage Python."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:145
Update French translation (cherry picked from commit 1c7e0733796de7c5804e4f216112c881c9380b4b)
2022-04-02 18:17:35 +08:00
msgid "Lua scripting"
msgstr "Prise en charge des scripts Lua"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:149
Update French translation (cherry picked from commit 1c7e0733796de7c5804e4f216112c881c9380b4b)
2022-04-02 18:17:35 +08:00
msgid "Allows you to use GIMP plugins written in Lua scripting language."
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Permet la prise en charge des greffons GIMP écrits en langage Lua."
Update French translation (cherry picked from commit 1c7e0733796de7c5804e4f216112c881c9380b4b)
2022-04-02 18:17:35 +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:153
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid "MyPaint brushes"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Brosses Mypaint"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in: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"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Installe le lot de brosses MyPaint par défaut"
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 "Prise en charge de PostScript"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:165
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Allow GIMP to load PostScript files"
msgstr "Permet le chargement de fichiers PostScript dans 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: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"
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Prise en charge des greffons 32 bits"
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:173
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"Include files necessary for using 32-bit plug-ins.%nRequired for Python "
"support."
msgstr ""
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
"Inclut les fichiers nécessaires à l’utilisation de greffons 32 bits.%nRequis "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"pour la prise en charge de Python."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:178
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Additional icons:"
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
msgstr "Icônes additionnelles :"
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: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 "Créer une icône sur le &bureau"
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 "Créer une icône dans la barre de lancement &rapide"
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 "Supprimer les versions antérieures de GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:195
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"There was a problem updating GIMP's environment in %1. If you get any errors "
"loading the plug-ins, try uninstalling and re-installing GIMP."
msgstr ""
Updated French translations
2018-04-03 16:57:46 +08:00
"Une erreur s’est produite lors de la mise à jour de l’environnement de GIMP "
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
"dans %1. Si des erreurs surviennent au chargement des greffons, tentez de "
"désinstaller puis réinstaller GIMP."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:199
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Error extracting temporary data."
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Erreur durant l’extraction de données temporaires."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:203
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Error updating Python interpreter info."
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
msgstr ""
"Erreur durant la mise à jour des informations sur l’interpréteur Python."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in: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."
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Erreur durant la mise à jour des informations sur les brosses MyPaint."
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:211
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "There was an error updating %1."
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Erreur lors de la mise à jour de %1."
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: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 "Erreur de mise à jour du fichier %1 de configuration de 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: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 "Modifier avec GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:225
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Select file associations"
msgstr "Sélectionner les extensions à associer"
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:"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Extensions :"
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: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"
Update French translation
2023-06-26 16:56:03 +08:00
msgstr "Sélectionnez les extensions de fichiers à associer à GIMP"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in: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 ""
Updated French translations
2018-04-03 16:57:46 +08:00
"En double-cliquant dans l’Explorateur Windows, les fichiers portant ces "
"extensions s’ouvriront dans GIMP."
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in: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"
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
msgstr "Tout &sélectionner"
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: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"
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
msgstr "Tout &désélectionner"
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: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 "Sélectionner les &inutilisées"
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:"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Types de fichiers à associer à GIMP :"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in: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:"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Désinstallation de la version précédente de GIMP :"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in: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 ""
Update French translation
2023-06-26 16:56:03 +08:00
"GIMP %1 ne peut pas être installée par dessus votre version actuelle de "
"GIMP, et la désinstallation automatique de l'ancienne version a échoué."
"%n%nVeuillez désinstaller manuellement l’ancienne version de GIMP et "
"relancez l’installation dans %2, ou choisissez l’option d’installation "
"personnalisée puis définissez un dossier de destination différent."
Updated French translations
2018-04-03 16:57:46 +08:00
"%n%nL’installateur va à présent s’arrêter."
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: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 French translation
2023-06-26 16:56: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 ""
Update French translation
2023-06-26 16:56:03 +08:00
"GIMP %1 ne peut pas être installée par dessus votre version actuelle de "
"GIMP, et la méthode de désinstallation automatique de votre version actuelle "
"de GIMP n’a pu être déterminée.%n%nVeuillez désinstaller manuellement "
"l’ancienne version de GIMP et ses greffons avant de retenter une "
"installation dans %2, ou choisissez une installation personnalisée puis "
"définissez un dossier de destination différent.%n%nL’installateur va à "
"présent s’arrêter."
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: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 ""
Update French translation
2023-06-26 16:56:03 +08:00
"L'ancienne version de GIMP a été désinstallée avec succès, mais Windows "
Updated French translations
2018-04-03 16:57:46 +08:00
"requiert un redémarrage avant de poursuivre l’installation.%n%nAprès le "
"redémarrage, l’installation reprendra à la connexion d’un administrateur."
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)"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "L’installateur a rencontré une erreur au redémarrage. (%1)"
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:279
Updated French translations
2018-05-18 00:28:14 +08:00
msgid "Cleaning up old files..."
msgstr "Nettoyage des anciens fichiers…"
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 "GIMP est un Logiciel Libre.%n%nVisitez"
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 "pour des mises à jour gratuites."
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..."
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Associations des extensions de fichiers…"
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..."
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Configuration de l’environnement d’extension de GIMP en Python…"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:298
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid "Setting up MyPaint brushes..."
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Configuration des brosses MyPaint…"
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:301
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Setting up GIMP environment..."
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Configuration de l’environnement GIMP…"
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in: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 French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
msgstr "Configuration de la gestion des greffons 32 bits…"
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 "Exécuter GIMP"
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:314
build: use intltool for Windows installer translations Use intltool for managing the translations for the Windows installer, instead of manually maintaining the translated message files. The message files are generated in the source directory, under build/windows/installer/lang, as part of the build, and can be subsequently used to build the installer, as before.
2017-12-25 04:34:04 +08:00
msgid "Removing add-on"
Updated French translations
2018-04-03 16:57:46 +08:00
msgstr "Suppression de l’extension"
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: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 "Erreur interne (%1)."
po-windows-installer: fixing broken po files for Windows installers. This is purely fixing by meson rebuilds and some regexp fixes. I didn't touch any semantic. Basically the "&amp;" XML entity should not have made their way to the po files. I fixed our script in the previous commit, and now I just rebuild the po files and clean the entity programmatically so that our Windows installers for GIMP 2.99.12 release have valid text. Here is what I did: (1) I regenerated the pot and po files: $ meson compile gimp30-windows-installer-pot $ meson compile gimp30-windows-installer-update-po (2) I opened all the po files in vim and regexp through them. Get back the proper Report-Msgid-Bugs-To: :bufdo! %s$"Report-Msgid-Bugs-To: \\n"$"Report-Msgid-Bugs-To: https://gitlab.gnome.org/GNOME/gimp/issues\\n"$ge|update No translations were fuzzy in any po files before this change. I remove all the fuzzy flags, but only if the msgid contains an ampersand, hence leaving appropriate fuzzy strings in (the ones where the source string changed since the last translation): :bufdo! %s/#, fuzzy\n\([^&]*\)&/\1\&/ge|update Then I replaced &amp; in msgstr (msgid was fixed through the automatic regeneration thanks to previous commit, but not the translations) with: :bufdo! %s/&amp;/\&/ge|update (3) Finally I did a manual `git diff` review to verify all is good. In particular, I had to fix a bunch of "E&xit". The string is probably too short so gettext heuristic failed to consider it likely the same as "E&amp;xit".
2022-08-23 02:56:16 +08:00
#: build/windows/installer/lang/setup.isl.xml.in:323
po-windows-installer: regenerate gettext files with `make update-po`.
2017-12-27 09:56:28 +08:00
msgid ""
"GIMP does not appear to be installed in the selected directory. Continue "
"anyway?"
msgstr ""
Update French translation (cherry picked from commit 66a833f8f2f382b67baf052c71fa05b0f1179bb9)
2019-12-30 17:15:55 +08:00
"GIMP ne semble pas être installé dans le dossier sélectionné. Souhaitez-vous "
Update French translation
2023-06-26 16:56:03 +08:00
"continuer malgré tout ?"
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%n%nImage on opening "
#~ "page of Setup by Alexia_Death%nImage on closing page of Setup by Jakub "
#~ "Steiner"
#~ msgstr ""
#~ "Installateur réalisé par Jernej Simonèiè, jernej-gimp@ena.si%n%nImage "
#~ "d'accueil de l'installateur par Alexia_Death%nImage de fin de "
#~ "l'installateur par Jakub Steiner"