Remove "XQ" from comment, not sure what it was.

Perhaps I intended "XQ" to mean a sequence of fragments?
Or it was to be a UN that was a sequence?  In any case,
"XQ" was never used for anything in the code.
Fix library loading in TestDICOMJava.

It was using vtkJavaTesting.Initialize() to load the VTK libraries,
which doesn't in some installations.  Try using Java's own load path
first, before falling back on vtkJavaTesting.Initialize().
Add vtkPythonCore to the python link libraries.

The debian packaging system requires libraries to be fully linked,
transitive linking alone is not sufficient.
Comply with cmake policy CMP0042 (new in cmake 3).
Link libpython on UNIX.

Historically, on UNIX systems, vtk-python modules did not link to
libpython. Instead, they resolved their symbols when they were loaded.
Debian packages, however, require all libraries to be fully linked.
Make all install subdirs configurable.
More java corrections: manifest, target version.
Fix typo in docs.  Thanks to Mathieu Malaterre.
Add missing target version for javac.

This commit also adds VTK_JAVA_SOURCE_VERSION and VTK_JAVA_TARGET_VERSION
to the main CMakeLists.txt so that they can be set externally.
Fix typo that caused incorrect cmake file install.

The DICOM_CMAKE_DIR variable was not being set, which caused the
cmake files to be installed directly in CMAKE_INSTALL_PREFIX, rather
than in the right subdir.  This made it impossible to use vtk-dicom
from other projects.
Load the python library into VTK_PYTHON_LIBRARIES.
Also link the python module itself to libpython.
Revert previous commit.

Linking the module to libpython fails if libpython is static.
When comparing values, check for VL=0xFFFFFFFF.

This check is for values of type VR and UN, which might use VL=0xFFFFFFFF
for encapsulated data.
Add a Matches() method to support attribute matching.

Attribute matching is necessary in order to support DICOM queries.
The rules for attribute matching are given in DICOM part 4.  This
patch is more-or-less complete, except that it does not yet do
timezone adjustments for date and time comparisons, nor does it do
any normalization for name comparisons.
Add length check to Compare to simplify calling code.
Add CharacterSet check to "char" specialization of Compare.
Add a special case for comparing values with VR of AT.

If an AT attribute is part of a query, I can only guess that it
is there by mistake.  The safe approach is for it to always match.
The check in CompareEach was reversed.
When comparing dates, make sure to ignore space padding.