GNOME.org
 

[gimp] Issue #6446: Typo fixes.

commit 6457394069e6b86b8180234a89c779e10c506410
Author: luz paz <luzpaz users noreply github com>
Date:   Wed Feb 24 12:33:03 2021 +0100

    Issue #6446: Typo fixes.

 INSTALL.in                                    |  4 ++--
 NEWS                                          | 14 +++++++-------
 app/core/gimpboundary.c                       |  2 +-
 app/core/gimpimage-new.c                      |  2 +-
 app/text/gimpfont.c                           |  4 ++--
 app/widgets/gimpimagepropview.c               |  2 +-
 desktop/org.gimp.GIMP.appdata.xml.in.in       |  2 +-
 devel-docs/debug-plug-ins.txt                 |  2 +-
 libgimp/gimp.c                                |  2 +-
 libgimp/gimpproceduredialog.c                 |  2 +-
 libgimpwidgets/gimplabelspin.c                |  2 +-
 plug-ins/script-fu/scripts/palette-export.scm |  2 +-
 plug-ins/script-fu/tinyscheme/CHANGES         |  2 +-
 13 files changed, 21 insertions(+), 21 deletions(-)
---
diff --git a/INSTALL.in b/INSTALL.in
index e692ef08b2..deb96ff7c0 100644
--- a/INSTALL.in
+++ b/INSTALL.in
@@ -100,7 +100,7 @@ header files installed.
      (for instance "v1.6.1" tag at time of writing), or simply install
      from a tarball or from your favorite package manager.
 
-     In particular, do NOT install tags or release tarballs versionned
+     In particular, do NOT install tags or release tarballs versioned
      "v2.y.z". GIMP depends on the version 1 of libmypaint and is
      incompatible with the version 2 (which is still experimental anyway
      and has no stable release at time of writing).
@@ -113,7 +113,7 @@ header files installed.
      last tag "v1.y.z" (e.g. "v1.3.1" at time of writing).
      In particular do NOT install from `master` branch which installs
      brushes incompatible with GIMP (the `master` branch brushes are
-     targetted to libmypaint upcoming v2, not v1).
+     targeted to libmypaint upcoming v2, not v1).
 
      Also this is a data packages and therefore it will install the
      pkg-config file inside `$PREFIX/share/pkgconfig/`. If you install
diff --git a/NEWS b/NEWS
index 75ec6026fa..701b3d8a7b 100644
--- a/NEWS
+++ b/NEWS
@@ -149,7 +149,7 @@ User Interface:
       Selection", same as you can Alt+click a mask for showing it
       without triggering a selection change. This allows these
       alternative actions to not be redundant of the equivalent actions
-      but complementary with a slightly different targetting behavior.
+      but complementary with a slightly different targeting behavior.
     * The various interactions with modifiers now catch the exact
       modifier combination they require, hence avoiding interaction
       cases running several actions (e.g. Alt-Ctrl on a layer thumbnail
@@ -257,7 +257,7 @@ Plug-ins:
     gimp_get_num_processors().
   - Improved plug-in debugging helper infrastructure: GIMP_PLUGIN_DEBUG
     has a new `fatal-criticals` option and better defaults. Developer
-    documentation got some rewritting and debugging code benefited from
+    documentation got some rewriting and debugging code benefited from
     refactorization.
 
 Installer:
@@ -328,7 +328,7 @@ User Interface:
       theme variant if available` checkbox, allowing for instance to use
       your system theme in its light variant everywhere except in GIMP.
       This option is checked by default as graphics software are often
-      prefered in dark modes.
+      preferred in dark modes.
     * Symbolic icon themes are now recolored automatically according to
       the theme colors (no theme and icon theme tweaking anymore to end
       up with dark on dark or light on light interfaces), except for
@@ -396,7 +396,7 @@ API:
 
   - `GimpPDB` is now a class to represent the PDB communication channel
     with GIMP. It is a singleton which exist exactly once per running
-    plug-in, hence it is not meant to be manually instanciated and can
+    plug-in, hence it is not meant to be manually instantiated and can
     only be returned by gimp_get_pdb(). It is mostly used to look up
     procedures declared by other plug-ins or by GIMP core, check if a
     given procedure exist and run the procedures.
@@ -430,7 +430,7 @@ API:
     (including the last used values) and generated GUI using
     prop_widgets to plug-ins. This is still a work-in-progress.
     Currently `GimpProcedure` run function is called with a
-    `GimpValueArray` whose values can be transfered into a
+    `GimpValueArray` whose values can be transferred into a
     `GimpProcedureConfig` by calling `gimp_procedure_config_begin_run()`
     or `gimp_procedure_config_begin_export()`.
   - `GimpDisplay` is now a class of its own.
@@ -503,7 +503,7 @@ API:
     which simplify various file handling issues (path formats, encoding,
     etc.) and brings new features (remote access, secure protocol
     support, etc.). We also got rid of the "filename" vs "raw_filename"
-    differenciation in parameters. Hence all libgimp* functions with
+    differentiation in parameters. Hence all libgimp* functions with
     these parameters have been updated as well.
   - gimp_image_metadata_load_finish() is now fully GUI/GTK-code free.
     The first consequence is that it is not in libgimpui anymore, but in
@@ -517,7 +517,7 @@ API:
     call the Preferences-set policy on an image. This may result in a
     dialog being presented to the user if `interactive` is TRUE and
     settings is "Ask what to do".
-    It is unecessary to call these functions when developing a new
+    It is unnecessary to call these functions when developing a new
     GimpLoadProcedure because the core will automatically do the right
     thing and call these on normal image loading workflow.
     Instead if a plug-in calls such GimpLoadProcedure through the PDB,
diff --git a/app/core/gimpboundary.c b/app/core/gimpboundary.c
index 253fe475c5..6b7ecfd59d 100644
--- a/app/core/gimpboundary.c
+++ b/app/core/gimpboundary.c
@@ -965,7 +965,7 @@ simplify_subdivide (const GimpBoundSeg *segs,
       /* start and endpoint are at the same coordinates */
       for (i = start_idx + 1; i < end_idx; i++)
         {
-          /* compare the sqared distances */
+          /* compare the squared distances */
           gint dist = (SQR (segs[i].x1 - segs[start_idx].x1) +
                        SQR (segs[i].y1 - segs[start_idx].y1));
 
diff --git a/app/core/gimpimage-new.c b/app/core/gimpimage-new.c
index ade36025da..ab19e1acbc 100644
--- a/app/core/gimpimage-new.c
+++ b/app/core/gimpimage-new.c
@@ -319,7 +319,7 @@ gimp_image_new_copy_drawables (GimpImage *image,
           gimp_item_set_linked (GIMP_ITEM (new_layer),
                                 gimp_item_get_linked (iter->data), FALSE);
 
-          /* Visibility, mode and opacity mimick the source image if
+          /* Visibility, mode and opacity mimic the source image if
            * multiple items are copied. Otherwise we just set them to
            * defaults.
            */
diff --git a/app/text/gimpfont.c b/app/text/gimpfont.c
index 42dc236b7a..2332ceefd8 100644
--- a/app/text/gimpfont.c
+++ b/app/text/gimpfont.c
@@ -428,13 +428,13 @@ gimp_font_get_sample_string (PangoContext         *context,
     /* CJK are first because fonts that support these characters
      * presumably are primarily designed for it.
      *
-     * Though not a universal rules, most fonts targetting Korean will
+     * Though not a universal rules, most fonts targeting Korean will
      * also have the ideographs as they were used historically (and
      * still in some cases). As for Japanese, ideographs are still
      * definitely used daily. After all the block is called "*CJK*
      * (Chinese-Japanese-Korean) Unified Ideographs". So let's give the
      * Chinese representation less priority towards finding
-     * Korean/Japanese targetting.
+     * Korean/Japanese targeting.
      * Then we prioritize Korean because many fonts for Korean also
      * design Hiragana/Katakana blocks. On the other hand, I could see
      * very few (none so far) Japanese fonts designing also Hangul
diff --git a/app/widgets/gimpimagepropview.c b/app/widgets/gimpimagepropview.c
index 584021e095..e9563f9485 100644
--- a/app/widgets/gimpimagepropview.c
+++ b/app/widgets/gimpimagepropview.c
@@ -550,7 +550,7 @@ gimp_image_prop_view_realize (GimpImagePropView *view,
                               gpointer           user_data)
 {
   /* Ugly trick to avoid extra-wide dialog at construction because of
-   * overlong file path. Basically I give a reasonnable max size at
+   * overlong file path. Basically I give a reasonable max size at
    * construction (if the path is longer, it is just ellipsized per set
    * rules), then once the widget is realized, I remove the max size,
    * allowing the widget to grow wider if ever the dialog were
diff --git a/desktop/org.gimp.GIMP.appdata.xml.in.in b/desktop/org.gimp.GIMP.appdata.xml.in.in
index 224ff8a73f..e63c2d7983 100644
--- a/desktop/org.gimp.GIMP.appdata.xml.in.in
+++ b/desktop/org.gimp.GIMP.appdata.xml.in.in
@@ -91,7 +91,7 @@
           The action search now shows all actions even inactive ones (yet pushed below)
           </_li>
           <_li>
-          Fonts targetted for Korean and Japanese language show appropriate characters
+          Fonts targeted for Korean and Japanese language show appropriate characters
           </_li>
           <_li>
           Different default tools depending on pointer device type
diff --git a/devel-docs/debug-plug-ins.txt b/devel-docs/debug-plug-ins.txt
index 101eeca081..9dbe570368 100644
--- a/devel-docs/debug-plug-ins.txt
+++ b/devel-docs/debug-plug-ins.txt
@@ -134,7 +134,7 @@ To get a backtrace for a plug-in in any language:
      ( e.g. ">GIMP_PLUGIN_DEBUG=all,fatal-criticals gimp" )
      Expect GIMP to start normally.
 
-  2. In GIMP, do somthing that would invoke a plugin.
+  2. In GIMP, do something that would invoke a plugin.
 
      Whenever the specified plug-in processes generate log events of
      the specified levels or worse, libgimp will print or offer to print
diff --git a/libgimp/gimp.c b/libgimp/gimp.c
index 0c686efe1f..2ccc9b3499 100644
--- a/libgimp/gimp.c
+++ b/libgimp/gimp.c
@@ -734,7 +734,7 @@ gimp_export_iptc (void)
  * preferences. This information can be used by plug-ins wishing to
  * follow user settings for multi-threaded implementations.
  *
- * Returns: the prefered number of threads to use.
+ * Returns: the preferred number of threads to use.
  *
  * Since: 3.0
  **/
diff --git a/libgimp/gimpproceduredialog.c b/libgimp/gimpproceduredialog.c
index a52f4c7aac..0d764cc2aa 100644
--- a/libgimp/gimpproceduredialog.c
+++ b/libgimp/gimpproceduredialog.c
@@ -1397,7 +1397,7 @@ gimp_procedure_dialog_check_mnemonic (GimpProcedureDialog *dialog,
  *                              exists yet
  * @properties: (nullable) (element-type gchar*): the list of property names.
  *
- * A generic function to be used by various publich functions
+ * A generic function to be used by various public functions
  * gimp_procedure_dialog_fill_*_list(). Note in particular that
  * @container is taken over by this function which may return it or not.
  * @container is assumed to be a floating GtkContainer (i.e. newly
diff --git a/libgimpwidgets/gimplabelspin.c b/libgimpwidgets/gimplabelspin.c
index 33ed62387c..d2d93a6c7c 100644
--- a/libgimpwidgets/gimplabelspin.c
+++ b/libgimpwidgets/gimplabelspin.c
@@ -175,7 +175,7 @@ gimp_label_spin_init (GimpLabelSpin *spin)
 
   /* We want the adjustment to exist at init so that construction
    * properties can apply (default values are bogus but should be
-   * properly overrided with expected values if the object was created
+   * properly overridden with expected values if the object was created
    * with gimp_label_spin_new().
    */
   priv->spin_adjustment = gtk_adjustment_new (0.0, 0.0, 100.0, 1.0, 10.0, 0.0);
diff --git a/plug-ins/script-fu/scripts/palette-export.scm b/plug-ins/script-fu/scripts/palette-export.scm
index 0286c4bad7..167f8e790d 100644
--- a/plug-ins/script-fu/scripts/palette-export.scm
+++ b/plug-ins/script-fu/scripts/palette-export.scm
@@ -62,7 +62,7 @@
   )
 
 ; -----------------------------------------------------------------------------
-; Color convertors
+; Color converters
 ; -----------------------------------------------------------------------------
 
 ; The standard way for representing a color would be a list of red
diff --git a/plug-ins/script-fu/tinyscheme/CHANGES b/plug-ins/script-fu/tinyscheme/CHANGES
index 2f7a33a16f..05a6b7349f 100644
--- a/plug-ins/script-fu/tinyscheme/CHANGES
+++ b/plug-ins/script-fu/tinyscheme/CHANGES
@@ -162,7 +162,7 @@ Version 1.28
     Dennis Taylor remarked that OP_VALUEPRINT reset sc->value instead
     of preserving it. He submitted a modification which I adopted
     partially. David Hovemeyer sent me many little changes, that you
-    will find in version 1.28, and Partice Stoessel modified the
+    will find in version 1.28, and Patrice Stoessel modified the
     float reader to conform to R5RS.
 
 Version 1.27
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]