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

[Karl Berry]

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       06/12/14 23:00:10

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

Log message:
        fix failed merge, from eggert

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

Patches:
Index: fsf-html-style-sheet.html
===================================================================
RCS file: /web/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -b -r1.33 -r1.34
--- fsf-html-style-sheet.html   5 Dec 2006 01:02:11 -0000       1.33
+++ fsf-html-style-sheet.html   14 Dec 2006 23:00:04 -0000      1.34
@@ -216,8 +216,6 @@
 directory they are in:
 <pre>
 &lt;A 
href="ftp://ftp.gnu.org/gnu/GNUinfo/standards.info"&gt;&lt;URL:ftp://ftp.gnu.org/gnu/GNUinfo/standards.info&gt;&lt;/A&gt;
-<<<<<<< fsf-html-style-sheet.html
-       
 </pre>
 which browsers display this way:<br />
 <a href=
@@ -389,223 +387,12 @@
 permitted worldwide, without royalty, in any medium, provided this
 notice, and the copyright notice, are preserved.</p>
 <p>Updated: <!-- timestamp start -->
-$Date: 2006/12/05 01:02:11 $ $Author: mattl $ 
+$Date: 2006/12/14 23:00:04 $ $Author: karl $
 <!-- timestamp end --></p>
 </div>
 <div id="translations">
 <h3>Translations of this page</h3>
 <ul>
-=======
-       </PRE>
-       which browsers display this way:
-       <BR>
-<A 
href="ftp://ftp.gnu.org/gnu/GNUinfo/standards.info";>&lt;URL:ftp://ftp.gnu.org/gnu/GNUinfo/standards.info&gt;</A>
-       <BR>
-       It is less confusing to the user, because it's clear that it's
-       source code to download, not a http: link to another WWW page.
-
-       Also, if the user saves a copy of the page, he will have a copy
-       of the FTP location he can use, without going back to his web
-       broswer.
-
-       We encourage FTP sites to use a directory for each package,
-       and only put one package's files in each directory,
-       so that the users can see what versions of that package and related
-       information can be downloaded (e.g. a ReadMe file,
-       information of what versions are available, documentations, fonts, 
etc.).
-
-       Also, it means that the FTP location URLs do not need to be changed,
-       on this and other sites, as new versions are released into that 
-       directory.</LI>
-  <LI>There is no reliable way to make a non-breaking space in HTML.
-       Despite the standard, many browsers out there don't understand
-       <STRONG>&amp;nbsp;</STRONG>.  Some browsers (such as DosLynx) use the
-       Operating System current codepage so even if you use
-       <STRONG>&amp;#160;</STRONG> -- the ISO Latin-1 code -- it still won't
-       look right.</LI>
-  <LI>If you specify any color attribute, you should specify all of
-       them that are allowed for that tag.
-       This is because some browsers allow users to specify defaults for
-       the color attributes, and the user's choices could conflict with
-       your choices, as your choices override the user's choices.
-       In the worse case, the foreground and background could end up the 
-       same.  Please use a style sheet for this, and not HTML 3.2
-       (HTML 4 Transitional) deprecated markup.</LI>
-  <LI>Please use tables to organize data, not the presentation of the
-      webpage.</LI>
-  <LI>Some people like to use tables to organize links as a menu to
-       the left or right of content when using graphical browsers. That does
-       not work very well with text browsers since they will make the menu
-       appear either on top of the page or at the bottom. If you have a menu
-       that is more than 30 lines long, then it's very probable that a user
-       viewing the page will never bother to read the text because it will
-       be too far down. You should make an effort to keep such menus under
-       20 lines long so that the content of the page is visible on the
-       first page when viewing it with a text browser.
-       A menu bar of one or two horizontal lines might accomplish your 
-       purpose as well.
-       </LI>
-  <LI>Consider others linking to your page when removing page
-  anchors.  Also, though ID is prefered, include name, so as
-  to be backwards compatible with older browsers.  Please use
-  /gnu.css for your stylesheet, unless you have a specific reason
-  to do otherwise.  Please do not break the style of other pages
-  that use gnu.css.</LI>
-  <LI>Screen reader software used by most blind people reads the text from
-       left to right, ignoring any tables that you make. If you use tables,
-       you should make an effort to make sure that reading a whole page left
-       to right doesn't confuse such software.  Please follow the
-       WAI compatibility guidelines to ensure that tables are
-       properly marked for accessibility.</LI>
-  <LI>SGML and XML are case sensitive.  TITLE and title are not the same
-  thing in HTML.  (This means that text/html and application/xhtml+xml
-  are mutually exclusive, which also means that strictly speaking XHTML
-  and HTML are mutually exclusive.)</LI>
-  <LI>Do not add comments at the top of a document.  Web
-  browsers expect the doctype, XML declaration, or Schema to be
-  at the top.  Comments will confuse web browsers, and often
-  cause them to incorrectly interpret your markup.</LI>
-</UL>
-
-<H3><A href="/server/fsf-html-style-sheet.html#TOCUseofGraphics"
-       name="UseofGraphics">Use of Graphics</A></H3>
-
-<UL>
-  <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) have expired, 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 well as
-    PNG alpha channels, as it includes features not fully supported by
-    older browsers, and has potential patent issues as well).
-  </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>
-  <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
-             <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> 
-  <CODE>
-  <A href="/graphics/agnuhead.html">
-     <IMG src="/graphics/gnu-head-sm.jpg" alt=" [image of the Head of a GNU] ">
-  </A> 
-  </CODE>
-  <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>
-  <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>
-  <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
-       to draw more attention to one block in the text.</LI>
-</UL>
-
-<H3><A href="/server/fsf-html-style-sheet.html#TOCUsefulResources"
-       id="UsefulResources"
-       name="UsefulResources">Useful Resources</A></H3>
-<P>
-<UL>
-  <LI>Appendix B Tips and Hints,
-       and other style tips in the
-       <A 
href="http://www.delorie.com/gnu/docs/texinfo/texinfo_toc.html";><CITE>Texinfo 
Manual</CITE></A>.</LI>
-  <LI>We follow the guidelines of
-       <A href="http://www.anybrowser.org/campaign/";>Best
-       Viewed with Any Browser</A> campaign.</LI>
-  <LI>Basic info on the WWW and its technical specifications can be found
-       at <A href="http://www.w3.org/";>The World Wide Web Consortium</A>.
-  <LI>Use of the <a href="https://www.cs.tcd.ie/15445/UG.HTML";>ISO</a> 
-      standard for the <A href="http://www.w3.org/MarkUp/";>Hypertext Markup 
-      Language (HTML)</A> allows for consistent backwards compatibility 
-      among web user agents.</LI>
-  <LI>The GNU web server follows the w3.org
-      <A href="http://www.w3.org/Provider/Style/Overview.html";>Style Guide</A>.
-  </LI>
-</UL>
-
-<DIV class="copyright">
-<P>
-Return to the <a href="/home.html">GNU Project home page</a>.
-</P>
-
-<P>
-Please send FSF &amp; GNU inquiries to 
-<A href="mailto:address@hidden";><em>address@hidden</em></A>.
-There are also <A href="/home.html#ContactInfo">other ways to
-contact</A> the FSF.
-<BR>
-Please send broken links and other corrections (or suggestions)
-to <A href="mailto:address@hidden";><EM>address@hidden</EM></A>.
-</P>
-
-<P>
-Please see the 
-<A href="/server/standards/README.translations.html">Translations
-README</A> for information on coordinating and submitting
-translations of this article.
-</P>
-
-<P>
-Copyright &copy; 1996, 1997, 1998, 1999, 2001, 2003, 2004, 2005, 2006 
-Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110, USA
-<BR>
-Verbatim copying and distribution of this entire article are
-permitted worldwide, without royalty, in any medium, provided
-this notice, and the copyright notice, are preserved.
-</P>
-
-<P>
-Updated:
-<!-- timestamp start -->
-$Date: 2006/12/05 01:02:11 $ $Author: mattl $
-<!-- timestamp end -->
-</P>
-</DIV>
-
-<P class="translations">
-<A id="translations" name="translations"></a>
-<B><A href="/server/standards/README.translations.html">Translations</A>
-of this page:</B><BR>
-
->>>>>>> 1.30
 <!-- Please keep this list alphabetical. -->
 <!-- Comment what the language is for each type, i.e. DE is Deutsch.-->
 <!-- If you add a new language here, please -->