You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the contribution, and apologies for the slow reply...
Unfortunately, behind the scenes, VSCode insists on converting all data to valid UTF-8 sequences, and thus, invalid UTF-8 sequences, which are valid PDF as binary data, get swallowed. This means any stream saving may not always be a faithful representation of the data (e.g. inline image data in content streams or operands to string painting operators. I suggest using other PDF forensic tools that are better suited to this, such as Apache PDFBox Debugger, iText RUPS, PDF Stream Dumper, PDFXplorer 4, Kyktir, etc. (I'm sure there are others too).
I am working on a major update that will hopefully address some issues with binary data. It basically involves having the PDF file in memory twice: once in VSCode in a UTF-8-mangled form and another in a pure binary form that the extension manages, and then trying to synchronize what VSCode is doing with the bytes in the PDF binary version.
It would be great to have functionality to save the (possibly uncompressed) stream of an object.
The text was updated successfully, but these errors were encountered: