www/server fsf-html-style-sheet.html

[D. E. Evans]

CVSROOT:        /web/www
Module name:    www
Changes by:     D. E. Evans <sinuhe>    06/10/05 04:58:33

Modified files:
        server         : fsf-html-style-sheet.html 

Log message:
        Update information relevant to the GIF patent problem.  GIF 87a and 89a
        standards are now acceptable.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/fsf-html-style-sheet.html?cvsroot=www&r1=1.27&r2=1.28

Patches:
Index: fsf-html-style-sheet.html
===================================================================
RCS file: /web/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- fsf-html-style-sheet.html   10 Feb 2006 05:06:24 -0000      1.27
+++ fsf-html-style-sheet.html   5 Oct 2006 04:58:26 -0000       1.28
@@ -382,58 +382,63 @@
        name="UseofGraphics">Use of Graphics</A></H3>
 
 <UL>
-  <LI>The use of graphics should be minimized, so pages load fast over
-       slow links.  The GNU Project is for everyone, even those with slow
-       Internet access and/or text-only WWW browsers.</LI>
-  <LI>Due to the patent problem with GIFs, all in-line images should be 
-      in PNG or JPEG format and possibly with a pointer to our page on 
-      the GIF problem
+  <LI>
+    The use of graphics should be minimized, so pages load fast over slow
+    links, especially animations.  The GNU Project is for everyone, even
+    those with slow Internet access and/or text-only WWW browsers.
+  </LI>
+  <LI>
+    In the past, GIFs have had patent problems.  However, now that the IBM
+    and Unisys patents (and other patents world-wide that are relevant
+    to LZW compression), GIFs that are based on the 87a or 89a standard
+    are acceptable.  Please be wary of proprietary applications that may
+    include non-standard patented technologies (we'd prefer you use free
+    software applications when authoring for our websites).  In general,
+    PNG or JPEG format, are still safe, and are probably better from a
+    technical standpoint.  For details regarding the old GIF problem, see
      <A href="/philosophy/gif.html">http://www.gnu.org/philosophy/gif.html</A>.
-      Other formats are also allowed, though JPEG is the one most
-      widely recognized by Web browsers, (be careful with JPEG
-      2000, as it includes features not fully supported by older
-      browsers).</LI>
+    Other formats are also allowed, though JPEG is the one most widely
+    recognized by Web browsers, (be careful with JPEG 2000, as well as
+    PNG alpha channels, as it includes features not fully supported by
+    older browsers).
+  </LI>
   <LI>Before you take any graphics or text from another Web site,
-       please ask for permission to use it.
-       It's polite to do so.  It is also essential for us to
-       avoid copyright infringement.</LI>
+       please ask for permission to use it.  It's polite to do so.
+       It is also essential for us to avoid copyright infringement.</LI>
   <LI>Whenever you add a graphic to this site's web pages, please:
        <UL>
-        <LI>locate the graphic file in the '/graphics/' subdirectory.</LI>
-         <LI>create a new html web page in '/graphics/'</LI>
-        <LI>add a link to it on the
+        <LI>locate the graphic file in the '/graphics/'
+        subdirectory.</LI> <LI>create a new html web page in
+        '/graphics/'</LI> <LI>add a link to it on the
              <A href="/graphics/graphics.html">GNU graphics</A> page.
              This is so it's easy for visitors to the site to find all
              the graphics on the site in one place.</LI>
        </UL>
-  </LI>
-  <LI>Tag all images like this:
-  <BR>
-  <A href="/graphics/agnuhead.html">
-     <IMG SRC="/graphics/gnu-head-sm.jpg"
-     ALT=" [image of the Head of a GNU] ">
-  </A>
-  <BR>
-  This will allow the user to quickly go to a page related to the picture
-  if he or she is interested.</LI>
-  <LI>Always have a textual alternative for in-line images:<BR>
-      &lt;img src="/graphics/*.jpg" alt=" [Image of DESCRIPTIVE TEXT] 
"&gt;.<BR>
-       The FSF wants users who have text-only access to the Web to be treated
-       as well as those who have both text and graphic access.<BR>
-       We add the spaces and square brackets to separate the
-       DESCRIPTIVE TEXT from adjacent text, and help the user realize that
-       this is a stand-in for a graphic.</LI>
-  <LI>Use width and height attributes for in-line images, but
-  not in ISO HTML:<BR>
+  </LI> <LI>Tag all images like this: <BR> <A
+  href="/graphics/agnuhead.html">
+     <IMG SRC="/graphics/gnu-head-sm.jpg" ALT=" [image of the Head of
+     a GNU] ">
+  </A> <BR> This will allow the user to quickly go to a page related to
+  the picture if he or she is interested.</LI> <LI>Always have a textual
+  alternative for in-line images:<BR>
+      &lt;img src="/graphics/*.jpg" alt=" [Image of DESCRIPTIVE TEXT]
+      "&gt;.<BR>
+       The FSF wants users who have text-only access to the Web to be
+       treated as well as those who have both text and graphic access.<BR>
+       We add the spaces and square brackets to separate the DESCRIPTIVE
+       TEXT from adjacent text, and help the user realize that this is
+       a stand-in for a graphic.</LI>
+  <LI>Use width and height attributes for in-line images, but not in
+  ISO HTML:<BR>
        &lt;img src="/graphics/*.jpg"
-           alt=" [Image of DESCRIPTIVE TEXT] "
-           width="999" height="666" /&gt;.<BR>
-       This improves the performance of, and display on, some browsers.</LI>
+          alt=" [Image of DESCRIPTIVE TEXT] " width="999" height="666"
+          /&gt;.<BR>
+       This improves the performance of, and display on, some
+       browsers.</LI>
   <LI>We do not use
-       backgrounds
-       on our pages, as they make text significantly harder to read.
-       Improving readability is also the reason we specify black text
-       on a white background as the default on our pages.</LI>
+       backgrounds on our pages, as they make text significantly harder
+       to read.  Improving readability is also the reason we specify
+       black text on a white background as the default on our pages.</LI>
   <LI>Sometimes it can be useful to add some HTML tags, for example with
   &lt;SPAN&gt; and CSS, that gives
        a broader "white" area around a block of text. This can be used
@@ -497,7 +502,7 @@
 <P>
 Updated:
 <!-- timestamp start -->
-$Date: 2006/02/10 05:06:24 $ $Author: sinuhe $
+$Date: 2006/10/05 04:58:26 $ $Author: sinuhe $
 <!-- timestamp end -->
 </P>
 </DIV>