Stopping ligatures in konsole
After upgrading to Fedora 29 konsole has started to use ligatures for my monowidth fonts (currently Inconsolata), which is beyond terrible for example when it decides to combine "fi". I have futzed with fontconfig tweaks like the following, to no avail:
$ cat ~/.config/fontconfig/fonts.conf
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<description>Disable ligatures for monospaced fonts to avoid ff, fi, ffi, etc. becoming only one character wide</description>
<match target="font">
<test name="family" compare="contains" ignore-blanks="true">
<string>Inconsolata</string>
</test>
<edit name="fontfeatures" mode="append">
<string>liga off</string>
<string>dlig off</string>
</edit>
</match>
</fontconfig>
I can work around it by switching fonts, but this behavior is just unhelpful. How do I properly prevent konsole from using any kind of ligatures for my fonts?
fedora fonts kde konsole fontconfig
asked Dec 14 '18 at 19:30
ChristianChristian
1162
add a comment |
After upgrading to Fedora 29 konsole has started to use ligatures for my monowidth fonts (currently Inconsolata), which is beyond terrible for example when it decides to combine "fi". I have futzed with fontconfig tweaks like the following, to no avail:
$ cat ~/.config/fontconfig/fonts.conf
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<description>Disable ligatures for monospaced fonts to avoid ff, fi, ffi, etc. becoming only one character wide</description>
<match target="font">
<test name="family" compare="contains" ignore-blanks="true">
<string>Inconsolata</string>
</test>
<edit name="fontfeatures" mode="append">
<string>liga off</string>
<string>dlig off</string>
</edit>
</match>
</fontconfig>
I can work around it by switching fonts, but this behavior is just unhelpful. How do I properly prevent konsole from using any kind of ligatures for my fonts?
fedora fonts kde konsole fontconfig
asked Dec 14 '18 at 19:30
ChristianChristian
1162
Fyi, by now I've figured out that there were two sources at play for the Inconsolata font (fontforge and levien-inconsolata-fonts), and in the latter the font wasn't marked as a monospace one. Still, I am puzzled as to why the fontconfig tweak shown above didn't work.
– Christian
Dec 18 '18 at 18:12
add a comment |
After upgrading to Fedora 29 konsole has started to use ligatures for my monowidth fonts (currently Inconsolata), which is beyond terrible for example when it decides to combine "fi". I have futzed with fontconfig tweaks like the following, to no avail:
$ cat ~/.config/fontconfig/fonts.conf
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<description>Disable ligatures for monospaced fonts to avoid ff, fi, ffi, etc. becoming only one character wide</description>
<match target="font">
<test name="family" compare="contains" ignore-blanks="true">
<string>Inconsolata</string>
</test>
<edit name="fontfeatures" mode="append">
<string>liga off</string>
<string>dlig off</string>
</edit>
</match>
</fontconfig>
I can work around it by switching fonts, but this behavior is just unhelpful. How do I properly prevent konsole from using any kind of ligatures for my fonts?
fedora fonts kde konsole fontconfig
asked Dec 14 '18 at 19:30
ChristianChristian
1162
After upgrading to Fedora 29 konsole has started to use ligatures for my monowidth fonts (currently Inconsolata), which is beyond terrible for example when it decides to combine "fi". I have futzed with fontconfig tweaks like the following, to no avail:
$ cat ~/.config/fontconfig/fonts.conf
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<description>Disable ligatures for monospaced fonts to avoid ff, fi, ffi, etc. becoming only one character wide</description>
<match target="font">
<test name="family" compare="contains" ignore-blanks="true">
<string>Inconsolata</string>
</test>
<edit name="fontfeatures" mode="append">
<string>liga off</string>
<string>dlig off</string>
</edit>
</match>
</fontconfig>
I can work around it by switching fonts, but this behavior is just unhelpful. How do I properly prevent konsole from using any kind of ligatures for my fonts?
fedora fonts kde konsole fontconfig
fedora fonts kde konsole fontconfig
asked Dec 14 '18 at 19:30
ChristianChristian
1162
asked Dec 14 '18 at 19:30
ChristianChristian
1162
asked Dec 14 '18 at 19:30
ChristianChristian
1162
asked Dec 14 '18 at 19:30
ChristianChristian
1162
asked Dec 14 '18 at 19:30
ChristianChristian
1162
1162
Fyi, by now I've figured out that there were two sources at play for the Inconsolata font (fontforge and levien-inconsolata-fonts), and in the latter the font wasn't marked as a monospace one. Still, I am puzzled as to why the fontconfig tweak shown above didn't work.
– Christian
Dec 18 '18 at 18:12
add a comment |
Fyi, by now I've figured out that there were two sources at play for the Inconsolata font (fontforge and levien-inconsolata-fonts), and in the latter the font wasn't marked as a monospace one. Still, I am puzzled as to why the fontconfig tweak shown above didn't work.
– Christian
Dec 18 '18 at 18:12
Fyi, by now I've figured out that there were two sources at play for the Inconsolata font (fontforge and levien-inconsolata-fonts), and in the latter the font wasn't marked as a monospace one. Still, I am puzzled as to why the fontconfig tweak shown above didn't work.
– Christian
Dec 18 '18 at 18:12
Fyi, by now I've figured out that there were two sources at play for the Inconsolata font (fontforge and levien-inconsolata-fonts), and in the latter the font wasn't marked as a monospace one. Still, I am puzzled as to why the fontconfig tweak shown above didn't work.
– Christian
Dec 18 '18 at 18:12
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1383667%2fstopping-ligatures-in-konsole%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1383667%2fstopping-ligatures-in-konsole%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
Fyi, by now I've figured out that there were two sources at play for the Inconsolata font (fontforge and levien-inconsolata-fonts), and in the latter the font wasn't marked as a monospace one. Still, I am puzzled as to why the fontconfig tweak shown above didn't work.
– Christian
Dec 18 '18 at 18:12