Steve Pieper

Is there an easy way to replicate this issue?

Hi @WoonchanCho and @hackermd - these sound like great improvements to me. The core code is pretty stable at this point so now would be a good time to put...

Hi @WoonchanCho - yes, that sounds very reasonable. We want dcmjs to follow the standard and behave like other dicom libraries.

Hi @WoonchanCho - It makes sense to do some basic pixel manipulation in this library, particularly related to codecs, but not image processing per se. The [dicomParser](https://github.com/cornerstonejs/dicomParser) project is more...

Those look like the most common transfer syntax use cases to me. Of course we will also want test cases for those. I've started brainstorming about how we might best...

> @pieper I've played burning-in an area in few samples dicom images of few transfer syntaxes and saving the changes. it worked. Great! > A goal of this library supports...

I haven't worked with it so I don't know if there are drawbacks, but I was thinking that something like [this web-worker npm package](https://www.npmjs.com/package/web-worker) would abstract away the differences between...

It looks like the PR got messed up and now has a bunch of conflicts. Bigger question is about the reason for the changes and how they might related to...

This is very timely and we should put our heads together on this. There has been a lot of SR activity also in python for [highdicom](https://github.com/MGHComputationalPathology/highdicom) and also for pathology...

> > Also, it would be better to use SCT rather than SRT codes, since the former are deprecated. > > > > E.g., instead of (G-A185,SRT,"Long Axis"), use (103339001,SCT,"Long...