[gimp-web] Update GIMP 2.99.2 news.

[Jehan <jehanp src gnome org>]

commit c7a07a707a8139024ecee4f3d8fd3e80523f7022
Author: Jehan <jehan girinstud io>
Date:   Wed Oct 28 01:23:37 2020 +0100

    Update GIMP 2.99.2 news.

 .../2020/2020-06_GIMP-2.99.2_Released/index.md     | 81 ++++++++++++++++++----
 1 file changed, 66 insertions(+), 15 deletions(-)
---
diff --git a/content/news/2020/2020-06_GIMP-2.99.2_Released/index.md 
b/content/news/2020/2020-06_GIMP-2.99.2_Released/index.md
index 86cb4d8f..7180e488 100644
--- a/content/news/2020/2020-06_GIMP-2.99.2_Released/index.md
+++ b/content/news/2020/2020-06_GIMP-2.99.2_Released/index.md
@@ -15,7 +15,7 @@ Release highlights:
 - Major refactoring and cleanup
 - New plug-in API
 - Plugins now possible with Python 3, JavaScript, Lua, and Vala
-- Space invasion completed
+- More space invasion
 - Render caching available for better performance
 
 <figure>
@@ -39,7 +39,7 @@ TODO: maybe a screenshot GIMP 2.10.22 and GIMP 2.99.2 side by side?
 
 ### High pixel density displays
 
-One of the main issues of GTK2 for nowaday display material was the
+One of the main issues of GTK2 for screens used these days was the
 absent support for high pixel density displays (e.g. small screens with
 high resolution or big screens with extremely high resolution) which
 become more widespread nowadays, especially among graphics
@@ -70,18 +70,19 @@ It is to be noted that some touch support work had been experimented a
 while ago but has not been finished because we realized this was not a
 priority compared to some other features (we are talking about specific
 touch features, like zooming, panning, rotating or other gestures made
-with fingers; *touch* as an input device already works and was also
-already working with GIMP 2 versions). Touch gestures are very nice and
-awesome but also sometimes becomes a burden. Actually many professional
+with fingers; *touch* as an input device already works and was already
+working with GIMP 2 versions). Touch gestures are very nice and awesome
+but also sometimes becomes a burden. Actually many professional
 graphists even disable touch-sensitivity to prevent unwanted inputs
 while working with a stylus (high-end tablets often come with a physical
-switch for this nowadays, and this can also be disabled by tablet
+switch for this nowadays, and this can also be disabled in tablet
 settings). With this in mind, we have decided to not make it a priority
-and it is therefore not sure if GIMP 3 will come with specific gesture
-support. This is not to say that we don't want it, and we welcome any
-patches from anyone willing to make it one's priority.
+compared to some other work-in-progress so it is therefore not sure if
+GIMP 3 will come with specific gesture support. This is not to say that
+we don't want it, and we welcome any patches from anyone willing to make
+it one's priority.
 
-*Work-in-progress*: some more work needs to be done to simplify device
+*Work-in-progress*: more work needs to be done to simplify device
 support as a lot of legacy features are either not needed anymore
 nowadays or can be better presented. Some Wayland-specific handling may
 be in order as well, since Wayland brings news abilities to input
@@ -99,7 +100,8 @@ Moreover symbolic icon theme are much better supported. They will follow
 the theme-set foreground and background colors. For anyone who changed
 one's theme in GIMP 2.10 from dark to a light theme, you probably
 remember you also had to switch the symbolic icon themes manually. This
-won't be necessary anymore.
+won't be necessary anymore as symbolic icons will be recolored according
+to your theme.
 
 Finally a same theme may propose both a dark and light variant so the
 Theme preferences shows a "*Use dark theme variant if available*"
@@ -151,8 +153,8 @@ export process.
 
 ## Multi-layer selection
 
-One of the major annoyance of layer management in GIMP until now was the
-inability to select more than one layer. Before even being a pixel
+One of the major annoyances of layer management in GIMP until now was
+the inability to select more than one layer. Before even being a pixel
 processing feature, this is an organizational bother for professional
 and advanced users who often use several dozens of layers in their most
 complicated images. Imagine having to move 20 layers into a layer group,
@@ -214,6 +216,15 @@ that a single-file plug-in working for the GIMP 2.10 series can be
 ported to GIMP 3 in between 5 and 30 minutes. We will provide a porting
 documentation when releasing GIMP 3.
 
+One of the first step you can work on if you already have working
+plug-ins on GIMP 2.10.x is to make sure you don't use any deprecated
+functions. All deprecated functions have been removed from GIMP 3 API
+(since we bump the major version, this is the time to make a clean
+slate). We compiled a [list of functions removed and their
+replacement](https://gitlab.gnome.org/GNOME/gimp/-/blob/master/devel-docs/GIMP3-plug-in-porting-guide/removed_functions.md).
+You can already do this part of the port while still targetting GIMP
+2.10.x versions.
+
 #### Object API
 
 Among the noteworthy changes, we moved away from object IDs to real
@@ -315,9 +326,15 @@ can now be scripted (additionally to C and C++ of course) with:
 
 One of the main difference with how GIMP used to be scriptable, with
 Python 2 notably, is that an additional layer API is not needed anymore.
+
+Also GIMP 2 bindings used to be made around the PDB protocol which is
+only a subset of the full C `libgimp` API. The new bindings are built
+around `libgimp` itself. This basically mean that plug-ins in Python 3
+or Javascript for instance will have the same possibilities as C
+plug-ins. This is a bright new world for GIMP plug-in developers!
+
 This means in particular that the API is basically the same for all
 these languages, except for language idiosyncracies.
-
 Therefore if finding an intersection of a drawable with a selection in C
 is:
 
@@ -403,9 +420,39 @@ plug-in ecosystem with GIMP 3. They are the first step of
 "self-documenting demo plug-ins" (while doing something a bit more
 exciting that a bare "Hello World").
 
+### Documentation
+
+We have started to write down some documentation regarding plug-in
+development in GIMP 3, and will progressively start to publish some
+tutorials. Hopefully we will even be able to relaunch our developer
+website who have been abandonned for too many years.
+
+We really hope that GIMP 3 will breath some new life into the GIMP
+plug-in ecosystem!
+
 ## Extensions
 
-TODO
+Extensions are a new file format which is basically only a wrapper of
+data (brushes, splash screens, patterns, dynamics…) or plug-ins,
+associated with some metadata (name, description, screenshots, version,
+requirements…). The goal will be to allow plug-in developers to publish
+their work on a repository allowing anyone to search third-party
+plug-ins, install/uninstall, enable/disable and update them, all within
+GIMP.
+
+The menu `Edit > Manage Extensions` shows the base dialog. In the
+"System Extensions" tab in particular, you will notice an "Official Demo
+Plug-ins" which is our first extension, which in fact bundles all the
+Goat Exercises plug-ins we talked about earlier. If you click the
+switch, you will notice after a restart (right now you have to restart
+GIMP to see the effect) that the menu category `Filters > Development >
+Goat Exercises`.
+
+We will explain further this feature when we will have developed more,
+and in particular we will provide appropriate documentation for
+extension creation.
+It is definitely something plug-in and resource creators should look
+forward to, as it will help share your creations with others.
 
 ## Space invasion
 
@@ -479,6 +526,10 @@ flatpak make-current --user org.gimp.GIMP stable
 As usual, we provide a Windows installer for GIMP, you will find it on the
 [Development Downloads page](https://www.gimp.org/downloads/devel/).
 
+Some features may be missing. In particular, you won't find the
+Javascript binding on the Windows build because of the complexity of
+some dependencies.
+
 ### macOS
 
 Our macOS packager has still not fully returned, so unfortunately there