| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
| |
This is a more general dependency and eases packaging on Ubuntu.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
[dgit (3.12) quilt-fixup]
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
[dgit (3.11) quilt-fixup]
|
| | |
|
| |
|
|
| |
[dgit (3.11) quilt-fixup]
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is more or less a refactoring release, but with deep changes in the
tools that I was hoping to look into for a long time.
The codebase is in a very consistent state now, also thanks to the
introduction of a set of common utility-functions.
What really makes me think is the fact that it takes so many iterations
and a high level of detail to get the library handling and I/O right.
It just makes you wonder how much software is out there that is full
of little subtle bugs that might blow up in your face some day.
Thanks for all the feedback!
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
To be honest, it can happen too easily that the user forgets to put
the colour in quotation marks, yielding in the rest of the
pipeline to be discarded as a comment.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
so they align with the manpages.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I noticed that it would be beneficial to release the invert.c code
listing under a very permissive license.
I like the style of the "Copy me if you can"-License, but thought
that 0BSD would make it even clearer that everyone can do whatever
he wants with this code.
The code itself was not bad beforehand, but lacked some elementary
features like checked flushing at the end and proper error messages.
I also reworked the data structures a bit to make it more appealing
and clearer where the "guts" of the code are (i.e. in invert()).
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Make them more consistent, and only maintain a list of the conversion
tools in farbfeld.5.
Refine the wording on the jpg-manpages.
|
| | |
| |
| |
| |
| | |
Rework the introductory paragraph and show examples directly afterwards.
If people are interested in the tl;dr-sections, they can then read on.
|
| | |
| |
| |
| |
| |
| | |
Else the user might be left wondering what happened. The output from
imagemagick might not be the nicest in the world, but it's bearable for
some given edge-cases.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Unix philosophy teaches us that tools should strive to output only
necessary diagnostic information and also reflect errors properly with
the return value.
There were three subtle problems with 2ff:
1) If the farbfeld-passthrough failed, it would return 1 instead
of 1.
2) If the first 8 bytes contained a NUL byte, bash would print
an ugly warning message. Passing it through tr -d '\0' fixes
that.
3) Lack of comments. I added some to make the structure even
clearer, also including using an if-else-structure.
I removed the 2ff error message; the tools themselves print proper
messages already.
|
| | | |
|
| | |
| |
| |
| | |
It's not very useful for the reader any more.
|
| | |
| |
| |
| | |
instead of per-tool-settings.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
For small images, it could happen that the output stream would not be
flushed before exit(), resulting in a lack of error-reporting on
a full device. Using fflush(), a function I first introduced in sbase,
we do the flushing before returning manually and report errors if they
occurred.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The truncation issue is solved now by checking the return values. Maybe
for small images where the FILE-buffer is not flushed early enough we
can rethink that.
The utility functions were written to the extent it was desired.
I added a note not to forget to take a look at the part in the jpg-code
which does the color mixing.
|
| | |
| |
| |
| |
| | |
We make use of the utility functions for parsing the color mask and
other things and generally align the code with the general coding style.
|
| | |
| |
| |
| |
| |
| |
| | |
We split out the libpng-setup into a separate function, it is very very
ugly.
The code also received a general cleanup and aligns itself much better
with the general coding style and structure.
|
| | |
| |
| |
| |
| | |
I chose to go with a row-based-approach here, which is a bit easier
to read and is somewhat "closer" to the input data.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
First of all, there was lots of libjpeg-specific cruft that just didn't
have any right to exist (METHODDEF(), strange typedefs, use of the
internal memory pool for no reason). This is gone now.
Additionally, we make use of the save and proven utility functions and
in general the code should be more well-separated now.
What is left to do is clear up the part where we mix the colors with the
mask.
|
| | | |
|
