Bug #554
Updated by Jörg Riesmeier over 8 years ago
When one of the two global flags dcmEnableOtherFloatStringVRGeneration or dcmEnableOtherDoubleStringVRGeneration are set to OFFalse and their corresponding VR is mapped to OB, do we need to consider endianness (i.e. conditionally swap bytes) because OF and OD consist of 4/8 bytes per value? Currently, OF and OD are and handled the same way as UN and UT. See DcmVR::getValidEVR() for details.