--- /dev/null
+<!DOCTYPE HTML><!--
+ *
+ * contact.html
+ *
+ * Summary of approved methods for contacting the members of the
+ * MinGW.org user and developer community.
+ *
+ *
+ * $Id$
+ *
+ * Written by Keith Marshall <keith@users.osdn.me>
+ * Copyright (C) 2020, MinGW.org Project
+ *
+ *
+ * Redistribution and use in source and 'compiled' forms (SGML, HTML,
+ * PDF, PostScript, RTF, etc) with or without modification, are permitted
+ * provided that the following conditions are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer as
+ * the first lines of this file, unmodified.
+ *
+ * 2. Redistributions in compiled form (transformed to other DTDs,
+ * converted to PDF, PostScript, RTF and other formats) must
+ * reproduce the above copyright notice, this list of conditions
+ * and the following disclaimer in the documentation and/or other
+ * materials provided with the distribution.
+ *
+ * THIS DOCUMENTATION IS PROVIDED BY THE MINGW.ORG PROJECT "AS IS" AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE MINGW.ORG PROJECT, OR
+ * ITS CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ * OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+ * DAMAGE.
+ *
+ *
+ * Note: this page assumes browser support for the following numeric
+ * HTML entity code:
+ *
+ * ‑ non-breaking hyphen
+ * “ left (opening) typographic double quote
+ * ” right (closing) typographic double quote
+ *
+-->
+<dl class="masthead"><!-- hidden for masthead class -->
+<!-- FIXME: is there a better way to do this? We need to propagate
+ content to the "as-page-title" and "as-page-subtitle" place-holders,
+ within the "page-content" div of "index.html"; our javascript page
+ loader will explicitly look for these hidden elements, and copy
+ their content into the corresponding visible place-holders.
+-->
+ <dt id="page-title">Contacting MinGW.org</dt>
+ <dt id="page-subtitle">When a Web-Search Fails to Resolve your Issue</dt>
+</dl><!-- masthead -->
+<p>If you have exhausted all of the web‑site resources,
+and you have searched all of the
+<a href="index.html?page=mailing.html"
+>available mailing‑list archives</a>,
+and all of the on‑line
+<a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/projects/mingw/ticket/"
+>bug report and feature request tickets</a>,
+then you may wish to contact MinGW.org for assistance.
+Please refer to the relevant sections below,
+for guidance on <a href="#general-enquiry">making general enquiries</a>,
+on <a href="#bug-report">filing bug reports</a>,
+or on <a href="#feature-request">requesting new features</a>.
+</p>
+<p><em>Please note:
+the mingw‑w64 and MSYS2 projects are <strong>not</strong>,
+in any way, affiliated with MinGW.org;
+MinGW.org <strong>does not</strong> support the products
+of these projects.</em>
+</p>
+<div id="general-enquiry">
+<h3>General Enquiries</h3>
+<p>If you encounter a problem using MinGW, or MSYS,
+and you cannot find a satisfactory answer on our web‑site,
+in our
+<a href="index.html?page=mailing.html">mailing‑list archives</a>,
+or elsewhere on the internet,
+or if you simply need some advice relating to MinGW, or MSYS,
+then we advise you to
+<a rel="noopener noreferrer" target="_blank"
+ href="https://lists.osdn.me/mailman/listinfo/mingw-users"
+>subscribe to the MinGW‑Users mailing‑list</a>,
+and ask.
+</p>
+<p><em>Do please note that, to help avoid spam,
+this mailing‑list is open to subscribers only.
+Please <strong>do not</strong>
+attempt to circumvent the subscription process,
+by sending mail to either the mingw-users-owner,
+or the mingw-users-admin addresses.
+Doing so will be of no benefit to you,
+since subscription is free‑of‑charge in any case,
+and you will get no reply from the former address,
+while the latter is reserved for automated self‑help replies,
+in response to specific subject keywords.</em>
+</p>
+<p>Before posting to this mailing‑list,
+we <em>strongly</em> recommend that you acquaint yourself with
+<a href="index.html?page=mailing.html#list-etiquette"
+>the mailing‑list posting etiquette</a>;
+compliance with this may improve your chances of receiving a response,
+whereas non‑compliance may result in your post being ignored.
+</p></div><!-- general-enquiry -->
+<div id="bug-report">
+<h3>Reporting Bugs</h3>
+<p>After discussing an issue on the mailing‑list,
+as described above, you may be asked to file a formal bug report.
+(Alternatively,
+if you are certain that you have identified a bug in a MinGW.org product,
+you may choose to file such a bug report of your own volition;
+however, if you choose this course of action,
+please be aware that many bug reports,
+which are filed <em>without</em> prior discussion,
+are ultimately dismissed as user error).
+</p>
+<p><em>Before you even consider filing a bug report,
+please review
+<a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/projects/mingw/ticket/"
+>the list of existing tickets</a>,
+(<strong>including closed tickets</strong>
+— ensure that the “Open” and “Closed”
+status check‑boxes are <strong>both</strong> selected,
+and click the “Search” button),
+to ensure that the issue has not already been reported</em>.
+</p>
+<p><em>Please <strong>do not</strong> file a bug report,
+if your issue relates to an unimplemented API feature;
+it is more appropriate to file
+a “<a href="#feature-request">Feature Request</a>” instead</em>.
+</p>
+<p><em>Please do not waste your time, (and ours),
+reporting issues with your anti‑virus software;
+the heuristic nature of such software, all too frequently,
+results in false‑positive reports,
+and in the absence of deterministic evidence of infection,
+we will take no action in response.</em>
+</p>
+<p>Regardless of your motivation for filing a bug report,
+you <em>must</em>, (unless you already have one),
+<em><a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/account/register.php"
+>create a personal OSDN.net account</a></em>,
+and you should also
+<em><a target="_blank" href="index.html?page=buginfo.html"
+>acquaint yourself with the bug reporting guidelines</a></em>.
+You may then
+<em><a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/account/login.php?return_to=/ticket/newticket.php?group_id=3917"
+>log in to your OSDN.net account</a></em>,
+and proceed to
+<em><a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/ticket/newticket.php?group_id=3917"
+>the bug report submission form</a></em>.
+Please review the submission instructions,
+(which appear at the top of the submission form),
+then complete the form,
+leaving the ticket type set to “Issue”.
+</p>
+<p><em>Please <strong>do not</strong> ignore the submission instructions.
+In particular, note that,
+unless you are a member of the MinGW.org Project development team,
+you are <strong>not</strong> authorized to assign a specific responder
+for the ticket; nor are you authorized to assign an elevated priority
+or severity attribute for your ticket.
+If you exceed your authority,
+your ticket <strong>will</strong> be reassigned to <strong>lowest</strong>
+priority/severity, and may even be rejected altogether</em>.
+</p>
+<p>Before you finally submit your report,
+please use the “Preview” facility to check for,
+and correct, any markup errors;
+(these are, alas, all too common,
+and create a bad impression of the reporter).
+Finally, when you are satisfied, click the “Submit” button
+to complete the ticket submission process.
+</p></div><!-- bug-report -->
+<div id="feature-request">
+<h3>Feature Requests</h3>
+<p>When you wish to request the implementation of a new feature,
+(e.g. to support a currently unsupported MSVC or POSIX API function),
+you should file a feature request ticket.
+The procedure is effectively the same as that for
+<a href="#bug-report">filing a bug report</a>,
+<em>except</em> that you set the ticket type to “Feature Request”,
+instead of leaving it as “Issue”.
+</p>
+<p><em>Please be aware that feature request submissions are subject
+to the same restrictions on your authority,
+as are applicable to <a href="#bug-report">bug reporting</a></em>.
+</p>
+<p>Before you submit a feature request,
+it is recommended that you discuss the feasibility of implementing
+the proposed feature, as a <a href="#general-enquiry">general enquiry topic</a>,
+on the mailing‑list.
+Additionally, <em>after</em> you have submitted such a request,
+you should use the mailing‑list to bring it to the
+attention of the MinGW user community,
+and invite them to support your request,
+by <em>voting</em> on your ticket;
+(please note that MinGW developers will consider votes,
+when prioritizing feature requests).
+</p></div><!-- feature-request -->
--- /dev/null
+<!DOCTYPE HTML><!--
+ *
+ * mailing.html
+ *
+ * $Id$
+ *
+ * Written by Keith Marshall <keith@users.osdn.me>
+ * Copyright (C) 2020, MinGW.org Project
+ *
+ * Uses a web-search form-field implementation derived from the
+ * DuckDuckGo search widget implementation by Juri Wornowitski, as
+ * described at https://www.plainlight.com/ddg
+ *
+ *
+ * Redistribution and use in source and 'compiled' forms (SGML, HTML,
+ * PDF, PostScript, RTF, etc) with or without modification, are permitted
+ * provided that the following conditions are met:
+ *
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer as
+ * the first lines of this file, unmodified.
+ *
+ * 2. Redistributions in compiled form (transformed to other DTDs,
+ * converted to PDF, PostScript, RTF and other formats) must
+ * reproduce the above copyright notice, this list of conditions
+ * and the following disclaimer in the documentation and/or other
+ * materials provided with the distribution.
+ *
+ * THIS DOCUMENTATION IS PROVIDED BY THE MINGW.ORG PROJECT "AS IS" AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+ * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE MINGW.ORG PROJECT, OR
+ * ITS CONTRIBUTORS, BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+ * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+ * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+ * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+ * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+ * OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
+ * DAMAGE.
+ *
+ *
+ * Note: this page assumes browser support for the following numeric
+ * HTML entity codes:
+ *
+ * ‑ non-breaking hyphen
+ * ’ typographic apostrophe
+ * “ left (opening) typographic double quote
+ * ” right (closing) typographic double quote
+ *
+-->
+<dl class="masthead"><!-- hidden for masthead class -->
+<!-- FIXME: is there a better way to do this? We need to propagate
+ content to the "as-page-title" and "as-page-subtitle" place-holders,
+ within the "page-content" div of "index.html"; our javascript page
+ loader will explicitly look for these hidden elements, and copy
+ their content into the corresponding visible place-holders.
+-->
+ <dt id="page-title">MinGW.org Mailing-Lists</dt>
+ <dt id="page-subtitle">Mailing-Lists and Mail Archives Operated by MinGW.org</dt>
+</dl><!-- masthead -->
+<p>MinGW.org’s preferred method for communication,
+between users and the project team, is by way of mailing‑lists.
+Historically, there were several topic‑specific lists, originally
+<a rel="noopener noreferrer" target="_blank"
+ href="https://sourceforge.net/p/mingw/mailman/"
+>hosted on SourceForge.net</a>;
+today, only two remain operational, and both are
+<a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/projects/mingw/lists/"
+>hosted on OSDN.net</a>.
+</p>
+<h3>Operational Mailing‑Lists</h3>
+<p>The currently operational
+MinGW.org mailing‑lists are:—
+</p>
+<dl class="no-indent" id="mingw-users">
+<dt><a rel="noopener noreferrer" target="_blank"
+ href="https://lists.osdn.me/mailman/listinfo/mingw-users"
+>MinGW‑Users Mailing‑List</a>
+</dt>
+<dd>This is the primary conduit for dialogue between MinGW users
+and the MinGW.org project team;
+(you are advised to use this mailing‑list
+at any time when you wish to engage in such dialogue).
+It is a public mailing‑list, but to avoid spam,
+<a rel="noopener noreferrer" target="_blank"
+ href="https://lists.osdn.me/mailman/listinfo/mingw-users"
+>you <em>must</em> subscribe</a>
+<em>before</em> you will be
+permitted to post your first message,
+(and your subscription <em>must</em> remain active,
+if you wish to post subsequent messages).
+</dd>
+<dd>Before
+posting to this mailing‑list
+you are advised to acquaint yourself with the
+<a href="#list-etiquette">posting etiquette</a>;
+failure to comply with this etiquette may seriously impair
+your chances of receiving a useful response,
+and, in cases of flagrant disregard,
+may even result in your future posts being moderated.
+</dd>
+<dd>Previous correspondence,
+posted to this mailing‑list between February 2018
+and the present day, has been
+<a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/projects/mingw/lists/archive/users"
+>archived on OSDN.net</a>;
+(earlier correspondence, prior to February 2018, has also been
+<a rel="noopener noreferrer" target="_blank"
+ href="https://sourceforge.net/p/mingw/mailman/mingw-users"
+>archived, on SourceForge.net</a>).
+As noted in the <a href="#list-etiquette">etiquette</a>,
+before you introduce a new topic on this mailing‑list,
+you are advised to search these archives,
+to ensure that you are not asking a question
+which has already been answered.
+You may use the following pair of search boxes to perform
+keyword searches within the OSDN.net (upper),
+and the SourceForge.net (lower box) archives, respectively.
+(If your question relates to MSYS, you may also wish to refer to the
+<a href="#mingw-msys">historical MinGW‑MSYS archive, below</a>).
+<form class="search" method="get" action="https://duckduckgo.com/" target="_blank">
+ <button class="fa fa-search" type="submit"></button>
+ <input type="text" name="q" placeholder="Search MinGW-Users on OSDN.net ..." />
+ <input type="hidden" name="sites" value="https://osdn.net/projects/mingw/lists/archive/users" />
+ <input type="hidden" name="kn" value="1" />
+</form>
+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
+ <button class="fa fa-search" type="submit"></button>
+ <input type="text" name="q" placeholder="Search MinGW-Users on SourceForge.net ..." />
+ <input type="hidden" name="mailing_list" value="mingw-users" />
+</form>
+</dd>
+</dl><dl class="no-indent" id="mingw-notify">
+<dt><a rel="noopener noreferrer" target="_blank"
+ href="https://lists.osdn.me/mailman/listinfo/mingw-notify"
+>MinGW‑Notify Mailing‑List</a>
+</dt>
+<dd>This is a <em>read‑only</em> mailing‑list,
+which is used to deliver notifications of source code repository updates,
+issue tracker submissions, and feature request submissions.
+If you would like to receive such notifications,
+you are welcome to subscribe to this mailing‑list,
+but please <em>do not</em> attempt to post messages to it.
+</dd>
+<dd>Notifications posted to this mailing‑list,
+since November 2017, have been
+<a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/projects/mingw/lists/archive/notify"
+>archived on OSDN.net</a>,
+while notifications posted prior to September 2017 have been
+<a rel="noopener noreferrer" target="_blank"
+ href="https://sourceforge.net/p/mingw/mailman/mingw-notify"
+>archived, on SourceForge.net</a>.
+Once again, you may use the following pair of search boxes
+to perform keyword searches on these archives, respectively.
+<form class="search" method="get" action="https://duckduckgo.com/" target="_blank">
+ <button class="fa fa-search" type="submit"></button>
+ <input type="text" name="q" placeholder="Search MinGW-Notify on OSDN.net ..." />
+ <input type="hidden" name="sites" value="https://osdn.net/projects/mingw/lists/archive/notify" />
+ <input type="hidden" name="kn" value="1" />
+</form>
+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
+ <button class="fa fa-search" type="submit"></button>
+ <input type="text" name="q" placeholder="Search MinGW-Notify on SourceForge.net ..." />
+ <input type="hidden" name="mailing_list" value="mingw-notify" />
+</form>
+</dd>
+</dl>
+<h3>Historical Mailing‑List Archives</h3>
+<p>In earlier days of the project history,
+the volume of mailing‑list traffic was significantly greater
+than it is today.
+This traffic was distributed over five topic‑specific
+mailing‑lists, of which only the two identified above
+remain operational today;
+the other three historical lists, which are identified below,
+are now closed, and it is no longer possible to subscribe,
+or to post messages to them.
+However, archives of historical postings remain
+<a rel="noopener noreferrer" target="_blank"
+ href="https://sourceforge.net/p/mingw/mailman/"
+>available on SourceForge.net</a>,
+and may be searched using their respective keyword‑search boxes,
+below.
+</p>
+<dl class="no-indent" id="mingw-msys">
+<dt><a rel="noopener noreferrer" target="_blank"
+ href="https://sourceforge.net/p/mingw/mailman/mingw-msys"
+>MinGW‑MSYS Mailing‑List</a>
+</dt>
+<dd>This was a public mailing‑list,
+dedicated to correspondence relating specifically to MSYS,
+in order to segregate it from more general MinGW‑Users list traffic;
+today, such correspondence should be directed to
+<a href="#mingw-users">the MinGW‑Users mailing‑list</a>.
+</dd>
+<dd>You may use this search box to perform a keyword search
+on the historical MinGW-MSYS archive.
+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
+ <button class="fa fa-search" type="submit"></button>
+ <input type="text" name="q" placeholder="Search MinGW-MSYS on SourceForge.net ..." />
+ <input type="hidden" name="mailing_list" value="mingw-msys" />
+</form>
+</dd>
+<dt><a rel="noopener noreferrer" target="_blank"
+ href="https://sourceforge.net/p/mingw/mailman/mingw-dvlpr"
+>MinGW‑Dvlpr Mailing‑List</a>
+</dt>
+<dd>This was a private, but publicly archived mailing‑list,
+which was used by MinGW.org Project contributors, to discuss various
+aspects of project development; this mailing‑list has now been
+superseded by alternative web technologies, for such discussion.
+</dd>
+<dd>You may use this search box to perform a keyword search
+on the historical MinGW-Dvlpr public archive.
+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
+ <button class="fa fa-search" type="submit"></button>
+ <input type="text" name="q" placeholder="Search MinGW-Dvlpr on SourceForge.net ..." />
+ <input type="hidden" name="mailing_list" value="mingw-dvlpr" />
+</form>
+</dd>
+<dt><a rel="noopener noreferrer" target="_blank"
+ href="https://sourceforge.net/p/mingw/mailman/mingw-cvs"
+>MinGW‑CVS Mailing‑List</a>
+</dt>
+<dd>This obsolete <em>read‑only</em> mailing‑list was
+formerly used for posting of notifications of updates to the
+MinGW.org CVS, (and more recently <em>git</em>),
+source code repositories;
+since migration of these repositories to
+<a rel="noopener noreferrer" target="_blank"
+ href="https://osdn.net/projects/mingw/scm/"
+>OSDN.net</a>, such notifications have been directed to
+<a href="#mingw-notify">the MinGW‑Notify mailing‑list</a>.
+</dd>
+<dd>You may use this search box to perform a keyword search
+on the historical MinGW-CVS archive.
+<form class="search" method="get" action="https://sourceforge.net/p/mingw/mailman/search/" target="_blank">
+ <button class="fa fa-search" type="submit"></button>
+ <input type="text" name="q" placeholder="Search MinGW-CVS on SourceForge.net ..." />
+ <input type="hidden" name="mailing_list" value="mingw-cvs" />
+</form>
+</dd>
+</dl>
+<div id="list-etiquette">
+<h3>Mailing‑List Posting Etiquette</h3>
+<p>MinGW is an open source project.
+As such, it is heavily dependent on people who dedicate
+their spare time to the goals and continuing development of the project,
+so please keep this in mind when posting to the mailing‑list.
+</p>
+<p>Before you post, you are advised to
+acquaint yourself with the following commonly accepted guidelines,
+with which you are strongly encouraged to comply,
+when composing your posts.
+Failure to comply with these guidelines may result
+in your posts being ignored by a number of knowledgeable people,
+and repeated offenses may even lead to your posts being vetted,
+and potentially rejected, by the list moderator.
+</p>
+<ul style="padding-right: 1em">
+<li>The language of the lists is <em><strong>English</strong></em> ;
+if you post in any other language, you are unlikely to elicit a response.
+</li>
+<li><em><strong>Do search</strong></em> the mailing list archives,
+(both the current archives, and those of the historical topic‑specific
+lists), before posting, (see the links associated with each of the lists above);
+many questions have already been asked and answered.
+</li>
+<li><em><strong>Do use</strong></em>
+a <em><strong>meaningful</strong></em> subject line.
+A subject line should include a pertinent few words summarizing
+the subject of the email;
+(when one replies to emails,
+one should always make certain the subject line of the email is still
+relevant to the reply).
+In particular, if you receive list mail in digest format,
+<em><strong>do always</strong></em>
+set the subject back to the original text,
+from the message to which you are replying.
+<em><strong>Do not</strong></em> reply with a subject of
+<em>“Re: MinGW-??? Digest no. ???”</em>;
+such replies are prime candidates for deletion, without being read.
+</li>
+<li><em><strong>Do post</strong></em> in a MIME format with
+<em>“Content-Type: text</em>/<em>plain”</em>.
+<em><strong>Do not</strong></em> post as HTML, or in any other MIME format,
+(and in particular, <em><strong>do not</strong></em> use multi-part MIME,
+with plain text duplicated as HTML);
+some list subscribers are unable to, or choose not to read such mail,
+and will be unable or unwilling to answer you.
+</li>
+<li><em><strong>Do not</strong></em>
+post messages with very long lines of text;
+except when pasting screenshots, where line wrapping might lead to confusion,
+ensure that lines of running text are wrapped with hard line breaks,
+at a length of between 65 and 72 characters.
+</li>
+<li><em><strong>Do quote</strong></em> sections of the original text,
+and <em><strong>interleave</strong></em> your replies to individual points,
+<em><strong>below</strong></em> the relevant context.
+<em><strong>Do not</strong></em>
+<a rel="noopener noreferrer" target="_blank"
+ href="http://en.wikipedia.org/wiki/Top_post"
+>top-post</a>;
+(this
+<a rel="noopener noreferrer" target="_blank"
+ href="http://redballoon.net/~snorwood/quote-rant.shtml"
+>treatise</a>
+explains why top-posting is considered unacceptable).
+</li>
+<li><em><strong>Do trim out</strong></em> sections of the original mail,
+which are not required to establish the context of your reply.
+(Once more,
+this is particularly important when replying to mail received in digest form;
+<em><strong>do reply</strong></em>
+to <em><strong>one subject at a time</strong></em>,
+and <em><strong>do remove</strong></em> all content related to other subjects).
+<em><strong>Do not</strong></em> persistently recycle irrelevant junk,
+quoted from earlier messages in the thread.
+</li>
+<li><em><strong>Do not</strong></em>
+include <em>“legal mumble”</em> signatures.
+You are posting to a list that will be read by thousands of users,
+and anything you say will be archived in the public domain;
+in this context, such drivel in your signature is neither enforceable,
+nor meaningful.
+</li>
+<li><em><strong>Do not hijack</strong></em> an existing topic thread,
+when you wish to introduce an unrelated subject;
+(i.e. <em><strong>do not</strong></em> reply to an existing message,
+when your reply is unrelated to the original subject).
+When you want to introduce a new topic, plainly start a new thread,
+(i.e. a completely new message).
+Replying in an existing thread confuses mail readers
+and humans who are trying to participate in the original discussion;
+it is a sure way to irritate other subscribers,
+and will likely get you ignored,
+if not even black-listed.
+</li>
+</ul>
+<p>Historical information on <em>netiquette</em> may be found in
+<a rel="noopener noreferrer" target="_blank"
+ href="http://www.faqs.org/rfcs/rfc1855.html"
+>RFC-1855</a>.
+</p>
+<p>This
+<a rel="noopener noreferrer" target="_blank"
+ href="http://linuxmafia.com/faq/Essays/smart-questions.html"
+>article</a>,
+(also available
+<a rel="noopener noreferrer" target="_blank"
+ href="http://www.catb.org/~esr/faqs/smart-questions.html"
+>here</a>),
+offers valuable advice on how to ask questions,
+in a manner most likely to elicit useful replies.
+</p>
+</div><!-- list-etiquette -->
+
+<!-- $RCSfile$: end of file -->
*
*/
-/* General page layout and formatting
+/* General Page Layout and Formatting
* ==================================
*/
body
{ /* Also maintain a deeper space between paragraph text and any
* intervening horizontal rule.
*/
- margin-top: 1.3em;
+ margin-top: 1.2em;
}
-p+ul
-{ /* Keep any unordered list closer to preceding paragraph text
- * than normal inter-paragraph spacing, but separated slightly
+p+ul, p+ol, p+dl
+{ /* Keep any unordered list, ordered list, or defining list
+ * closer to any immediately preceding paragraph text than
+ * normal inter-paragraph spacing, but separated slightly
* more than single-line text spacing.
*/
margin-top: 0.3em; margin-bottom: 0;
}
+ul li, ol li
+{ margin-top: 0.12em;
+}
+ul li:first-child, ol li:first-child
+{ margin-top: 0;
+}
+dl dt
+{ /* Similarly, set explicit layout rules for definition lists.
+ */
+ margin-top: 0.8em; font-weight: bold;
+}
+dl dt:first-child, dl dd+dd
+{ margin-top: 0.4em;
+}
+dl dt+dd
+{ margin-top: 0.2em;
+}
+dl.no-indent dd
+{ /* Suppress indentation of definition blocks, within any
+ * definition list of the "no-indent" class.
+ */
+ margin-left: 0;
+}
-/* Fixed position page header block formatting
+/* Fixed Position Page Header Block Formatting
* ===========================================
*/
#header
* becomes (99 - 15) / 5 = 16.8%.
*/
display: inline-block;
- min-width: 16.8%; margin-left: 1px; margin-right: 1px;
- border-top: 1px solid; border-left: 1px solid; border-right: 2px solid;
+ min-width: 16.8%; margin: 0 1px; border-bottom: 3px solid;
+ border-top: 1px solid; border-left: 1px solid; border-right: 3px solid;
border-top-left-radius: 7px; border-top-right-radius: 7px;
border-bottom-style: none; border-color: #336699;
color: #003366; background-color: #d9d9ff;
}
-/* General page content formatting
+/* General Page Content Formatting
* ===============================
*/
.page-view
margin-top: 1.3em;
}
-/* Supplementary formatting for sections with numbered headings
+
+/* Supplementary Formatting for Sections with Numbered Headings
* ============================================================
*/
.h3-numbered
content: counter(h3-number) ". ";
}
+
+/* Styling for In-Line Web-Search Form Fields
+ * ==========================================
+ * Derived from Juri Wornowitski's DuckDuckGo search widget implementation,
+ * version 3.0, as described at https://www.plainlight.com/ddg
+ */
+form.search
+{ /* Let the search box fill the entire width of its containing
+ * element, with 0.3em spacing above and below; (thus, when two
+ * search boxes are placed together, they will be separated by
+ * 0.6em vertical space).
+ */
+ width: 100%; margin: 0.3em auto;
+}
+form.search input
+{ /* Establish styling attributes for the keywords input field,
+ * which fills the search box from its left-hand side, most of
+ * the way across to the right...
+ */
+ display: block; outline: none; box-sizing: border-box;
+ border: 1px solid #003366; border-right: none; border-radius: 7px 0 0 7px;
+ height: 30px; width: calc( 100% - 60px ); padding: 0.6em;
+ font-size: 0.8em; background-color: #f3f3ff;
+}
+form.search button
+{ /* ...with a search button occupying the rightmost 60px.
+ */
+ float: right; height: 30px; width: 60px; font-size: 1em;
+ border: 1px solid #003366; border-left: none; border-radius: 0 7px 7px 0;
+ cursor: pointer; color: #336699; background-color: #ccccff;
+}
+form.search button:active, form.search button:hover
+{ /* Invert search button colours, when the mouse is placed
+ * over it, or while a search is in progress.
+ */
+ color: #ccccff; background-color: #6699cc;
+}
+form.search button:focus
+{ /* Do not outline the button, even when it has the focus.
+ */
+ outline:none;
+}
+
/* $RCSfile$: end of file */
OSDN Git Service
