X-Git-Url: https://git.creatis.insa-lyon.fr/pubgit/?a=blobdiff_plain;f=Doc%2FWebsite%2FMain.html;h=97273beba7174743f8590995f06900a866a8b50a;hb=ba0a18abbcfc4963482d968fdc684f31fa995241;hp=cdb7fb589f442145df45b772d40ac95b99442271;hpb=4672e071f29ed17f7258b27e40d47642abfbb53f;p=gdcm.git

diff --git a/Doc/Website/Main.html b/Doc/Website/Main.html
index cdb7fb58..97273beb 100644
--- a/Doc/Website/Main.html
+++ b/Doc/Website/Main.html
@@ -18,7 +18,7 @@ Gdcm is yet another C++ library dedicated to reading/parsing and writing
 <B>D</B>i<B>C</B>o<B>M</B>. 
 
 <!###################################>
-<H2>What gdcm IS</H2>
+<H2>What gdcm <font color=#00ff00>IS</font></H2>
 <UL>
 <LI>gdcm implements the
    <A HREF="http://www.dclunie.com/dicom-status/status.html">
@@ -28,16 +28,30 @@ Gdcm is yet another C++ library dedicated to reading/parsing and writing
    <UL>
    <LI>ACR-NEMA version 1 and 2
    </LI>
-   <LI>Dicom version 3.0 (including various encodings of jpeg, RLE).
+   <LI>Dicom version 3.0 (including various encodings of JPEG -lossless and
+       lossy-, RLE).
        Please refer to
        <A HREF="ConformanceSummary.html">gdcm conformance summary</A>
        for more details.
+   <LI>Papyrus V2 and V3 file headers are readable; the user will have to use 
+       low level accessors if he wants to get the image pixels -sorry-
    </LI>
    </UL>
+<LI> gdcm includes a lot of heuristics that allow reading all the 
+    'exotic' files (headers with oddities) we had to deal with.<BR>
+     Any king of 'exotic' Dicom file is welcome, to help us to improve our
+     library.
+</LI>
 </LI>
 <LI>gdcm is distributed with
    <A HREF="License.html">Berkeley-like license</A>.
 </LI>
+<LI>gdcm is cross platform (it compiles with gcc 2.95, 2.96, 3.0.x, 3.2.x,
+     3.3.x, 3.4.x, 4.0.x, 4.1.x , icc , cc (SunOS), VisualC++, Borland, 
+     nmake... )
+</LI>
+<LI> gdcm has a nightly Dashboard (the whole lib is checked every night)
+</LI>
 <LI>gdcm targets both GNU/Un*ces and Windows/VC++
    (refer to
    <A HREF="Installation.html#gdcmRequirements">requirements</A>
@@ -59,7 +73,7 @@ Gdcm is yet another C++ library dedicated to reading/parsing and writing
 </UL>
 
 <!###################################>
-<H2>What gdcm is NOT</H2>
+<H2>What gdcm is <font color=#ff0000>NOT</font></H2>
 
 Except for
 <A HREF="http://www.dclunie.com/dicom-status/status.html">
@@ -67,7 +81,7 @@ Except for
 gdcm does NOT implement any other part of the Dicom base standard
 (as opposed to other C++ based with open license libraries like
 <A HREF="http://www.offis.de/projekte/ig/dicom/soft-docs/soft01_d.html">
-        DCMTK </A>.
+        DCMTK</A>&nbsp;
 or
 <A HREF="http://www.erl.wustl.edu/DICOM/ctn.html">CTN</A>).
 <BR>
@@ -75,7 +89,8 @@ In particular <B>gdcm is not aware</B> of:
 <UL>
 <LI>the Dicom network file exchange protocol (Query/Retrieve),
 </LI>
-<LI>the Dicom media storage formats,
+<LI>the Dicom media storage formats (well ... it knows about the DICOMDIR
+-reading and writing- and its parts PATIENT, STUDY, SERIES, IMAGE)
 </LI>
 <LI>Print, Verification
 </LI>
@@ -92,10 +107,13 @@ Among all the features of the
 gdcm doesn't implement (yet?)
 <UL>
   <LI>the integration of (optional) overlays on image.
-  </LI>
-  <LI>a more complete supports of the 
-     <A HREF="ConformanceSummary.html">various Jpeg encodings</A>
-  </LI>
+  </li>
+  <LI>a support to write files according to the 
+     <A HREF="ConformanceSummary.html">various classical Jpeg encodings</A>
+             (only read methods are provided)
+  </li>
+  <LI>a support to deal with JPEG 2000 encodings</A>
+  </li>
 </UL>
 Gdcm also still needs
 <UL>