New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work as expected #1
Comments
Hello! Fira Code in particular has been quite thoroughly tested with this app as I also use it myself, so I'm sure we can figure this out. I suppose you checked
|
Yes I have checked ss03 and ss05 and I have been using Fira Font's latest version v6.2. When I reopen the generated TTF file in fontFreeze, the preview is as expected. But when I open the same TTF file in fontforge app or use it in notepad++, then I don't see the glyphs changed. |
It is the correct behavior that you won't see glyph changes in FontForge because that's not how FontFreeze force activating the features (see readme for more details). I don't use Notepad++ myself, but my understanding is that it doesn't natively support coding ligatures, so the default activation method of FontFreeze won't work with it. Could you try changing the “Target feature for activation” setting to |
Ok got it. After following the link I can see the new @ and & in notepad++. I was thinking by default on any editor this should show the alternate variant of @ and & without needing to enable ligature. |
It works directly on Chrome, VS Code, Visual Studio, Android Studio, and PowerShell at least. Notepad++ seems to be an exception that doesn't strictly follow OpenType specifications. Maybe you can report an issue to them. |
Meanwhile, I can also try to implement actual glyph subsitituion (when it comes to features involving just a single character) in the next version for maximal compatibility. I've created an new issue #2 to track this. |
@w0am1 The new feature is now on in v1.3. I've tested with Fira Code + ss03-05, and the generated font works in Notepad++ without additional settings. If you found this app helpful, please star and spread the news to others 😁 |
Checked with v1.3 and it works perfectly. Thanks 👍 :) |
I tried freezing couple of features (use alternate variant of @ and &) of fira font, but in the generated ttf file both the glyps are still same as the default variant.
The text was updated successfully, but these errors were encountered: