The issues you have found earlier (filed as PDFNEWNET-16222) have been fixed in Aspose.Pdf for .NET 10.6.0.
A quick follow up on this issue.
jwiegand-1:I'm afraid the documentation link didn't make it into your reply, but I found http://www.aspose.com/docs/display/pdfnet/Convert+a+PDF+from+RGB+colorspace+to+Grayscale , which I believe is the page that you were referring to. I updated my code accordingly and have two questions about the output.
jwiegand-1:The pdf was converted to just two shades, black and white, without any shades of gray in between. This obviously results in a very severe quality impact for any images, and some text as well. Are there any plans to enable conversion to shades of gray, as the name implies?
jwiegand-1:Despite loading my regular aspose.pdf license file, the converted pdf is still marked with several boxes containing "Evaluation only. Created with Aspose.Imaging". A updated copy of my after.pdf file is attached.
jwiegand-1:Its been about two months, so I just wanted to check in and see if there are any updates on the status of this issue?Given that this was originally reported in May and was supposed to be fixed in July with 10.6, I was very disappointed to see that it is still broken as of 10.9. Is there any chance that we might see a fix in 10.10?Hi Jim,Thanks for your patience.The first issue reported in this thread was PDFNEWNET-16222 reported on 14May15 and it was fixed in Aspose.Pdf for .NET 10.6.0 release published on 14July15. However later on couple of more issues were reported in the month of August-2015. Please note that issues are resolved in first come first serve basis as we believe its the fairest policy to all the customers. Furthermore, I could not see any post where we have mentioned the timeframe regarding their resolution.We do consider and understand the inconvenience that you have been facing and as soon as we have some definite updates regarding the resolution of these issues, we will update you within this forum thread. Please be patient and spare us little time.jwiegand-1:We were able to work around this feature being broken in the short term, but that is not an option for us long term. Fairly soon we will be forced to start looking at alternatives.
Any update on this issue or ETA as to when these issues will be fixed?
The issues you have found earlier (filed as PDFNET-39257) have been fixed in Aspose.Pdf for .NET 17.3.0.