<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style><head>
  <style></style>
    <table class="backgroundTable" width="100%" cellpadding="0"
      cellspacing="0" bgcolor="#ffffff">
      <tbody>
        <tr>
          <td valign="top" align="left">
            <table cellpadding="0" cellspacing="0">
              <tbody>
                <tr>
                  <td style="border-top: 0px solid rgb(0, 0, 0);
                    border-bottom: 1px solid rgb(255, 255, 255);
                    background-color: rgb(255, 255, 255); text-align:
                    center;" align="center"><span style="font-size:
                      10px; color: rgb(96, 96, 96); line-height: 200%;
                      font-family: verdana; text-decoration: none;">Email
not
                      displaying correctly? <a
                        href="http://www.oplin.org/4cast/"
                        style="font-size: 10px; color: rgb(0, 0, 255);
                        line-height: 200%; font-family: verdana;
                        text-decoration: none;">View
                        it in your browser.</a></span></td>
                </tr>
                <tr>
                  <td style="border-top: 0px solid rgb(51, 51, 51);
                    border-bottom: 0px solid rgb(255, 255, 255);
                    background-color: rgb(255, 255, 255);">
                    <center><a href=""><img id="editableImg1"
                          src="cid:part2.09080202.05040306@oplin.org"
                          title="OPLIN" alt="OPLIN 4Cast" align="middle"
                          border="0"></a></center>
                  </td>
                </tr>
              </tbody>
            </table>
            <table style="width: 763px; height: 877px;" cellpadding="20"
              cellspacing="0" bgcolor="#ffffff">
              <tbody>
                <tr>
                  <td style="font-size: 12px; color: rgb(0, 0, 0);
                    line-height: 150%; font-family: trebuchet ms;"
                    valign="top"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
                    bgcolor="#ffffff">
                    <p><!-- Make sure you modify the 4Cast title in this section -->
                      <span style="font-size: 20px; font-weight: bold;
                        color: rgb(0, 0, 0); font-family: arial;
                        line-height: 110%;">OPLIN 4cast #347:
                        Photocopier gotcha</span><br>
                      <!-- Make sure you modify the date of the 4Cast in this section -->
                      <span style="font-size: 11px; font-weight: normal;
                        color: rgb(102, 102, 102); font-style: italic;
                        font-family: arial;">August 14th, 2013</span></p>
                    <!-- Begin copy of Web Source here  -->
                    <p style="text-align: justify;font-size: 16px;
                      font-family: arial; line-height: 110%;"><img
                        alt="xerox copier"
                        src="cid:part4.04070902.01030409@oplin.org"
                        height="95" width="110" align="left">We have a
                      confession to make. We used to chuckle at people
                      using the library photocopier who carefully
                      compare their fresh copy to their original
                      document. That's crazy behavior! Except now it
                      turns out that it's not so crazy after all. Three
                      weeks ago, a German researcher looked closely at
                      one of his photocopies and discovered that it did
                      <em>not</em> match the original. Even more
                      astounding, Xerox (the company that made his
                      photocopier) admitted that it is possible for a
                      photocopier to mistakenly change a document.
                      Really?! If you can't trust your photocopier, what
                      <em>can</em> you trust?
                    </p>
                    <div> </div>
                    <ul style="text-align: left;">
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_are_switching_written_numbers_when_scanning?">Xerox
                          scanners/photocopiers randomly alter numbers
                          in scanned documents</a> (David Kriesel) "This
                        is not an OCR problem (as we switched off OCR on
                        purpose), it is a lot worse - patches of the
                        pixel data are randomly replaced in a very
                        subtle and dangerous way: The scanned images
                        look correct at first glance, even though
                        numbers may actually be incorrect."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://realbusinessatxerox.blogs.xerox.com/2013/08/07/update-on-scanning-issue-software-patches-to-come/?CMP=SMO-EXT#.Ugj4RuZDsz8">Update
                          on scanning issue: software patches to come</a>
                        (Real Business at Xerox/Ken Ericson) "We
                        continue to work tirelessly and diligently to
                        develop a software patch to address the problem.
                        We'll pass along information about the timing of
                        the patch as soon as we have it. We want to
                        reiterate, we believe the issue deals with
                        'stress documents,' which include documents with
                        small fonts, those scanned multiple times and
                        hard to read."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://page2pixel.org/2013/08/when-copiers-arent-copying-as-they-should/">When
                          copiers aren't copying as they should...</a>
                        (From Page2Pixel/Isaiah Beard) "Of course, the
                        expectation is that the PDF will exactly match
                        the original paper document. There's just one
                        problem: an absolute, exact copy would mean
                        generating large, uncompressed images, resulting
                        in huge PDF files that would be difficult to
                        pass around in e-mail attachments, and cost a
                        lot of money to store on large hard drives for
                        archival purposes. For many corporate settings,
                        this would be a deal-breaker. So, to keep file
                        sizes down, nearly all of these copy systems
                        (not just Xerox) compress the scanned images,
                        using the industry-standard <a
                          href="http://en.wikipedia.org/wiki/JBIG2">JBIG2
                          algorithm</a>."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://nakedsecurity.sophos.com/2013/08/09/security-flaw-with-a-difference-the-xerox-scanner-that-makes-your-house-smaller/">Security
                          flaw with a difference - the Xerox scanner
                          that makes your house smaller!</a> (Naked
                        Security/Paul Ducklin) "It turns out that the
                        Xerox scanner in question was using a
                        compression scheme called JBIG2, which emerged
                        from the grandly-named Joint Bi-level Image
                        Experts Group. Bi-level images, as the name
                        suggests, have just one bit per pixel, such as
                        the images used in fax machines (if you remember
                        them). And JBIG2 has a clever, yet, with
                        hindsight very reckless, feature: if two
                        'swatches' of the image look like each other,
                        the same data is used for both swatches, so that
                        they effectively become identical."</li>
                    </ul>
                    <div style="text-align: left;"> </div>
                    <p style="text-align: left; font-size: 20px;
                      font-family: arial; line-height: 110%;"><small><strong><em>Copiers
                            fact:</em></strong></small><br>
                    </p>
                    <div style="text-align: justify; font-size: 16px;
                      font-family: arial; line-height: 110%;">So far,
                      the copiers primarily affected by this problem
                      seem to be older Xerox WorkCentre machines. See
                      the list <a
href="http://realbusinessatxerox.blogs.xerox.com/2013/08/07/update-on-scanning-issue-software-patches-to-come/?CMP=SMO-EXT#.Ugj4RuZDsz8">posted
                        by Xerox</a>.
                    </div>
                    <div style="text-align: left;"> </div>
                    <!-- End paste of web source here --> </td>
                </tr>
                <tr>
                  <td style="" solid="" background-color:="" rgb(255,=""
                    255,="" 255);="" >="" valign="top" width="760"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"><span
                      style="font-size: 10px; color: rgb(96, 96, 96);
                      line-height: 100%; font-family: verdana;">
                      <hr><!-- Begin standard subscription verbiage -->
                      <div style="text-align: justify;">The <strong><em>OPLIN
                            4cast</em></strong>
                        is a weekly compilation of
                        recent headlines, topics, and trends that could
                        impact public
                        libraries. You can subscribe to it in a variety
                        of ways, such as: <br>
                      </div>
                      <div style="text-align: left;"> </div>
                      <ul>
                        <li style="text-align: justify;"><strong>RSS
                            feed.</strong>
                          You
                          can receive the OPLIN 4cast
                          via RSS feed by subscribing to the following
                          URL:
                          <a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/index.php/?feed=rss2">http://www.oplin.org/4cast/index.php/?feed=rss2</a>.
                        </li>
                        <li style="text-align: justify;"><strong>Live
                            Bookmark.</strong>
                          If you're using the Firefox
                          web browser, you can go to the 4cast website
                          (<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/">http://www.oplin.org/4cast/</a>) and click on the
                          orange "radio wave" icon
                          on the right side of the address bar. In
                          Internet Explorer 7, click on
                          the same icon to view or subscribe to the
                          4cast RSS feed. </li>
                        <li style="text-align: justify;"><strong>E-mail.</strong>
                          You
                          can have the OPLIN 4cast
                          delivered via e-mail (a'la OPLINlist and
                          OPLINtech) by subscribing to
                          the 4cast mailing list at
                          <a class="moz-txt-link-freetext" href="http://mail.oplin.org/mailman/listinfo/OPLIN4cast">http://mail.oplin.org/mailman/listinfo/OPLIN4cast</a>.
                        </li>
                      </ul>
                    </span> </td>
                </tr>
                <tr>
                  <td style="border-top: 0px solid rgb(255, 255, 255);
                    background-color: rgb(255, 255, 204);" valign="top"
                    width="760"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickfooter.jpg">
                    <br>
                  </td>
                </tr>
              </tbody>
            </table>
          </td>
        </tr>
      </tbody>
    </table>
    <title>OPLIN 4Cast</title>
    <style>
 .headerTop { background-color:#FFFFFF; border-top:0px solid #000000; border-bottom:1px solid #FFFFFF; text-align:center; }
 .adminText { font-size:16px; color:#0000FF; line-height:200%; font-family:verdana; text-decoration:none; }
 .headerBar { background-color:#FFFFFF; border-top:0px solid #333333; border-bottom:0px solid #FFFFFF; }
 .title { font-size:20px; font-weight:bold; color:#000000; font-family:arial; line-height:110%; }
 .subTitle { font-size:11px; font-weight:normal; color:#000000; font-style:italic; font-family:arial; }
 .defaultText { font-size:12px; color:#000000; line-height:150%; font-family:trebuchet ms; }
 .footerRow { background-color:#FFFFCC; border-top:0px solid #FFFFFF; }
 .footerText { font-size:10px; color:#996600; line-height:100%; font-family:verdana; }
 a { color:#0000FF; color:#0000FF; color:#0000FF; }
  </style>
  </body>
</html>