added explanation of usage of definite article of FSFE

svn path=/trunk/; revision=22182
This commit is contained in:
samtuke 2012-01-30 17:16:35 +00:00
parent e06c6bd648
commit 6ee0c9d493
1 changed files with 41 additions and 38 deletions

View File

@ -22,52 +22,56 @@ wish.
<h2>Tone and Style</h2>
<ul>
<li>Articles shouldn't feel like a sales pitch (even if what's being 'sold' is
Free).</li>
<li>Articles should be informative: they should center on a concept and detail
that concept, breaking it down in longer pieces, using subtitles. </li>
<li>Make sure that the articles are educated: its important that the writing
sounds authoritative. If you use quotes, or refer to sources, link to them. The
UK's Guardian Newspaper adheres particularly well to these three points, and is
a useful place for <a
href="http://www.guardian.co.uk/uk/2010/may/17/british-airways-strike-called-
off">examples</a></li>
<li>Articles shouldn't feel like a sales pitch (even if what's being 'sold' is
Free).</li>
<li>Articles should be informative: they should center on a concept and detail
that concept, breaking it down in longer pieces, using subtitles. </li>
<li>Make sure that the articles are educated: its important that the writing
sounds authoritative. If you use quotes, or refer to sources, link to them. The
UK's Guardian Newspaper adheres particularly well to these three points, and is
a useful place for <a
href="http://www.guardian.co.uk/uk/2010/may/17/british-airways-strike-called-
off">examples</a></li>
</ul>
<h2>Spelling and Grammar</h2>
<ul>
<li>Use British English spelling.</li>
<li>Use complete sentences. Avoid beginning sentences with however, because,
or so.</li>
<li>Numbers below 10 should be written in letters (one, two, three) but numbers
above 10 must be in numbers ('167', not 'one hundred sixty seven')</li>
<li>Dont use dashes. Instead utilise colons, and semi colons.</li>
<li>Almost always use abbreviated forms. For example: "it's" and not "it is";
"that's" and not "that is"; "they're" and not "they are".</li>
<li>Use British English spelling.</li>
<li>Use complete sentences. Avoid beginning sentences with however, because,
or so.</li>
<li>Numbers below 10 should be written in letters (one, two, three) but numbers
above 10 must be in numbers ('167', not 'one hundred sixty seven')</li>
<li>Dont use dashes. Instead utilise colons, and semi colons.</li>
<li>Almost always use abbreviated forms. For example: "it's" and not "it is";
"that's" and not "that is"; "they're" and not "they are".</li>
<li>Always use the definite article of "Free Software Foundation Europe", but never
when using the acronym "FSFE". eg. "The Free Software Foundation Europe is 10 years
old. FSFE has accomplished much...". Not "Free Software Foundation Europe is 10 years
old. The FSFE has accomplished much..."</li>
</ul>
<h2>Formatting</h2>
<ul>
<li>If the text is more than 500 words, break it up with sub-titles.</li>
<li>Use short paragraphs. As a rule, aim for paragraphs between 30 and 45
words.</li>
<li>The on-line marketing resource Copyblogger provides a very informative
<a href="http://www.copyblogger.com/copywriting-101">10-step
guide</a> to copywriting. Of course, some of its points are sales orientated,
but
its general sentiment Is very useful indeed:
</li>
<li>Do not use footnotes. This ensures greater portability of the article to
different mediums and formats, and also makes for easier reading, if handled
carefully.</li>
<li>Use the HTML abbr tag for acronyms and initialisms where appropriate. Note
that this should not be used for the first instance of the use of the FSFE
acronym, however.</li>
<li>Don't make any attempt to paginate documents that are intended for
publication
on-line in the first instance.</li>
<li>If the text is more than 500 words, break it up with sub-titles.</li>
<li>Use short paragraphs. As a rule, aim for paragraphs between 30 and 45
words.</li>
<li>The on-line marketing resource Copyblogger provides a very informative
<a href="http://www.copyblogger.com/copywriting-101">10-step
guide</a> to copywriting. Of course, some of its points are sales orientated,
but
its general sentiment Is very useful indeed:
</li>
<li>Do not use footnotes. This ensures greater portability of the article to
different mediums and formats, and also makes for easier reading, if handled
carefully.</li>
<li>Use the HTML abbr tag for acronyms and initialisms where appropriate. Note
that this should not be used for the first instance of the use of the FSFE
acronym, however.</li>
<li>Don't make any attempt to paginate documents that are intended for
publication
on-line in the first instance.</li>
</ul>
@ -75,8 +79,7 @@ on-line in the first instance.</li>
<ul>
<li>When referring to the activities, views etc. of FSFE, the organisation's
name
(or its acronym) should be used. Avoid use of 'we' and 'us' in text for
name (or its acronym) should be used. Avoid use of 'we' and 'us' in text for
publication. Occasionally using such terms can be useful for greater impact in
headlines and tag-lines. In these cases text should always be in quotes. Use of
the third person maintains portability, clarity and professionalism.</li>