Adding upstream version 2.10.34.upstream/2.10.34upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

2 files changed, 168 insertions, 0 deletions

diff --git a/README b/README
new file mode 100644
index 0000000..171e49d
--- /dev/null
+++ b/README
@@ -0,0 +1,103 @@
+                   ------------------------------
+                   GNU Image Manipulation Program
+                         2.10 Stable Branch
+                   ------------------------------
+
+This is a stable release in the GIMP 2.10 series.
+
+GIMP 2.10 replaces earlier GIMP 2.x versions. It is advised that you
+uninstall them before installing GIMP 2.10. If you want to keep your
+older GIMP 2.x installation in parallel to GIMP 2.10, you have to
+choose a separate prefix which is not in your default library search
+path. Otherwise your previous GIMP installation will start to use the
+new libraries. You have been warned.
+
+If you think you found a bug in this version, please make sure that it
+hasn't been reported earlier and that it is not just new stuff that is
+still being worked on and obviously not quite finished yet.
+
+If you want to hack on GIMP, please read the file HACKING. For
+detailed installation instructions, see the file INSTALL.
+
+
+1. Web Resources
+================
+
+GIMP's home page is at:
+
+	https://www.gimp.org/
+
+Please be sure to visit this site for information, documentation,
+tutorials, news, etc.  All things GIMP-ish are available from there.
+
+The automated plug-in registry is located at:
+
+	https://registry.gimp.org/
+
+There you can get the latest versions of plug-ins, using a convenient
+forms-based interface.
+
+The latest version of GIMP can be found at:
+
+	https://www.gimp.org/downloads/
+
+
+2. Mailing Lists
+================
+
+We have several mailing lists dedicated to GIMP user and development
+discussion.  There is more info at
+
+	https://www.gimp.org/mail_lists.html
+
+Links to several archives of the mailing lists are included in that page.
+
+Gimp-user-list is a mailing list dedicated to user problems, hints and
+tips, discussion of cool effects, etc.  Gimp-developer-list is oriented
+to GIMP core and plug-in developers.  Gimp-gui-list is for discussing
+about GIMP interface to improve user experience. Most people will only
+want to be subscribed to gimp-user-list. If you want to help develop
+GIMP, the gimp-developer mailing list is a good starting point; if you
+want to help with GUI design, the gimp-gui list is where you want to
+subscribe.
+
+
+3. IRC
+======
+
+And finally, for the real junkies, there is an IRC channel devoted to
+GIMP. On GIMPNet (a private free software oriented network) there is
+#gimp.  Many of the developers hang out there.  Some of the GIMPNet
+servers are:
+
+	irc.gimp.org:6667
+	irc.us.gimp.org:6667
+	irc.eu.gimp.org:6667
+
+
+4. Customizing
+==============
+
+The look of GIMP's interface can be customized like any other GTK app
+by editing the ~/.gtkrc-2.0 file or by using "themes" (ready-made
+customizations).  For downloadable themes and further details, see
+http://art.gnome.org/themes/gtk2 . Additionally, GIMP reads the file
+~/.config/GIMP/2.10/gtkrc so you can have settings that only apply to GIMP.
+
+Included is a set of keybindings similar to those in Adobe Photoshop.
+You can find them in the ps-menurc file.  To use them, copy this file
+to ~/.config/GIMP/2.10/menurc. You can also manually change the keybindings
+to any of your choice by editing ~/.config/GIMP/2.10/menurc.
+
+
+Have fun,
+
+  Spencer Kimball
+  Peter Mattis
+  Federico Mena
+  Manish Singh
+  Sven Neumann
+  Michael Natterer
+  Dave Neary
+  Martin Nordholts
+  Jehan
diff --git a/README.i18n b/README.i18n
new file mode 100644
index 0000000..84f4ccd
--- /dev/null
+++ b/README.i18n
@@ -0,0 +1,65 @@
+This file contains some important hints for translators.
+
+
+The current status of the GIMP translation can be checked at
+
+  https://l10n.gnome.org/module/gimp
+
+
+Translation of the GNU Image Manipulation Program is handled by the
+GNOME Translation Project (see https://l10n.gnome.org/). If you want to
+help, we suggest that you get in touch with the translation team of
+your language (see https://l10n.gnome.org/teams/).
+
+
+GIMP is different
+
+ GIMP is a complex application which has a bunch of scripts and
+ plug-ins that all want to be internationalized. Therefore there is
+ not one catalog but many. For a full translation of GIMP's UI, you
+ will have to add translations for the following catalogs:
+
+   po/gimp20.po                                       --  the core
+   po-libgimp/gimp20-libgimp.pot                      --  the libgimp library
+   po-plugins/gimp20-std-plugins.pot                  --  the C plug-ins
+   po-python/gimp20-python.pot                        --  the pygimp plug-ins
+   po-script-fu/gimp20-script-fu.pot                  --  the script-fu scripts
+   po-tips/gimp20-tips.pot                            --  the startup tips
+   po-windows-installer/gimp20-windows-installer.pot  --  the windows installer
+
+ If you are looking for the translations of gimp-perl, please note that
+ gimp-perl has been moved into it's own git module called
+ gimp-perl.
+
+
+GIMP Tips dialog
+
+ In addition to message catalogs GIMP provides a file with tips that
+ are displayed in the Tips dialog. This file is in XML format and can
+ be found in the tips directory. The english tips messages are
+ extracted from gimp-tips.xml.in so translators can use the usual
+ tools to create a <lang>.po file that holds the translations. All
+ translations are then merged into gimp-tips.xml with language
+ identifiers taken from the po filename.
+
+ GIMP needs to know what language it should select from gimp-tips.xml.
+ Therefore, there's the special message "tips-locale:C" in the main
+ message catalog that needs to be translated correctly. For a german
+ translation of the tips this would look like this:
+
+ #: ../app/dialogs/tips-parser.c:188
+ msgid "tips-locale:C"
+ msgstr "tips-locale:de"
+
+
+Localization of third-party plug-ins
+
+ Third-party plug-ins (plug-ins that are not distributed with GIMP)
+ can't have their messages in the gimp-std-plugins textdomain.  We
+ have therefore provided a mechanism that allows plug-ins to install
+ their own message catalogs and tell GIMP to bind to that
+ textdomain. This is necessary so that GIMP can correctly translate
+ the menu paths the plug-in registers. Basically the plug-in has to
+ call gimp_plugin_domain_add() or gimp_domain_plugin_add_with_path()
+ before it registers any functions. Have a look at the script-fu
+ plug-in to see how this is done in detail.