<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: "Aptos Serif", Aptos_EmbeddedFont, Aptos_MSFontService, serif; font-size: 11pt; color: rgb(0, 0, 0);">
The image standard was originally set by WIPO. The problem isn't so much the standard, but the dithering algorithm the USPTO uses to convert the images into 1-bit monochrome images. The USPTO uses a bottom of the barrel, trash algorithm. In contrast, PDF-XChange
uses a very good, top notch algorithm.</div>
<div class="elementToProof" style="font-family: "Aptos Serif", Aptos_EmbeddedFont, Aptos_MSFontService, serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: "Aptos Serif", Aptos_EmbeddedFont, Aptos_MSFontService, serif; font-size: 11pt; color: rgb(0, 0, 0);">
Also, the requirement to use the TIFF compression algorithm should be replaced with something more modern such as JBIG 2. I use JBIG 2 for all black and white documents and it significantly reduces the file sizes.</div>
<div class="elementToProof" style="font-family: "Aptos Serif", Aptos_EmbeddedFont, Aptos_MSFontService, serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature" class="elementToProof">
<p style="margin: 0in; font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: "Aptos Serif", Aptos_EmbeddedFont, Aptos_MSFontService, serif; color: rgb(31, 56, 100);"><b>Scott Nielson</b></span></p>
<p style="margin: 0in; font-family: Calibri, sans-serif; font-size: 11pt;"><span style="font-family: "Aptos Serif", Aptos_EmbeddedFont, Aptos_MSFontService, serif; color: black;">801-660-4400</span></p>
</div>
<div id="appendonsend"></div>
<div style="font-family:"Aptos Serif",Aptos_EmbeddedFont,Aptos_MSFontService,serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Patentpractice <patentpractice-bounces@oppedahl-lists.com> on behalf of steve--- via Patentpractice <patentpractice@oppedahl-lists.com><br>
<b>Sent:</b> Thursday, January 9, 2025 12:41 PM<br>
<b>To:</b> 'For patent practitioners. This is not for laypersons to seek legal advice.' <patentpractice@oppedahl-lists.com><br>
<b>Cc:</b> steve@hoffberglaw.com <steve@hoffberglaw.com><br>
<b>Subject:</b> Re: [Patentpractice] Welcome Letter actually useful?</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:DengXian}
@font-face
{font-family:Calibri}
@font-face
{font-family:Aptos}
@font-face
{font-family:Roboto}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif}
a:link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
span.x_EmailStyle18
{font-family:"Aptos",sans-serif;
color:windowtext}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
</style>
<div lang="EN-US" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal">I have specifically noted to EBC and Director that there are other documents (e.g., receipts) regularly added to the IFW by the USPTO that are also (originally) color or half-toned, and result in illegible text or garbled and inefficiently
compressed images. I made note that this problem particularly extends to NPL references, where the native file is mutilated by the conversion process. (This issue arose because an Examiner cited an 805 page book, leading to a single file greater than the
100 MB limit, which could not be downloaded through PatentCenter).</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">I suggested that the entire morass evolved from a decision in the early and mid-1990s to adopt a TIFF-4 based PDF wrapper for scanned pages, supporting PDF-A, in order to be backward compatible with then-legacy systems. (Who exactly
is firing up an abacus from 1993 to handle IFWs?). This also results in ballooning of NPL references, in some cases 100-fold, when converting from their native format to PFD-A. I recommended reconsideration of the entire process, especially given the IFW-unsupported
mandatory docx filing.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Maybe the next Director will be more interested in improving the process than community outreach.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span style="color:#1F497D">Very truly yours,</span><span style="font-size:11.0pt; color:#1F497D"></span></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">Steven M. Hoffberg</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">Hoffberg & Associates</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">29 Buckout Road</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">West Harrison, NY 10604</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">(914) 949-2300 tel</span></p>
<p class="x_MsoNormal"><span style="color:#1F497D">(845) 625-2547 fax</span></p>
<p class="x_MsoNormal"><a href="mailto:steve@hoffberglaw.com"><span style="color:#0563C1">steve@hoffberglaw.com</span></a></p>
<p class="x_MsoNormal"><a href="https://www.linkedin.com/in/hoffberg/" data-auth="Verified" originalsrc="https://www.linkedin.com/in/hoffberg/" shash="A60mbM13RZ/ujs1e/HJ75oAaup3kUWYqwtgfcyK5k5lt061DS2Xle14KRXdrGouT08a3nu6zEavhFQLouAweWwnyt342QmIW9XXxMedC2icyefeURt9DG/X2RGH/1EYJaoAHPMaQWZNz4ZLIhsRy8erILjKEcIXnjTzr3hkgbTk="><span style="color:#0563C1">https://www.linkedin.com/in/hoffberg/</span></a></p>
<p class="x_MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="color:black; background:white">Emails and attachments received from us may be confidential and/or protected by the attorney-client privilege, as attorney work-product or based on other privileges or provisions of law. If
you are not designated as an intended recipient of this email, do not read, copy, use, forward or disclose the email or any of its attachments to others. Instead, immediately notify the sender by replying to this email and then delete it from your system.
We strictly prohibit any unauthorized disclosure, copying, distribution or use of emails or attachments sent by us to other than the intended recipient.</span><span style="color:black"> This communication does not create any legal obligations on behalf of
the sender, unless executed in a manner indicating an intent to be bound.</span></p>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"> Patentpractice <patentpractice-bounces@oppedahl-lists.com>
<b>On Behalf Of </b>Jeffrey Semprebon via Patentpractice<br>
<b>Sent:</b> Thursday, January 9, 2025 6:50 AM<br>
<b>To:</b> For patent practitioners. This is not for laypersons to seek legal advice. <patentpractice@oppedahl-lists.com><br>
<b>Cc:</b> Jeffrey Semprebon <jesemprebon@gmail.com><br>
<b>Subject:</b> [Patentpractice] Welcome Letter actually useful?</span></p>
</div>
<p class="x_MsoNormal"> </p>
<div>
<div>
<p class="x_MsoNormal">While forwarding a filing receipt and welcome letter to a client, I noted that while the filing receipt is razor sharp, the welcome letter (the version from IFW, signed by both Dir. Vidal and Dep. Brent rather than the downloadable one
from the top of the Documents tab in color and signed only by Acting Dir. Brent) has the horrible pixelated half-tone typical of image files (drawings, Declarations, etc.) uploaded and processed. <br>
<br>
It occurs to me that the Welcome Letter may have an unintentional value as an example to warn Applicants of the sort of image degradation that image files are likely to suffer when processed to get them into IFW; apparently even the USPTO's own documents are
not always spared in whatever processing.</p>
<div>
<p class="x_MsoNormal"> </p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-family:Roboto; letter-spacing:.1pt">-Jeff</span></p>
</div>
</div>
<div>
<div>
<div>
<div>
<p class="x_MsoNormal"><span style="font-family:Roboto; letter-spacing:.1pt"><br>
Jeffrey E. Semprebon<br>
Registered Patent Agent (mechanical) looking for remote work</span></p>
</div>
<div>
<p class="x_MsoNormal"><a href="mailto:jesemprebon@gmail.com">jesemprebon@gmail.com</a><span style="font-family:Roboto; letter-spacing:.1pt"><br>
72 Myrtle Street<br>
Claremont, New Hampshire 03743</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>