other words appear in the file path to the source code.

blending for drawing diagonal lines.

Ahti Leppänen.

to each detector individually.  This way one detector doesn't stomp on the
output of another detector.

directly on already loaded data rather than needing to use an XML file as
input.

some effort to detect them and output an identity matrix in that case.

small window when the first image was bigger than the screen.

Also added an overload of operator() for pyramid_down that takes just
a single image and downsamples it.

extract_fhog_features().  Also fixed a minor bug where empty planar HOG feature
maps had 0 planes in them rather than 31 empty planes as the spec says they
should.

what scanner type it is using.

This is the dlib/image_processing/generic_image.h file.  Then I changed all the
image processing functions so that they use this interface.  All the changes
are very minor, but there are just a lot of them.

Any user code that was using array2d objects to represent images will still
work.  However, this change makes it so that users can use their own custom
image objects with dlib by simply implementing a few global functions for their
image object.

In particular, array2d::set_size() now simply allows any row and
column sizes so long as they are non-negative.

byte.  This makes their serialization format the same as the format for std::string.  I had
to revert the previous mod for this because it didn't work in visual studio.  This change
fixes that.  The code should still be able to read all previously serialized data correctly.
Moreover, any char arrays that aren't null terminated will still be read and written in
their entirety.

serialized using the same format as std::string.  Previously, the
trailing 0 was also saved so if you deserialized them into a std::string
you ended up with a trailing 0 in the std::string which isn't what you
want.

code.  Also made the initial bracketing step a little more efficient.

find_min_single_variable() and find_max_single_variable() routines.  Also made
these functions a little more robust to unusual objective functions.

that happened when using find_max_single_variable().