You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,10 +41,24 @@ Keep in mind that you don't need to submit a perfect pull request; just follow t
41
41
42
42
First check that an [Inno Setup translation](http://www.jrsoftware.org/files/istrans/) exists for your language. Unofficial translations are acceptable, but require a bit of extra handling. If there isn't an official or unofficial translation for Inno Setup, you're better off making a translation and getting it listed on the linked page before continuing.
43
43
44
+
To translate the LOOT-specific messages:
45
+
46
+
1. Copy `resources/l10n/en/LC_MESSAGES/inno.islu` to `resources/l10n/<language>/LC_MESSAGES/inno.islu` if the latter file does not exist, where `<language>` is the [POSIX locale code](https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html) for your language.
47
+
2. Open the copied file in your favourite text editor.
48
+
2. Translate the string(s) into your language. Do not change the text before the first `=` as that is the message's name.
49
+
3. Save your changes.
50
+
51
+
To add your language as an option in LOOT's installer:
52
+
44
53
1. Open the installer script at `scripts/installer.iss` in a text editor of your choice.
45
54
2. If your language only has an unofficial translation, add a `#define <Language>Exists` block for it near the top of the script, like it has been done for Korean and Simplified Chinese.
46
-
3. Add your language to the `[Languages]` section. The `Name` should be the [POSIX locale code](https://www.gnu.org/software/gettext/manual/html_node/Locale-Names.html) for your language. The `MessagesFile` filename is the filename of the Inno Setup translation that you checked exists. If your language only has an unofficial translation, wrap its line in `#ifdef` and `#endif` lines, again like it has been done for Korean and Simplified Chinese.
47
-
4. Translate the string(s) in the `[CustomMessages]` into your language, following the example of the existing translations. Again, if your language only has an unofficial translation, wrap its line(s) in `#ifdef` and `#endif` lines.
55
+
3. Add your language to the `[Languages]` section.
56
+
57
+
The `Name` value should be the POSIX locale code for your language.
58
+
59
+
The `MessagesFile` value should be `compiler:Languages\<translation file>,resources/l10n/<language>/LC_MESSAGES/inno.islu`, where `<translation file>` is the filename of the Inno Setup translation that you checked exists and `<language>` is your language's POSIX locale code.
60
+
61
+
If your language only has an unofficial translation, wrap its line in `#ifdef` and `#endif` lines, again like it has been done for Korean and Simplified Chinese.
48
62
5. Save your changes.
49
63
50
64
If your language's Inno Setup translation is unofficial, also do the following:
0 commit comments