[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www gnu-new.css server/fsf-html-style-sheet.html
|
From: |
Matt Lee |
|
Subject: |
www gnu-new.css server/fsf-html-style-sheet.html |
|
Date: |
Tue, 05 Dec 2006 01:02:17 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Matt Lee <mattl> 06/12/05 01:02:17
Modified files:
. : gnu-new.css
server : fsf-html-style-sheet.html
Log message:
Checked in slight tweaks
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu-new.css?cvsroot=www&r1=1.26&r2=1.27
http://web.cvs.savannah.gnu.org/viewcvs/www/server/fsf-html-style-sheet.html?cvsroot=www&r1=1.32&r2=1.33
Patches:
Index: gnu-new.css
===================================================================
RCS file: /web/www/www/gnu-new.css,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- gnu-new.css 22 Nov 2006 15:20:05 -0000 1.26
+++ gnu-new.css 5 Dec 2006 01:02:02 -0000 1.27
@@ -204,7 +204,7 @@
border: 3px solid #ddd;
}
-#sidebar h3{text-align: center; margin-top: 0;}
+#sidebar h3{text-align: center; margin-top: 0; background-color: #e8edca;}
#sidebar ul{margin-bottom: 1.2em; padding-left: 1em;margin-left: 0;}
Index: server/fsf-html-style-sheet.html
===================================================================
RCS file: /web/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- server/fsf-html-style-sheet.html 23 Oct 2006 14:13:33 -0000 1.32
+++ server/fsf-html-style-sheet.html 5 Dec 2006 01:02:11 -0000 1.33
@@ -1,312 +1,401 @@
-<!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HTML//EN">
-<HTML LANG="EN">
-<HEAD>
- <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <TITLE>Web Site Guidelines - GNU Project - Free Software
- Foundation (FSF)</TITLE>
- <LINK rel="stylesheet" type="text/css" href="/gnu.css">
- <LINK rev="made" href="mailto:address@hidden";>
-</HEAD>
+<!--#include virtual="/server/header.html" -->
-<BODY>
-<P>
- <A href="#translations">Translations</A> of this page.
-</P>
-
-<H1>The GNU/FSF Web Site Guidelines</H1>
-<P>
-<A href="/graphics/atypinggnu.html">
-<IMG src="/graphics/gnu-type-sm.jpg" alt=" [image of the typing GNU] ">
-</A>
-</P>
-
-<P>
-These are style guidelines for writing WWW web pages in HTML for the
-GNU/FSF web server.
-</P>
-
-<P>
-The standards documented here are the default for the GNU project and
-FSF websites. All pages should appear this way by default. However, if
-you want to design alternative pages that differ from these guidelines,
-it's all right to do so as long as those features are supported by some
-Free Software web browsers.
-</P>
-
-<P>
-However, when new features are used, they should be used in a consistent
-way, and standards should be developed for how we use them. Please
-contact the other maintainers of www.gnu.org pages that use similar
-features, and discuss with them new standards for using these features,
-so we can note those new standards here.
-</P>
-
-<P>
-Talk with <address@hidden> if you are having trouble finding
-other web page authors using the features you are interested in.
-</P>
-
-<P>
-Please note, however, that regardless, frames should not be used, even
-in the alternative pages, because they interfere with bookmarking.
-But if you think you know of a good reason to use frames, please tell
-us about it.
-</p>
-
-<HR>
-
-<P>
-
-<H2>Table of Contents</H2>
-<UL>
- <LI><A href="/server/fsf-html-style-sheet.html#CopyrightGuidelines"
- id="TOCCopyrightGuidelines"
- name="TOCCopyrightGuidelines">Copyright Guidelines</A></LI>
- <LI><A href="/server/fsf-html-style-sheet.html#GeneralGuidelines"
- id="TOCGeneralGuidelines"
- name="TOCGeneralGuidelines">General Guidelines</A></LI>
- <LI><A href="/server/fsf-html-style-sheet.html#FilenameAndURLGuidelines"
- id="TOCilenameAndURLGuidelines"
- name="TOCFilenameAndURLGuidelines">Filename and URL Guidelines</A></LI>
- <LI><A href="/server/fsf-html-style-sheet.html#HTMLGuidelines"
- id="TOCHTMLGuidelines"
- name="TOCHTMLGuidelines">HTML Guidelines</A></LI>
- <LI><A href="/server/fsf-html-style-sheet.html#UseofGraphics"
- id="TOCUseofGraphics"
- name="TOCUseofGraphics">Use of Graphics</A></LI>
- <LI><A href="/server/fsf-html-style-sheet.html#UsefulResources"
- id="TOCUsefulResources"
- name="TOCUsefulResources">Useful Resources</A></LI>
-</UL>
-
-<HR>
-
-<H3><A href="/server/fsf-html-style-sheet.html#TOCCopyrightGuidelines"
- name="CopyrightGuidelines"
- id="CopyrightGuidelines">Copyright Guidelines</A></H3>
-
-<UL>
- <LI>Every page should have a Copyright notice.</LI>
- <LI>The default is what's at the bottom of
- <A href="/server/standards/boilerplate.html">boilerplate.html</A>.
- </LI>
- <LI>
- If the page is copyrighted by someone else, make sure their
- Copyright notice replaces the FSF Copyright, but maintains the address,
- etc. The user of our pages should always find the copyright information
- at the same place on each page.
- </LI>
- <LI>If the source text for a set of pages is copyrighted by someone else,
- (i.e. you split a document into more than one page)
- make sure their Copyright notice is at the bottom of each page,
- where the default FSF Copyright notice would otherwise be.
- </LI>
- <LI>All pages should have a notice saying that they are freely distributable.
- If you can not get such a permission from the author, please discuss
- this with the webmasters first.
- </LI>
-</UL>
-
-<H3><A href="/server/fsf-html-style-sheet.html#TOCGeneralGuidelines"
- name="GeneralGuidelines"
- id="GeneralGuidelines">General Guidelines</A></H3>
-
-<UL>
- <LI>Good spelling is encouraged.</LI>
- <LI>The FSF will install only
- <A href="/philosophy/free-sw.html">free software</A>
- on the GNU web server. We prefer that only
- <A href="/philosophy/free-sw.html">free software</A>
- be used to develop content for the GNU web server.
- </LI>
- <LI>The GNU web server <STRONG>only</STRONG> lists and links
- <STRONG>only</STRONG> to
- <A href="/philosophy/free-sw.html">free software</A>.
- The software's source code and executables
- have to be freely redistributable and modifiable to and by all people,
- companies, and organizations.
- If in doubt, ask
- <A href="mailto:address@hidden";><address@hidden></A>.
- </LI>
- <LI>The GNU web server gives priority to software covered by either
- the GNU General Public License or GNU Lesser General Public License,
- which is always listed first.</LI>
- <LI>The GNU web server is interested first in content.
- Substance is more important than style. 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 or text-only
- WWW browsers.</LI>
- <LI>Often a page will start off with some links, then have the GNU text.
- The goal is to get each user quickly to what they want to find out,
- having most of the info on the first screen.
- This is similar to having the start of a Menu within the
- first 24 lines of an Info page.</LI>
- <LI>Offer a document in as many formats as the GNU Project has it.
- For an example, see
- <A href="/copyleft/fdl.html">The GNU Free Documentation License</A>.
- This lets the user get the document in the format most useful to him.
- </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>Do not list an address of an individual, including the
- maintainer of a GNU package, unless explicitly asked to have
- it listed. Most GNU maintainers do not want a lot of extra mail
- and prefer to get bug reports, etc. from the GNU bug report <A
- href="/prep/mailinglists.html">mailing lists (50k characters)</A>.
- </LI>
-</UL>
-
-<H3><A href="/server/fsf-html-style-sheet.html#TOCFilenameAndURLGuidelines"
- name="FilenameAndURLGuidelines"
- id="FilenameAndURLGuidelines">Filename and URL Guidelines</A>
-</H3>
-
-<UL>
- <LI>Hand-written URLs which refer to other files should be
- absolute, starting from the root page. That is, file names should
- start with "/" (e.g. "/order/order.html",
- <STRONG>not</STRONG> "http://www.gnu.org/"). This makes
- it easier to copy and paste "<a href="s from other
- pages, and also makes it easier to set up mirror servers.
- </LI>
- <LI>It is ok to omit the file name entirely
- when referring to a tag in the same file.</LI>
- <LI>When the link points to another page on the GNU server,
- omit the word "http:" at the beginning. In other words,
- use "http:" only before a host name.</LI>
- <LI>Collections of files produced automatically from Texinfo source
- contain links with relative file names. They always refer to
- another file in the same directory. These relative links are to
- be tolerated.</LI>
- <LI>To make it easier to edit many files at once in Emacs:
- <UL>
- <LI>Try and give each HTML file a unique name.</LI>
- <LI>The filename index.html should only be used as a
- symbolic link.</LI>
- </UL>
- </LI>
- <LI>Each directory, in the web server tree,
- should have an index.html symbolic link to the top-level html
- file for that directory. Use the <CODE>.symlinks</CODE> file to
- handle this.</LI>
- <LI>Don't use just a directory name in a URL; always include the
- specific file name. E.g. use "/gnu/gnu-history.html"
- not just "/gnu/". Never use "index.html"
- in a URL. Both of these are kindnesses to the users, as browsers
- change the highlighting on a link if a user has already seen it.
- If the link is known by several different file names, the user
- will not get a highlighted link on the file names the user hasn't
- explicitly referenced. So the user goes to pages the user has
- already seen, which is irritating. Also, this helps
- mirroring.</LI>
-</UL>
-
-<H3><A href="/server/fsf-html-style-sheet.html#TOCHTMLGuidelines"
- name="HTMLGuidelines"
- id="HTMLGuidelines">HTML Guidelines</A></H3>
-
-<UL>
- <LI>Our goal is to get information to people.
- Keeping the site design simple helps accomplish that.</LI>
- <LI>HTML on the GNU web server should be strictly compliant with W3C
- and ISO standards. Though we generally use XHTML 1.0 Strict, with
- content type text/html, we prefer ISO 15445 or HTML 4.01 Strict.
- We don't want to experiment with non-standard browser features.
- Though XML and XHTML are important, when they are used they need
- to follow both accessibility standards, and the guidelines for HTML
- compatibility. Please be meticulously careful to make our documents
- accessible. For example, XHTML normally uses MIME type xhtml+xml
- which many browsers do not recognize, (it is understand that this
- will be implimented with IE 7, though the question still stands
- regarding the breadth of IE's XHTML support; lynx added support for
- xhtml+xml with 2.8.6dev.5, and text/xml and application/xml with
- 2.8.6dev.11). Also, even though the HTML compatibility guidelines
- assist with backwards compatibility to some browsers (such as MS
- IE), they will be interpreted incorrectly by strict HTML and SGML
- parsers. It is important that the pages on the GNU web server,
- display well on <em>all</em> browsers, even those that implement
- no more than HTML 2.0. Using HTML 2.0 is fine; we'd prefer
- you didn't use HTML 3.2. ISO HTML is best for most situations.
- Use XHTML to benefit the use of XML and XHTML modularity.
- </LI>
- <LI>Two boilerplates are provided, the primary
- <A href="/server/standards/boilerplate.html">boilerplate</A>,
- and a <A href="/server/standards/boilerplate.xhtml">XHTML
- boilerplate</A>. When in doubt use the primary
- boilerplate, as you will know when you need or want XHTML.</LI>
- <LI>Regarding character encoding, in general, the use of 8
- bit unicode makes life easy on our translators, so when using
- XHTML, UTF-8 is preferred as a general rule. When using HTML
- please keep in mind the W3C recommendation and the appropriate
- character set respective to the language in question.
- </LI>
- <LI>We support the <A href="http://www.anybrowser.org/campaign/";>Best
- Viewed with Any Browser</A> campaign, and WAI.</LI>
- <LI>Please be considerate of all who access our web pages, and
- accomodate them, including those who use text-only browsers,
- or old browsers. We wish to prevent HTML design that looks great
- under one version of one browser, and ugly under many others.
- Of course, please don't install any of the proprietary software
- browsers available if you don't already use them anyway.
- </LI>
- <LI>Please follow the above mentioned web standards strictly.
- Don't neglect
- <A href="http://www.w3.org/TR/html401/struct/global.html#h-7.1";>
- required elements</A> such as <HTML> <HEAD>
- <TITLE> <BODY>, etc. when using (X)HTML, and always
- include the appropriate DTD or Schema reference. This makes up for
- overly pedantic browsers.</LI>
- <LI>All pages should have contact info for both the FSF (or
- responsible party) and the webmasters at the bottom of each page.
- The reason to note this at the bottom is so the user always finds
- this contact information at the same place on each page.</LI>
- <LI>The first header tag, <H[n]>, should have its text duplicated
- at the start of the <TITLE> tag. The <TITLE> tag is
- used by many browsers in menus like the history and bookmarks lists,
- as a link to that page. It helps the user to have them the same,
- so when he clicks on an item in a list, he gets a page with the same
- "TITLE". Please properly use your headers in numerical
- order: 1, 2, etc. These are not used for looks, but for
- the organization of the document.</LI>
- <LI>The <TITLE> tag should include the phrases
- "GNU Project" and "Free Software Foundation (FSF)"
- so the pages will be found when WWW search engines are used.
- The default is to add this at the end:
- " - GNU Project - Free Software Foundation (FSF)".</LI>
- <LI>The <HEAD> pair should have this line after the <TITLE>
- pair:
- <BR>
- <LINK rev="made" href="mailto:address@hidden">
- <BR>
- Some browsers use this information to allow users to easily report
- problems they find on a page.</LI>
- <LI>On pages with dated entries (e.g. What's New, Thank GNUs, and
- GNU's Bulletins, the newer entries should be first (i.e
- reverse chronological order).
- <LI>Cite people with e-mail addresses this way:
- <PRE>
+<title>Web Site Guidelines - GNU Project - Free Software Foundation
+(FSF)</title>
+<!--#include virtual="/server/banner.html" -->
+<h2>The GNU/FSF Web Site Guidelines</h2>
+<p>These are style guidelines for writing WWW web pages in HTML for
+the GNU web server.</p>
+<p>The standards documented here are the default for the GNU
+project website. All pages should appear this way by
+default.</p><!-- However, if you want to design alternative pages that
+differ from these guidelines, it's all right to do so as long as
+those features are supported by some Free Software web
+browsers.</p>
+<p>However, when new features are used, they should be used in a
+consistent way, and standards should be developed for how we use
+them. Please contact the other maintainers of www.gnu.org pages
+that use similar features, and discuss with them new standards for
+using these features, so we can note those new standards here.</p>
+<p>Talk with <address@hidden> if you are having trouble
+finding other web page authors using the features you are
+interested in.</p> -->
+<p>Please note, however, that regardless, frames should not be
+used, even in the alternative pages, because they interfere with
+bookmarking. But if you think you know of a good reason to use
+frames, please tell us about it.</p>
+<h3 id="CopyrightGuidelines">Copyright
+Guidelines</h3>
+<ul>
+<li>Every page should have a Copyright notice.</li>
+<li>The default is what's at the bottom of <a href=
+"/server/standards/boilerplate.html">boilerplate.html</a>.</li>
+<li>If the page is copyrighted by someone else, make sure their
+Copyright notice replaces the FSF Copyright, but maintains the
+address, etc. The user of our pages should always find the
+copyright information at the same place on each page.</li>
+<li>If the source text for a set of pages is copyrighted by someone
+else, (i.e. you split a document into more than one page) make sure
+their Copyright notice is at the bottom of each page, where the
+default FSF Copyright notice would otherwise be.</li>
+<li>All pages should have a notice saying that they are freely
+distributable. If you can not get such a permission from the
+author, please discuss this with the webmasters first.</li>
+</ul>
+<h3 id="GeneralGuidelines">General
+Guidelines</h3>
+<ul>
+<li>Good spelling is encouraged.</li>
+<li>The FSF will install only <a href=
+"/philosophy/free-sw.html">free software</a> on the GNU web server.
+We prefer that only <a href="/philosophy/free-sw.html">free
+software</a> be used to develop content for the GNU web
+server.</li>
+<li>The GNU web server <strong>only</strong> lists and links
+<strong>only</strong> to <a href="/philosophy/free-sw.html">free
+software</a>. The software's source code and executables have to be
+freely redistributable and modifiable to and by all people,
+companies, and organizations. If in doubt, ask <a href=
+"mailto:address@hidden";><address@hidden></a>.</li>
+<li>The GNU web server gives priority to software covered by either
+the GNU General Public License or GNU Lesser General Public
+License, which is always listed first.</li>
+<li>The GNU web server is interested first in content. Substance is
+more important than style. 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 or text-only WWW
+browsers.</li>
+<li>Often a page will start off with some links, then have the GNU
+text. The goal is to get each user quickly to what they want to
+find out, having most of the info on the first screen. This is
+similar to having the start of a Menu within the first 24 lines of
+an Info page.</li>
+<li>Offer a document in as many formats as the GNU Project has it.
+For an example, see <a href="/copyleft/fdl.html">The GNU Free
+Documentation License</a>. This lets the user get the document in
+the format most useful to him.</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>Do not list an address of an individual, including the
+maintainer of a GNU package, unless explicitly asked to have it
+listed. Most GNU maintainers do not want a lot of extra mail and
+prefer to get bug reports, etc. from the GNU bug report <a href=
+"/prep/mailinglists.html">mailing lists (50k characters)</a>.</li>
+</ul>
+<h3 id=
+"FilenameAndURLGuidelines">Filename and URL Guidelines</h3>
+<ul>
+<li>Hand-written URLs which refer to other files should be
+absolute, starting from the root page. That is, file names should
+start with "/" (e.g. "/order/order.html", <strong>not</strong>
+"http://www.gnu.org/";). This makes it easier to copy and paste
+"<a href="s from other pages, and also makes it easier to set up
+mirror servers.</li>
+<li>It is ok to omit the file name entirely when referring to a tag
+in the same file.</li>
+<li>When the link points to another page on the GNU server, omit
+the word "http:" at the beginning. In other words, use "http:" only
+before a host name.</li>
+<li>Collections of files produced automatically from Texinfo source
+contain links with relative file names. They always refer to
+another file in the same directory. These relative links are to be
+tolerated.</li>
+<li>To make it easier to edit many files at once in Emacs:
+<ul>
+<li>Try and give each HTML file a unique name.</li>
+<li>The filename index.html should only be used as a symbolic
+link.</li>
+</ul>
+</li>
+<li>Each directory, in the web server tree, should have an
+index.html symbolic link to the top-level html file for that
+directory. Use the <code>.symlinks</code> file to handle this.</li>
+<li>Don't use just a directory name in a URL; always include the
+specific file name. E.g. use "/gnu/gnu-history.html" not just
+"/gnu/". Never use "index.html" in a URL. Both of these are
+kindnesses to the users, as browsers change the highlighting on a
+link if a user has already seen it. If the link is known by several
+different file names, the user will not get a highlighted link on
+the file names the user hasn't explicitly referenced. So the user
+goes to pages the user has already seen, which is irritating. Also,
+this helps mirroring.</li>
+</ul>
+<h3 id="HTMLGuidelines">HTML Guidelines</h3>
+<ul>
+<li>Our goal is to get information to people. Keeping the site
+design simple helps accomplish that.</li>
+<li>HTML on the GNU web server should be strictly compliant with
+W3C and ISO standards. Though we generally use XHTML 1.0 Strict,
+with content type text/html, we prefer ISO 15445 or HTML 4.01
+Strict. We don't want to experiment with non-standard browser
+features. Though XML and XHTML are important, when they are used
+they need to follow both accessibility standards, and the
+guidelines for HTML compatibility. Please be meticulously careful
+to make our documents accessible. For example, XHTML normally uses
+MIME type xhtml+xml which many browsers do not recognize, (it is
+understand that this will be implimented with IE 7, though the
+question still stands regarding the breadth of IE's XHTML support;
+lynx added support for xhtml+xml with 2.8.6dev.5, and text/xml and
+application/xml with 2.8.6dev.11). Also, even though the HTML
+compatibility guidelines assist with backwards compatibility to
+some browsers (such as MS IE), they will be interpreted incorrectly
+by strict HTML and SGML parsers. It is important that the pages on
+the GNU web server, display well on <em>all</em> browsers, even
+those that implement no more than HTML 2.0. Using HTML 2.0 is fine;
+we'd prefer you didn't use HTML 3.2. ISO HTML is best for most
+situations. Use XHTML to benefit the use of XML and XHTML
+modularity.</li>
+<li>Two boilerplates are provided, the primary <a href=
+"/server/standards/boilerplate.html">boilerplate</a>, and a
+<a href="/server/standards/boilerplate.xhtml">XHTML
+boilerplate</a>. When in doubt use the primary boilerplate, as you
+will know when you need or want XHTML.</li>
+<li>Regarding character encoding, in general, the use of 8 bit
+unicode makes life easy on our translators, so when using XHTML,
+UTF-8 is preferred as a general rule. When using HTML please keep
+in mind the W3C recommendation and the appropriate character set
+respective to the language in question.</li>
+<li>We support the <a href=
+"http://www.anybrowser.org/campaign/";>Best Viewed with Any
+Browser</a> campaign, and WAI.</li>
+<li>Please be considerate of all who access our web pages, and
+accomodate them, including those who use text-only browsers, or old
+browsers. We wish to prevent HTML design that looks great under one
+version of one browser, and ugly under many others. Of course,
+please don't install any of the proprietary software browsers
+available if you don't already use them anyway.</li>
+<li>Please follow the above mentioned web standards strictly. Don't
+neglect <a href=
+"http://www.w3.org/TR/html401/struct/global.html#h-7.1";>required
+elements</a> such as <HTML> <HEAD> <TITLE>
+<BODY>, etc. when using (X)HTML, and always include the
+appropriate DTD or Schema reference. This makes up for overly
+pedantic browsers.</li>
+<li>All pages should have contact info for both the FSF (or
+responsible party) and the webmasters at the bottom of each page.
+The reason to note this at the bottom is so the user always finds
+this contact information at the same place on each page.</li>
+<li>The first header tag, <H[n]>, should have its text
+duplicated at the start of the <TITLE> tag. The <TITLE>
+tag is used by many browsers in menus like the history and
+bookmarks lists, as a link to that page. It helps the user to have
+them the same, so when he clicks on an item in a list, he gets a
+page with the same "TITLE". Please properly use your headers in
+numerical order: 1, 2, etc. These are not used for looks, but for
+the organization of the document.</li>
+<li>The <TITLE> tag should include the phrases "GNU Project"
+and "Free Software Foundation (FSF)" so the pages will be found
+when WWW search engines are used. The default is to add this at the
+end: " - GNU Project - Free Software Foundation (FSF)".</li>
+<li>The <HEAD> pair should have this line after the
+<TITLE> pair:<br />
+<LINK rev="made" href="mailto:address@hidden"><br />
+Some browsers use this information to allow users to easily report
+problems they find on a page.</li>
+<li>On pages with dated entries (e.g. What's New, Thank GNUs, and
+GNU's Bulletins, the newer entries should be first (i.e reverse
+chronological order).</li>
+<li>Cite people with e-mail addresses this way:
+<pre>
<A href="http://www.stallman.org/rms.html">Richard Stallman</A>
<A href="mailto:address@hidden">&lt;address@hidden&gt;</A>
- </PRE>
- which browsers display this way:
- <BR>
-<A href="http://www.stallman.org/rms.html";>Richard Stallman</A>
-<A href="mailto:address@hidden";><address@hidden></A>
- <BR>
- It is less confusing to the user, because it's clear what
- is a http: link to another WWW page and what is a mailto: anchor that
- will bring up a mail form to fill out and send, if this is supported
- by the client.
- Also, if the user saves a copy of the page, he will have a copy
- of the e-mail address he can use, without going back to his web
- browser. If the person doesn't have a web page, leave the
- name unanchored.</LI>
- <LI>Cite FTP locations of source code with the full URL of the
- directory they are in:
- <PRE>
+
+</pre>
+which browsers display this way:<br />
+<a href="http://www.stallman.org/rms.html";>Richard Stallman</a>
+<a href="mailto:address@hidden";><address@hidden></a><br />
+It is less confusing to the user, because it's clear what is a
+http: link to another WWW page and what is a mailto: anchor that
+will bring up a mail form to fill out and send, if this is
+supported by the client. Also, if the user saves a copy of the
+page, he will have a copy of the e-mail address he can use, without
+going back to his web browser. If the person doesn't have a web
+page, leave the name unanchored.</li>
+<li>Cite FTP locations of source code with the full URL of the
+directory they are in:
+<pre>
<A
href="ftp://ftp.gnu.org/gnu/GNUinfo/standards.info"><URL:ftp://ftp.gnu.org/gnu/GNUinfo/standards.info></A>
+<<<<<<< fsf-html-style-sheet.html
+
+</pre>
+which browsers display this way:<br />
+<a href=
+"ftp://ftp.gnu.org/gnu/GNUinfo/standards.info";><URL:ftp://ftp.gnu.org/gnu/GNUinfo/standards.info></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>&nbsp;</strong>. Some browsers (such as DosLynx) use
+the Operating System current codepage so even if you use
+<strong>&#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" id="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), 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).</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 />
+<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 />
+<img src="/graphics/*.jpg" alt=" [Image of DESCRIPTIVE TEXT]
+">.<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 />
+<img src="/graphics/*.jpg" alt=" [Image of DESCRIPTIVE TEXT] "
+width="999" height="666" />.<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 <SPAN> 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>
+<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>
+<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>
+
+<!--#include virtual="/server/footer.html" -->
+
+<div id="footer">
+<p>Please send FSF & 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.</p>
+<p>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 © 1996, 1997, 1998, 1999, 2001, 2003, 2004, 2005,
+2006 Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+Boston, MA 02110, USA</p>
+<p>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>
+<div id="translations">
+<h3>Translations of this page</h3>
+<ul>
+=======
</PRE>
which browsers display this way:
<BR>
@@ -506,7 +595,7 @@
<P>
Updated:
<!-- timestamp start -->
-$Date: 2006/10/23 14:13:33 $ $Author: karl $
+$Date: 2006/12/05 01:02:11 $ $Author: mattl $
<!-- timestamp end -->
</P>
</DIV>
@@ -516,6 +605,7 @@
<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 -->
@@ -528,16 +618,12 @@
<!-- Please also check you have the 2 letter language code right versus -->
<!-- <URL:http://www.w3.org/WAI/ER/IG/ert/iso639.htm> -->
<!-- Please use W3C normative character entities -->
-
-[
-<!-- English -->
-<a href="/server/standards/fsf-html-style-sheet.html">en</a> |
+<li><!-- English --> <a href=
+"/server/standards/fsf-html-style-sheet.html">English</a></li>
<!-- Korean -->
-<a href="/server/standards/fsf-html-style-sheet.ko.html">ko</a>
-]
-
-</P>
-
-</BODY>
-</HTML>
-
+<li><a href="/server/standards/fsf-html-style-sheet.ko.html">ko</a></li>
+</ul>
+</div>
+</div>
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www gnu-new.css server/fsf-html-style-sheet.html,
Matt Lee <=