Commit 64573940 authored by luz paz's avatar luz paz Committed by Jehan
Browse files

Issue #6446: Typo fixes.

parent 72d1f9cb
Pipeline #260468 failed with stages
in 32 minutes
......@@ -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
......
......@@ -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,
......
......@@ -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));
......
......@@ -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.
*/
......
......@@ -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
......
......@@ -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
......
......@@ -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
......
......@@ -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
......
......@@ -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
**/
......
......@@ -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
......
......@@ -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);
......
......@@ -62,7 +62,7 @@
)
; -----------------------------------------------------------------------------
; Color convertors
; Color converters
; -----------------------------------------------------------------------------
; The standard way for representing a color would be a list of red
......
......@@ -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
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment