Skip to content

Commit

Permalink
Corrected grammar
Browse files Browse the repository at this point in the history
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
  • Loading branch information
radarhere and hugovk committed Mar 6, 2022
1 parent 2b9cc3c commit 8e9d320
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/handbook/writing-your-own-image-plugin.rst
Original file line number Diff line number Diff line change
Expand Up @@ -354,7 +354,7 @@ Setup
The current conventions are that the codec setup function is named
``PyImaging_[codecname]DecoderNew`` or ``PyImaging_[codecname]EncoderNew``
and defined in ``decode.c`` or ``encode.c``. The Python binding for it is
named ``[codecname]_decoder`` or ``[codecname]_encoder`` and is setup from
named ``[codecname]_decoder`` or ``[codecname]_encoder`` and is set up from
within the ``_imaging.c`` file in the codecs section of the function array.

The setup function needs to call ``PyImaging_DecoderNew`` or
Expand Down Expand Up @@ -400,7 +400,7 @@ Alternatively, if ``pulls_fd`` or ``pushes_fd`` is set, then the decode or
encode function is called once, with an empty buffer. It is the codec's
responsibility to transform the entire tile in that one call. Using this will
provide a codec with more freedom, but that freedom may mean increased memory
usage if entire tile is held in memory at once by the codec.
usage if the entire tile is held in memory at once by the codec.

If an error occurs, set ``state->errcode`` and return -1.

Expand Down

0 comments on commit 8e9d320

Please sign in to comment.