[gimp-web/testing] Preparing GIMP 2.10.12 news.

[Jehan <jehanp src gnome org>]

commit e175e18cf952a5584473216ffd9fee53ae576a94
Author: Jehan <jehan girinstud io>
Date:   Wed May 8 15:47:44 2019 +0900

    Preparing GIMP 2.10.12 news.
    
    The date was completely randomly set, with the hope we will release this
    version before LGM! :-)
    
    It's only a first draft which gets the gist of this new release.

 .../news/2019-05_GIMP-2.10.12_Released/index.md    | 166 +++++++++++++++++++++
 1 file changed, 166 insertions(+)
---
diff --git a/content/news/2019-05_GIMP-2.10.12_Released/index.md 
b/content/news/2019-05_GIMP-2.10.12_Released/index.md
new file mode 100644
index 00000000..8b68fa42
--- /dev/null
+++ b/content/news/2019-05_GIMP-2.10.12_Released/index.md
@@ -0,0 +1,166 @@
+Title: GIMP 2.10.12 Released
+Date: 2019-05-25
+Category: News
+Authors: Wilber
+Slug: gimp-2-10-12-released
+Summary: GIMP 2.10.12 released: free the bugs!
+Status: draft
+
+GIMP 2.10.12 is mostly a bug fix release as some annoying bugs were
+discovered, which is to be expected after a 2.10.10 with so many
+changes!
+
+Still, some very cool improvements are also available, in particular for
+Curves editing!
+
+# Improvement and features
+## Improving curves editing and Curves tool
+### Generic Curves interaction
+
+The interaction with curves in general has been greatly enhanced, which
+is an improvement both to the Curves tool and all other places where
+curves need tweaking (currently paint dynamics and input device settings):
+
+#### Use relative motion when dragging point
+
+When dragging an existing curve point, it won't "jump" anymore to the
+cursor position upon pressing the button. Instead it will move
+relatively to its current position as the cursor moves. This allows
+selecting a point with a quick click without moving it, and adjusting
+a point position more easily.
+
+Additionally, when the cursor hovers above a point, or when dragging a
+point, the coordinate indicator now show the point's position, rather
+than the cursor's.
+
+#### Snap to curve when holding Ctrl
+
+When holding down Ctrl while adding or dragging a point, the
+y-coordinate will snap to the original curve.
+This is particularly useful for adding points along the
+curve, without changing their y-coordinate.
+
+Likewise, the coordinate indicator shows the snapped coordinate.
+
+### Curves tool specific interaction
+
+Additionally some improvements are specific to the Curves tool:
+
+#### Numeric input of Curves tool points
+
+Two new spin-buttons labelled "*Input*" and "*Output*" are now available
+in the Curves tool interface. They allow setting the selected point's
+coordinates numerically and accurately if needed.
+
+#### Add smooth or corner curve-point types
+
+Control points can now be either **smooth** or **corner** points.
+Smooth points produce a smooth curve, while corner points result in
+sharp angles (previously, all points were smooth and this is still the
+default).
+
+Corner points are displayed using a diamond shape, instead of a circle
+and the type can be changed in the Curves tool.
+
+## TIFF now has layer support!
+
+Thanks to Tobias Ellinghaus, well known as a Darktable developer, TIFF
+can now export images without merging layers.
+
+## Support of user-installed fonts on Windows
+
+Though not fully tested, we now have a temporary support of a new
+Windows 10 feature. Windows 10 users indeed now have the ability to
+[install fonts without admin
+permissions](https://blogs.windows.com/windowsexperience/2018/06/27/announcing-windows-10-insider-preview-build-17704/#kt29svdWTKQ4QIx3.97)
+since a recent update.
+
+Therefore we add this non-admin font folder to our search path when
+running GIMP. As I said though, it should be only a temporary workaround
+since hopefully this [should be
+supported](https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/144)
+by the upstream library used to manage fonts, *fontconfig*.
+
+Note also that it is not fully tested because of our lack of Windows
+developers. Therefore we are mostly hoping it will work as expected, and
+this is a good time to make a call again:
+
+**Are you a Windows developer?  Do you love GIMP? [Please
+contribute](https://gitlab.gnome.org/GNOME/gimp/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=OS%3A%20Windows)!**
+
+Seriously none of our current developers use Windows and bugs are
+piling up in our bug tracker. We are happy to do the occasional good
+deeds, but there are limits to what we can do for a platform we don't
+use. On the other hands, we happily welcome patches and new
+contributors! Just come help us, we don't bite!
+
+## Incremental mode to the Dodge/Burn tool
+
+The Dodge and Burn tools got a new "Incremental" option which,
+similarly to the Paintbrush, Pencil, and Eraser tools, applies the
+effect incrementally as the pointer moves.
+
+## Free Select tool creates preliminary selection
+
+One of the GIMP 2.10.0 changes which annoyed many people was that the
+Free Select tool was not creating a selection immediately when the
+selection is closed. One was forced to perform an additional
+confirmation step (`Enter` or `double-click`).
+
+This was done on purpose because we wanted to leave ability to tweak the
+free selection. Yet it could obviously be better, proof being the
+Rectangle selection, which still allowed to edit the rectangle even
+though a selection was pre-created. The Free Select tool now works the
+same. Even though a preliminary selection exists (allowing to directly
+copy or delete a contents without additional step), you will still be
+able to edit this free selection as long as you don't start another
+selection nor change tools.
+
+# Bug fixing
+
+Many bugs were fixed, some more severe than others (in particular a
+few crashes), as well as some code cleaning, factorization, and so on.
+The usual deal!
+
+More than the new features, we actually thought these issues were enough
+to warrant this new release.
+
+## Color space mixup on exporting images
+
+In particular several people noticed that exporting some images ended up
+in washed-up colors. This was because in some cases, we were exporting
+by error sRGB colors with a linear profile (especially visible since
+GIMP 2.10.10 as we were exporting profiles by default even when using a
+default GIMP profile).
+
+Now we are always correctly exporting an explicitly set profile as-is,
+and pixel colors are stored according to this profile expectation. On
+the other hand, if no explicit profile was set, and if the export format
+is 8-bit only (such as JPEG), we transform the data to sRGB in order to
+avoid posterization and shadow artifacts.
+
+Note that there are still edge cases which we don't find optimal yet,
+regarding how profiles are handled. These should all be greatly improved
+when we will merge the "Space Invasion" code (an ongoing mid-term
+project, as we were already [talking about it when releasing GIMP
+2.10.8](https://www.gimp.org/news/2018/11/08/gimp-2-10-8-released/#whats-next)).
+This code merge should hopefully happen soon enough!
+
+# Around GIMP
+## GEGL and babl
+
+TODO
+
+# What's next
+
+Though it gets less visibility, work on upcoming GIMP 3 continues and is
+going well. We will give more news soon enough. For the time being,
+don't forget you [donate to the project and personally fund several
+GIMP developers](https://www.gimp.org/donating/), as a way to give back
+and to accelerate GIMP development.
+
+Moreover, we remind that members of the GIMP team will be at the [Libre
+Graphics Meeting 2019](https://libregraphicsmeeting.org/2019/) in
+**Saarbruecken, Germany**, from May 29 to June 2, and have talks
+planned. We would be happy to meet any person creating awesomeness with
+GIMP!