Updated contributing and credits info.

Now gives prominence to GitHub forks as a contribution method.

docs/LOOT Readme.html

@@ -311,13 +311,15 @@ Clicking on a plugin in the list will display the editing panel, where its load
 
 
 <h2 id="contrib">Contributing To LOOT</h2>
-<p>User contribution of additions and corrections to LOOT's masterlists are vital to the upkeep of LOOT. Please let us know what you know!
+<p>LOOT is very much a community project, and contributions from its users are vital to its upkeep. The best way to contribute is to <a href="https://github.com/loot/loot.github.io/wiki/How-To-Contribute">make changes yourself</a> at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our <a href="http://loot.github.io/credits/">credits</a>.
 
-<p>General discussion and the submission of questions, suggestions and metadata takes place in LOOT's official threads for Oblivion, Skyrim, Fallout 3 and Fallout: New Vegas. These are linked to at the bottom of <a href="http://loot.github.io">LOOT's homepage</a>.
+<p>Otherwise, general discussion takes place in LOOT's official forum threads. These are linked to at the bottom of <a href="http://loot.github.io">LOOT's homepage</a>.
+
+<p>If you want to submit metadata, the easiest way to do so is to add the metadata to your own LOOT install (either during sorting or in the Metadata Editor), and use the <a href="#editorCopyMetadataAsText">Copy Metadata As Text</a> feature to easily get it in a form that you can then edit into a masterlist on GitHub or post in the official forum threads.
 
 <p>Information on dirty plugins is very welcome, but for such information to be useful we require at least the filename and the CRC of the dirty plugin. The CRC may be calculated using Wrye Bash or 7-zip, with other sources being unverified as correct. In the case of 7-zip, the <q><em>CRC checksum for data</em></q> is the one required. In addition to the CRC, the number of records removed (the ITM count) and/or undeleted (the UDR count) are also welcome.
 
-<p>If you wish to submit metadata, the easiest way to do so is to add the metadata to your own LOOT install (either during sorting or in the Metadata Editor), and use the <a href="#editorCopyMetadataAsText">Copy Metadata As Text</a> feature to easily get it in a form that you can then post in the official forum threads.
+<p>
 
 
 <h2 id="translate">Translating LOOT</h2>
@@ -327,30 +329,18 @@ Clicking on a plugin in the list will display the editing panel, where its load
     <li>Masterlist messages can be translated, but translations must be submitted to the masterlist maintainers for addition.
     <li>The languages LOOT supports is hardcoded, so LOOT must be updated to include new translations.
 </ul>
-<p>Translations can be submitted for inclusion into LOOT in the <a href="https://github.com/loot/loot/issues/20">relevant issue tracker entry</a>, by posting it in one of LOOT's official threads (see <a href="#contrib">Contributing To LOOT</a>), or by contacting one of the LOOT team directly (see <a href="#project">Project Members</a>).
+<p>Translations are best submitted through GitHub's <a href="https://github.com/loot/loot.github.io/wiki/How-To-Contribute">forking system</a>. You will need to fork the LOOT <a href="https://github.com/loot/loot">source code repository</a>. All file paths given below are relative to the base folder of that repository.
 <p>To translate LOOT's installer:
 <ol>
-    <li>Download the <a href="https://github.com/loot/loot/blob/master/src/installer.nsi">installer script</a>.
-    <li>Open the downloaded installer script in a text editor of your choice.
+    <li>Open the installer script at <code>src/installer.nsi</code> in a text editor of your choice.
     <li>The English strings are located in the section with the heading <q>English Strings</q>. Copy and paste this section into a new text file, and translate the quoted strings, replacing the English text. For the lines beginning <code>VIAddVersionKey</code>, only translate the second quoted string.
     <li>Save the text file containing your translated strings.
 </ol>
 To translate the LOOT application:
 <ol>
  <li>Download and install the latest version of <a href="http://www.poedit.net/">Poedit</a>.
- <li>Download <a href="https://github.com/loot/loot/blob/master/resources/l10n/template.pot">LOOT's translation template file</a>.
- <li>If you are updating an existing translation, download the relevant translation file for the language you're interested in:
- <ul>
-  <li><a href="https://github.com/loot/loot/blob/master/resources/l10n/zh_CN/LC_MESSAGES/loot.po">Chinese</a>
-  <li><a href="https://github.com/loot/loot/blob/master/resources/l10n/fr/LC_MESSAGES/loot.po">French</a>
-  <li><a href="https://github.com/loot/loot/blob/master/resources/l10n/pl/LC_MESSAGES/loot.po">Polish</a>
-  <li><a href="https://github.com/loot/loot/blob/master/resources/l10n/pt_BR/LC_MESSAGES/loot.po">Brazilian Portuguese</a>
-  <li><a href="https://github.com/loot/loot/blob/master/resources/l10n/ru/LC_MESSAGES/loot.po">Russian</a>
-  <li><a href="https://github.com/loot/loot/blob/master/resources/l10n/es/LC_MESSAGES/loot.po">Spanish</a>
- </ul>
- <li>Open Poedit and select <q>File->Preferences</q>, then in the <q>Editor</q> tab ensure that the checkbox for the <q>Automatically compile .mo file on save</q> setting is checked. Click <q>OK</q> to close the preferences window.
- <li>If you are starting a new translation, select <q>File->New catalogue from POT file...</q> and choose the template file you downloaded. In the <q>Catalog properties</q> dialog, just click <q>OK</q> without changing anything.
- <li>If you are updating a previous translation, open the translation file you downloaded in Poedit, then select <q>Catalogue->Update from POT file...</q> and choose the template file you downloaded. Click <q>OK</q> in the <q>Update summary</q> dialog.
+ <li>If you are starting a new translation, select <q>File->New catalogue from POT file...</q> and choose the template file at <code>resources/l10n/template.pot</code>. In the <q>Catalog properties</q> dialog, just click <q>OK</q> without changing anything.
+ <li>If you are updating a previous translation, open in Poedit the <code>loot.po</code> translation file in the relevant subdirectory of <code>resources/l10n</code>, then select <q>Catalogue->Update from POT file...</q> and choose the template file you downloaded. Click <q>OK</q> in the <q>Update summary</q> dialog.
  <li>Edit the translation file to add or update translations of the programs' text. Strings that were added since the last translation are displayed in bold and dark blue, and strings you have edited the translations of are marked with a star to the left of their source text in the main list.
 <p>Some languages may use different words or phrases for different contexts where only one word or phrase may be used for all contexts in English. <strong>While no contextual information is supplied to translators by default, it can be added on request</strong>. To request the addition of contextual information to a text string, contact WrinklyNinja, quoting the structure that contains the string for which you are requesting contextual information.
 <p>Some strings to be translated may contain special characters. Different types of special character that may be encountered are:
@@ -361,12 +351,12 @@ To translate the LOOT application:
  <li>Words containing an ampersand <code>&amp;</code>. If a string contains a word that begins with or includes an ampersand, the string is for a menu item and the ampersand is a symbol placed before a specific letter and used to show which keyboard key can be used to select that menu item. The ampersand can be moved to be placed before a more appropriate letter in the translated text.
  <li>Formatting placeholders. Placeholders are used so that LOOT can substitute text or numbers that are generated at runtime into pre-made strings. They appear as a number surrounded by percentage signs, eg. <code>%1%</code>. If formatting placeholders are used in the untranslated string, they <strong>must all</strong> be present in the translated string, or LOOT will crash when it tries to display the translated string. Placeholders can be moved around so that the sentence makes grammatical sense in the target language.
 </ul>
- <li>Save the translation file with the filename <code>loot.po</code> in a location of your choosing. This will also create a <code>loot.mo</code> file in the same location.
+ <li>Save the translation file with the filename <code>loot.po</code> in a location of your choosing.
 </ol>
 
 
 <h2 id="credits">Credits</h2>
-<p>LOOT is developed by a team on <a href="https://github.com/loot/">GitHub</a>. An up-to-date list of team members past and present may be viewed  on the <a href="https://github.com/loot/loot.github.io/wiki/Team-Members">project wiki</a>. Unless otherwise noted, project members can be contacted on the <a href="http://forums.bethsoft.com/index.php">Bethesda Softworks Forums</a> or on <a href="http://forums.nexusmods.com/">The Nexus Forums</a> via the private messaging system.
+<p>LOOT is developed by a team on <a href="https://github.com/loot/">GitHub</a>, with contributions from users. A full list of GitHub contributors may be found <a href="http://loot.github.io/credits/">here</a>. An up-to-date list of team members may be viewed on the <a href="https://github.com/loot/loot.github.io/wiki/Team-Members">project wiki</a>. Unless otherwise noted, team members can be contacted on the <a href="http://forums.bethsoft.com/index.php">Bethesda Softworks Forums</a> or on <a href="http://forums.nexusmods.com/">The Nexus Forums</a> via the private messaging system.
 <p>LOOT's masterlists were largely converted from <a href="http://boss-developers.github.io">BOSS</a>'s masterlists, and so credit is due to the very large number of sources and people who have contributed to them.
 <p>In addition, the following are credited with application-related support:
 <ul>