From bda674751c3a4fd9ea15099b1acdf1243a6f7458 Mon Sep 17 00:00:00 2001 From: WrinklyNinja Date: Wed, 27 Aug 2014 19:37:06 +0100 Subject: [PATCH] Removed translation section. Also merged troubleshooting and contributing sections. Translation info has moved to LOOT's wiki. --- docs/LOOT Readme.html | 45 +++++-------------------------------------- 1 file changed, 5 insertions(+), 40 deletions(-) diff --git a/docs/LOOT Readme.html b/docs/LOOT Readme.html index 2cc0257e..928bb54d 100644 --- a/docs/LOOT Readme.html +++ b/docs/LOOT Readme.html @@ -95,9 +95,7 @@ h3{
  • Customising LOOT's Results
  • Editing Settings -
  • Troubleshooting -
  • Contributing To LOOT -
  • Translating LOOT +
  • Contributing & Support
  • Credits
  • License
  • Appendices @@ -291,51 +289,18 @@ h3{

    Note that for Skyrim, multiple copies or Total Conversions will all edit the same plugins.txt file, and so they lack the level of independence that is achievable for other games. -

    Troubleshooting

    -

    If you encounter an issue, check the Frequently Asked Questions wiki page in case a solution is available there. If no solution for your problem is listed there, please seek further support in an official LOOT thread (see Contributing To LOOT). +

    Contributing & Support

    +

    LOOT is very much a community project, and contributions from its users are vital to its upkeep, whether they be metadata, translations, code or anything else. The best way to contribute is to make changes yourself at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our credits. +

    If you encounter an issue with LOOT, check the Frequently Asked Questions wiki page in case a solution is available there. -

    Contributing To LOOT

    -

    LOOT is very much a community project, and contributions from its users are vital to its upkeep. The best way to contribute is to make changes yourself at GitHub! It's the fastest way to get changes you want applied, and you'll get your name automatically immortalised in our credits. - -

    Otherwise, general discussion takes place in LOOT's official forum threads. These are linked to at the bottom of LOOT's homepage. +

    Otherwise, general discussion and support takes place in LOOT's official forum threads. These are linked to at the bottom of LOOT's homepage.

    If you want to submit metadata, the easiest way to do so is to add the metadata to your own LOOT install, then use the Copy Metadata As Text 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.

    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 CRC checksum for data 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. -

    Translating LOOT

    -

    LOOT supports translation into other languages, with the following limitations: -

    -

    Translations are best submitted through GitHub's forking system. You will need to fork the LOOT source code repository. All file paths given below are relative to the base folder of that repository. -

    To translate LOOT's installer: -

      -
    1. Open the installer script at src/installer.nsi in a text editor of your choice. -
    2. The English strings are located in the section with the heading English Strings. Copy and paste this section into a new text file, and translate the quoted strings, replacing the English text. For the lines beginning VIAddVersionKey, only translate the second quoted string. -
    3. Save the text file containing your translated strings. -
    -To translate the LOOT application: -
      -
    1. Download and install the latest version of Poedit. -
    2. If you are starting a new translation, select File->New catalogue from POT file... and choose the template file at resources/l10n/template.pot. In the Catalog properties dialog, just click OK without changing anything. -
    3. If you are updating a previous translation, open in Poedit the loot.po translation file in the relevant subdirectory of resources/l10n, then select Catalogue->Update from POT file... and choose the template file you downloaded. Click OK in the Update summary dialog. -
    4. 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. -

      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. While no contextual information is supplied to translators by default, it can be added on request. To request the addition of contextual information to a text string, create an issue for your request in LOOT's issue tracker, quoting the structure that contains the string for which you are requesting contextual information. -

      Some strings to be translated may contain special characters. Different types of special character that may be encountered are: -

        -
      • Backslashes \. Backslashes must be escaped using another backslash, so if you wanted to display a single backslash \, you would put \\ in your translated string. -
      • Double-quotation marks ". Double-quotation marks must be preceded by a backslash, ie. \", or LOOT will crash when it tries to display the string. -
      • 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. %1%. If formatting placeholders are used in the untranslated string, they must all 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. -
      -
    5. Save the translation file with the filename loot.po in resources/l10n/<locale>/LC_MESSAGES/, where <locale> is your language's locale code. -
    - -

    Credits

    LOOT is developed by a team on GitHub, with contributions from users. A full list of GitHub contributors may be found here. An up-to-date list of team members may be viewed on the project wiki. Unless otherwise noted, team members can be contacted on the Bethesda Softworks Forums or on The Nexus Forums via the private messaging system.

    LOOT's masterlists were largely converted from BOSS's masterlists, and so credit is due to the very large number of sources and people who have contributed to them.