<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <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" cellpadding="0" cellspacing="0"
      bgcolor="#ffffff" width="100%">
      <tbody>
        <tr>
          <td align="left" valign="top">
            <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.04040008.01010505@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;"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
                    bgcolor="#ffffff" valign="top">
                    <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 #395: Trimming
                        down web images</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;">July 23th, 2014</span></p>
                    <!-- Begin copy of Web Source here  -->
                    <p style="text-align: justify;font-size: 16px;
                      font-family: arial; line-height: 110%;"><img
                        src="cid:part4.09020708.05090201@oplin.org"
                        alt="scissors" align="left" height="110"
                        width="100">About four years have passed since
                      Google <a
href="http://blog.chromium.org/2010/09/webp-new-image-format-for-web.html">announced</a>
                      that the company had decided to release a new
                      image format called WebP. Back then, Google
                      estimated that about 65% of Internet traffic was
                      composed of images and photos, and WebP was
                      designed to reduce the size of those image files
                      and thus speed up loading time for web pages that
                      used the WebP format. Lean image formats are back
                      in the news lately because the Mozilla browser
                      group has decided WebP is not the best solution to
                      the problem of image bloat on the Internet, and
                      has decided to release its own solution instead.
                    </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://gigaom.com/2014/07/19/the-story-of-webp-how-google-wants-to-speed-up-the-web-one-image-at-a-time/">The
                          story of WebP: How Google wants to speed up
                          the web, one image at a time</a> (GigaOM |
                        Janko Roettgers) "Firefox, Internet Explorer and
                        Safari don't natively support WebP, and it's
                        unlikely that the makers of these browsers are
                        going to change their mind anytime soon. That's
                        because like so often, everyone has their own
                        vision of how the future is going to look like.
                        Microsoft is pushing for its own format, dubbed
                        <a
href="http://msdn.microsoft.com/en-us/library/windows/desktop/hh707223%28v=vs.85%29.aspx">JPEG
                          XR</a>, to replace traditional JPEGs, and
                        Apple has long steered clear of Google's media
                        formats. The most logical ally for Google would
                        be Mozilla, which has traditionally been a
                        proponent of open media formats."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://www.techspot.com/news/57430-mozillas-new-mozjpeg-20-image-encoder-improves-jpeg-compression.html">Mozilla's
                          new Mozjpeg 2.0 image encoder improves JPEG
                          compression</a> (Techspot | Himanshu Arora)
                        "The JPEG format, which has been in use for more
                        than 20 years, is one of the most widely used
                        image formats on the Internet. It's a lossy
                        format, which means that you can remove some
                        data to reduce the file size without
                        significantly affecting the original image's
                        integrity. Google has been promoting the use of
                        its <a
href="http://www.techspot.com/news/56109-googles-new-webp-software-brings-animated-graphics-and-25-faster-display-times.html">WebP</a>
                        image format, a derivative of the video format
                        VP8, but Mozilla has long resisted the call to
                        adopt it."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://arstechnica.com/information-technology/2014/07/we-dont-need-new-image-formats-mozilla-works-to-build-a-better-jpeg/">We
                          don't need new image formats: Mozilla works to
                          build a better JPEG</a> (Ars Technica | Peter
                        Bright) "Mozilla has also been looking at the
                        issue, but the open source browser organization
                        has come up with a different conclusion: we
                        don't need a new image format, we just need to
                        make better JPEGs. To that end, the group has
                        released its own JPEG compression library,
                        mozjpeg 2.0, which reduces file sizes by around
                        five percent compared to the widely used
                        libjpeg-turbo. Facebook has announced that it
                        will be testing mozjpeg 2.0 to reduce its
                        bandwidth costs, similar to its <a
href="http://arstechnica.com/information-technology/2013/04/chicken-meets-egg-with-facebook-chrome-webp-support/">WebP
                          trial</a>."</li>
                      <li style="text-align: justify; font-size: 16px;
                        font-family: arial; line-height: 110%;"><a
href="http://thenextweb.com/insider/2014/07/15/mozilla-releases-mozjpeg-2-0-facebook-tests-backs-jpeg-encoder-60000-donation/">Mozilla
                          releases mozjpeg 2.0 as Facebook tests and
                          backs the JPEG encoder with $60,000 donation</a>
                        (The Next Web | Emil Protalinski) "Facebook
                        could use the encoder on photos that users have
                        already uploaded to the site, or it could apply
                        it dynamically on images that are regularly
                        accessed, such as profile pictures or link
                        thumbnails. Whatever the case may be, the
                        potential to reduce loading time is very high,
                        given that Facebook is such an image-heavy
                        service."</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>Articles
                            from <a href="http://ohioweblibrary.org">Ohio
                              Web Library</a>:</em></strong></small><br>
                    </p>
                    <div style="text-align: justify; font-size: 16px;
                      font-family: arial; line-height: 110%;">
                      <li><a
href="http://web.b.ebscohost.com.proxy.oplin.org/pov/detail?sid=f619ba6f-54ac-4ad4-9d5a-8977df8f2e15%40sessionmgr111&vid=1&hid=122&bdata=JnNpdGU9cG92LWxpdmU%3d#db=pwh&AN=EU9XEFY.20140306.674758">Here's
                          'mozjpeg' to reduce webpage loads</a>.
                        (EFYtimes.com, 03/06/2014)</li>
                      <li><a
href="http://web.a.ebscohost.com.proxy.oplin.org/ehost/detail?sid=a5b40f3b-73ca-43b8-b597-3209a116dd30%40sessionmgr4002&vid=1&hid=4212&bdata=JnNpdGU9ZWhvc3QtbGl2ZQ%3d%3d#db=buh&AN=91690761">Higher
                          compression of images using MR-JPEG scheme and
                          images standard deviation</a>. (<em>IUP
                          Journal of Telecommunications</em>, August
                        2013, p39-46 | Vikas Saxena)</li>
                      <li><a
href="http://web.a.ebscohost.com.proxy.oplin.org/lrc/detail?sid=d2b01f3e-ae6f-44c9-89e0-123bfd2fe77f%40sessionmgr4005&vid=3&hid=4212&bdata=JnNpdGU9bHJjLWxpdmU%3d#db=lfh&AN=1538430">Beyond
                          GIF and JPEG: New digital image technologies</a>.
                        (<em>Library Journal</em>, 2/15/1999, p111 | Roy
                        Tennant) [Interesting list of image formats that
                        looked promising 15 years ago, but are unknown
                        now.]</li>
                    </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);="" >=""
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
                    valign="top" width="760"><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);"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickfooter.jpg"
                    valign="top" width="760"> <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>