Repository navigation
Feature proposal: interlaced PNG encoding #244
Description
Activity
@atruskie If you implemented it we would be more than happy to accept it! 😄
It's something we would like to have it's just something we have set very low on our priority list.
Reacted by Anthony Truskinger@JimBobSquarePants @atruskie If the task is not assigned, please assign it to me.
Reacted by Anton FirszovReacted by James Jackson-SouthReacted by James Jackson-South@IldarKhayrutdinov there's no need for such formalities! :)
Feel free to submit a PR, we will review, and most likely accept it (probably after a few change requests).@antonfirsov Ok ) I did not want that a few people to do the same task. I will take the task, I think it will take some time.
Reacted by Anthony TruskingerHi, I implement interlaced algorithm for pixels, but there are bugs with writing of chunks. Continue working. Unfortunately, there is little time free from the main work.
Reacted by James Jackson-South@IldarKhayrutdinov Thanks! 😄 It's a start which I'm sure we can help with.
If you can open a Work-In-Progress PR against our repo with the check box checked that allows us to push to your PR we should be able to figure this out together.
- added a commit that references this issue
on Sep 19, 2018 - added a commit that references this issue
on Nov 21, 2018 - added a commit that references this issue
on Jun 23, 2019 - added a commit that references this issue
on Aug 8, 2019 Fixed with #955
- added a commit that references this issue
on Aug 25, 2019
I see in #9 that support was added for decoding interlaced PNG images but that support for encoding interlaced images was not considered because it is an uncommon use case.
My question is: if someone (like myself in a fictional world of plentiful free time) were to implement interlaced PNG encoding, would ImageSharp be interested in adopting that feature?