Each time it's possible to assume a 'reasonable' default value for missing
'mandatory' tag, gdcm does it. <br>
For instance if the Tag 'Samples Per Pixels' is missing, we assume its value is
-'1' (Grey pixels, as opposite to RGB); <br>if the tag 'High Bit' is missing, we
+'1' (Grey pixels, as opposite to RGB); <br>
+if the tag 'High Bit' is missing, we
assume its value is 'Bits stored -1' (i.e. : no bad trick inside the pixels)<br>
As gdcm wants to read *as well* old ACR-NEMA files, it has to be widely
tolerant.
<LI>Both <TT>vtkgdcmViewer</TT> and <TT>vtkgdcmViewer2</TT>
are available to allow easy displaying of single/multiframe
GreyLevel/RGB/PaletteColor images
- <LI>
+
</UL>
<LI> Bug fixes
<UL>
<LI> The difference between <TT>MONOCHROME1</TT> (low values = bright,
high values = dark) and <TT>MONOCHROME2</TT> (low values = dark,
- high values = bright) is now taken into account.
+ high values = bright) is now taken into account.<br>
It's no longer up to the user to change the pixels value
- <LI>
+
</UL>
<LI> A.P.I. breaking modifications (since previous version : <TT>1.0</TT>)
<UL>
<LI>
- <LI>
+
</UL>
<TR><TD BGCOLOR="#99ccff">
<A HREF="http://www.creatis.insa-lyon.fr/public/source/gdcm/"
target="rite">
- Online browsing of sources</A>
+ Online browsing of source files</A>
</TD></TR>
<TR><TD BGCOLOR="#99ccff">