I'm trying to downdistill PDF 1.6. ps2pdfwr -dPDFSETTINGS=/screen -dCompatibilityLevel=1.6 works fine, but the resulting PDF is 1.5, not 1.6. Googling found me http://ghostscript.com/irclogs/20100409.html, where you asked for a bug report; here it is. :-)
Fixed in revision 11747, patch here: http://ghostscript.com/pipermail/gs-cvs/2010-September/011774.html This allows specifying CompatibilityLevel up to 1.7.
The link: http://ghostscript.com/pipermail/gs-cvs/2010-September/011774.html is not accessible. Can we download the patch from elsewhere?
(In reply to Sebastian Nasturica from comment #2) > The link: > > http://ghostscript.com/pipermail/gs-cvs/2010-September/011774.html > > is not accessible. > > Can we download the patch from elsewhere? We have migrated (come considerable time ago) from Subversion to Git as our source repository. The patch is of course available there, though it might take some effort to locate a patch from 5 years ago. More sensibly you could simply update to a more recent version.
git log --grep=11747 says the specfic commit is 414963420412e905bd5a9646cbe5d17a455d6a0c and the above should show up as a direct link to the specific commit in web interface of the git repository.
BTW, 'git log --grep=11747' (which greps for strings in the commit message) works because the subversion revision number is written into the git commit log message during the migration, so it is quite easy to look up git commit corresponding to a svn id. A slightly more specific way is 'git log --grep=trunk@11747' . You can do that same for sub version branches also, such as the icc one of Michael's with "git log --grep=icc_work@9982". (e.g. the list at the bottom of http://bugs.ghostscript.com/show_bug.cgi?id=695074#c13)