qBittorrent/dist/windows
sledgehammer999 cfa7a6db46
Bump to 4.6.3
2024-01-15 01:45:17 +02:00
..
3rdparty NSIS: Refactor configuration to ease installer creation via scripting 2022-10-02 12:59:40 +03:00
installer-translations NSIS: Add Hebrew translation 2023-11-27 22:22:28 +02:00
nsis plugins Windows installer: also detect running process when it is 64-bit 2017-07-20 19:33:19 +02:00
CMakeLists.txt CMake: overhaul and improve scripts 2020-09-17 13:13:26 +01:00
config.nsi Bump to 4.6.3 2024-01-15 01:45:17 +02:00
gather_qt_translations.py NSIS: Fix missing slash in Qt translations script 2023-06-24 13:10:00 +08:00
installer.nsi NSIS: Display correct Minimum Windows OS requirement 2023-11-24 12:06:18 +03:00
qbittorrent.nsi NSIS: Require Windows 10 1809 for Qt6 builds 2022-10-02 12:54:36 +03:00
qt.conf Fixed blurry text under Windows by setting DPI awareness to default 2017-10-12 22:23:02 +03:00
README.txt NSIS: Refactor configuration to ease installer creation via scripting 2022-10-02 12:59:40 +03:00
translations.nsi Revert "NSIS: Add Bengali translation" 2021-10-25 00:46:34 +03:00
UAC.nsh Fix extra/missing trailing new lines in files 2020-10-28 14:20:18 +00:00
uninstaller.nsi Improve .torrent associate handling 2023-10-18 12:12:30 +08:00

TRANSLATORS:

1. Use an editor that has NSIS syntax highlighting(eg Notepad++/Geany). This will
   make your life easier.
2. Open the relevant .nsi file that exists in the folder named
   "installer-translations"
3. Lines starting with ";" are considered comments. These include the
   english message to help you with the translation.
4. Edit only the part inside the quotation marks(""). Unless you know
   what you are doing.
5. Save the files with UTF-8 encoding, without BOM
   (this should be the default in any modern text editor).
6. Submit your changes: 1) as a pull request to the official git repo or
   2) open an issue to the bugtracker and attach them or 3) via email or
   4)the same way you provide the translations for qbt itself

PACKAGERS:

You will need NSIS 3 to make the installer. UPX is an optional requirement.

1. Open the config.nsi file in an editor and change line that contains
   "!define QBT_VERSION "3.0.3"" to the version of qbittorrent you just built.
2. config.nsi contains some other defines that control the installer output. Read the comments in that file.
3. Extract the plugins found in the folder "nsis plugins" into your
   NSIS's unicode Plugin directory(usually C:\Program Files\NSIS\Plugins\x86-unicode).
   Only the *.dll files are needed. Use the unicode version of the dlls.
4. The script you need to compile is "qbittorrent.nsi". It includes all other necessary scripts.
5. The script expects the following file tree:

The installer script expects the following file tree:

Root:
installer-translations
	afrikaans.nsi
	....
	(all the .nsi files found here in every source release)
	welsh.nsi
translations
	qt_ar.qm
	...
    (All the .qm files found in the 'translations' folder of your Qt install. Those files differ between Qt5 and Qt6.
     You will need the files that conform to this globbing expression 'qt_??.qm qt_??_??.qm qtbase_??.qm qtbase_??_??.qm'.
     Some of those files will be stubs. Filter any file that is smaller than 10KB in size.
     Alternatively you can use the 'gather_qt_translations.py' script found in the same folder as this file.
     Run it with '--help' to see its usage.)
	qt_zh_TW.qm
installer.nsi
license.txt
config.nsi
helper.nsi
qbittorrent.exe
qbittorrent.pdb
qbittorrent.nsi
qt.conf
translations.nsi
UAC.nsh
uninstaller.nsi


6. "license.txt" is a text file that contains the text rendered
   from src\gui\gpl.html
7. "qbittorrent.exe" is the compiled binary file.
8. "qbittorrent.pdb" is the compiled binary's PDB file.

SCRIPT HACKERS:

If you add any new LangString variable to the scripts you NEED to provide
"translations" of it to all the .nsi files inside "installer-translations.
You can always leave the english string but you have to use all the LANG_<lang name>
for the given variable. Otherwise, if the user chooses a language that you
haven't provided a LANG_<lang name> for your variable then your string will be empty.
Don't worry though, NSIS throws warnings for this when compiling the scripts.