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

[Matt Lee]

CVSROOT:        /web/www
Module name:    www
Changes by:     Matt Lee <mattl>        07/01/23 20:04:13

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

Log message:
        added acronyms info

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

Patches:
Index: fsf-html-style-sheet.html
===================================================================
RCS file: /web/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- fsf-html-style-sheet.html   17 Jan 2007 14:11:11 -0000      1.35
+++ fsf-html-style-sheet.html   23 Jan 2007 20:04:09 -0000      1.36
@@ -126,31 +126,10 @@
 <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>
+W3C standards.</li>
+<li>A boilerplates is provided, the primary <a href=
+"/server/standards/boilerplate.html">boilerplate</a></li>
+<li>Acronyms and abbreviations should be added in the form where the first 
acronym or abbreviation in a section (ie. under a heading) is displayed in full 
- &lt;acronym title="Alfred M. Szmidt"&gt;ams&lt;/acronym&gt; but later 
occurances would simply be &lt;acronym&gt;ams&lt;/acronym&gt;</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
@@ -288,18 +267,18 @@
 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 usually
-preferable from a technical standpoint. For details regarding the old
-GIF problem, see <a href=
+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>
+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>
@@ -387,7 +366,7 @@
 permitted worldwide, without royalty, in any medium, provided this
 notice, and the copyright notice, are preserved.</p>
 <p>Updated: <!-- timestamp start -->
-$Date: 2007/01/17 14:11:11 $ $Author: karl $
+$Date: 2007/01/23 20:04:09 $ $Author: mattl $
 <!-- timestamp end --></p>
 </div>
 <div id="translations">