Wine anti aliasing doesn't work
I'm using infinality for my font rendering on my Arch machine. (And yes, I've installed the multilib packages.) My fonts are beautiful everywhere except in Wine since anti aliasing does not work out of the box.
I've found a fix here: I have to run xrdb -query | grep -vE 'Xft.(anti|hint|rgba)' | xrdb in the terminal and then anti aliasing works. There are 3 reasons I'm not satisfied with this solution:
- It's not permanent. I have to run this command every time I restart my pc.
- It's hacky.
- I have no idea what this is doing. I'd like to understand what's going on.
If anyone can give me a solution that fixes anti aliasing and meets at least some of my requirements I would really appreciate it.
fonts wine
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm using infinality for my font rendering on my Arch machine. (And yes, I've installed the multilib packages.) My fonts are beautiful everywhere except in Wine since anti aliasing does not work out of the box.
I've found a fix here: I have to run xrdb -query | grep -vE 'Xft.(anti|hint|rgba)' | xrdb in the terminal and then anti aliasing works. There are 3 reasons I'm not satisfied with this solution:
- It's not permanent. I have to run this command every time I restart my pc.
- It's hacky.
- I have no idea what this is doing. I'd like to understand what's going on.
If anyone can give me a solution that fixes anti aliasing and meets at least some of my requirements I would really appreciate it.
fonts wine
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm using infinality for my font rendering on my Arch machine. (And yes, I've installed the multilib packages.) My fonts are beautiful everywhere except in Wine since anti aliasing does not work out of the box.
I've found a fix here: I have to run xrdb -query | grep -vE 'Xft.(anti|hint|rgba)' | xrdb in the terminal and then anti aliasing works. There are 3 reasons I'm not satisfied with this solution:
- It's not permanent. I have to run this command every time I restart my pc.
- It's hacky.
- I have no idea what this is doing. I'd like to understand what's going on.
If anyone can give me a solution that fixes anti aliasing and meets at least some of my requirements I would really appreciate it.
fonts wine
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
I'm using infinality for my font rendering on my Arch machine. (And yes, I've installed the multilib packages.) My fonts are beautiful everywhere except in Wine since anti aliasing does not work out of the box.
I've found a fix here: I have to run xrdb -query | grep -vE 'Xft.(anti|hint|rgba)' | xrdb in the terminal and then anti aliasing works. There are 3 reasons I'm not satisfied with this solution:
- It's not permanent. I have to run this command every time I restart my pc.
- It's hacky.
- I have no idea what this is doing. I'd like to understand what's going on.
If anyone can give me a solution that fixes anti aliasing and meets at least some of my requirements I would really appreciate it.
fonts wine
fonts wine
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
asked Jul 5 '15 at 8:04
Wietse de VriesWietse de Vries
1334
1334
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 10 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Why does the xrdb command fix font smoothing?
xrdb manages X resources.
xrdb -query lists currently loaded resources.
Piping that to grep -vE 'Xft.(anti|hint|rgba)' filters out resources containing "anti", "hint" or "rgba".
Finally the filtered list is piped back to xrdb, which by default will overwrite any existing settings.
So this has the effect of removing any X settings to do with antialiasing, hinting, or rgba smoothing. This means at some point those values are being set to something you don't want, because the defaults are fixing the problem.
How can we permanently fix this?
How the values are set depends entirely on how you start your session. Often startup scripts will load them from ~/.Xresources, so you can try putting the filtered output in there.
In my case I use Xfce and to get the correct values to stick I had to set them within xfconf. That can be done graphically (xfce4-settings-editor, navigate to xsettings), or from the terminal, e.g. to set RGBA smoothing correctly:
xfconf-query -c xsettings -p /Xft/RGBA -s "rgb".
Also see the Arch wiki page on X resources.
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f213953%2fwine-anti-aliasing-doesnt-work%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
Why does the xrdb command fix font smoothing?
xrdb manages X resources.
xrdb -query lists currently loaded resources.
Piping that to grep -vE 'Xft.(anti|hint|rgba)' filters out resources containing "anti", "hint" or "rgba".
Finally the filtered list is piped back to xrdb, which by default will overwrite any existing settings.
So this has the effect of removing any X settings to do with antialiasing, hinting, or rgba smoothing. This means at some point those values are being set to something you don't want, because the defaults are fixing the problem.
How can we permanently fix this?
How the values are set depends entirely on how you start your session. Often startup scripts will load them from ~/.Xresources, so you can try putting the filtered output in there.
In my case I use Xfce and to get the correct values to stick I had to set them within xfconf. That can be done graphically (xfce4-settings-editor, navigate to xsettings), or from the terminal, e.g. to set RGBA smoothing correctly:
xfconf-query -c xsettings -p /Xft/RGBA -s "rgb".
Also see the Arch wiki page on X resources.
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
add a comment |
Why does the xrdb command fix font smoothing?
xrdb manages X resources.
xrdb -query lists currently loaded resources.
Piping that to grep -vE 'Xft.(anti|hint|rgba)' filters out resources containing "anti", "hint" or "rgba".
Finally the filtered list is piped back to xrdb, which by default will overwrite any existing settings.
So this has the effect of removing any X settings to do with antialiasing, hinting, or rgba smoothing. This means at some point those values are being set to something you don't want, because the defaults are fixing the problem.
How can we permanently fix this?
How the values are set depends entirely on how you start your session. Often startup scripts will load them from ~/.Xresources, so you can try putting the filtered output in there.
In my case I use Xfce and to get the correct values to stick I had to set them within xfconf. That can be done graphically (xfce4-settings-editor, navigate to xsettings), or from the terminal, e.g. to set RGBA smoothing correctly:
xfconf-query -c xsettings -p /Xft/RGBA -s "rgb".
Also see the Arch wiki page on X resources.
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
add a comment |
Why does the xrdb command fix font smoothing?
xrdb manages X resources.
xrdb -query lists currently loaded resources.
Piping that to grep -vE 'Xft.(anti|hint|rgba)' filters out resources containing "anti", "hint" or "rgba".
Finally the filtered list is piped back to xrdb, which by default will overwrite any existing settings.
So this has the effect of removing any X settings to do with antialiasing, hinting, or rgba smoothing. This means at some point those values are being set to something you don't want, because the defaults are fixing the problem.
How can we permanently fix this?
How the values are set depends entirely on how you start your session. Often startup scripts will load them from ~/.Xresources, so you can try putting the filtered output in there.
In my case I use Xfce and to get the correct values to stick I had to set them within xfconf. That can be done graphically (xfce4-settings-editor, navigate to xsettings), or from the terminal, e.g. to set RGBA smoothing correctly:
xfconf-query -c xsettings -p /Xft/RGBA -s "rgb".
Also see the Arch wiki page on X resources.
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
Why does the xrdb command fix font smoothing?
xrdb manages X resources.
xrdb -query lists currently loaded resources.
Piping that to grep -vE 'Xft.(anti|hint|rgba)' filters out resources containing "anti", "hint" or "rgba".
Finally the filtered list is piped back to xrdb, which by default will overwrite any existing settings.
So this has the effect of removing any X settings to do with antialiasing, hinting, or rgba smoothing. This means at some point those values are being set to something you don't want, because the defaults are fixing the problem.
How can we permanently fix this?
How the values are set depends entirely on how you start your session. Often startup scripts will load them from ~/.Xresources, so you can try putting the filtered output in there.
In my case I use Xfce and to get the correct values to stick I had to set them within xfconf. That can be done graphically (xfce4-settings-editor, navigate to xsettings), or from the terminal, e.g. to set RGBA smoothing correctly:
xfconf-query -c xsettings -p /Xft/RGBA -s "rgb".
Also see the Arch wiki page on X resources.
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
answered Nov 8 '16 at 6:32
John SalamonJohn Salamon
12
12
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f213953%2fwine-anti-aliasing-doesnt-work%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
