Description
When no SpecificCharacterSet tag is provided in C-Find request to foDicom based SCP, foDicom seems to use default charset (i.e. ASCII) to decode e.g. PN tags, which results in '?' in place of certain chars. After a quick look at the source,
was it intentional for any reason to use DicomDatasetReaderObserver contructor with only a command (DicomService->ProcessPDataTFAsync) instead of providing also the fallBackEncoding available in DicomService?
e.g.
var reader = new DicomReader(); reader.IsExplicitVR = false; reader.Read(new StreamByteSource(_dimseStream, FileReadOption.Default), new DicomDatasetReaderObserver(command, _fallbackEncoding));
instead of:
var reader = new DicomReader(); reader.IsExplicitVR = false; reader.Read(new StreamByteSource(_dimseStream, FileReadOption.Default), new DicomDatasetReaderObserver(command));
Best regards
Jarek
Fellow Oak DICOM 4.0.7
OS: Windows 10 x64
Platform: NET Framework 4.5.2