Konsole and other applications render FontBureau's âInput Monoâ as proportional
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
In KDE's Konsole, when using a custom build of FontBureau's "Input Mono" font, things are rendered as though the fonts are proportional. This causes no end of problems, as Konsole isn't prepared to handle proportional fonts. The most obvious problem is that the cursor position frequently is incorrect.
For example, the first line of "|" and the line of "M" should be same width, but they aren't. The cursor on the bottom line should be at the very end of the second line of "|", but there is a gap.
It should look like this:
fonts konsole fontconfig
add a comment |Â
up vote
0
down vote
favorite
In KDE's Konsole, when using a custom build of FontBureau's "Input Mono" font, things are rendered as though the fonts are proportional. This causes no end of problems, as Konsole isn't prepared to handle proportional fonts. The most obvious problem is that the cursor position frequently is incorrect.
For example, the first line of "|" and the line of "M" should be same width, but they aren't. The cursor on the bottom line should be at the very end of the second line of "|", but there is a gap.
It should look like this:
fonts konsole fontconfig
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In KDE's Konsole, when using a custom build of FontBureau's "Input Mono" font, things are rendered as though the fonts are proportional. This causes no end of problems, as Konsole isn't prepared to handle proportional fonts. The most obvious problem is that the cursor position frequently is incorrect.
For example, the first line of "|" and the line of "M" should be same width, but they aren't. The cursor on the bottom line should be at the very end of the second line of "|", but there is a gap.
It should look like this:
fonts konsole fontconfig
In KDE's Konsole, when using a custom build of FontBureau's "Input Mono" font, things are rendered as though the fonts are proportional. This causes no end of problems, as Konsole isn't prepared to handle proportional fonts. The most obvious problem is that the cursor position frequently is incorrect.
For example, the first line of "|" and the line of "M" should be same width, but they aren't. The cursor on the bottom line should be at the very end of the second line of "|", but there is a gap.
It should look like this:
fonts konsole fontconfig
asked Jun 26 at 16:21
Alan De Smet
1286
1286
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
The problem has several parts:
- If you're using a custom version, either customized on the FontBureau web site or using the provided
inputCustomize.py
, the resulting fonts have a family name of "Input", not "Input Mono" as one might expect. - Downloads include the "template" fonts, which the customization tool can use to create new custom versions. These template fonts can be found in
Scripts/_template_*.txt
. They also have a family name of "Input". They are (kinda of?) proportional, and not intended for direct use. - I unzipped the entire contents of the
Input_Font.zip
file into my font directory. - fontconfig can find fonts even if they have unusual extensions, including
.txt
.
When fontconfig rebuilt the cache with the Input fonts it found the template fonts in addition to my custom build. It ended up choosing the template fonts over my monospace custom version. So Konsole seemed to be using proportional fonts because it was!
This is also why the two screenshots above are more different than just widths; the correct version looks distinctly lighter. It is, because it's a different font.
The easy fix is to delete the Scripts
directory, or otherwise modify the template files so fontconfig doesn't recognize them. I did this:
$ cd Scripts
$ find -name '*.txt' -print0 | xargs -0 gzip
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
The problem has several parts:
- If you're using a custom version, either customized on the FontBureau web site or using the provided
inputCustomize.py
, the resulting fonts have a family name of "Input", not "Input Mono" as one might expect. - Downloads include the "template" fonts, which the customization tool can use to create new custom versions. These template fonts can be found in
Scripts/_template_*.txt
. They also have a family name of "Input". They are (kinda of?) proportional, and not intended for direct use. - I unzipped the entire contents of the
Input_Font.zip
file into my font directory. - fontconfig can find fonts even if they have unusual extensions, including
.txt
.
When fontconfig rebuilt the cache with the Input fonts it found the template fonts in addition to my custom build. It ended up choosing the template fonts over my monospace custom version. So Konsole seemed to be using proportional fonts because it was!
This is also why the two screenshots above are more different than just widths; the correct version looks distinctly lighter. It is, because it's a different font.
The easy fix is to delete the Scripts
directory, or otherwise modify the template files so fontconfig doesn't recognize them. I did this:
$ cd Scripts
$ find -name '*.txt' -print0 | xargs -0 gzip
add a comment |Â
up vote
1
down vote
accepted
The problem has several parts:
- If you're using a custom version, either customized on the FontBureau web site or using the provided
inputCustomize.py
, the resulting fonts have a family name of "Input", not "Input Mono" as one might expect. - Downloads include the "template" fonts, which the customization tool can use to create new custom versions. These template fonts can be found in
Scripts/_template_*.txt
. They also have a family name of "Input". They are (kinda of?) proportional, and not intended for direct use. - I unzipped the entire contents of the
Input_Font.zip
file into my font directory. - fontconfig can find fonts even if they have unusual extensions, including
.txt
.
When fontconfig rebuilt the cache with the Input fonts it found the template fonts in addition to my custom build. It ended up choosing the template fonts over my monospace custom version. So Konsole seemed to be using proportional fonts because it was!
This is also why the two screenshots above are more different than just widths; the correct version looks distinctly lighter. It is, because it's a different font.
The easy fix is to delete the Scripts
directory, or otherwise modify the template files so fontconfig doesn't recognize them. I did this:
$ cd Scripts
$ find -name '*.txt' -print0 | xargs -0 gzip
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
The problem has several parts:
- If you're using a custom version, either customized on the FontBureau web site or using the provided
inputCustomize.py
, the resulting fonts have a family name of "Input", not "Input Mono" as one might expect. - Downloads include the "template" fonts, which the customization tool can use to create new custom versions. These template fonts can be found in
Scripts/_template_*.txt
. They also have a family name of "Input". They are (kinda of?) proportional, and not intended for direct use. - I unzipped the entire contents of the
Input_Font.zip
file into my font directory. - fontconfig can find fonts even if they have unusual extensions, including
.txt
.
When fontconfig rebuilt the cache with the Input fonts it found the template fonts in addition to my custom build. It ended up choosing the template fonts over my monospace custom version. So Konsole seemed to be using proportional fonts because it was!
This is also why the two screenshots above are more different than just widths; the correct version looks distinctly lighter. It is, because it's a different font.
The easy fix is to delete the Scripts
directory, or otherwise modify the template files so fontconfig doesn't recognize them. I did this:
$ cd Scripts
$ find -name '*.txt' -print0 | xargs -0 gzip
The problem has several parts:
- If you're using a custom version, either customized on the FontBureau web site or using the provided
inputCustomize.py
, the resulting fonts have a family name of "Input", not "Input Mono" as one might expect. - Downloads include the "template" fonts, which the customization tool can use to create new custom versions. These template fonts can be found in
Scripts/_template_*.txt
. They also have a family name of "Input". They are (kinda of?) proportional, and not intended for direct use. - I unzipped the entire contents of the
Input_Font.zip
file into my font directory. - fontconfig can find fonts even if they have unusual extensions, including
.txt
.
When fontconfig rebuilt the cache with the Input fonts it found the template fonts in addition to my custom build. It ended up choosing the template fonts over my monospace custom version. So Konsole seemed to be using proportional fonts because it was!
This is also why the two screenshots above are more different than just widths; the correct version looks distinctly lighter. It is, because it's a different font.
The easy fix is to delete the Scripts
directory, or otherwise modify the template files so fontconfig doesn't recognize them. I did this:
$ cd Scripts
$ find -name '*.txt' -print0 | xargs -0 gzip
answered Jun 26 at 16:21
Alan De Smet
1286
1286
add a comment |Â
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f452052%2fkonsole-and-other-applications-render-fontbureaus-input-mono-as-proportional%23new-answer', 'question_page');
);
Post as a guest
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
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
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