Big PDF Ghent July 2012 - Ghent PDF Workgroup
Big PDF Ghent July 2012 - Ghent PDF Workgroup
Big PDF Ghent July 2012 - Ghent PDF Workgroup
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Minutes General Meeting<br />
General meeting<br />
GWG Meeting <strong>July</strong> <strong>2012</strong><br />
info@gwg.org<br />
www.gwg.org<br />
Authors Vicki Blake<br />
Executive Director<br />
Isabelle De Milde<br />
Admin Assistant<br />
Date August 28, <strong>2012</strong><br />
Status Final
Minutes General Meeting<br />
Table of Contents<br />
1 General Meeting Minutes .................................................................................. 3<br />
1.1 Agenda ........................................................................................................ 3<br />
1.2 Attendance .................................................................................................. 3<br />
1.3 Meeting overview .......................................................................................... 4<br />
1.4 Observers/Members ...................................................................................... 4<br />
1.5 Meeting Structure ......................................................................................... 4<br />
1.6 Next meetings .............................................................................................. 5<br />
1.7 Treasurer ..................................................................................................... 6<br />
1.8 Meetings 2013 .............................................................................................. 6<br />
1.9 Action items ................................................................................................. 6
Minutes General Meeting<br />
1 General Meeting Minutes<br />
1.1 Agenda<br />
THURSDAY <strong>July</strong> 12 th<br />
9:00-11:00 Executive Committee Meeting<br />
11:00-12:00 SubCommittee Chairs Meeting<br />
12:00-1:00 Lunch<br />
1:00-2:00 General Mtg VB<br />
2:00-3:00 Specifications PK/EC<br />
3:00-3:15 Break<br />
3:15-4:00 Compliancy DH<br />
4:00-5:00 Job Ticketing TB<br />
FRIDAY <strong>July</strong> 13 th<br />
9:00-9:15 Standards Update LR<br />
9:15-10:00 Process Control SJ<br />
10:00-11:00 Marketing HJ<br />
11:00-11:15 Break<br />
11:15-12:00 Cross Media Bvl/ED<br />
12:00-12:45 Lunch<br />
12:45-1:15 Cross Media Bvl/ED<br />
1:15-2:15 Variable data - DI<br />
2:15-2:30 Color - DZ<br />
2:30-3:15 Job Ticketing - TB<br />
3:15 Wrap up/Adjourn<br />
1.2 Attendance<br />
Name Company<br />
Bailes-Collins Andrew Enfocus<br />
Battrick George ERA<br />
Beckenham Tom Specle<br />
Blake Vicki CGS<br />
Brunner Laurel Digital Dots<br />
Caza Michel FESPA Ltd<br />
Claes Peter Febelgra<br />
Cloots Elli Enfocus<br />
Danis Erwin Medibel+<br />
De Milde Isabelle GWG<br />
Dressler Holger EFI<br />
Ginguené Pascale UNIC<br />
Guenther Matthias Quark<br />
Haazen Didier VIGC
Minutes General Meeting<br />
Name Company<br />
Hagen Eddy VIGC<br />
Isaacs Dov Adobe Systems Incorporated<br />
Jaeggi Stephan VSD<br />
Josefsen Hanne rotasjon.no<br />
Kennedy Dianne IDEAlliance<br />
Kleinheider Peter <strong>PDF</strong>X-Ready<br />
Korsmit Peter CMBO<br />
Lataste Pierre Dalim Software GmbH<br />
Leurs Laurens Agfa Graphics<br />
Lindstrom Paul Digital Dots<br />
Maes Peter Medibel+<br />
Mooij Menno CMBO<br />
Rosenthol Leonard Adobe Systems Incorporated<br />
Salicetti Denis Taga Italia<br />
Stark Igor Mediagraf<br />
van der Meulen Arjen Kodak Graphic Communications<br />
Van Looy Bart Sanoma Magazines Belgium NV<br />
Viscardo Damiano Soluzionisubito<br />
Vorländer Sebastian GMG GmbH & C° KG<br />
Zwang Dave Printing Industries of America<br />
1.3 Meeting overview<br />
The Packaging subcommittee meeting was cancelled as no co-chair present.<br />
1.4 Observers/Members<br />
1.4.1 New observers - Paul Lindstrom, consultant, and Laurel Brunner, consultant, of<br />
Digital Dots & Spindrift. They want to be aware of GWG activities.<br />
1.4.2 Lost members<br />
- Onevision<br />
- Andy Psarianos resigns as Treasurer and Chair positions<br />
- future membership by FE Burman not confirmed<br />
1.5 Meeting Structure<br />
1.5.1 Group Charter<br />
This should normally be discussed at the Annual Meeting. We need to revise this practice.<br />
There is a request to think about the group charter (direction/path) and discuss this<br />
during the General Meeting in October. For those not attending, please send comments<br />
to Vicki B.
Minutes General Meeting<br />
1.5.2 Membership & Participation<br />
Increase membership, value to members, and active/consistent participation by<br />
members.<br />
Dov I. asks what we can do to get the expertise of vendors (new and old)?? *Not sure<br />
what this means?<br />
1.5.3 Agenda Revision<br />
Following are proposals:<br />
- Have focused (working) subcommittees and move the general meeting to the end as a<br />
summary meeting; everyone agrees<br />
- Have overlapping subcommittee meetings where participants chose their meetings of<br />
interest; general disagreement – though specific ones could overlap<br />
- Provide a separate room for those who are not interested; general agreement - first<br />
trial in Oct <strong>2012</strong> meeting<br />
- Change the number of meetings per year to accommodate the changes,<br />
- 3 meetings per year (1 in <strong>Ghent</strong>, 1 in Europe, 1 in the US); everyone agrees<br />
- 3 days (2 full days for all SC, general, and seminar); everyone agrees<br />
- Provide commercial/educational sessions - based on group vote; everyone agrees<br />
- Increase in-between subcommittee meetings<br />
1.5.4 Reporting<br />
Subcommittee minutes will be provided to Isabelle by the end of the meeting.<br />
1.5.5 Association input<br />
Increased association input is necessary.<br />
Associations & Vendors (2 each) get 5 min presentations per meeting to present how<br />
they support the GWG (PIA & <strong>PDF</strong>/X* as associations and Adobe & Specle). * do you<br />
mean pdf/x ready?<br />
1.6 Next meetings<br />
1.6.1 Seminar on Tuesday, Oct 9 at Graph Expo in Chicago<br />
We need an agenda for the seminar. This agenda will be used for future seminars next<br />
year. The audience will be primarily printers.<br />
At the GWG we do not have many designers; however, we must address these at a later<br />
seminar.<br />
A number of the vendor members will have solutions that support <strong>PDF</strong>/X-4.<br />
There will be a review of all presentations before the seminar.<br />
Agenda:<br />
- Why do we need <strong>PDF</strong>/X-4?<br />
- Why do we need GWG?<br />
- <strong>PDF</strong>/X-4 Creation (including problems and fixes)<br />
- <strong>PDF</strong>/X-4 preflight, settings and guideline/tools<br />
- How to proof<br />
- How to process<br />
- How to move from here to there<br />
- Advantages & Problems<br />
- Solving Problems<br />
- Use cases: Novartis and Endress + Hauser<br />
Presenters: Dave Z, Elli C, Menno M (?)<br />
Authoring: Menno M, Dov, Leonard, Pierre L, Didier H, Peter K<br />
1.6.2 Pittsburgh Meeting on October 11 & 12 (hosted by Printing Industries of<br />
America)<br />
Doubletree Hilton hotel in Pittsburgh<br />
Meeting on the Printing Industries of America premises (transportation will be provided)
Minutes General Meeting<br />
1.7 Treasurer<br />
Call for nominations for Treasurer as Andy P resigned.<br />
1.8 Meetings 2013<br />
Jan 23-25: London (Adobe)<br />
Jun 5-7: Gent<br />
Oct 23-25: Canada (Ryerson University) or Minneapolis (CGS) - both are same for EU<br />
cost-wise and ease of access<br />
1.9 Action items<br />
Action Item Assigned to Due<br />
Send in thoughts about the GWG charter to Vicki<br />
Blake<br />
All members Oct <strong>2012</strong><br />
meeting in<br />
Pittsburgh<br />
Send in nominations for Treasurer to Vicki Blake All members 2 weeks
<strong>Ghent</strong> <strong>Workgroup</strong><br />
General Meeting<br />
<strong>July</strong> 12, <strong>2012</strong>
<strong>July</strong> Meeting Agenda<br />
THURSDAY <strong>July</strong> 12 th<br />
9:00-11:00 Executive Committee Meeting<br />
11:00-12:00 SubCommittee Chairs Meeting<br />
12:00-1:00 Lunch<br />
1:00-2:00 General Mtg VB<br />
2:00-3:00 Specifications PK/EC<br />
3:00-3:15 Break<br />
3:15-4:00 Compliancy DH<br />
4:00-4:30 Job Ticketing TB<br />
4:30-5:00 Standards update LR<br />
FRIDAY <strong>July</strong> 13 th<br />
9:00-10:00 Process Control SJ<br />
10:00-11:00 Marketing HJ<br />
11:00-11:15 Break<br />
11:15-12:00 Cross Media Bvl/ED<br />
12:00-12:45 Lunch<br />
12:45-1:15 Cross Media Bvl/ED<br />
1:15-2:30 Variable data - DI<br />
2:30-3:00 Color - DZ<br />
3:00 Wrap up/Adjourn
Agenda<br />
• Intro’s / Welcome<br />
• Executive Committee<br />
• Membership update<br />
• New Meeting Format<br />
• Next Meetings<br />
− Chicago Seminar
Intros/Welcome
Welcome<br />
• Observers:<br />
Laurel Brunner – Digital Dots<br />
Paul Lindstrom – Digital Dots
Membership<br />
• New Members:<br />
• Lost Members:<br />
• OneVision<br />
• Andy Psarianos
Executive Committee<br />
• Treasurer:<br />
− Andy Psarianos has resigned<br />
− Please send nominations to Vicki within by 30 th<br />
<strong>July</strong>
Membership Update<br />
• 46 members<br />
− 17 associations<br />
− 15 vendors<br />
− 11 industry<br />
− 3 educational
Association Members (17)<br />
BPIF UK<br />
CMBO the Netherlands<br />
DDPFF Denmark<br />
ERA Europe<br />
Febelgra Belgium<br />
Fespa UK<br />
FTA USA<br />
Idealliance USA<br />
Medibel+ Belgium<br />
Nederlands Uitgeversverbond Netherlands<br />
Pdf/x-ready Switzerland<br />
Printing Industries of America USA<br />
rotasjon Norway<br />
Taga Italia Italy<br />
UNIC France<br />
VIGC Belgium<br />
VSD Switzerland
Vendor Members (15)<br />
Adobe<br />
Adstream<br />
Agfa<br />
Callas<br />
CGS<br />
Dalim<br />
EFI<br />
Enfocus Software<br />
EskoArtwork<br />
GMG<br />
Kodak<br />
Quark<br />
Remote Director<br />
Screen<br />
Specle
Industry Members (11)<br />
Associated News UK<br />
bleuprocess France<br />
F.E. Burman UK<br />
Four Pees Belgium<br />
Litografia Roses Spain<br />
Phototype USA<br />
PublishingTools4U Belgium<br />
Sagamgraphic Belgium<br />
Sanoma Media Belgium<br />
Soluzionisubito Italy<br />
Square France
Educational Members (3)<br />
University of Wuppertal Germany<br />
Ryerson University Canada<br />
Mediagraph France
Meeting attendance Reminder<br />
Please pay for dinner tonight!!<br />
Please let Isabelle know:<br />
hotel needs<br />
dinner attendance<br />
MEETING attendance<br />
must have accurate counts for hotel/internet, etc.<br />
Thanks!
Goals<br />
• Per Executive Committee, we need to improve:<br />
• Reviewing Group Charter Annually<br />
• Membership – benefits to existing – attractiveness to new ones<br />
• Participation<br />
• Reporting<br />
• Association Input
Meeting Structure<br />
Group Charter<br />
please prepare to discuss this @ October meeting<br />
Agenda Revisions<br />
General Mtg/Summary meeting<br />
– move to end & summarize all SC meetings – VOTED YES<br />
SC meetings<br />
overlap? VOTED NO<br />
# of meetings VOTED 3/year<br />
Commercial/Education Sessions – VOTED YES<br />
Subcommittee Meeting Structure<br />
focused<br />
participants/participation<br />
more inbetween meetings<br />
I’net? VOTED for separate rooms<br />
Reporting
Next Meetings
<strong>2012</strong> meetings<br />
• <strong>July</strong> 12,13 – Gent, Belgium<br />
• October 11,12 – Pittsburgh, USA – update<br />
• Conflicts:<br />
− ICC/Fogra week jan 30 th<br />
− Spectrum<br />
− SGIA<br />
− Easter & Passover – 5-14 april?<br />
− Drupa 3 may - ??<br />
− Graph Esko – 7-10 Oct<br />
− IFRA 29-? Oct
October in Pittsburgh<br />
Meeting room, I’net confirmed @ Printing Industries<br />
of America<br />
Hotel rooms confirmed @ Hilton DoubleTree<br />
Hotel PittsburghdowntownDoubleTree.com<br />
Seminar planned for Tuesday in Chicago (during<br />
Graph Expo)
October Seminar<br />
Dave Zwang<br />
Chicago<br />
Meeting room confirmed
<strong>PDF</strong>/X-4 Seminar<br />
• Why do we need <strong>PDF</strong>/X-4 ?<br />
• <strong>PDF</strong>/X-4 + GWG<br />
• <strong>PDF</strong>/X-4 Creation (incl. problems and<br />
fixes)/Tools<br />
• <strong>PDF</strong>X-4 preflight, settings and<br />
guideline/Tools<br />
• How to Proof<br />
• How to Process/Tools<br />
− aggregation
<strong>PDF</strong>/X-4 Seminar<br />
• - How to move from here to there<br />
• - Advantages/Problems<br />
− Solving problems<br />
• Use cases: Novartis and Endress +<br />
Hauser<br />
• Deliverables
2013 meetings – 3 meetings<br />
• January 23-25 – London?<br />
• June 5-7 – Gent, Belgium<br />
• October 23-25 – US Ryerson (Toronto)?<br />
• Conflicts:<br />
CGS offers Minneapolis<br />
− Print 8-12 sept<br />
− Ifra 7-9 Oct<br />
− Fespa 25-29 june<br />
• EDU? Ryerson, wuppertal?<br />
• ADOBE CAN HOST: germany, paris, london,<br />
dublin, edinburough, basel, amsterdam,<br />
bucherest,<br />
• Roularta CAN HOST - Paris<br />
• Sanoma can host in BE fall ‘13
Thank You!
Meeting minutes<br />
Specification<br />
subcommittee<br />
Meeting minutes of <strong>July</strong> 12 th <strong>2012</strong><br />
info@gwg.org<br />
www.gwg.org<br />
Authors Elli Cloots and Peter Kleinheider<br />
Co-chairs<br />
Date August 3 rd, <strong>2012</strong><br />
Status Draft 1
Document Title<br />
Table of Contents<br />
1 Minutes .......................................................................................................... 3<br />
1.1 Approval of last meeting minutes .................................................................... 3<br />
1.2 Topic 1 ............................................................ Error! Bookmark not defined.<br />
1.3 Topic 2 ........................................................................................................ 4<br />
2 Action items ................................................................................................... 5
Document Title<br />
1 Minutes<br />
1.1 Agenda<br />
• Approval of meeting minutes<br />
• Final approval of GWG<strong>2012</strong><br />
• Status of implementations<br />
• What to release to the public?<br />
• What to do next?<br />
o Packaging specifications<br />
o RGB variant<br />
o Other?<br />
1.2 Approval of last meeting minutes<br />
The meeting minutes of April 19th were approved by the group.<br />
1.3 Final approval of GWG<strong>2012</strong><br />
1.3.1 Current status<br />
After the last meeting, the Golden Master of the GWG<strong>2012</strong> specification was sent out to<br />
the group for approval. Everybody that voted, said “yes” but no official outcome of the<br />
votes was sent out yet. Afterwards, more comments came in when vendors started to<br />
implement the specification and found more inconsistencies.<br />
Therefore the following topics were brought to the group:<br />
1. Inconsistency in wording:<br />
4.11 Black Text – smaller than<br />
4.12 Black Text- smaller than<br />
4.13 Thin Black Line – less than<br />
4.14 Thin Black Line – less than or equal to<br />
Proposal is to change to 'less than’<br />
2. Inconsistency for Spotcolor selection<br />
4.20 Spot color naming applies to Separation & Device N<br />
4.21 Ambiguous spot color applies to Separation only<br />
Proposal is to also include Device N<br />
3. Comparing of equal numeric values (3.15)<br />
Text, Image and Path elements are mentioned, but not page geometry<br />
Proposal is to check Page Geometry with the same values as path elements, 3<br />
digits<br />
Note: this could influence <strong>PDF</strong>/X-4 requirements like nesting of page boxes<br />
4. What size should a thin white line be checked for<br />
Current: … (B) … elements colored with more than 1 colorant as specified in the<br />
table of a specific Variant<br />
Proposal: … (B) … elements colored with 0 colorants (white object) or more than 1<br />
colorant as specified in the table of a specific Variant.<br />
5. Rounding for comparing color values.<br />
Background: a color value of 0.0019 (less 1/512) is treated as 0% by Acrobat.<br />
This has an effect when checking white overprint.<br />
1.3.2 Discussion<br />
The discussion should not be re-opened as the spec was massively approved. (Leonard)
Document Title<br />
The fact that white lines are no longer covered by the specification is a problem. They<br />
were covered in the previous specification, by changing and formalizing the definitions,<br />
they got excluded accidently. (Elli)<br />
Diane will send a document that we could use to communicate about editorial changes<br />
No implementation shipping yet, Adobe going in test with VIGC soon.<br />
1.3.3 Conclusion<br />
The problem will be discussed further, outside of the meeting, between Didier, Peter,<br />
Leonard and Elli. The goal is to come with a solution that works for the end user and the<br />
vendors who are finalizing implementation.<br />
1.4 Status of implementation<br />
1.4.1 Implementation<br />
Implementation in Acrobat, pdfToolbox and PitStop are expected soon.<br />
1.4.2 Beta profiles<br />
Should follow shortly after the finalization of the implementation stage.<br />
1.4.3 Status of <strong>PDF</strong> Export Settings<br />
Bart gave an overview of the tests Sanoma did<br />
Conclusions:<br />
Do downsampling.<br />
Downsample to 350 and downsample starting from 700.<br />
For Newspapers use the values: to 250 from 500 dpi.<br />
Create separate CS6 export settings and allow JPEG2000.<br />
Remark: there are printers that still have rips that don’t support JPEG2000 yet. But this<br />
would be a rip that doesn’t support <strong>PDF</strong>/X-4 so it’s irrelevant for this discussion.<br />
It was agreed by the group to use these values. Peter Kleinheider will create new<br />
settings.<br />
1.5 What to release to the public?<br />
• Give the final specification to David Zwang to be published to the website.<br />
• The rest of the discussion will happen in the marketing committee.<br />
1.6 What to do next?<br />
Skipped this topic as we ran out of time.
Document Title<br />
2 Action items<br />
Action Item Assigned to Due<br />
Finalize the discussion about the finalization of GM Leonard, Didier,<br />
<strong>July</strong> 13th<br />
GWG<strong>2012</strong><br />
Peter Kleinheider<br />
and Elli<br />
Provide new export settings and test how CS6<br />
setting behave in previous versions<br />
Peter Kleinheider August<br />
Give the final specification to David Zwang to David Zwang, Peter Next<br />
be published to the website<br />
Kleinheider, Elli<br />
Cloots<br />
meeting
Specification SC<br />
Peter Kleinheider & Elli Cloots<br />
Co-chairs specification subcommittee
Agenda<br />
• Approval of meeting minutes<br />
• Final approval of GWG<strong>2012</strong><br />
• Status of implementations<br />
• What to release to the public?<br />
• What to do next?<br />
− Packaging specifications<br />
− RGB variant<br />
− Other?
Approve minutes<br />
• Meeting of April 19 th<br />
− See email from Peter Kleinheider<br />
− Also available on the FTP server<br />
• Please approve
Final approval of GWG<strong>2012</strong><br />
• Proposed changes since GM1<br />
− Inconsistency in wording:<br />
• 4.11 Black Text – smaller than<br />
• 4.12 Black Text- smaller than<br />
• 4.13 Thin Black Line – less than<br />
• 4.14 Thin Black Line – less than or equal to<br />
Proposal is to change to 'less than’<br />
− Inconsistency for Spotcolor selection<br />
• 4.20 Spot color naming applies to Separation & Device N<br />
• 4.21 Ambiguous spot color applies to Separation only<br />
- Proposal is to also include Device N
Final approval of GWG<strong>2012</strong><br />
• Proposed changes since GM1<br />
− 3.15 Comparing of equal numeric values<br />
• Text, Image and Path elements are mentioned, but not page<br />
geometry<br />
• Proposal is to check Page Geometry with the same values as<br />
path elements, 3 digits<br />
• Note: this could influence <strong>PDF</strong>/X-4 requirements like nesting<br />
of page boxes<br />
− What size should a thin white line be checked for<br />
• Current: … (B) … elements colored with more than 1 colorant<br />
as specified in the table of a specific Variant<br />
• Proposal: … (B) … elements colored with 0 colorants (white<br />
object) or more than 1 colorant as specified in the table of a<br />
specific Variant.
Final approval of GWG<strong>2012</strong><br />
• Proposed changes since GM1<br />
− Rounding for comparing color values.<br />
• Background: a color value of 0.0019 (less 1/512) is treated as 0% by<br />
Acrobat. This has an effect when checking white overprint.
Status of implementation<br />
• Implementation update of<br />
− Acrobat<br />
− PitStop<br />
− Toolbox<br />
• Status Beta profiles<br />
• Status <strong>PDF</strong> Export Settings
What to release to the<br />
public?<br />
• Documentation<br />
• Whitepaper<br />
• Marketing waiting on text (Peter)<br />
• Who can help with writing?
What to do next?<br />
• Packaging specifications<br />
− Table created by Peter Kleinheider<br />
− Under review by Christian Blaise<br />
• RGB variant<br />
− Altona2 – rendering discussion<br />
− Many question marks with RGB rendering<br />
− Why do you want RGB variants?<br />
− What do you want to solve?<br />
• More?
Thank You!
Meeting minutes<br />
Compliance testing<br />
subcommittee<br />
Meeting minutes<br />
info@gwg.org<br />
www.gwg.org<br />
Authors Elli Cloots & Didier Haazen<br />
Vice-chair Specs & Chair Compl. Testing<br />
Date <strong>July</strong> 12, <strong>2012</strong><br />
Status v1.0
Compliance testing subcommittee<br />
Table of Contents<br />
1 Minutes ........................................................................................................ 3<br />
1.1 Agenda ........................................................................................................ 3<br />
1.2 Approval of last meeting minutes .................................................................... 3<br />
1.3 GWG compliancy overview ............................................................................. 3<br />
1.4 Status GWG <strong>2012</strong> compliancy tests ................................................................. 3<br />
1.5 VIGC Output essential panel ........................................................................... 4<br />
2 Action items ................................................................................................. 5
Compliance testing subcommittee<br />
1 Minutes<br />
1.1 Agenda<br />
- GWG compliancy overview<br />
- Status GWG <strong>2012</strong> compliancy tests<br />
1.2 Approval of last meeting minutes<br />
The meeting minutes of <strong>2012</strong>-05-04 were approved by the group.<br />
1.3 GWG compliancy overview<br />
Kodak:<br />
• Not compliant yet.<br />
• We have informed them that a new version of the specification is coming up (GWG<br />
<strong>2012</strong>). They wanted to continue with this version (GWG v4) to have a solution on the<br />
short term.<br />
Quark:<br />
• QuarkXPress 9.3 or higher should be stated on the website as these now have fixed<br />
the issue raised by Peter Maes.<br />
Adobe:<br />
• We should update the website for InDesign CS6 and Distiller 10 as these are<br />
available and also support GWG v4.<br />
• Onevision: GWG v4 settings files have been uploaded to the GWG website (search<br />
for ‘v4’, and ‘Onevision’)<br />
1.4 Status GWG <strong>2012</strong> compliancy tests<br />
Lot’s has happened.<br />
- Mostly to match the updates to the golden master specification.<br />
o Chapter numbers match the Golden Master specification again.<br />
- Shortened the suffixes that indicate if test files should generate warning or errors.<br />
- Also included the output suite patches.<br />
o E.g. blending color spaces, font types, and layers.<br />
o But stripped them from any unnecessary information (i.e. typical <strong>Ghent</strong><br />
Output Suite layout, reference images, etc.)<br />
- Optimized patches to match the new rounding rules (GWG<strong>2012</strong>, Ch. 3.15).<br />
- Minor updates based on feedback<br />
o LZW compressed file lost the compression and has been added again.<br />
o Magenta backgrounds for visualization reasons.<br />
o Removed redundant errors for DeviceRGB objects in ‘4.25’ files.<br />
o Added small images to the test files as these should/shouldn’t be checked<br />
depending is one metric is more than 65pixels (last line of Ch. 4.27, GWG<br />
<strong>2012</strong> specs).<br />
- First live tests show that some fine-tuning is needed and even serious revisions of<br />
certain parts of the spec<br />
o Place (white) text outside test objects for ink coverage test files (they are<br />
disturbing the test objects).<br />
o Clarification of 4.25 (explicitly defined CS), adjusted definition 4.20 (spot<br />
color naming, etc.)<br />
Agfa raised the issue that they can only give this to development when the<br />
documentation is available. DH explained that:<br />
- the test files are pretty self-explanatory and refer to the right section in the spec
Compliance testing subcommittee<br />
- this should already be a good base to start from<br />
- proper documentation is certainly a priority on the wish list as soon as the test files<br />
are really finalized (should happen now that we’re using the test files to validate<br />
reference implementations)<br />
1.5 VIGC Output essential panel<br />
- VIGC created custom panels for Adobe InDesign and Adobe Photoshop to guide<br />
people through all the steps of color correction and page layout correctly. E.g. import<br />
the live preflight settings, setup overprint preview correctly, check color<br />
management settings, etc.<br />
- It is even possible to set up correctly for print output or epub/web/tablet.<br />
- Advantage is that you can do everything from 1 panel and you don’t need to go<br />
through all the panels/menu’s separately.<br />
- For more info or get access to the panels, send an e-mail to eddy.hagen@vigc.org.
Compliance testing subcommittee<br />
2 Action items<br />
Action Item Assigned to Due<br />
Change website to mention QuarkXPress 9.3 or<br />
higher.<br />
Didier Asap<br />
Change website to match new CS6 version numbers Didier Asap<br />
Didier and Quark should check what is needed to Didier & Guenther By next<br />
publish the compliant settings on the website (e.g.<br />
update documentation) once QuarkXPress is<br />
pronounced compliant.<br />
Matthias (Quark) meeting<br />
Didier continues fine-tuning the test files based on Didier By next<br />
the feedback, test with reference implementations<br />
meeting<br />
Add test files for the thin white lines (beta) and<br />
keep in touch with other changes / additions in<br />
GWG <strong>2012</strong> errata (see minutes specs meeting)<br />
Didier By <strong>July</strong> 16<br />
Test the test files All By next<br />
meeting
Compliancy Testing<br />
SC meeting<br />
GWG meeting <strong>Ghent</strong><br />
<strong>July</strong> 12, <strong>2012</strong>
Agenda
Agenda<br />
• GWG compliancy overview<br />
• Status GWG <strong>2012</strong> test set<br />
• VIGC Output Essentials panel
GWG compliancy overview
GWG compliancy overview<br />
• Kodak, GWG v4, (GWG <strong>2012</strong>)<br />
− Will be working on completing the compliancy<br />
in the next few weeks<br />
− Likely do each (v4 and <strong>2012</strong>) separately
GWG compliancy overview<br />
• Onevision, GWG v4<br />
− Settings files uploaded to website
GWG compliancy overview<br />
• Quark XPress 9, GWG v4<br />
− Fixed the bug of the wrong offset of registration<br />
marks<br />
− On the website, we might want to state<br />
“QuarkXPress 9.3 or higher” because of the<br />
issue
GWG compliancy overview<br />
• Adobe InDesign CS6 (8.x)<br />
− Updated on GWG website*<br />
• Means that if you download settings files, it will now mention<br />
‘InDesign CS2-CS6’ instead of ‘InDesign CS2-CS5’<br />
• Same for Acrobat Distiller (‘Distiller 7-10’ instead of ‘Distiller<br />
7-9’)
Status GWG <strong>2012</strong> test set
What has been going on…<br />
• A lot!
What has been going on…<br />
• Previous meeting<br />
− Work on <strong>Ghent</strong> Output Suite patches
What has been going on…<br />
• Between previous and this meeting<br />
− Updated Patch File Names<br />
− Shortened suffixes<br />
− Incorporated Output Suite patches<br />
− Optimized existing test files to GM1-rules<br />
− Other minor updates<br />
− First real tests with reference<br />
implementation(s)
Updated Patch File Names<br />
• Old (GWG<strong>2012</strong>, draft 9)
Updated Patch File Names<br />
• New (GWG<strong>2012</strong>, GM1)
Updated Patch File Names<br />
• Changes<br />
− Now also reflected in file names
Shortened suffixes<br />
• Old style<br />
− Error = error<br />
− Warning = warning<br />
− Good = ‘’
Shortened suffixes<br />
• New style<br />
− Error = E<br />
− Warning = W<br />
− Good = G
Inc. Output Suite patches<br />
• E.g. GWG_Testfile_x4_6.20_par4_a1_MagAds_G.pdf<br />
• But stripped Output Suite layout<br />
(no use in these files)
Inc. Output Suite patches<br />
• E.g. GWG_Testfile_x4_5_c_MagAds_G.pdf<br />
• But stripped Output Suite layout<br />
(no use in these files)
Inc. Output Suite patches<br />
• E.g. GWG_Testfile_x4_6.24_par1b_SheetSpot_G.pdf<br />
• But stripped Output Suite layout<br />
(no use in these files)
Optimized patches<br />
• Rounding values<br />
− Older draft (GWG <strong>2012</strong>, draft 9)
Optimized patches<br />
• Rounding values<br />
− GWG <strong>2012</strong>, GM1
Optimized patches<br />
• Rounding values<br />
− New rules, new files (the overview)
Optimized patches<br />
• Rounding values<br />
− New rules, new files (some examples)<br />
• GWG_Testfile_GWG<strong>2012</strong>_4.11_4.13_MagAds_a1_W_W.pdf<br />
• GWG_Testfile_GWG<strong>2012</strong>_4.11_4.13_MagAds_a2_W.pdf<br />
• GWG_Testfile_GWG<strong>2012</strong>_4.11_4.13_MagAds_b1_W_W.pdf<br />
• GWG_Testfile_GWG<strong>2012</strong>_4.11_4.13_MagAds_c_G 2.pdf<br />
• GWG_Testfile_GWG<strong>2012</strong>_4.17_4.18_MagAds_a1_W_W_W_W.pdf<br />
• GWG_Testfile_GWG<strong>2012</strong>_4.27_4.28_d_MagAds.pdf
Other minor updates<br />
• LZW compression patch<br />
• Magenta colored backgrounds<br />
• Redundant warnings ‘not<br />
recommended ICC profiles’<br />
− GWG_Testfile_GWG<strong>2012</strong>_4.5_c_SheetSpot_W.pdf<br />
• DeviceRGB images outside in GWG<br />
4.25 files<br />
− GWG_Testfile_GWG<strong>2012</strong>_4.25_b_MagAds_E.pdf<br />
• Added image resolution objects<br />
− E.g.: GWG_Testfile_GWG<strong>2012</strong>_4.27_4.28_c1_MagAds_E.pdf
First live tests<br />
• Did a test with Callas<br />
• For Enfocus hopefully soon
First live tests<br />
• Still some open issues though<br />
− Cfr. Specs meeting<br />
− Ink coverage test files
To do<br />
• Continue finilizing files / bug out issues<br />
• (Re)test applications<br />
• Have approved applications and<br />
preflight profiles by (hopefully) next<br />
meeting in Pittsburg
To do<br />
• Timeline (see previous meeting)<br />
− Still on schedule<br />
• 1, 2, 3, 4: by <strong>July</strong> meeting (<strong>Ghent</strong>) to max. October meeting<br />
in Pittsburgh<br />
• 5, 6: October – Dec. <strong>2012</strong> to max. first GWG meeting 2013<br />
• Parallel timeline for creation settings (see Specifications SC<br />
meeting minutes)
VIGC Output Essentials panel<br />
• 5 minute talk: ‘how do associations<br />
support GWG work’<br />
• Here’s something new we prepared…
VIGC Output Essentials panel<br />
• Adobe InDesign panel
VIGC Output Essentials panel<br />
• Adobe Photoshop panel
VIGC Output Essentials panel<br />
• Not available yet, but keep in touch<br />
with the news sites<br />
• Or contact us directly<br />
(eddy.hagen@vigc.org)
Thank You!
<strong>PDF</strong> Standards Update<br />
Leonard Rosenthol | <strong>PDF</strong> Architect<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.
<strong>PDF</strong>/X (ISO 15930)<br />
§� Met in Indonesia in April<br />
§� VERY small turnout<br />
§� Discussed issues concerning <strong>PDF</strong> transparency and the Altona Test Suite v2<br />
§� Made some decisions speci�c to <strong>PDF</strong>/X, but le� larger issues to ISO 32000<br />
§� Discussion of <strong>PDF</strong>/X futures<br />
§� <strong>PDF</strong>/X Futures<br />
§� Align with <strong>PDF</strong> 2.0 (ISO 32000-2)<br />
§� Choose which features we think are important and which are not<br />
§� Details and text to be worked out<br />
§� UNKNOWN: <strong>PDF</strong>/X-4:20xx or <strong>PDF</strong>/X-6<br />
§� Packaging needs?<br />
§� Still waiting on feedback from that industry L�<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
2
<strong>PDF</strong>/VT (ISO 16612-2)<br />
§� Expect that as <strong>PDF</strong>/X commi�ee evaluates its plans around <strong>PDF</strong> 2.0 alignment,<br />
the <strong>PDF</strong>/VT commi�ee may need to meet again<br />
§� �ere has been some VERY early discussion about a future <strong>PDF</strong>/VT that is<br />
actually more “variable” (or dynamic) in nature.<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
3
<strong>PDF</strong>/UA (ISO 14289)<br />
§� PUBLISHED<br />
§� (just this week)<br />
§� US TAG is developing an “implementation guide” to help developers produce<br />
compliant documents<br />
§� Working in conjunction with the WCAG “best practices around <strong>PDF</strong>” project<br />
§� Joint AdHoc Commi�ee formed with 32K to work on “Improvements to<br />
Tagging” for future versions of <strong>PDF</strong> (2.0?)<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
4
<strong>PDF</strong>/E (ISO 24517)<br />
§� <strong>PDF</strong>/E-2 : Long-term archiving of engineering documents<br />
§� CD3 is currently out for ballot<br />
§� Based on <strong>PDF</strong> 2.0 (ISO 32000-2)<br />
§� Aligned (but not necessary compatible) with <strong>PDF</strong>/A-3<br />
§� Two conformance levels – with and w/o security/ encryption<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
5
<strong>PDF</strong>/A (ISO 19005)<br />
§� <strong>PDF</strong>/A-3 - PUBLISHED<br />
§� Commi�ee is currently going inactive, though members will be helping the<br />
<strong>PDF</strong>/E folks on their archival version.<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
6
<strong>PDF</strong> (ISO 32000)<br />
§� Currently in a second DIS<br />
§� LOTS of (major!) things are still being worked on<br />
§� Transparency<br />
§� Tagging & Structure<br />
§� Rich Text Fields<br />
§� JavaScript<br />
§� Expect at least two more DIS (or one DIS + one FDIS)<br />
§� Best case is end of 2013 for rati�cation<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
7
ICC<br />
§� Mobile & Web<br />
§� Spectral Data (ICC Labs – ICC.2)<br />
§� ICC DevCon <strong>2012</strong><br />
§� November 12, <strong>2012</strong><br />
§� In conjunction with CIC conference in Los Angeles, CA.<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
8
Questions<br />
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
Copyright 2010 Adobe Systems Incorporated. All rights reserved. Adobe con!dential.<br />
9<br />
®
© <strong>2012</strong> Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.
Process Control SC<br />
<strong>July</strong> 13th, <strong>2012</strong><br />
<strong>Ghent</strong><br />
Stephan Jaeggi<br />
Co-Chair Process Control SC
Agenda<br />
• Minutes of last meeting<br />
• Action items of last meeting<br />
• VIGC <strong>PDF</strong>/X-4 tests (Didier)<br />
• <strong>Ghent</strong> <strong>PDF</strong> Output Suite 4.0 (Stephan)<br />
– Feedback from reviewers (all)<br />
– Changes to patches (Didier, Peter)<br />
– 19.3 NChannel vs. DeviceN (Leonard)<br />
– Documentation (Didier, Peter, Stephan)<br />
• Assembly <strong>PDF</strong> White Paper (Leonard)<br />
• Problem Report tracking database<br />
• New Action items<br />
• Agenda for next meeting
Minutes of Oslo meeting (19.4)<br />
• Detailed slides of the meeting (which<br />
serve as also as minutes) were sent to<br />
SC list and uploaded twice to the GWG<br />
FTP on 20.4.<br />
• Approval<br />
– Yes: 6<br />
– No: 0<br />
– Abstention: 7<br />
– Note vote: 15
Action items from last meeting<br />
• Finish patches (DH, PK, StJ, LDR)<br />
– DH, PK, StJ: Done<br />
– LDR: Not done<br />
• Start documentation (DH, PK, StJ, LDR)<br />
– Not yet started<br />
• Assemble package for reviewers (StJ)<br />
– Done<br />
• Review (Reviewers)<br />
– Partially done<br />
• Assembly <strong>PDF</strong> White Paper (LDR)<br />
– ???
VIGC <strong>PDF</strong>/X-4 tests (Didier)<br />
This created confusion in the market.
<strong>Ghent</strong> <strong>PDF</strong> Output Suite 4.0b2<br />
• Received all the corrections from Didier<br />
and Peter Kleinheider. THANKS!!!<br />
• DeviceN/NChannel patch from Leonard<br />
missing...<br />
• Sent out existing patches for review<br />
– 19 separate patches<br />
– 2 A4 pages with 16 amalgated patches<br />
(without 3 optional content patches)
<strong>Ghent</strong> <strong>PDF</strong> Output Suite 4.0b2
Acrobat 9<br />
Different display in A9 + AX<br />
Acrobat X
Feedback<br />
• Leonard<br />
– 16.2: undefined blend spaces<br />
(original AI export) => fixed by Didier<br />
old new<br />
Correct display in Acrobat 9 with new patch!
<strong>Ghent</strong> <strong>PDF</strong> Output Suite 4.0b3<br />
• 16.2: set blendspace to DeviceCMYK<br />
• 17.3: Added a 0.5 pt line around the X<br />
to avoid ghost effect<br />
Maybe a good idea also for other patches!
19.2 DeviceN Overprint (Peter)<br />
• Ghosting effect in Acrobat<br />
(due to anti-aliasing)<br />
• Possible solution: adding a 0.5 pt line<br />
around the X to avoid ghost effect
Harlequin V9<br />
• Faint X in 17.0 (JPEG 2K)<br />
• Minor deviations in 16.9
Other Feedback<br />
• Successful tests by FOGRA<br />
– GMG Colorproof 5<br />
– EFI Fiery CMS 5<br />
– Heidelberg Prinect Meta Dimension 10.0<br />
• Roularta<br />
– Patch 20 (Color Conversion Indicator) did not<br />
change after processing with Ink Optimizer<br />
– Reason: Ink Optimizer first flattends<br />
transparency before applying color management.
19.3 NChannel vs. DeviceN (LDR)<br />
• New patch showing different behaviour of<br />
NChannel regarding alternate colors as<br />
DeviceN in case one of the colors is not<br />
available<br />
– DeviceN: All alternate colors are used<br />
– NChannel: only the alternate color of the<br />
missing color is used<br />
On 11.07.12 14:15, Leonard Rosenthol wrote:<br />
> Still nonexistent.<br />
dDecision to not include 19.3 in Output Suite 4.0
Next steps<br />
• Upload Beta 4 (jaeggi.info and GWG-FTP)<br />
• Remind reviewers to send feedback.<br />
• Ask vendor members to run the patches and<br />
report at the next meeting.<br />
• Create documentation for each patch<br />
(template is on the FTP server).<br />
• Prepare a press release.<br />
• Publish on www.gwg.org
Assembly <strong>PDF</strong> White Paper (LDR)<br />
• Many publishers are in process to go <strong>PDF</strong>/X-4<br />
during upcoming years.<br />
• Some will stay with <strong>PDF</strong>/X-1a for a while.<br />
• The assembly process of ads with different<br />
flavours and different output intents (and<br />
editorial stuff) might cause problems, or at<br />
least challenges.<br />
• Different applications do play a role here:<br />
InDesign, Adobe Library, Quark(?)<br />
• Which issues should publishers / printers be<br />
aware of, when managing the assembly of<br />
multiple <strong>PDF</strong>s in one page?<br />
• This should be the goal of this white paper.<br />
Promised for next meeting!
Problem report tracking<br />
• 2 new problems (Søren + Stephan)<br />
• 17 open problems; 3 problems solved
.notdef Bug<br />
• Again a support case this week<br />
Dov reported that the promised is fixed in InDesign 8.0
New (and open) actions items<br />
• <strong>Ghent</strong> <strong>PDF</strong> Output Suite 4.0<br />
– Fix patch 19.2 (Peter)<br />
– Upload Beta 4 on jaeggi.info and GWG-FTP<br />
(Stephan)<br />
– Remind reviewers to send feedback (Stephan)<br />
– Ask vendor members to run the patches and<br />
report at the next meeting (Stephan)<br />
– Create documentation for each patch<br />
(template is on the FTP server) (Didier, Peter,<br />
Stephan).<br />
– Prepare a press release (Stephan)<br />
• Assembly <strong>PDF</strong> White Paper (Leonard)
Agenda for next meeting<br />
• Action items from last meeting<br />
• <strong>Ghent</strong> <strong>PDF</strong> Output Suite 4.0<br />
• Assembly <strong>PDF</strong> White Paper (LDR)<br />
• Problem Report tracking database<br />
• New (and open) Action items<br />
• Agenda for next meeting
Marketing Subcommittee Meeting<br />
Marketing<br />
Subcommittee<br />
Meeting Minutes<br />
info@gwg.org<br />
www.gwg.org<br />
Authors Hanne Josefsen<br />
Marketing Officer<br />
Isabelle De Milde<br />
Admin Assistant<br />
Date 13-Jul-12<br />
Status Final
Marketing Subcommittee Meeting<br />
Table of Contents<br />
1 Minutes .......................................................................................................... 3<br />
1.1 Member Profiles ............................................................................................ 3<br />
1.2 Website ....................................................................................................... 3<br />
1.3 Press Releases .............................................................................................. 3<br />
1.4 Seminar at Graph Expo .................................................................................. 3<br />
1.3 Downloads ................................................................................................... 3<br />
2 Action items ................................................................................................... 4
Marketing Subcommittee Meeting<br />
1 Minutes<br />
1.1 Member profiles<br />
There is a request from some members to not use specific persons but the companies<br />
themselves for the member profiles on our website.<br />
- no issue to quote the company or name the representatives of the company<br />
1.2 Website<br />
Reactions to the proposal to update the website:<br />
- There is a request to update with RSS feeders to update members when there is<br />
something new<br />
- Provide an easy link to download on the homepage<br />
- Create a homepage with a clear overview and not too much text<br />
- Leonard raises a question about maintenance: security patches/template updates.<br />
There is a suggestion to keep Alex on retainer to help when needed<br />
- Dave Z raises the issue we have to ensure we have a continuity of the specification<br />
download system; that need to be discussed with Alex<br />
- Responsibility for the content: marketing team<br />
- Isabelle to send an overview of GWG presence on members website to Hanne<br />
1.3 Press Releases<br />
- Upon creation of press releases, send these first to the marketing team then to the<br />
group<br />
- Press release for the <strong>PDF</strong>/X survey (Peter K)<br />
- Press release for the CM survey (Bart)<br />
1.4 Seminar at Graph Expo<br />
- Members to let Isabelle know who needs Graph Expo passes<br />
- There is cross promotion with Graph Expo for the GWG seminar (included in their<br />
overview and a link to our website)<br />
- Create a white paper for the new specifications (who?)<br />
- Record the presentations during the seminar and put the videos online<br />
1.5 Downloads<br />
We do track the number of visits/downloads on our website. It would be a good idea to<br />
present this at the next meeting.
Marketing Subcommittee Meeting<br />
2 Action items<br />
Action Item Assigned to Due<br />
Send an overview of GWG presence on members<br />
website to Hanne<br />
Isabelle<br />
Ask Isabelle for Graph Expo passes Isabelle<br />
Discuss website issues with Alex Hanne
Marketing Subcomittee<br />
Hanne Josefsen<br />
<strong>July</strong> 13, <strong>2012</strong>
Agenda<br />
• Different goals<br />
• How to reach the market<br />
− website<br />
− memberprofiles<br />
− seminars
Different goals<br />
• To get the market to use the new<br />
specifications<br />
− Different levels, designers, printers and vendors<br />
• Why and how<br />
– Why should the market use GWG-settings?<br />
– Why should the market trust GWG as the standard for <strong>PDF</strong><br />
– How to use the settings, and how to implement it in the workflow<br />
• To get new members<br />
• What are the benefits to becoming a member of GWG?<br />
• Why should the member pay the fee and use free time to work<br />
in GWG - what is in it for them?<br />
• What does GWG want from new members?<br />
(active participant)
Member profiles<br />
• Each member shall have their own<br />
profile on the GWG website<br />
• Template is made to fill out easily, and<br />
we will take pictures of everybody.
Website<br />
• Update existing GWG website to a userfriendly<br />
Wordpress format<br />
• Easy to update<br />
− we will make a timetable for updating the<br />
website<br />
• Easy to integrate with social networks as<br />
facebook, linkedin and twitter<br />
• Easily handle future article updates as new<br />
news/events happen<br />
• Put video of seminars online
Member Marketing<br />
• Each member takes responsibility to<br />
talk about the GWG<br />
− in social media<br />
− in local seminars<br />
− update local associations<br />
− link to the website from their own websites
Press releases<br />
• One per quarter minimum<br />
• After each meeting<br />
• Before every seminar
Why <strong>PDF</strong>/X-4 + GWG<br />
• Text for the market is made by Peter<br />
Kleinheider to use in press release and<br />
on the web
Seminars<br />
• GraphExpo<br />
− no charge for the room<br />
− link to GWG page with info<br />
− add seminar to GraphExpo schedule (1/2 day)<br />
− events schedule will be checked to avoid<br />
conflict<br />
− GWG members get a free expo pass to<br />
GRAPH EXPO
Timetable website<br />
• 2 1/2 months (including testing &<br />
training time) starting <strong>July</strong> <strong>2012</strong><br />
(site development and launch by<br />
10-sep-12)
Thank You!
GWG Cross Media SC Minutes - 13 <strong>July</strong> <strong>2012</strong><br />
Cross Media<br />
subcommittee<br />
Meeting Minutes <strong>Ghent</strong> <strong>July</strong> 13th, <strong>2012</strong><br />
info@gwg.org<br />
Authors Elli Cloots<br />
Bart van Looy<br />
Erwin Danis<br />
Date 16 <strong>July</strong> <strong>2012</strong><br />
Status Final<br />
www.gwg.org
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
Table of Contents<br />
1 Minutes .......................................................................................................... 3<br />
1.1 Approval meeting minutes .............................................................................. 3<br />
1.2 Co-Chairs ..................................................................................................... 3<br />
1.3 Action items status ........................................................................................ 3<br />
1.4 <strong>PDF</strong> export for mobile devices (BVL) ................................................................ 3<br />
1.5 <strong>PDF</strong> standards survey – presentation of the survey results (PK*) ......................... 5<br />
1.6 Ad Exchange in Digital Publications exchange (LR) ............................................. 5<br />
1.7 Standard Digital Photography – Presentation by Medibel+ .................................. 6<br />
1.8 General remarks/sugestions ........................................................................... 7<br />
2 Action items ................................................................................................... 8
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
1 Minutes<br />
1.1 Approval meeting minutes<br />
The meeting minutes (April meeting) were approved.<br />
1.2 Co-Chairs<br />
Andy P. resigned so there is no longer a third co-chair. Having only 2 co-chairs is ok for<br />
the group and for Bart and Erwin.<br />
Tom B is considering to be a candidate.<br />
1.3 Action items status<br />
• Press release � not done yet<br />
• Distribute draft <strong>PDF</strong> export settings for mobile devices � done<br />
• Test first <strong>PDF</strong> export settings for mobile devices � no feedback<br />
• Presentation about raster images using XMP for “hot zones” � out of scope �<br />
closed<br />
• Proposal on aggregating files � still to do<br />
1.4 <strong>PDF</strong> export for mobile devices (BVL)<br />
Scope, goal, scenarios:<br />
How does a <strong>PDF</strong> file need to look in order to be able to be used successfully in a nonprint<br />
destination, more specifically on a tablet?<br />
2 starting points:<br />
- Repurposing <strong>PDF</strong> files that have been created for high quality print or another<br />
purpose and will be reused in a tablet environment (usually starting as a <strong>PDF</strong>/X1a<br />
file)<br />
- Generate content as <strong>PDF</strong> for use in cross-media workflows<br />
Goal:<br />
The goal is to end up with a <strong>PDF</strong> file that meets the following requirements; smallest file<br />
size possible, fast buildup speed, correct viewing (content wise without artifacts −<br />
color!), keep text as text (text recognition)<br />
Scenarios:<br />
- <strong>PDF</strong> creation (export from creative applications).<br />
- <strong>PDF</strong> optimization (optimization of current <strong>PDF</strong>'s mostly intended for PRINT<br />
purposes).<br />
- Interactive <strong>PDF</strong> (currently out of scope due to a lack of support of these features<br />
in Readers on mobile devices).<br />
1.4.1 Quality tests<br />
No feedback from the group.
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
Tests done by Roularta – presented by PM<br />
Conclusions:<br />
• iPad 3 gives a way better quality for the smaller tests files.<br />
• 300 dpi even gave moiré effect on iPad 3.<br />
• Going to a higher resolution doubles the file size.<br />
So it’s best to stay on 150 dpi above 200 dpi<br />
We should also do tests to see what happens if you create the files with these settings,,<br />
the Roularta tests were all focused on downsampling starting from a high-res print-ready<br />
pdf.<br />
Who volonteers to test more?<br />
• Peter Kleinheider can help with with technical data but the files should come from<br />
the publishers.<br />
• Bart Van Looy, Peter Maes<br />
• Provide Diane with a description on what needs to vbe tested and she’ll try to get<br />
more volonteers.<br />
• Tom Beckenham is willing to help test or get people to do them.<br />
Remarks:<br />
• Can we put the results of the tests on the website? Yes (action item Bart/Peter).<br />
• Tom sais that nobody puts <strong>PDF</strong>s on the tablet. Bart doesn’t agree, this might be<br />
an intermediate thing, but still it is happening today. Leonard points out that we<br />
should stick to our first goal which is to view <strong>PDF</strong> through a native <strong>PDF</strong> viewer on<br />
a tablet. Possible <strong>PDF</strong>-into-app conversions were set at a lower priority.<br />
• What are the difference between the GWG<strong>2012</strong> export settings and the ones for<br />
this purpose?<br />
o Downsampling value<br />
o Bleed<br />
o We keep the RGB version<br />
• We’ll also discuss to change some settings to avoid the dull CMYK colors<br />
1.4.2 Color conversion or not<br />
What is the problem?<br />
- A <strong>PDF</strong> that is completely RGB is fine for tablet viewing as the device is RGB.<br />
- Once you have a CMYK object with transparency on the page, the RGB image is<br />
first converted to CMYK as it needs to go to the page blanding color space for<br />
rendering the transparency (and this blending color space is by default<br />
DeviceCMYK) . As the device is RGB, you’ll have a second conversion to RGB also<br />
again for the RGB imgae.<br />
- But the result is that the RGB objects will become less vivit like it would be with<br />
CMYK images (because of the double conversion).<br />
- Also there is no consistency between the different applications that can view <strong>PDF</strong>s<br />
as all of them need to do the conversions for viewing (and the file is not stored<br />
like that).<br />
Test results:<br />
• See also the presentation by Peter Kleiheider - Bart Van Looy for detailed test<br />
results
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
• Test 2: the blendspace is device RGB and the objects are all RGB so no<br />
conversions needed. Result is that there are very little differences anymore so it is<br />
a lot more consisten. Viewing is faster as no coversions are needed anymore.<br />
• CMYK slide: the renderer is doing the transparency rendering but in 2 applications<br />
this is just ignored.<br />
The advice is that we should do conversion to RGB and change the blendcolor space to<br />
RGB. This is not without concequences as some transparency effects have weird results,<br />
but it seems the best option for now.<br />
Action item should be to do tests to detect the transparency effects that cause a<br />
problem.<br />
All tests that happened on apple devices.<br />
Question: could we flatten before to avoid problems?<br />
No as this gives other problems:<br />
- file size goes up<br />
- stiching problems (quality issues)<br />
- would still be a problem of flat colors or split objects, etc.<br />
Note:<br />
Currently you can only have a pdf that is good for tablet or one that is good for print but<br />
it is not possible to have both in 1 file. We should start investigating into how we would<br />
be able to do this if we ever want this to be possible.<br />
1.5 <strong>PDF</strong> standards survey – presentation of the survey<br />
results (PK*)<br />
Survey of CMBO / DalTC, NUV, Printarena.nl in the Netherlands and Febelgra, Medibel +<br />
and VIGC in Belgium "for graphic companies about using <strong>PDF</strong> and <strong>PDF</strong>-based standards<br />
See presentation, including conclusion.<br />
See presentation for all the feedback<br />
- Missing standards: mainly digital print and X-media<br />
- 15-30 % doesn’t preflight<br />
We would like to get the survey so that we can also send it out exactly the same in<br />
English? Marketing can advertise this survey and then we consolidate all the results.<br />
Menno will do a translation<br />
Peter Claes offers to help to proof why you need <strong>PDF</strong>/X-4 as he has an automated<br />
process to count the number of errors. Peter is willing to describe why this is important<br />
and how to use it.<br />
1.6 Ad Exchange in Digital Publications exchange (LR)<br />
4 different Ad Types:<br />
- (SFP) Straight from Print > replicated straight from print submission<br />
- (SFP+) Straight from Print Plus >replicated straight from print submission<br />
allowing URLs<br />
- (DFT) Designed for Tablets >purpose built for tablet, matching print ad and<br />
allowing URLs & Media
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
- (EFT) Enhanced for Tablets >purpose built for tablet ad with enhancements<br />
Idealiance: does not agree with the definitions – Diane will work with Leonard and Bart to<br />
finetune the definitions.<br />
Feedback:<br />
• Leonard wants to ty the formats to the different types of ads to know how to go<br />
forward.<br />
• Bart: there is a problem to exchange the ads, especially those with interactive<br />
content. And we need to think about how we can solve the future. Everyone is<br />
using different kind or combinations of tools to create aggregate, validate, view<br />
advertisements. Because there are no rules and standards this causes issues and<br />
misunderstanding from time to time.<br />
• The goal should be to go directly to a tablet optimized version. Expectation is that<br />
the ads will be send into HTML.<br />
• Today the digital part is very much at the publishers side and not at all at the ad<br />
agency side. The published doesn’t as the agency as they don’t have the tools to<br />
create and view it.<br />
• ePub (3) can not be used as this is for a complete publication as this is a much<br />
more complete format that overshoots the purpose of trasfering an ad. (Even<br />
though they are conseptionally very similar).<br />
Conclusions:<br />
• We all agree that we need an open standard to allow this.<br />
• We need a solution that is <strong>PDF</strong> bases (Leonard: not only as an intermediate think)<br />
• We need the HTML5 based part<br />
• We skip the image/rasterized format.<br />
• Focus on <strong>PDF</strong>/X-4 for digital ads. Everybody agrees to start working on this and<br />
try to get it as the industry standard. The Spectrum conference wants to focus on<br />
this (Leonard, Diane- BArt will discuss).<br />
• We’ll start working on “AOM-“. (Open Ajax Metadata) AOM has no restrictions<br />
(which is a pro and con) on what you can put into it. E.g. it can load images from<br />
the internet, do streaming, ett. It is HTML5 based, with support for XML so we can<br />
continue to use the job ticket as we have it today, and much more.<br />
• .Folio is not something that Adobe is willing to push forward as the new standard<br />
for digital publishing. It is and will remain the internal Adobe format for DPS.<br />
• Adobe is starting to talk with other vendors to ensure that this way of thinking will<br />
be implemented by other vendors in the future<br />
1.7 Standard Digital Photography – Presentation by<br />
Medibel+<br />
Proposed changes:<br />
See presentation for overview of proposed changes<br />
Question:<br />
Why do we still use metadata in IPTC and not just in XMP?<br />
Because it is still used daily, e.g. part of newspaper systems, used by default in<br />
databases, etc.<br />
Feedback on proposal:<br />
Send feedback to: peter.maes@roularta.be & bart.vanlooy@sanomamedia.be<br />
before august 15 th <strong>2012</strong>
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
To be reviewed and approved by the group by/before the next meeting.<br />
1.8 General remarks/sugestions<br />
1.8.1 Do we need a preflight profile?<br />
Yes, we need to define what the issues are that we should detect.<br />
We’re not ready to get started on this yet but should stay on the list.
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
2 Action items<br />
Action item Assigned to Due<br />
Press release survey cross media Bart Van Looy ASAP<br />
Send out updated <strong>PDF</strong> export settings<br />
for mobile devices + color changes +<br />
several resolutions<br />
Test first <strong>PDF</strong> export settings for mobile<br />
devices<br />
Proposal on aggregating files Leonard<br />
Rosenthal<br />
Provide Diane with a description on what<br />
needs to be tested with the <strong>PDF</strong> export<br />
settings.<br />
Get the publishers to test the <strong>PDF</strong> export<br />
settings<br />
Bart Van Looy ASAP<br />
All Before next meeting<br />
Next meeting ? (to be<br />
confirmed)<br />
Bart Van Looy End of <strong>July</strong><br />
Diane<br />
Kennedy<br />
Test the <strong>PDF</strong> export settings Tom<br />
Beckenham<br />
Put the results of the tests on the<br />
website<br />
Do tests to detect the transparency<br />
effects that cause a problem when<br />
converting to RGB and changing the<br />
blend color space to RGB.<br />
Finetune the definitions SFP, SFP+, DFT,<br />
EFT +<br />
Bart Van Looy<br />
Peter Maes<br />
By next meeting<br />
By next meeting<br />
By next meeting<br />
All By next meeting<br />
Bart, Tom,<br />
Diane and<br />
Leonard<br />
Translate the <strong>PDF</strong> Standards survey Menno Mooy ASAP<br />
Send out the <strong>PDF</strong> Standards survey<br />
through as many channels as possible<br />
Review and approve proposed changes<br />
for Standard Digital Photography<br />
Describe on how everyone can use the<br />
automated process to count number of<br />
errors. To prove the need for <strong>PDF</strong>/X-4<br />
Marketing SC ASAP<br />
By next meeting<br />
All Send feedback to<br />
peter.maes@roularta.be &<br />
bart.vanlooy@sanomamedia.be<br />
before august 15 th <strong>2012</strong><br />
Peter Claes Before next meeting<br />
Note: all action items should be listed here, have an assignee and if possible a due date.<br />
Used (name) abbriviations<br />
BVL BArt Van Looy<br />
LR Leonard Rosenthol<br />
PK Peter Kleinheider
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
TB Tom Beckenham<br />
PK* Peter Korsmit<br />
PM Peter Maes<br />
DK Dianne Kennedy
Cross Media SC<br />
BArt Van Looy, Sanoma Media<br />
Erwin Danis, Peter Maes Medibel+<br />
Co-chair(s) Cross Media Subcommittee<br />
<strong>Ghent</strong> <strong>July</strong> 27 th, <strong>2012</strong>
Agenda<br />
• Before lunch<br />
− Approval meeting minutes (ALL)<br />
− Co-chair (ALL)<br />
− Done since last meeting (ALL)<br />
− <strong>PDF</strong> export for mobile devices (BVL)<br />
• After lunch<br />
− <strong>PDF</strong> and Image usage for ad distribution"…. (LR)<br />
− Agenda for next meeting (ALL)<br />
Extra<br />
− Update Digital Photography v3 – Medibel + (PM)<br />
− Results <strong>PDF</strong>/X-4 Belgium – Netherlands (PKorsmit)
Approval meeting minutes<br />
• Oslo meeting<br />
meeting minutes<br />
v2<br />
• Yes / No ?<br />
<strong>Ghent</strong> <strong>PDF</strong> <strong>Workgroup</strong> Cross Media SC<br />
1 Minutes<br />
1.1 Approval meeting minutes<br />
No meeting minutes from the last meeting.<br />
Meeting minutes will be created from now on for each Cross Media SC meeting.<br />
1.2 Done since last meeting<br />
� Press release about cross media survey results is in preparation, release after the<br />
meeting.<br />
� Conference calls to discuss “<strong>PDF</strong> export for mobile devices” testing and creation of<br />
first export settings proposal<br />
� Additional testing for “optimization of <strong>PDF</strong> files for tablets”<br />
1.3 <strong>PDF</strong> export for mobile devices (BVL, AP, DVD,...)<br />
1.3.1 Scope, goal, scenario's<br />
How does a <strong>PDF</strong> file need to look in order to be able to be used successfully in a nonprint<br />
destination, more specifically on a tablet?<br />
2 starting points:<br />
- Repurposing <strong>PDF</strong> files that have been created for high quality print or another<br />
purpose and will be reused in a tablet environment (usually starting as a <strong>PDF</strong>/X1a<br />
file)<br />
- Generate content as <strong>PDF</strong> for use in cross-media workflows<br />
Goal:<br />
The goal is to end up with a <strong>PDF</strong> file that meets the following requirements; smallest file<br />
size possible, fast buildup speed, correct viewing (co�������������������������������color<br />
!), keep text as text (text recognition)<br />
Scenarios:<br />
- <strong>PDF</strong> creation (export from creative applications).<br />
- <strong>PDF</strong> optimization (optimization of current <strong>PDF</strong>'s mostly intended for PRINT<br />
purposes).<br />
- Interactive <strong>PDF</strong> (currently out of scope due to a lack of support of these features<br />
in Readers on mobile devices).<br />
1.3.2 Tests view results on tablets<br />
Several tests done by Andy, Bart, David and others to get a good overview of the current<br />
support capabilities for <strong>PDF</strong> on several iOS and tablets.<br />
Test - output suite v3, v4 on different devices<br />
If we open the test suite patches said Bart on different devices we can conclude that only<br />
the basic functionality of <strong>PDF</strong> is currently supported. The following things is barely or no<br />
support for;<br />
- Overprint is not supported<br />
- Output intent and color-management are barely supported
Status co-chair<br />
• Andy P. decided will be no longer one of the cochair<br />
of the Cross Media SC<br />
• Co-Chair(s), Any volunteer(s) ?<br />
− And no I don’t eat my Co-Chairs ;-)
Action items status<br />
Action item Assigned<br />
to<br />
Due Status ?<br />
Press release BVL May 5 th Not Done<br />
Distribute Draft <strong>PDF</strong> export<br />
version for mobile devices<br />
Test first <strong>PDF</strong> export settings<br />
for mobile devices<br />
Presentation/proposal;<br />
Raster images used<br />
embedded XMP for "hot<br />
zones"<br />
(LR, Adobe)<br />
Proposal on aggregating<br />
files<br />
BVL May 3 th Done<br />
ALL No feedback<br />
LR Next <strong>July</strong><br />
meeting<br />
LR Next <strong>July</strong><br />
meeting<br />
Closed, not in<br />
scope anymore<br />
?
“<strong>PDF</strong> export for mobile<br />
devices”<br />
Feedback conference calls<br />
Extra test results<br />
Next steps<br />
(BVL/DVD/PM/PK/LR/ALL …)
<strong>PDF</strong> export settings<br />
• First proposal: <strong>PDF</strong> export<br />
settings: GWG_CrossMedia_<strong>PDF</strong>X4_vD1<br />
− Based on<br />
• <strong>PDF</strong>/X-4-2010<br />
• <strong>PDF</strong> 1.6<br />
− No color conversion<br />
• CMYK stays CMYK<br />
• RGB stays RGB<br />
− No interactive elements included<br />
• Draft sent out after April<br />
meeting to the cm mailing<br />
group<br />
− No reaction so far
Working items<br />
• During last conference call 2 action items came<br />
out<br />
− Quality / resolution ?<br />
− Color conversion or not ?
Quality test<br />
• Knack magazine 108 pages<br />
• Goal: Quality check<br />
− Is 150 DPI enough for iPad 3 (New iPad)<br />
− Pinching or not ?!<br />
• Goal: consistency<br />
• Viewed by using the build in web viewer of iOS<br />
• iPad 2, iPad 3
Findings iPad 2 /iPad 3<br />
• Text & vector elements > sharpness<br />
iPad 2 iPad 3
Findings iPad 2 /iPad 3<br />
• Impact:<br />
− Sometimes to sharp<br />
− moirée
Findings iPad 2 /iPad 3<br />
• Hardly impact on images:<br />
− 150 – 200 – 225 - 256 - 300 Dpi<br />
− File size<br />
• Impact on file size<br />
DPI MB<br />
150 14,6<br />
200 19,2<br />
225 21,6<br />
256 24,6<br />
300 29,0
Color conversion or not ?<br />
• Question: Color conversion or not ?<br />
• Goal: consistency
Test 1<br />
• Conditions:<br />
− Images: RGB<br />
− Vector: CMYK<br />
− Blend space: CMYK<br />
• Founding's<br />
− Different rendering<br />
− Color difference<br />
(butterfly)
Test 2<br />
• Conditions<br />
− Images: RGB<br />
− Vector: RGB<br />
− Blend space: RGB<br />
• Founding's:<br />
− Color difference not as<br />
dramatic then for CMYK<br />
− All transparency effects<br />
are still visible
Test 3<br />
• Color is not as vivid even it is RGB<br />
• Objects cannot be seen<br />
CMYK RGB
RGB
CMYK
RGB<br />
• Used Dull<br />
• But result is the same
CMYK
Next steps<br />
• Definitive version export settings<br />
• Do we need “preflight” profiles ?<br />
• ….
“<strong>PDF</strong> and Image usage for<br />
ad distribution….”<br />
<strong>PDF</strong>/X-4 based (LR, Adobe)
Ad Exchange in Digital Publications<br />
Leonard Rosenthol | <strong>PDF</strong> Architect • Principal Scientist<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.
Ad Types<br />
1. (SFP) Straight from Print<br />
§� replicated straight from print submission<br />
2. (SFP+) Straight from Print Plus<br />
§� replicated straight from print submission allowing URLs<br />
3. (DFT) Designed for Tablets<br />
§� purpose built for tablet, matching print ad and allowing URLs & Media<br />
4. (EFT) Enhanced for Tablets<br />
§� purpose built for tablet ad with enhancements<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
2
What’s the problem?<br />
In a “pure Adobe” work�ow, everything just works…<br />
§� Our tools utilize a proprietary format (.folio) to<br />
exchange rich information about digital publication<br />
authoring.<br />
Unfortunately, some people use tools from other companies L�<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
3
Standardizing Formats for Submission<br />
Straight from Print X X 1<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
<strong>PDF</strong>/X-1a <strong>PDF</strong>/X-4 Raster (PNG/JPG) HTML5-based<br />
Straight from Print Plus X 2 X 1,2 X 3<br />
Designed for Tablets X 2 X 1,2 X 3<br />
Enhanced for Tablets X<br />
1 Hopefully the industry will move towards X-4, though not there today<br />
2 <strong>PDF</strong>/X doesn’t support having annotations (inside Bleed) – will need exception<br />
3 Raster images with embedded XMP for “hot zones”<br />
4
So what’s missing & what do we really need?<br />
§� <strong>PDF</strong>/X doesn’t support having annotations/links (inside Bleed)<br />
§� How to handle this?<br />
§� Can’t call it <strong>PDF</strong>/X if we allow this<br />
§� Authoring is no problem (could create the JobOptions �les), but we’d need special Pre�ight<br />
se�ings<br />
§� Could use <strong>PDF</strong>/A, but no support for direct <strong>PDF</strong>/A from creative tools<br />
§� <strong>PDF</strong>/X-1 vs. X-4<br />
§� Hopefully the industry will move towards X-4, though not there today<br />
§� Could we use this as a driver for X-4, as X-1a was for print ads??<br />
§� Raster images with embedded XMP for “hot zones”<br />
§� Do we really need this? Andy wanted it, but does anyone else?<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
5
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential. 6
Open Ajax Metadata<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
7
OpenAjax metadata<br />
§� h�p://www.openajax.org/member/wiki/OpenAjax_Metadata_Speci�cation<br />
§� OpenAjax Metadata represents a set of industry-standard metadata de�ned by<br />
the OpenAjax Alliance that enhances interoperability across Ajax toolkits and<br />
Ajax products.<br />
§� UCF (Universal Container Format) �le containing<br />
§� the OAM XML �le<br />
§� CSS (if any)<br />
§� Assets (images, etc. if any)<br />
§� XMP-based Metadata (if any)<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
8
Adobe’s Support for OAM<br />
§� Adobe Dreamweaver CS 5.x/CS6<br />
§� Widget Browser<br />
§� Import to page<br />
§� Adobe Edge<br />
§� Export animations as<br />
§� Adobe InDesign CS6<br />
§� Import animation<br />
§� Adobe Muse<br />
§� Import animation<br />
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.<br />
9
© 2011 Adobe Systems Incorporated. All Rights Reserved. Adobe Con�dential.
Digital Photography v3<br />
Medibel +
1. SCREEN CALIBRATION<br />
Whitepoint: 6500 K in non-normalized ambient light<br />
Whitepoint: 5000 K in normalized ambient light<br />
Gamma 2.2, The calibration of the screen has to be done with a professional measuring device.<br />
Luminance: 100 cd/m 2<br />
2. GENERAL COLOUR SETTINGS FOR EVALUATION ON SCREEN<br />
For evaluation of the RGB image use the adjusted settings.<br />
MEDIBEL+ NEWS PHOTOGRAPHY<br />
ISOnewspaper26v4<br />
Standaard Digital Photography NEWS PHOTOGRAPHY v.3 march <strong>2012</strong><br />
Standaard Digital Photography NEWS PHOTOGRAPHY v.3<br />
june <strong>2012</strong><br />
screenshot Photoshop CS5<br />
3. SHOOT, OPTIMIZE AND SAVE<br />
Low End Camera<br />
Shoot in JPEG, maximum quality (eg. Fine, Best, ...). The colour space is Adobe RGB or sRGB and is automatically saved with the image.<br />
The picture is saved as JPEG (.jpg) with, compression 8 / baseline (minimum setting). Forward the unprocessed image with embedded profile.<br />
Do not convert the RGB image to CMYK. The necessary adjustments for the printing process are made by the publisher.<br />
Open in Photoshop:<br />
If the shot was done in sRGB, this colour space has to be embedded in the image.<br />
Do not convert profiles in image editing programmes!<br />
screenshot Photoshop CS5 and higher<br />
Attention please: This setting is only<br />
necessary when the image is converted<br />
to CMYK. We strongly advise against<br />
converting RGB images to CMYK. The<br />
CMYK color space can be used for soft proofing<br />
the RGB image on the screen (on a calibrated<br />
monitor only). For that purpose use<br />
the correct CMYK printing profile depending<br />
on the printing process and substrate (paper).<br />
Colour Management Policies: Preserve<br />
embedded profile: It is very important that<br />
the profile is embedded in the image. In this<br />
way, the image always opens in the right<br />
colour space.<br />
Conversion Options: This does not<br />
apply because these options are only used<br />
whenthe image is converted to another<br />
colour space.
High End Camera<br />
Shoot in raw:<br />
Images have to be shot in RAW.<br />
Attention please: In some cases shots in JPEG Fine with Adobe RGB colour space can be sufficient,but they can only be used in consultation with the client.<br />
After optimization save in JPEG maximum quality<br />
Optimization must be done in the raw convertor of the camera, in the raw convertor of Photoshop CS<br />
or in another raw convertor<br />
screenshot Photoshop CS5 and higher<br />
Do not convert the RGB image to CMYK. This also applies to analogue pictures scanned by the photographer.<br />
Always embed the colour space and/or the colour profile!<br />
Photoshop Settings when saving the file:<br />
4. NAME<br />
Use a descriptive name for the images, e.g. abbreviationphotographer_productionname_ddmmyy.extension<br />
Special characters, spaces, punctuation marks and accented characters are not allowed in the name.<br />
Allowed are: a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z / 0,1, 2, 3, 4, 5, 6, 7, 8, 9 /A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z /<br />
‘underscore’ and the ‘dot’ before the extension. Attention please: max. 23 signs not including the ‘dot’ and the ‘extension’ (max. 28 signs)<br />
Some examples: jv_herftsmode_140612.jpg / mvl_geboorte_111012.jpeg / jvc_parijs_praag_211112.jpg<br />
5. IPTC INFORMATION<br />
Standaard Digital Photography NEWS PHOTOGRAPHY v.3 march <strong>2012</strong><br />
Standaard Digital Photography NEWS PHOTOGRAPHY v.3<br />
june <strong>2012</strong><br />
When opened in Photoshop:<br />
If the shot was done in sRGB, this colour space has to be embedded in the image.<br />
Do not convert profiles in image editing programmes!<br />
screenshots Photoshop CS5 and higher<br />
We recommend Adobe RGB.
8. IMAGE RESOLUTION AND SIZE<br />
The optimal resolution for news photography is 300 pixels/inch<br />
This setting is immediately OK if the image is treated in the RAW convertor as described above.<br />
With a shot in JPEG-fi ne the resolution can be changed in the image size window<br />
as described below.<br />
9. EXAMPLE<br />
Standaard Digital Photography NEWS PHOTOGRAPHY v.3<br />
june <strong>2012</strong><br />
6. THE FOLLOWING IPTC FIELDS SHOULD ALWAYS BE FILLED IN!<br />
IPTC NUMBER/NAME PHOTOSHOP NAME XMP NAME CONTENT<br />
Production date, correction date and exif-data are saved automatically.<br />
The place of the data can be different depending on the version of Photoshop or other programmes to add IPTC data!<br />
7. DATA EXCHANGE<br />
Electronic data exchange can be done by FTP or e-mail (This has to be done in consultation with the publisher.).<br />
The photographer keeps the original RAW file, which can be demanded if necessary.<br />
screenshot Photoshop CS5 and higher<br />
When the image is saved after entering the<br />
resolution of 300dpi, the image immediately<br />
appears with realistic dimensions in the<br />
publisher’s lay-out.<br />
To recalculate the image pixels<br />
you have to turn OFF Resample Image.<br />
MAX NUMBER<br />
CHARACTERS<br />
5 Title Document Title Title Image name 64<br />
80 Creator Author Creator Photographer’s name 32<br />
120 Description Description Description<br />
116<br />
Copyright<br />
Notice<br />
Copyright Notice Copyright Notice<br />
25 Keywords Keywords Keywords<br />
110 Credit Credit Provider<br />
Standaard Digital Photography NEWS PHOTOGRAPHY v.3 march <strong>2012</strong><br />
Description of the<br />
content of the image<br />
If the copyright status<br />
is active, owner of the<br />
image<br />
Terms or keywords<br />
describing the subject<br />
Supplier, payment<br />
receiver<br />
2000<br />
128<br />
64<br />
32<br />
REMARKS<br />
e.g. The ministers vote on<br />
a new taxation<br />
Strongly recommendable<br />
keywords:<br />
- place (city or country)<br />
- person or object<br />
- event<br />
- category
1. SCREEN CALIBRATION<br />
Whitepoint: 6500 K in non-normalized ambient light<br />
Whitepoint: 5000 K in normalized ambient light<br />
Gamma 2.2, The calibration of the screen has to be done with a professional measuring device.<br />
Luminance: 100 cd/m 2<br />
2. GENERAL COLOUR SETTINGS FOR EVALUATION ON SCREEN<br />
For evaluation of the RGB image use the adjusted settings.<br />
MEDIBEL+SHOOTINGS<br />
ISOcoated_V2_300_eci<br />
3. SHOOT, OPTIMIZE AND SAVE<br />
Shoot in raw:<br />
Images have to be shot in RAW.<br />
Attention please: In some cases shots in JPEG Fine with Adobe RGB colour space can be sufficient,<br />
but they can only be used in consultation with the client.<br />
Standard Digital Photography SHOOTINGS v.3 march <strong>2012</strong><br />
Standard Digital Photography SHOOTINGS v.3<br />
june <strong>2012</strong><br />
screenshot Photoshop CS5<br />
After optimization save in JPEG maximum quality<br />
Optimization must be done in the raw convertor of the camera, in the raw convertor of Photoshop CS or in another raw convertor<br />
When opened in Photoshop:<br />
If the shot was done in sRGB, this colour space has to be embedded in the image.<br />
Do not convert profiles in image editing programmes!<br />
screenshot Photoshop CS5 and higher<br />
Attention please: This setting is only<br />
necessary when the image is converted<br />
to CMYK. We strongly advise against<br />
converting RGB images to CMYK. The<br />
CMYK color space can be used for soft proofing<br />
the RGB image on the screen (on a calibrated<br />
monitor only). For that purpose use<br />
the correct CMYK printing profile depending<br />
on the printing process and substrate (paper).<br />
Colour Management Policies: Preserve<br />
embedded profile: It is very important that<br />
the profile is embedded in the image. In this<br />
way, the image always opens in the right<br />
colour space.<br />
Conversion Options: This does not<br />
apply because these options are only used<br />
whenthe image is converted to another<br />
colour space.
Do not convert the RGB image to CMYK. This also applies to analogue pictures scanned by the photographer.<br />
Always embed the colour space and/or the colour profile!<br />
Photoshop Settings when saving the file:<br />
4. NAME<br />
Use a descriptive name for the images, e.g. abbreviationphotographer_productionname_ddmmyy.extension<br />
Special characters, spaces, punctuation marks and accented characters are not allowed in the name.<br />
Allowed are: a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z / 0,1, 2, 3, 4, 5, 6, 7, 8, 9 /A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z /<br />
‘underscore’ and the ‘dot’ before the extension. Attention please: max. 23 signs not including the ‘dot’ and the ‘extension’ (max. 28 signs)<br />
Some examples: jv_herftsmode_140605.jpg / mvl_geboorte_111011.jpeg / jvc_parijs_praag_111011.jpg<br />
5. IPTC INFORMATION<br />
Standard Digital Photography SHOOTINGS v.3 march <strong>2012</strong><br />
Standard Digital Photography SHOOTINGS v.3<br />
june <strong>2012</strong><br />
screenshots Photoshop CS5 and higher<br />
We recommend Adobe RGB.
6. THE FOLLOWING IPTC FIELDS SHOULD ALWAYS BE FILLED IN!<br />
IPTC NUMBER/NAME PHOTOSHOP NAME XMP NAME CONTENT<br />
Production date, correction date and exif-data are saved automatically.<br />
The place of the data can be different depending on the version of Photoshop or other programmes to add IPTC data!<br />
7. DATA EXCHANGE<br />
Electronic data exchange can be done by FTP or e-mail (This has to be done in consultation with the publisher.).<br />
The photographer keeps the original RAW fi le, which can be demanded if necessary.<br />
8. IMAGE RESOLUTION AND SIZE<br />
The optimal resolution for shootings is 300 pixels/inch<br />
This setting is immediately OK if the image is treated in the RAW convertor as described above.<br />
With a shot in JPEG-fi ne the resolution can be changed in the image size window<br />
as described below.<br />
9. EXAMPLE<br />
screenshot Photoshop CS5 and higher<br />
When the image is saved after entering the<br />
resolution of 300dpi, the image immediately<br />
appears with realistic dimensions in the<br />
publisher’s lay-out.<br />
To recalculate the image pixels<br />
you have to turn OFF Resample Image.<br />
MAX NUMBER<br />
CHARACTERS<br />
5 Title Document Title Title Image name 64<br />
80 Creator Author Creator Photographer’s name 32<br />
120 Description Description Description<br />
116<br />
Copyright<br />
Notice<br />
Copyright Notice Copyright Notice<br />
25 Keywords Keywords Keywords<br />
110 Credit Credit Provider<br />
Standard Digital Photography SHOOTINGS v.3 march <strong>2012</strong><br />
Standard Digital Photography SHOOTINGS v.3<br />
june <strong>2012</strong><br />
Description of the<br />
content of the image<br />
If the copyright status<br />
is active, owner of the<br />
image<br />
Terms or keywords<br />
describing the subject<br />
Supplier, payment<br />
receiver<br />
2000<br />
128<br />
64<br />
32<br />
REMARKS<br />
e.g. The ministers vote on<br />
a new taxation<br />
Strongly recommendable<br />
keywords:<br />
- place (city or country)<br />
- person or object<br />
- event<br />
- category
Feedback Survey results<br />
about the use of <strong>PDF</strong><br />
standards<br />
Survey of CMBO / DalTC, NUV, Printarena.nl in the<br />
Netherlands and Febelgra, Medibel + and VIGC in<br />
Belgium "for graphic companies about using <strong>PDF</strong><br />
and <strong>PDF</strong>-based standards
Survey goals<br />
• <strong>PDF</strong>/X-4 survey to gain insight into<br />
possible use.<br />
• Are manufacturing and supplying<br />
parties ready for use?<br />
• Demands of the market for other<br />
specifications (RGB, transparency,<br />
language versions)
Survey goals II<br />
• For delivery and processing<br />
• Measure success of print-ready <strong>PDF</strong><br />
• Review of quality communication with<br />
industry organizations
Overall impression<br />
• High response rate> 360<br />
− Many printers / printing companies<br />
• Q13 85% believe to have everything to<br />
create <strong>PDF</strong>/X-4?<br />
• Q33 70% Thinks they can handle<br />
<strong>PDF</strong> X/4?
Q1 Company Type NL & BE<br />
• Many (digital) printers<br />
• Delivery and processing
Q2 Printing Type NL/ BE<br />
• Deliveries and processing<br />
mostly for Sheetfed /<br />
Digital Printing
Q5 <strong>PDF</strong> usage B/NL<br />
• In Belgium, more native<br />
and image files (large<br />
size / PhotoShop)
Q8 GWG acceptance B/NL<br />
• NL somewhat higher<br />
GWG implementation
Q11 meet the standards NL/BE<br />
• For 14-18% the<br />
standards do not match
Q12 missing standards B/NL?<br />
• Digital printing and<br />
packaging standards,<br />
less known<br />
• <strong>PDF</strong> for X-media desired
Q13 Creating <strong>PDF</strong>/X-4? B/NL<br />
• 82% thinks they can<br />
create <strong>PDF</strong>/X-4
60,0%<br />
50,0%<br />
40,0%<br />
30,0%<br />
20,0%<br />
10,0%<br />
0,0%<br />
Q15 <strong>PDF</strong> incoming preflight B/NL<br />
Indien u <strong>PDF</strong>'s ontvangt, maakt u gebruik van speciale software<br />
voor ingangscontrole? (meerdere antwoorden mogelijk)<br />
Wij ontvangen geen<br />
<strong>PDF</strong>'s<br />
Gewoon controle<br />
met behulp van<br />
mijn teken of<br />
Ja, Callas<br />
pdfToolbox<br />
Ja, Markzware<br />
Flightcheck<br />
Anders, nl.:<br />
• 15 – 30% no preflight<br />
• Important for efficient<br />
"transparent production =<br />
cost-effective for all<br />
parties<br />
70,0%<br />
60,0%<br />
50,0%<br />
40,0%<br />
30,0%<br />
20,0%<br />
10,0%<br />
0,0%<br />
Indien u <strong>PDF</strong>'s ontvangt, maakt u gebruik van speciale software<br />
voor ingangscontrole? (meerdere antwoorden mogelijk)<br />
Wij ontvangen geen<br />
<strong>PDF</strong>'s<br />
Gewoon controle met<br />
behulp van mijn teken<br />
of<br />
Ja, Callas pdfToolbox<br />
Ja, Markzware<br />
Flightcheck<br />
Anders, nl.:
Q20 Freq. Problems NL/BE<br />
• Font errors!?!<br />
= no checks<br />
• Transparancy / Overprint<br />
• Color (Lab/RGB Spot)<br />
• Low Resolution<br />
• Layers (Language versions)<br />
• TAC
Q23 permit <strong>PDF</strong>/X-4 NL/BE<br />
• 80% Transparancy<br />
• 60–80% RGB icc<br />
• 40% RGB no icc
Q24 problems in <strong>PDF</strong> NL/BE<br />
• 66% experience<br />
(sometimes) <strong>PDF</strong>/X-1a<br />
problems and color<br />
problems
Q32 PostScript / <strong>PDF</strong> NL/BE<br />
• PostScript or <strong>PDF</strong> RIP<br />
• PostScript and <strong>PDF</strong> RIP<br />
• PS = no <strong>PDF</strong>/X-4<br />
= other workflow
Q33 <strong>PDF</strong>/X-4 RIP/Workflow NL/BE<br />
• Less than + / - 35%<br />
response?!<br />
• Tested?
Agenda for next meeting<br />
• Approval meeting minutes<br />
• <strong>PDF</strong> export for mobile devices<br />
• Other topics suggestion(s)???
Current standaards<br />
Supplying parties<br />
• For more than 80% <strong>PDF</strong>/X-1a good<br />
• 20% no preflight on files<br />
• + / - 15% of files are not good (output<br />
feedback)<br />
• 60% usage of FC Colorproofs<br />
• 50-60% ISO compliant Colorproofs
Current standaards<br />
Manufacturing parties<br />
• 25% experience with RIP problems<br />
• 28 – 46% font problems<br />
(not checked!!!!)<br />
• 40% RGB delivery m./z. Icc profiles?<br />
• 30% PMS at Full Colour<br />
• 30% transparancy
View on <strong>PDF</strong>/X-4<br />
• <strong>PDF</strong>/X-4 Supplying parties<br />
• Seems convinced about <strong>PDF</strong>/X-4<br />
• <strong>PDF</strong>/X-4 Receiving parties<br />
• Seems convinced about <strong>PDF</strong>/X-4<br />
• 50% will allow transparancy<br />
• 50% do not know if they can process <strong>PDF</strong>/X-4<br />
• RGB in NL more desirable<br />
• Layers in B more desirable
Conclusion<br />
• Good response<br />
• 40% seems happy with current <strong>PDF</strong>/X-1a<br />
− Will remain in use for long time<br />
• <strong>PDF</strong>/X-4 CMYK and ICC versions<br />
− Market request for new specifications<br />
( Transparancy, RGB, Layers)<br />
− Market request for new specifications<br />
( Large Format, Mobile Publications)<br />
− Lot off work to do:<br />
Education and support via Associations and GWG<br />
Information about RGB (icc) , transparancy, layers
In between the meeting<br />
• Conference call in between the meetings<br />
− Send out doodle(s) with dates<br />
• Separate working group(s) on the defined topics<br />
− Hand on testing<br />
− Need more calls in between to move forward
Thank You!
GWG Job Ticketing Minutes - 14 <strong>July</strong> <strong>2012</strong><br />
GWG Job Ticketing<br />
subcommittee<br />
Meeting minutes of <strong>July</strong> 14 <strong>2012</strong><br />
Authors Matthias Guenther & Tom Beckenham<br />
info@gwg.org<br />
www.gwg.org<br />
Date Sunday, 15 <strong>July</strong> <strong>2012</strong><br />
Status Final
GWG Job Ticketing Minutes - 14 <strong>July</strong> <strong>2012</strong><br />
Table of Contents<br />
Minutes ............................................................................................................... 3<br />
Approval of last meeting minutes ............................................................................ 3<br />
Co Chair .............................................................................................................. 3<br />
ADAM Ad Ticket & PSV .......................................................................................... 3<br />
JSON Ad Ticket .................................................................................................... 3<br />
Action items ........................................................................................................ 4
GWG Job Ticketing Minutes - 14 <strong>July</strong> <strong>2012</strong><br />
1 Minutes<br />
1.1 Approval of last meeting minutes<br />
The meeting minutes of Ad Ticketing of the Oslo meeting were approved by the group.<br />
1.2 Co Chair<br />
1.2.1 Description of the topic<br />
As Stéphane has resigned as co-chair. Tom nominated Diane.<br />
Nobody else was interested in co-chairing.<br />
1.2.2 Conclusion<br />
Diane accepted the nomination and was elected by unisonous vote.<br />
1.3 ADAM Ad Ticket & PSV<br />
Diane gave an overview of what used to be called NextPub, now PSV (Prism Source<br />
Vocabulary) and the ADAM Ad Ticket. See Diane’s slide deck for details.<br />
Dave pointed out that publishers he visited are looking to support PSV.<br />
Diane asked Leonard to talk to IAB to see whether they will start supporting it too, which<br />
Leonard agreed to do and will head creating a presentation about PSV.<br />
Diane will distribute a document about Best Practices about Positioning an Ad on a<br />
Tablet.<br />
1.4 JSON Ad Ticket<br />
Tom presented a JSON method to create an ad ticket and showed a demo of a JSON ad<br />
ticket instance.<br />
The JSON specs are still work-in-progress. For details please see the draft of the JSON<br />
specs. As there were still some questions, Diane and Tom will distribute the draft with<br />
requests for comments.<br />
Also Tom will set up a regular monthly call for the subgroup.
GWG Job Ticketing Minutes - 14 <strong>July</strong> <strong>2012</strong><br />
2Action items<br />
Action Item Assigned to Due<br />
Talk to IAB about PSV Leonard Next meeting<br />
Send URL of JSON specs draft to GWG members Tom asap<br />
Set up regular monthly calls for this subgroup Tom asap<br />
Note: all action items should be listed here, have an assignee and if possible a due date.