mirror of
https://github.com/loot/libloot.git
synced 2026-07-27 14:16:01 -07:00
Update remaining HTTPSifiable URLs.
This commit is contained in:
Frederik “Freso” S. Olesen
+1
-1
@@ -43,7 +43,7 @@ First check that an [Inno Setup translation](http://www.jrsoftware.org/files/ist
|
||||
|
||||
### Translating the LOOT application
|
||||
|
||||
1. Download and install the latest version of [Poedit](http://www.poedit.net/).
|
||||
1. Download and install the latest version of [Poedit](https://poedit.net/).
|
||||
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.
|
||||
|
||||
@@ -25,11 +25,11 @@ For example `LOOT v0.7.0-alpha-2-10-gf6d7e80_dev.7z` was built using the revisio
|
||||
|
||||
## Building LOOT
|
||||
|
||||
LOOT's build process uses [CMake](http://cmake.org). Most of LOOT's C++ dependencies are managed by CMake, but the following must be obtained manually:
|
||||
LOOT's build process uses [CMake](https://cmake.org). Most of LOOT's C++ dependencies are managed by CMake, but the following must be obtained manually:
|
||||
|
||||
* [Boost](http://www.boost.org) v1.55+
|
||||
|
||||
Building LOOT's GUI also uses [Node.js](http://nodejs.org/). With it installed, run `npm install` then `node_modules/.bin/bower install` from the repository root to install the additional tools and dependencies required.
|
||||
Building LOOT's GUI also uses [Node.js](https://nodejs.org/). With it installed, run `npm install` then `node_modules/.bin/bower install` from the repository root to install the additional tools and dependencies required.
|
||||
|
||||
The GUI's HTML file is automatically built when building the LOOT GUI binary, but it can also be built by running `node scripts/vulcanize.js` from the repository root.
|
||||
|
||||
@@ -52,4 +52,4 @@ Packaging scripts are provided for creating an installer on Windows and compress
|
||||
|
||||
Run the `scripts/installer.iss` [Inno Setup](http://www.jrsoftware.org/isinfo.php) script to build an installer executable in the `build` folder. If the unofficial Korean and Simplified Chinese Inno Setup translation files are installed alongside the official translation files, then the installer script will also offer those language options. If they are not found, the installer will be built without them.
|
||||
|
||||
The archive packaging script requires [Git](http://git-scm.com/), and on Windows it also requires [7-Zip](http://7-zip.org), while on Linux it requires `tar` and `xz`. It can be run using `node scripts/archive.js`, and creates archives for LOOT, its API and the metadata validator in the `build` folder. The archives are named as described in the Downloads section above.
|
||||
The archive packaging script requires [Git](https://git-scm.com/), and on Windows it also requires [7-Zip](http://7-zip.org), while on Linux it requires `tar` and `xz`. It can be run using `node scripts/archive.js`, and creates archives for LOOT, its API and the metadata validator in the `build` folder. The archives are named as described in the Downloads section above.
|
||||
|
||||
@@ -459,7 +459,7 @@ figure > div {
|
||||
<tr><td>Master File<td>The game's main master file. This is checked for when detecting if the game is installed.
|
||||
<tr><td id="settingsMasterlistURL">Masterlist Repository URL<td>The URL of the repository that LOOT uses to update its local copy of the masterlist. If left empty, masterlist updating will be skipped.
|
||||
<br><br>
|
||||
Masterlist repositories are <a href="http://git-scm.com/">Git</a> repositories that are configured to allow unauthenticated read access and contain a masterlist file named <code>masterlist.yaml</code> in their root directory. The LOOT team maintains a set of official repositories for the games that LOOT supports by default.
|
||||
Masterlist repositories are <a href="https://git-scm.com/">Git</a> repositories that are configured to allow unauthenticated read access and contain a masterlist file named <code>masterlist.yaml</code> in their root directory. The LOOT team maintains a set of official repositories for the games that LOOT supports by default.
|
||||
<tr><td>Masterlist Repository Branch<td>The branch of the masterlist repository that LOOT should get masterlist updates from.
|
||||
<tr><td>Install Path<td>The path to the game's folder, in which the Data folder lies. Either this or a registry key must be supplied.
|
||||
<tr><td>Install Path Registry Key<td>The registry key, in <code>HKEY_LOCAL_MACHINE</code>, that contains the install path of the game. This is used to obtain the install path if LOOT has no previous record of the game's install path, or LOOT's stored install path is invalid. Either this or an install path must be supplied.
|
||||
@@ -483,7 +483,7 @@ figure > div {
|
||||
|
||||
<h2 id="credits">Credits</h2>
|
||||
<p>LOOT is developed on <a href="https://github.com/loot/">GitHub</a>, and a full list of GitHub contributors may be found <a href="https://loot.github.io/credits/">here</a>.
|
||||
<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>LOOT's masterlists were largely converted from <a href="https://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>
|
||||
<li>Original icon: jonwd7
|
||||
|
||||
+6
-6
@@ -50,13 +50,13 @@
|
||||
*
|
||||
* @section credit_sec Credits
|
||||
* The LOOT API is written by [WrinklyNinja]
|
||||
* (http://github.com/WrinklyNinja) in C/C++ and makes use of the
|
||||
* (https://github.com/WrinklyNinja) in C/C++ and makes use of the
|
||||
* [Boost](http://www.boost.org/),
|
||||
* [libespm](http://github.com/WrinklyNinja/libespm),
|
||||
* [libgit2](http://github.com/libgit2/libgit2),
|
||||
* [libloadorder](http://github.com/WrinklyNinja/libloadorder/),
|
||||
* [Pseudosem](http://github.com/WrinklyNinja/pseudosem) and
|
||||
* [yaml-cpp](http://github.com/WrinklyNinja/yaml-cpp) libraries. Copyright
|
||||
* [libespm](https://github.com/WrinklyNinja/libespm),
|
||||
* [libgit2](https://github.com/libgit2/libgit2),
|
||||
* [libloadorder](https://github.com/WrinklyNinja/libloadorder/),
|
||||
* [Pseudosem](https://github.com/WrinklyNinja/pseudosem) and
|
||||
* [yaml-cpp](https://github.com/WrinklyNinja/yaml-cpp) libraries. Copyright
|
||||
* license information for all these may be found in the
|
||||
* "docs/licenses/Licenses.txt" file.
|
||||
*
|
||||
|
||||
Reference in New Issue
Block a user