Add a short notice for some nightmarish files

diff --git a/MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt b/MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt
new file mode 100644 (file)
index 0000000..cd0b3a8
--- /dev/null
+++ b/MR_Philips_Intera_No_PrivateSequenceImplicitVR.README.txt
@@ -0,0 +1,7 @@
+MR_Philips_Intera_Broken.dcm was read again on ViewForum, sent on Philips
+EasyVision console, and a CDROM was burnt
+No more trouble, nowhere !
+Private Sequences are 'Implicit VR', (and their length is *not* 0xffffffff)
+Readers cannot know it's a Sequence; they just read it as a long value.
+If we take into account Phillips Intera 'shadow dictionnary', same problem as
+for MR_Philips_Intera_Broken.dcm occurs again.

diff --git a/MR_Philips_Intera_PrivateSequenceImplicitVR.README.txt b/MR_Philips_Intera_PrivateSequenceImplicitVR.README.txt
new file mode 100644 (file)
index 0000000..45878e4
--- /dev/null
+++ b/MR_Philips_Intera_PrivateSequenceImplicitVR.README.txt
@@ -0,0 +1,7 @@
+As usual for ViewForum burnt CDROMs, the Endianness switches from Little Endian
+to Big Endian, and then back to Little Endian within an 'Explicit VR' 
+private DICOM Sequence (the length of which is *not* 0xffffffff).
+The heuristics to guess the endianness looking at the 'delimitors' works.
+There are a lot a 'Private Sequences'.
+Bad luck for us : there are Implicit VR, we cannot guess it's a Sequence...
+We have to backtrack when an Item Starter is found 'out of' any SQItem.

diff --git a/MR_Philips_Intera_SwitchIndianess_noLgtSQItem_in_trueLgtSeq.README.txt b/MR_Philips_Intera_SwitchIndianess_noLgtSQItem_in_trueLgtSeq.README.txt
new file mode 100644 (file)
index 0000000..22f1d6e
--- /dev/null
+++ b/MR_Philips_Intera_SwitchIndianess_noLgtSQItem_in_trueLgtSeq.README.txt
@@ -0,0 +1,7 @@
+Most Dicom Readers breaker image
+(Philips MR intera, comming from an ViewForum-burned CDROM)
+Within an 'Explicit VR' private DICOM Sequence (the length or which is *not
+0xffffffff), the Endianness switches from Little Endian to Big Endian, and then
+back to Little Endian.
+We have to guess the endianness looking at the 'delimitors'
+(whether they start with 0xfffe or 0xfeff)

diff --git a/MR_SIEMENS_forceLoad29-1010_29-1020.README.txt b/MR_SIEMENS_forceLoad29-1010_29-1020.README.txt
new file mode 100644 (file)
index 0000000..2f83f43
--- /dev/null
+++ b/MR_SIEMENS_forceLoad29-1010_29-1020.README.txt
@@ -0,0 +1,9 @@
+This images contains two 'long' Entries (29|1010,29|1020), not loaded with the standard value of
+MAX_SIZE_LOAD_ELEMENT_VALUE (4096); but the user needs them.
+Use method
+Document::AddForceLoadElement()
+before calling
+Document::Load().
+
+Check the result with 
+PrintFile filein=... forceload=29-1010,29-1020