search

gabrielelana / awesome-terminal-fonts

Tools and instructions on how to have awesome symbols in a terminal with a monospace font
MIT License
2.45k stars 230 forks source link

SourceCodePro+Powerline+Awesome Not working in Chrome 55 on Win10 #32

Closed grizleeeee closed 7 years ago

grizleeeee commented 7 years ago

I'm trying to use the fonts with Secure Shell in Chrome, and they're not displaying properly. At first I thought it was my installation/method of usage, but after setting my mono-spaced font to SourceCodePro+Powerline+Awesome in the Chrome preferences, I'm beginning to think this is a Chrome incompatibility.

It displays fine in the preferences preview: snip1 But when it comes to actually displaying text on a page, it fails: snip2

If this is a Chrome issue, then so be it, but other iterations of SouceCodePro work without an issue in hterm (Secure Shell), so I'm not 100% sure where the problem lies. If there's anything else I should try, let me know.

gabrielelana commented 7 years ago

I don't know if you still have this issue but I bet you have better chances at overriding the CSS classes of Secure Shell in Chrome that make the patched font work. The patched font is kind of an hack for situations where you cannot use multiple fonts at once. Browsers supports the usage of multiple fonts and with Tampermonkey you can customize the appearence of Secure Shell, you can inject a CSS rule that forces the browser to display a certain range of codepoints with a specified font

@font-face {
    font-family: Foobar;
    src: local('Times New Roman');
    unicode-range: U+61-6E;
}