7543060f1d
[src\meson.build] Add DirectWrite has dependency
[src\font_file_lister_gdi] Rework GDI FontCollector to use DirectWrite
This replaces all the logic of using the Windows registry to obtain the font path by using DirectWrite. The goal is simply to improve the quality of the code. This doesn't change any functionality
[src\meson.build] Remove Uniscribe has dependency
Uniscribe was only used for the FontCollector. Since we now use DirectWrite, we don't need it anymore.
[src\dialog_fonts_collector] Catch exceptions that FontCollector may raise
On Windows, the initialization of the FontCollector can raise an exception
[src\font_file_lister] Document the exception that GdiFontFileLister can throw
[src\font_file_lister_gdi] Correct possible memory leak when an error occur
Fix error caused by AddFontResource on Windows 10 or higher
[meson.build] Replace add_project_arguments with conf.set for HAVE_DWRITE_3
[src\dialog_fonts_collector] Update message error and optimisation
[src\font_file_lister_gdi] Correct documentation typo
[src\font_file_lister_gdi] Cosmetic nit - Initialize hfont in one line
[src\font_file_lister_gdi] Cosmetic nit - Remove if statements brace
[src\font_file_lister_gdi] Replace WCHAR param of normalizeFilePathCase to std::wstring
[src\font_file_lister_gdi] Replace WCHAR by std::wstring
[src\font_file_lister_gdi] Use IDWriteFontFace::GetSimulations to detect fake_italic/fake_bold
See this comment: https://github.com/arch1t3cht/Aegisub/pull/107#issuecomment-1975229652
[src\font_file_lister_gdi] If Win7/8 has Win 10 SDK on compile time, correctly verify if font has character(s)
With the Visual Studio 2019 toolchain on Windows 7, it installs the Windows 10 SDK by default. Because of this, ``HAVE_DWRITE_3`` is true, so the ``QueryInterface`` always fails. Now, if the ``QueryInterface`` fails, we try to verify if the font has characters with a Windows Vista SP2 compatible code.
[src\font_file_lister_gdi] Support facename that contains only whitespace AND truncated facename
Problem 1:
Previously, if a user wrote "\fn ", it would return the font Arial, which is not what we want. This is because when we request EnumFontFamiliesEx with whitespace or an empty lfFaceName, it will enumerate all the installed fonts.
Solution 1:
To resolve this issue, let's implement a solution similar to libass to determine if the selected facename exists:
|
||
|---|---|---|
| .github/workflows | ||
| automation | ||
| docs | ||
| libaegisub | ||
| packages | ||
| po | ||
| src | ||
| subprojects | ||
| tests | ||
| tools | ||
| .gitignore | ||
| LICENCE | ||
| README.md | ||
| meson.build | ||
| meson_options.txt | ||
README.md
Aegisub
For binaries and general information see the homepage.
The bug tracker can be found at https://github.com/Aegisub/Aegisub/issues.
Support is available on Discord or IRC.
Building Aegisub
Windows
Prerequisites:
- Visual Studio (Community edition of any recent version is fine)
- The June 2010 DirectX SDK (the final release before DirectSound was dropped)
- Python 3
- Meson
- CMake
- Powershell execution policy set to Unrestricted
There are a few optional dependencies that must be installed and on your PATH:
- msgfmt, to build the translations
- InnoSetup, to build the regular installer
- 7zip, to build the regular installer
- Moonscript, to build the regular installer
All other dependencies are either stored in the repository or are included as submodules.
Building:
- Clone Aegisub's repository:
git clone https://github.com/TypesettingTools/Aegisub.git - From the Visual Studio "x64 Native Tools Command Prompt", generate the build directory:
meson build -Ddefault_library=static(if building for release, add--buildtype=release) - Build with
cd buildandninja
You should now have a binary: aegisub.exe.
Installer:
You can generate the installer with ninja win-installer after a successful build. This assumes a working internet connection and installation of the optional dependencies.
You can generate the portable zip with ninja win-portable after a successful build.
OS X
A vaguely recent version of Xcode and the corresponding command-line tools are required.
For personal usage, you can use pip and homebrew to install almost all of Aegisub's dependencies:
pip3 install meson
brew install cmake ninja pkg-config libass boost zlib ffms2 fftw hunspell
export LDFLAGS="-L/usr/local/opt/icu4c/lib"
export CPPFLAGS="-I/usr/local/opt/icu4c/include"
export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig"
Once the dependencies are installed, build Aegisub with meson build && meson compile -C build.
Build dmg
meson build_static -Ddefault_library=static -Dbuildtype=debugoptimized -Dbuild_osx_bundle=true -Dlocal_boost=true
meson compile -C build_static
meson test -C build_static --verbose
meson compile osx-bundle -C build_static
meson compile osx-build-dmg -C build_static
Updating Moonscript
From within the Moonscript repository, run bin/moon bin/splat.moon -l moonscript moonscript/ > bin/moonscript.lua.
Open the newly created bin/moonscript.lua, and within it make the following changes:
- Prepend the final line of the file,
package.preload["moonscript"](), with areturn, producingreturn package.preload["moonscript"](). - Within the function at
package.preload['moonscript.base'], remove references tomoon_loader,insert_loader, andremove_loader. This means removing their declarations, definitions, and entries in the returned table. - Within the function at
package.preload['moonscript'], remove the line_with_0.insert_loader().
The file is now ready for use, to be placed in automation/include within the Aegisub repo.
License
All files in this repository are licensed under various GPL-compatible BSD-style licenses; see LICENCE and the individual source files for more information. The official Windows and OS X builds are GPLv2 due to including fftw3.