While talking about PDF validation workflows I often come across questions like "Can I let the validation fail if the paper format does not match our corporate rules?". This and other customer specific requirements are indeed useful extensions to the pure file format and standard conformance tests.
Scan to PDF/A - some insights
Traditionally a scanner produces a TIFF or JPEG image for each page. Some of them can directly produce PDF files. And newer devices produce files conforming to the PDF/A standard. However, the quality of the produced files differ significantly. Why is this and why is it worth to use a central scan server?
Are the PDF/A space requirements a show stopper for archiving?
A PDF/A document requires that all resources such as fonts, color profiles, etc. must be embedded in the file. The archiving of transactional documents can be nightmare because such documents are usually short by nature and contain huge number of copies of the same Frutiger font, sRGB color profile and company logo. Many archives therefore prefer TIFF over PDF/A when it comes to born-digital documents. But that is certainly not the idea of a uniform standard. How can this problem be solved?
Subscribe to:
Comments
(
Atom
)