We will be doing maintenance work on Vivaldi Translate on the 11th of May starting at 03:00 (UTC) (see the time in your time zone).
Some downtime and service disruptions may be experienced.
Thanks in advance for your patience.
Spacing of Roboto font incorrect
-
Hi all,
I have an issue which seems (AFAICT) to do with the spacing in between characters of the Roboto font in Vivaldi. The issue does not happen in Chrome.
In the small screenshot below, you can see that the "not" is spaced very differently to many of the other letters (screenshot taken from Gmail):
Another example is from the page for the Font Rendering Enhancer extension (note that I don't have this or any other font changing extensions installed). It's very clear in the "tp" in the "http" and "https", but also in some of the other text:
This seems to only happen with the Roboto font. I have confirmed these text sections use the Roboto font by looking at the computed properties in developer tools, and for all the pages that I've looked at that don't have this problem, none of them use Roboto. As I said earlier, this doesn't happen in Chrome (suggesting it's not an issue with my installation of the Roboto font).
I have wondered whether Vivaldi was enabling, or otherwise doing something with, ligatures. But I don't know enough about it to know which letters are likely to be joined together etc.
Does anyone have any idea of what might be wrong?
Thanks.
-
Thanks for the reply.
- I'm using openSUSE Leap 15.1
- Roboto font version: 20161103.2.135-lp151.2.1
- Still happens with hardware acceleration disabled
You may well be right that my font and/or config is broken, but as I said, this issue doesn't seem happen in Chrome, meaning it's either not a problem with my font/config, or Chrome does something to fix it.
-
Turns out it was a problem with my configuration.
In my system settings, when "Hinting" is was set to "Full", the problem would show up, but when it's set back to "Slight", the problem goes away and the fonts look great.
Still not sure why Chrome showed different behaviour to Vivaldi, but whatever, at least I have a fix.
-
Ppafflick unlocked this topic on
-
Ppafflick moved this topic from Vivaldi for Linux on