attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Smith,<div class=""><br class=""></div><div class="">I think we want to include the finishings registrations in the latest standard document.<div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 14, 2016, at 4:55 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I wasn't sure whether the registrations posted earlier to the reflector were sufficient or if they needed to be included. I will make these changes in the next draft, to be posted hopefully by EOD tomorrow, in preparation for the F2F.<div class=""><br class=""><div class=""><div class="">
Smith<br class=""><br class=""><br class="">
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On 2016-04-14, at 2:32 PM, Michael Sweet <<a href="mailto:msweet@apple.com" class="">msweet@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Bill,<div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Apr 14, 2016, at 4:06 PM, <a href="mailto:wamwagner@comcast.net" class="">wamwagner@comcast.net</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Menlo-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hi Smith,</div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">My notes indicated that EcoStaple (perhaps as “crimp”) and Engineering Z Fold values would be included in Finishings 2.1, but I do not see them. Am I just missing tem or was there a change of approach?</div></div></div></blockquote><br class=""></div><div class="">Yes, I think these should be in there but currently are not.</div><div class=""><br class=""></div><div class="">The changes that are needed are:</div><div class=""><br class=""></div><div class="">1. Figure 1: Add 'fold-engineering-z' (I owe you this one Smith)</div><div class=""><br class=""></div><div class="">2. New Section 5.1.x PWG 5100.1-YYYY "finishings Values"</div><div class=""><br class=""></div><div class=""> - New "finishings" enum value 101 with keyword name 'fold-engineering-z'</div><div class=""> - "Fold the hardcopy output vertically into three sections, forming a Z but leaving room for binding, punching, or stapling along the top edge."</div><div class=""><br class=""></div><div class="">3. Section 5.2.6.4 “folding” Examples</div><div class=""><br class=""></div><div class=""> `fold-engineering-z’</div><div class=""> folding = { folding-direction=’inward’ folding-offset=11593</div> folding-reference-edge=’top’ },<br class=""> { folding-direction=’outward’ folding-offset=20646</div><div class=""> folding-reference-edge=’top’ }<div class=""><br class=""></div><div class="">4. New Section 5.2.12.5 stitching-type (type2 keyword)</div><div class=""><br class=""></div><div class=""> The "stitching-type" member attribute specifies the type of stitching to use. The following values are defined by this specification:</div><div class=""><br class=""></div><div class=""> 'auto': Automatically choose a stitching type based on the Set being finished.</div><div class=""> 'crimp': Crimp the Set together.</div><div class=""> 'wire': Use wire staples.</div><div class=""><br class=""></div><div class="">5. New Section 6.x stitching-type-supported (1setOf type2 keyword)</div><div class=""><br class=""></div><div class=""> The "stitching-type-supported" Printer attribute lists the supported values for the "stitching-type" (section 5.2.12.5) member attribute.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Note: JDF has a "stitching type" with values "corner", "saddle", and "side". Perhaps we should use the name "stitching-kind" instead to avoid confusion (since JDF doesn't currently support crimping/eco-staples)???</div><div class=""><br class=""></div><div class="">
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; border-spacing: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></div></div></div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></div></div></body></html>