They say a problem shared is a problem halved. Well, two weeks on from our launch of our Advanced Inkjet Screens it’s been gratifying to see how much the discussion of inkjet output quality has resonated among the press vendor community.
Just in case you missed it, we’ve introduced a set of screens that mitigate the most common artifacts that occur in inkjet printing, particularly in single-pass inkjet but also in scanning heads. Those of you who’ve attended Martin Bailey’s presentations at the InkJet Conference ( The IJC) will know that we’ve been building up to making these screens available for some time. And we’ve worked with a range of industry partners who’ve approached us for help because they’ve struggled to resolve problems with streaking and orange peel effect on their own.
Well, now Advanced Inkjet Screens are available as standard screens that are applied by our ScreenPro screening engine. They can be used in any workflow with any RIP that allows access to unscreened raster data, so that’s any Adobe PDF RIP including Esko. Vendors can replace their existing screening engine with ScreenPro to immediately benefit from improved quality, not to mention the high data rates achievable. We’ve seen huge improvements in labels and packaging workflows. Advanced Inkjet Screens are effective with all the major inkjet printheads and combinations of electronics. They work at any device resolution with any ink technology.
Why does a halftone in software work so well? Halftones create an optical illusion depending on how you place the dots. Streaking or graining on both wettable and non-absorbent substrates can be corrected. Why does this work in software so well? Halftoning controls precisely where you place the dots. It just goes to show that the assumption that everything needs to be fixed in hardware is false. We’ve published a white paper if you’re interested in finding out more.
In the middle of 2017 ISO 32000-2 will be published, defining PDF 2.0. It’s eight years since there’s been a revision to the standard. We’ve already covered the main changes affecting print in previous blog posts and here Martin Bailey, the primary UK expert to the ISO committee developing PDF 2.0, gives a roundup of a few other changes to expect.
The encryption algorithms included in previous versions of PDF have fallen behind current best practices in security, so PDF adds AES-256-bit and states that all passwords used for AES-256 encryption must be encoded in Unicode.
A PDF 1.7 reader will almost certainly error and refuse to process any PDF files using the new AES-256 encryption.
Note that Adobe’s ExtensionLevel 3 to ISO 32000-1 defines a different AES-256 encryption algorithm, as used in Acrobat 9 (R=5). That implementation is now regarded as dangerously insecure and Adobe has deprecated it completely, to the extent that use of it is forbidden in PDF 2.0. Deprecation and what this means in PDF!
PDF 2.0 has deprecated a number of implementation details and features that were defined in previous versions. In this context ‘deprecation’ means that tools writing PDF 2.0 are recommended not to include those features in a file; and that tools reading PDF 2.0 files are recommended to ignore those features if they find them.
Global Graphics has taken the deliberate decision not to ignore relevant deprecated items in PDF files that are submitted and happen to be identified as PDF 2.0. This is because it is quite likely that some files will be created using an older version of PDF and using those features. If those files are then pre-processed in some way before submitting to Harlequin (e.g. to impose or trap the files) the pre-processor may well tag them as now being PDF 2.0. It would not be appropriate in such cases to ignore anything in the PDF file simply because it is now tagged as PDF 2.0.
We expect most other PDF readers to take the same course, at least for the next few years. And the rest… PDF 2.0 header: It’s only a small thing, but a PDF reader must be prepared to encounter a value of 2.0 in the file header and as the value of the Version key in the Catalog.
PDF 1.7 readers will probably vary significantly in their handling of files marked as PDF 2.0. Some may error, others may warn that a future version of that product is required, while others may simply ignore the version completely.
Harlequin 11 reports “PDF Warning: Unexpected PDF version – 2.0” and then continues to process the job. Obviously that warning will disappear when we ship a new version that fully supports PDF 2.0. UFT-8 text strings: Previous versions of PDF allowed certain strings in the file to be encoded in PDFDocEncoding or in 16-bit Unicode. PDF 2.0 adds support for UTF-8. Many PDF 1.7 readers may not recognise the UTF-8 string as UTF-8 and will therefore treat it as using PDFDocEncoding, resulting in those strings being treated as what looks like a random sequence of mainly accented characters. Print scaling: PDF 1.6 added a viewer preferences key that allowed a PDF file to specify the preferred scaling for use when printing it. This was primarily in support of engineering drawings. PDF 2.0 adds the ability to say that the nominated scaling should be enforced. Document parts: The PDF/VT standard defines a structure of Document parts (common called DPart) that can be used to associate hierarchical metadata with ranges of pages within the document. In PDF/VT the purpose is to enable embedding of data to guide the application of different processing to each page range.
PDF 2.0 has added the Document parts structure into baseline PDF, although no associated semantics or required processing for that data have been defined.
It is anticipated that the new ISO standard on workflow control (ISO 21812, expected to be published around the end of 2017) will make use of the DPart structure, as will the next version of PDF/VT. The specification in PDF 2.0 is largely meaningless until such time as products are written to work with those new standards.
The last few years have been pretty stable for PDF; PDF 1.7 was published in 2006, and the first ISO PDF standard (ISO 32000-1), published in 2008, was very similar to PDF 1.7. In the same way, PDF/X‑4 and PDF/X‑5, the most recent PDF/X standards, were both published in 2010, six years ago.
In the middle of 2017 ISO 32000-2 will be published, defining PDF 2.0. Much of the new work in this version is related to tagging for content re-use and accessibility, but there are also several areas that affect print production. Among them are some changes to the rendering of PDF transparency, ways to include additional data about spot colors and about how color management should be applied.
You often read news items about a new press having been installed at a beta site but it’s not a topic that gets much of an airing apart from the odd news bulletin, is it?
And that got me thinking.
What is considered to be a successful beta test? And why should we care?
Well, if you do care, you are not just going through the motions to get your press out of the door. You are more likely to be focussed on delivering a good product. You probably view beta testing as an opportunity to make changes for the better and to help improve product management. You care what comes back because you want to develop a good product. It’s important to you to get understandable and useful data.
So what do you want to know? Your beta test should provide you with proof points as to why your printer is going to be successful in the market. “Real” users will use and abuse your press and put it through its paces in a way that your own internal hardware and software engineers will not. Any weaknesses will be exposed. And you’ll get closer to your customer by working together with them in a way that just wouldn’t be open to you if you didn’t run a beta program.
The thing is how do you extract meaningful data from your test? And how do you rule out those problems that have nothing to do with your press, such as humidity, ambient temperature, the way the site is being operated?
Somehow you need to control the environment that the beta test is conducted in and approach the beta test in quite a formal way to rule out any subjectivity that might creep in.
We’ve got some ideas on how to achieve this which I’ll share in another post. But I’d be interested in hearing how you do it. What are your top tips?
One of the many highlights of our drupa stand will be the new Harlequin RIP. We asked Martin Bailey, CTO at Global Graphics, to tell us more about it. He told us that there are a host of new features to improve inkjet output quality including richer, multi-level screening controls, more controls for variable data printing, and new features for labels and packaging applications. Hear his summary in this video below.
Fancy a test drive? Join us at drupa 2016, Stand 70 B21/C20 in the dip. Simply contact us to book a demonstration.
Stay tuned for more announcements over the next couple of weeks.