search

equalsraf / neovim-qt

Neovim client library and GUI, in Qt5.
https://github.com/equalsraf/neovim-qt/wiki
ISC License
1.85k stars 171 forks source link

Low Resolution Font Rendering #367

Open SuborbitalSentinel opened 6 years ago

SuborbitalSentinel commented 6 years ago

image

On the Left is Neovim with :GuiFont Source Code Pro for Powerline:h11 On the Right is Neovim with :GuiFont Consolas:h11

Does anyone have any idea why the left is rendering at what I can only describe as "Low Resolution"?

This is on Windows 10 running neovim-qt.

Below is what I am expecting the left to look right (Vim running in wsltty on Windows 10):

image

ezpuzz commented 6 years ago

could be related to Source Code Pro being an OpenType font

Zyst commented 6 years ago

Not sure, but similar issue here.

comparison of font rendering issues

Using Operator Mono, left is WSL running in WSLtty, right is nvim-qt.exe.

The rendering really is a deal breaker in my case. Operator Mono is also an OpenType font, if we want to continue with that theory.

yzlnew commented 5 years ago

Same here. The font looks unreadable. image

xarthurx commented 4 years ago

Any update here? It seems Opentype is treated differently than TrueType.

Hyvok commented 4 years ago

I seem to have the same issue using Powerline fonts with nvim-qt v0.5.0-g3acfefb63 on Windows. The fonts just look "low res". Specifically trying to use the font https://github.com/powerline/fonts/blob/master/Inconsolata/Inconsolata%20for%20Powerline.otf

It also seems that if I attach my laptop to the dock with a separate screen then the fonts get even weirder (seems character spacing gets too tight and the characters touch each other).

neovim_inconsolate
Hyvok commented 4 years ago

I can report that setting environment variable QT_SCALE_FACTOR=1 in my case seems to make the font rendering look correct. By default it seemed to be not set.

NgrNxk commented 4 years ago

For me, setting QT_SCALE_FACTOR=1 made no difference at all. grafik

But setting QT_SCALE_FACTOR=1.01 makes the font readable: grafik

(I need GuiLinespace 1because some "g"s where cut.)

shadyalfred commented 3 years ago

Any updates on this issue?

ghost commented 3 years ago

Has somebody been able to determine the root cause here?

david-schuler commented 3 years ago

I experienced the same problem (on Windows 10) for OTF fonts. Replacing them (in Windows\Fonts) with TTF files solved the problem for me. In the Font Settings (in System Settings) dialog, you can check whether a TTF or OTF font is used.