-
-
Notifications
You must be signed in to change notification settings - Fork 869
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
Is there a way to add a TTF font? #240
Comments
You have to add the font file to app/qml/resources.qrc as well. And you also need to define the font in FontsScanlines.qml and FontsPixel.qml |
This particular font is redundant with the way cool-retro-term already renders scanlines. |
Is it possible to replace a font already in CRT? I'm planning to replace the included normal Terminus font with a version patched for Powerline (more supported characters). |
You can replace and add fonts. However at least the Hack font doesn't look right. I have tried re-compiling with different settings for it in Fonts.qml a few times but my changes don't seem to make a difference. Perhaps |
terminus has newer versions, than what you ship: http://files.ax86.net/terminus-ttf/files/ |
a good option for fonts, at least on mac, is to store them outside a resource file (like in cool-retro-term.app/Contents/Resources/fonts) and parse fonts available when the application starts. For linux I think the same should apply, but as linux install fonts in a common place we're facing a problem trying to scan a bunch of fonts at start. |
http://sid.ethz.ch/debian/cool-retro-term/2020/ system fonts are supported! |
I found this really sweet VT220 font: http://christfollower.me/misc/glasstty/
Is there a way to add it? When I modify app/qml/Fonts.qml and add an entry for the TTF file, CRT outputs: qrc:/PreprocessedTerminal.qml:117:9: QML FontLoader: Cannot load font: "qrc:/fonts/VT220/VT220.ttf," but doesn't tell me much more about it.
This isn't a bug, more of a feature request or a good thing for the wiki.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: