Font hinting is lost in Chrome-like browsers (for some languages )
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Since Ubuntu 18.04 (maybe from 17.10, I can't remember), some languages' font hinting are lost in Chrome-like browsers (like Chromium, Bangla, ... ). Also, Chrome's UI font itself renders so bad that the use of Chromium on Ubuntu became impossible.
Interestingly, all Ubuntu derivatives inherited this bug but other distros like Manjaro don't show this behaviour.
Below is a screenshot demonstrating the problem: the text of "Autofill" and "Appearance" becomes fuzzy (Click on both of the images for a full-size image)
Below a screenshot of the expected behaviour:
What's an easy fix to this issue?
18.04 fonts 19.04
edited 9 hours ago
Fabby
27.1k1360161
asked 12 hours ago
AnwarAnwar
57.4k22149255
add a comment |
Since Ubuntu 18.04 (maybe from 17.10, I can't remember), some languages' font hinting are lost in Chrome-like browsers (like Chromium, Bangla, ... ). Also, Chrome's UI font itself renders so bad that the use of Chromium on Ubuntu became impossible.
Interestingly, all Ubuntu derivatives inherited this bug but other distros like Manjaro don't show this behaviour.
Below is a screenshot demonstrating the problem: the text of "Autofill" and "Appearance" becomes fuzzy (Click on both of the images for a full-size image)
Below a screenshot of the expected behaviour:
What's an easy fix to this issue?
18.04 fonts 19.04
edited 9 hours ago
Fabby
27.1k1360161
asked 12 hours ago
AnwarAnwar
57.4k22149255
There's a difference?
– Sean
7 hours ago
1
@Sean you have to look quite closely, at the words like "Themes", zoom in quite far, but this makes a difference when rendered on a screen at normal size
– cat
7 hours ago
add a comment |
Since Ubuntu 18.04 (maybe from 17.10, I can't remember), some languages' font hinting are lost in Chrome-like browsers (like Chromium, Bangla, ... ). Also, Chrome's UI font itself renders so bad that the use of Chromium on Ubuntu became impossible.
Interestingly, all Ubuntu derivatives inherited this bug but other distros like Manjaro don't show this behaviour.
Below is a screenshot demonstrating the problem: the text of "Autofill" and "Appearance" becomes fuzzy (Click on both of the images for a full-size image)
Below a screenshot of the expected behaviour:
What's an easy fix to this issue?
18.04 fonts 19.04
edited 9 hours ago
Fabby
27.1k1360161
asked 12 hours ago
AnwarAnwar
57.4k22149255
Since Ubuntu 18.04 (maybe from 17.10, I can't remember), some languages' font hinting are lost in Chrome-like browsers (like Chromium, Bangla, ... ). Also, Chrome's UI font itself renders so bad that the use of Chromium on Ubuntu became impossible.
Interestingly, all Ubuntu derivatives inherited this bug but other distros like Manjaro don't show this behaviour.
Below is a screenshot demonstrating the problem: the text of "Autofill" and "Appearance" becomes fuzzy (Click on both of the images for a full-size image)
Below a screenshot of the expected behaviour:
What's an easy fix to this issue?
18.04 fonts 19.04
18.04 fonts 19.04
edited 9 hours ago
Fabby
27.1k1360161
asked 12 hours ago
AnwarAnwar
57.4k22149255
edited 9 hours ago
Fabby
27.1k1360161
asked 12 hours ago
AnwarAnwar
57.4k22149255
edited 9 hours ago
Fabby
27.1k1360161
edited 9 hours ago
Fabby
27.1k1360161
edited 9 hours ago
Fabby
27.1k1360161
27.1k1360161
asked 12 hours ago
AnwarAnwar
57.4k22149255
asked 12 hours ago
AnwarAnwar
57.4k22149255
asked 12 hours ago
AnwarAnwar
57.4k22149255
57.4k22149255
There's a difference?
– Sean
7 hours ago
1
@Sean you have to look quite closely, at the words like "Themes", zoom in quite far, but this makes a difference when rendered on a screen at normal size
– cat
7 hours ago
add a comment |
There's a difference?
– Sean
7 hours ago
1
@Sean you have to look quite closely, at the words like "Themes", zoom in quite far, but this makes a difference when rendered on a screen at normal size
– cat
7 hours ago
There's a difference?
– Sean
7 hours ago
There's a difference?
– Sean
7 hours ago
1
1
@Sean you have to look quite closely, at the words like "Themes", zoom in quite far, but this makes a difference when rendered on a screen at normal size
– cat
7 hours ago
@Sean you have to look quite closely, at the words like "Themes", zoom in quite far, but this makes a difference when rendered on a screen at normal size
– cat
7 hours ago
add a comment |
1 Answer
1
active
oldest
votes
The fix:
sudo nano /etc/fonts/conf.avail/69-language-selector-ja.conf
change on line 8 family to lang
<test qual="all" name="lang" compare="contains">
TL;DR:
I began the test with replacing all Ubuntu *.conf files in the /etc/fonts/conf.d directory with Manjaro's to test whether it was a config bug (I thought it was in the freetype library). New configs worked well. Further investigating revealed that the specific issue is in the /etc/fonts/conf.avail/69-language-selector-ja.conf file. This file had at line 8
<test qual="all" name="family" compare="contains">
which seems to be wrong, since the family was already selected. It should be lang instead. Editing line 8 fixes all the annoyance.
<test qual="all" name="lang" compare="contains">
Hope, it will help some people like me. I filed a bug report in launchpad here. I encourage people to test the bug and click on "This bug affects me" link if this answer helped you.
edited 9 hours ago
Fabby
27.1k1360161
answered 12 hours ago
AnwarAnwar
57.4k22149255
1
Thanks for the suggested fix, Anwar. As I wrote in the bug report, it wouldn't be a proper fix, since it would break the intention with that configuration file. I have proposed another way to modify it, though.
– Gunnar Hjalmarsson
7 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131704%2ffont-hinting-is-lost-in-chrome-like-browsers-for-some-languages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The fix:
sudo nano /etc/fonts/conf.avail/69-language-selector-ja.conf
change on line 8 family to lang
<test qual="all" name="lang" compare="contains">
TL;DR:
I began the test with replacing all Ubuntu *.conf files in the /etc/fonts/conf.d directory with Manjaro's to test whether it was a config bug (I thought it was in the freetype library). New configs worked well. Further investigating revealed that the specific issue is in the /etc/fonts/conf.avail/69-language-selector-ja.conf file. This file had at line 8
<test qual="all" name="family" compare="contains">
which seems to be wrong, since the family was already selected. It should be lang instead. Editing line 8 fixes all the annoyance.
<test qual="all" name="lang" compare="contains">
Hope, it will help some people like me. I filed a bug report in launchpad here. I encourage people to test the bug and click on "This bug affects me" link if this answer helped you.
edited 9 hours ago
Fabby
27.1k1360161
answered 12 hours ago
AnwarAnwar
57.4k22149255
1
Thanks for the suggested fix, Anwar. As I wrote in the bug report, it wouldn't be a proper fix, since it would break the intention with that configuration file. I have proposed another way to modify it, though.
– Gunnar Hjalmarsson
7 hours ago
add a comment |
The fix:
sudo nano /etc/fonts/conf.avail/69-language-selector-ja.conf
change on line 8 family to lang
<test qual="all" name="lang" compare="contains">
TL;DR:
I began the test with replacing all Ubuntu *.conf files in the /etc/fonts/conf.d directory with Manjaro's to test whether it was a config bug (I thought it was in the freetype library). New configs worked well. Further investigating revealed that the specific issue is in the /etc/fonts/conf.avail/69-language-selector-ja.conf file. This file had at line 8
<test qual="all" name="family" compare="contains">
which seems to be wrong, since the family was already selected. It should be lang instead. Editing line 8 fixes all the annoyance.
<test qual="all" name="lang" compare="contains">
Hope, it will help some people like me. I filed a bug report in launchpad here. I encourage people to test the bug and click on "This bug affects me" link if this answer helped you.
edited 9 hours ago
Fabby
27.1k1360161
answered 12 hours ago
AnwarAnwar
57.4k22149255
1
Thanks for the suggested fix, Anwar. As I wrote in the bug report, it wouldn't be a proper fix, since it would break the intention with that configuration file. I have proposed another way to modify it, though.
– Gunnar Hjalmarsson
7 hours ago
add a comment |
The fix:
sudo nano /etc/fonts/conf.avail/69-language-selector-ja.conf
change on line 8 family to lang
<test qual="all" name="lang" compare="contains">
TL;DR:
I began the test with replacing all Ubuntu *.conf files in the /etc/fonts/conf.d directory with Manjaro's to test whether it was a config bug (I thought it was in the freetype library). New configs worked well. Further investigating revealed that the specific issue is in the /etc/fonts/conf.avail/69-language-selector-ja.conf file. This file had at line 8
<test qual="all" name="family" compare="contains">
which seems to be wrong, since the family was already selected. It should be lang instead. Editing line 8 fixes all the annoyance.
<test qual="all" name="lang" compare="contains">
Hope, it will help some people like me. I filed a bug report in launchpad here. I encourage people to test the bug and click on "This bug affects me" link if this answer helped you.
edited 9 hours ago
Fabby
27.1k1360161
answered 12 hours ago
AnwarAnwar
57.4k22149255
The fix:
sudo nano /etc/fonts/conf.avail/69-language-selector-ja.conf
change on line 8 family to lang
<test qual="all" name="lang" compare="contains">
TL;DR:
I began the test with replacing all Ubuntu *.conf files in the /etc/fonts/conf.d directory with Manjaro's to test whether it was a config bug (I thought it was in the freetype library). New configs worked well. Further investigating revealed that the specific issue is in the /etc/fonts/conf.avail/69-language-selector-ja.conf file. This file had at line 8
<test qual="all" name="family" compare="contains">
which seems to be wrong, since the family was already selected. It should be lang instead. Editing line 8 fixes all the annoyance.
<test qual="all" name="lang" compare="contains">
Hope, it will help some people like me. I filed a bug report in launchpad here. I encourage people to test the bug and click on "This bug affects me" link if this answer helped you.
edited 9 hours ago
Fabby
27.1k1360161
answered 12 hours ago
AnwarAnwar
57.4k22149255
edited 9 hours ago
Fabby
27.1k1360161
edited 9 hours ago
Fabby
27.1k1360161
edited 9 hours ago
Fabby
27.1k1360161
27.1k1360161
answered 12 hours ago
AnwarAnwar
57.4k22149255
answered 12 hours ago
AnwarAnwar
57.4k22149255
answered 12 hours ago
AnwarAnwar
57.4k22149255
57.4k22149255
1
Thanks for the suggested fix, Anwar. As I wrote in the bug report, it wouldn't be a proper fix, since it would break the intention with that configuration file. I have proposed another way to modify it, though.
– Gunnar Hjalmarsson
7 hours ago
add a comment |
1
Thanks for the suggested fix, Anwar. As I wrote in the bug report, it wouldn't be a proper fix, since it would break the intention with that configuration file. I have proposed another way to modify it, though.
– Gunnar Hjalmarsson
7 hours ago
1
1
Thanks for the suggested fix, Anwar. As I wrote in the bug report, it wouldn't be a proper fix, since it would break the intention with that configuration file. I have proposed another way to modify it, though.
– Gunnar Hjalmarsson
7 hours ago
Thanks for the suggested fix, Anwar. As I wrote in the bug report, it wouldn't be a proper fix, since it would break the intention with that configuration file. I have proposed another way to modify it, though.
– Gunnar Hjalmarsson
7 hours ago
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131704%2ffont-hinting-is-lost-in-chrome-like-browsers-for-some-languages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There's a difference?
– Sean
7 hours ago
1
@Sean you have to look quite closely, at the words like "Themes", zoom in quite far, but this makes a difference when rendered on a screen at normal size
– cat
7 hours ago