New customers can spin up VMs, build with AI, and query data at no cost.
Put your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
Start Free
Build Securely on AWS with Proven Frameworks
Lay a foundation for success with Tested Reference Architectures developed by Fortinet’s experts. Learn more in this white paper.
Moving to the cloud brings new challenges. How can you manage a larger attack surface while ensuring great network performance? Turn to Fortinet’s Tested Reference Architectures, blueprints for designing and securing cloud environments built by cybersecurity experts. Learn more and explore use cases in this white paper.
Better font rendering for Windows. Win10 compatible. CET compatible. Updated FreeType. Support for color fonts. New installer. Lots of bug fixes. Updates for multi-monitor support. Tray app can intercept explorer in Service Mode now. Tweaks for diacritics. Updates to EasyHook. Lower CPU in Tray Mode. Separate DirectWrite parameter adjustment. Traditional Chinese localization greatly improved thanks to GT Wang. English localization improved. Added Korea localization. MultiLang system improved.
Fira Code is a free and open source monospaced font containing programming ligatures for the most commonly-used multi-character combinations in programming. Programmers use a lot of symbols that are encoded through a series of characters. Often these symbols are quickly done and overlooked, causing errors due to spacing, etc. Fira Code helps solve such problems. While all programming languages should be designed with full-fledged Unicode symbols for operators, such is not yet the case. ...
...Hasklig solves the problem the way typographers have always solved ill-fitting characters which co-occur often, ligatures. The underlying code stays the same, only the representation changes. Not only can multi-character glyphs be rendered more vividly, other problematic things in monospaced fonts, such as spacing can be corrected.
...Assuming that you are using Gradle you should create the assets directory under src/main/ in your project directory if it does not already exist. As it's popular to use multi-project build with Gradle the path is usually app/src/main/assets/, where app is the project name. You might consider creating a fonts/ subdirectory in the assets directory. Define your default font using CalligraphyConfig, in your Application class in the #onCreate() method and pass it to the CalligraphyInterceptor that you add to your ViewPump builder. ...