Eduardo Pinho

Just letting you know that #489 was merged. It made `SpecificCharacterSet` opaque, so further contributions on text encoding can be brought in without breaking changes to the API.

Great! > Is there a way to test this new implementation after it is finished? By lack of a proper transcoding module (efforts are ongoing!), we can test the adapter...

Hello! Thank you for the pull request! It is great to see an initiative towards the integration on authorization mechanisms in DICOM-rs.

Hello @PRadeckiDH. The "Could not read data set token" message represents a DICOM parsing error, might may have multiple causes. In this case, the _Deflated Explicit VR Little Endian_ is...

> Hi @Enet4 thanks for the response! My apologies, I saw this [implementation](https://github.com/Enet4/dicom-rs/blob/master/transfer-syntax-registry/src/deflate.rs) and assumed that Deflated Explicit VR Little Endian was already supported. No worries, thank you for bringing...

At the moment, you can retrieve and insert elements with private tags, but they are treated like any other elements, and the private creator needs to be added or inspected...

Thank you for the initiative, @naterichman! From what I know about private data elements, that API seems to go in the right direction, at least for the in-memory object implementation....

So I took the liberty of continuing with this pull request: - rebased it to the latest upstream revision - updated the doc comment for `DumpFormat::Json` - ensured that dumping...

Thank you for the heads-up. I managed to get things sorted out in this PR. I suspect at this point that the dependency changes may have introduced trait implementations which...

Further testing shows that the tool chokes a bit on files with encapsulated pixel data, whereas it would be nicer if it just ignored the pixel data with a warning....