We ran across this issue updating from RTM to SP1 (SP 2013). I was able to implement the PDFFIX.js and have it working on a couple of site collections in our test environment.
I also have an active support ticket open with MS who sent me the link to this forum post and the following day (yesterday) sent me the exact instructions that are posted above. It seems in the time they have been doing "triage" in their product evaluation team, they still have no real fix for the issue. I am continuing to push for an actual fix/patch before implementing this in our production environment.
cs