naxclassic.blogg.se

OLD were:Ĭ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\AdobeSysFnt18.lstĬ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\AdobeCMapFnt18.lstĬ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\UserCache.binĬ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\Cache\AcroFnt18.lstĬ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\Ĭ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\Ĭ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\Ĭ:\Users\%USERNAME%\AppData\Local\Adobe\Acrobat\DC\Cache\ OLD and it appears to have so far resolved the issue, the machine has been rebooted several times and the issue has so far not returned. On an affected machine Microsoft Windows 7 64 Bit with Adobe Reader DC 2018.009.20044

A appears as 0 appears as / q appears as p ). We are experiencing the same issue with documents from a number of our suppliers affecting only those using the AXAPTA PDF Creation Component for MICROSOFT DYNAMICS AX where Encoding is Identity-H after performing the latest update to Adobe, in our garbled PDFS there is however a pattern in that the character appears to be an ASCII value lower than it should be ( i.e. Also let us know if the PDF appeared garbled in this second case or not.Īgain, we really appreciate your constant support in helping us out with this issue. C:\Users\\AppData\Local\Adobe\Acrobat\DC\Cache\AcroFnt18.lstĪfter doing this, repeat Steps#3 & 4 and share the new PML file.C:\Users\\AppData\Local\Adobe\Acrobat\DC\UserCache.bin.