pixel

Running the PNM fuzzing target, this input produces a crash due to an attempt to multiply with overflow:

[80, 54, 10, 52, 50, 57, 52, 56, 50, 57, 52, 56, 35, 56, 10, 52, 10, 48, 10, 12, 12, 56]

It looks like the offending multiply is this: https://github.com/image-rs/image/blob/0f1c38a97ec809f399a2a5edfb85c7e17fcd46ec/src/codecs/pnm/decoder.rs#L608

I suspect this should be a `checke

This is a Good First Issue to fix the following typos

./video_to_ascii/cli.py:8: usefull ==> useful
./video_to_ascii/render_strategy/ascii_strategy.py:72: correcly ==> correctly
./video_to_ascii/render_strategy/ascii_strategy.py:72: builded ==> built
./video_to_ascii/render_strategy/image_processor.py:1: usefull ==> useful
./video_to_ascii/render_strategy/image_processor.py:14: apropia

Is your feature request related to a problem? Please describe.
All the data need to be logged. That's why I think that the logging must be added to the image-comparison.

Describe the solution you'd like
The solution is to add SLF4J based on Log4j 2.* version.

Describe alternatives you've considered
Instead of the Log4J can be used Logback or even JUL(java.util.logging).
Th