pixel

Any comments on the questions below are welcome.

In light of #1318 and previously #1291 , #1232 , #1231 , #1072 , #792 (possibly more), I conclude that opening files with the functions in the main module is at least misunderstood but quite possibly a bad interface in itself. It's often not clear how to do combine aspects of these methods by performing parts of them manually—such as how to open

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