www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Karl Berry
Subject: www/server fsf-html-style-sheet.html
Date: Tue, 22 Sep 2009 18:54:32 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       09/09/22 18:54:31

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

Log message:
        some reformatting; update translation block to current boilerplate; 
move HTML Guidelines section nearer the top, since the boilerplate is one of 
the most important things to mention.  (Lots of this should be in webmastering, 
not here, seems to me.)

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

Patches:
Index: fsf-html-style-sheet.html
===================================================================
RCS file: /web/www/www/server/fsf-html-style-sheet.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -b -r1.42 -r1.43
--- fsf-html-style-sheet.html   23 Jun 2009 20:41:09 -0000      1.42
+++ fsf-html-style-sheet.html   22 Sep 2009 18:54:23 -0000      1.43
@@ -1,133 +1,88 @@
 <!--#include virtual="/server/header.html" -->
 
-<title>Web Site Guidelines - GNU Project - Free Software Foundation
-(FSF)</title>
+<title>Web Site Guidelines - GNU Project - Free Software Foundation</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 &lt;address@hidden&gt; 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>
+default.</p>
 
 <h3 id="CopyrightGuidelines">Copyright Guidelines</h3>
 
 <ul>
-
 <li>Every page should have a copyright notice.  See the boilerplate
 document linked below.</li>
 
 <li>If the page is copyrighted by someone else, make sure their
-Copyright notice replaces the FSF Copyright, but maintains the
+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>
+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>
+
+<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 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";>&lt;address@hidden&gt;</a>.</li>
+freely redistributable and modifiable to and by all people, companies,
+and organizations. If in doubt, ask <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</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>
+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>
+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>
+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>
+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>
+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</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
-"&lt;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>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>
+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</a>.</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>
 
@@ -139,59 +94,64 @@
 <a 
href="http://web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&amp;content-type=text%2Fplain";>view
 source</a> (with
 server-side includes intact).</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 
occurences would simply be &lt;acronym&gt;ams&lt;/acronym&gt;</li>
+<li>Acronyms and abbreviations should be added in the form where the
+first acronym or abbreviation in a section (e.g., under a heading) is
+displayed in full - &lt;acronym title="Alfred
+M. Szmidt"&gt;ams&lt;/acronym&gt; but later occurences 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 in mind the
+W3C recommendation and the appropriate character set respective to the
+language in question.</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>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>
+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
+neglect <a
+href="http://www.w3.org/TR/html401/struct/global.html#h-7.1";>required
 elements</a> such as &lt;HTML&gt; &lt;HEAD&gt; &lt;TITLE&gt;
 &lt;BODY&gt;, etc. when using (X)HTML, and always include the
-appropriate DTD or Schema reference. This makes up for overly
-pedantic browsers.</li>
+appropriate DTD or Schema reference. This appeases 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>
+responsible party) and the address for bug reports (webmasters for
+general pages, but project-specific addresses otherwise) 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, &lt;H[n]&gt;, should have its text
-duplicated at the start of the &lt;TITLE&gt; tag. The &lt;TITLE&gt;
-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>
+duplicated at the start of the &lt;TITLE&gt; tag. The &lt;TITLE&gt; 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 &lt;TITLE&gt; 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>
+end: <code> - GNU Project - Free Software Foundation</code>.</li>
 
 <li>The &lt;HEAD&gt; pair should have this line after the
 &lt;TITLE&gt; pair:<br />
 &lt;LINK rev="made" href="mailto:address@hidden"&gt;<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
+<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:
@@ -219,20 +179,13 @@
 <a href=
 "http://ftp.gnu.org/gnu/";>http://ftp.gnu.org/gnu/emacs</a><br />
 
-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>
+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 <code>README</code> 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>If you specify any color attribute, you should specify all of
 them that are allowed for that tag. This is because some browsers
@@ -242,8 +195,10 @@
 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
@@ -255,28 +210,72 @@
 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>
+
+<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 <code>/</code> (e.g., <code>/order/order.html</code>, <em>not</em>
+<code></code>http://www.gnu.org/<code></code>). This makes it easier to
+copy and paste links 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>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:
+try and give each HTML file a unique name; the filename
+<code>index.html</code> should only be used as a symbolic link, as
+explained next:</li>
+
+<li>Each directory in the web server tree should have an
+symbolic link named <code>index.html</code> to the top-level HTML file
+for that directory. Use the <a
+href="/server/standards/README.webmastering.html#symlinks"><code>.symlinks</code></a>
+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 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
@@ -294,28 +293,31 @@
 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
+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>install 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 />
@@ -325,42 +327,50 @@
 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>
+
+<h3><a 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>
 
@@ -379,34 +389,40 @@
 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, 2007, 2008 Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
-Boston, MA 02110, USA</p>
+2006, 2007, 2008, 2009 Free Software Foundation, Inc.</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: 2009/06/23 20:41:09 $
+$Date: 2009/09/22 18:54:23 $
 <!-- timestamp end --></p>
 </div>
+
 <div id="translations">
-<h3>Translations of this page</h3>
-<ul>
-<!-- Please keep this list alphabetical. -->
-<!-- Comment what the language is for each type, i.e. DE is Deutsch.-->
+<h4>Translations of this page</h4>
+
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
 <!-- If you add a new language here, please -->
 <!-- advise address@hidden and add it to -->
-<!--  - /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
 <!--  - /home/www/html/server/standards/README.translations.html -->
 <!--  - one of the lists under the section "Translations Underway" -->
 <!--  - if there is a translation team, you also have to add an alias -->
 <!--  to mail.gnu.org:/com/mailer/aliases -->
-<!-- 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 -->
-<li><!-- English --> <a href=
-"/server/fsf-html-style-sheet.html">English</a></li>
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+
+<ul class="translations-list">
+<!-- English --
+<li><a href= "/server/fsf-html-style-sheet.html">English&nbsp;[en]</a></li>
 <!-- Korean -->
-<li><a href="/server/fsf-html-style-sheet.ko.html">ko</a></li>
+<li><a href="/server/fsf-html-style-sheet.ko.html">Korean&nbsp;[ko]</a></li>
 </ul>
 </div>
 </div>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]