infinality-bundle: good looking fonts made (even) easier

bohoomil · 2014-11-04 18:18:46

@frabjous Thanks. Delete this stale, broken link and fc-presets should work correctly again.

93-final-lang-spec-free.conf -> ../conf.avail.infinality/free/93-final-lang-spec-free.conf

frabjous · 2014-11-05 00:14:31

bohoomil wrote:

@frabjous Thanks. Delete this stale, broken link and fc-presets should work correctly again.

Worked like a charm. Thanks again!

GordonGR · 2014-11-05 11:30:35

Thank you for the great work Boohoomil.

I'm having a small issue myself, ever since two or three updates ago. Dejavu sans mono size 14 under Geany doesn't show the undescore. Every other combination works. Example:
https://dl.dropboxusercontent.com/u/4361965/14.png
https://dl.dropboxusercontent.com/u/4361965/15.png

Everything is stock, I haven't messed with anything.

It's not realy important, but still help would be appreciated.

bohoomil · 2014-11-05 19:09:39

@GordonGR It seems to be a bug, or better yet: a buggy combination of an application and a typeface. I'm not sure if freetype2-iu has anything to do with it, though (other Gtk+ apps work fine with DejaVu Sans Mono 14px).

I've been thinking about packaging Meslo for a while. Like Menlo, it fixes several annoying DejaVu Sans Mono issues (the missing underscore in Geany being one of them), is licensed under Apache 2.0 and can be used as a fully compatible alternative to DejaVu. I'll try and upload it later tonight.

bohoomil · 2014-11-06 00:07:53

to whom it may concern Please, take a look at these four previews -- DejaVu Sans Mono / Menlo / Meslo -- and decide if you will benefit from adding Meslo to the repository.

Menlo's upsides

1. It eliminates several problems known from DejaVu Sans Mono and sometimes still present in Menlo (e.g. missing umlauts, underscores, badly aligned diacritics, etc.).
2. It works very well with stand-alone text editors and (presumably) IDEs. It's distinct, legible and well-suited to coding jobs.

Meslo's main downsides

1. Meslo needs to be used with autohinter in order to look fine. Disabling it for particular heights or applying it selectively introduces visible glitches to certain characters and groups of letters. Autohinter shrinks the font a bit vertically, too (the effect isn't drastic, though).
2. Due to the differences in vertical spacing (which is considered a feature), it may not be a good match for terminal emulators since it affects window width/height ratio. For example, for geometry 90x40, Meslo creates a window 722x842, while Menlo and DejaVu Sans Mono about 1/4 shorter, 722x602. Consequently, it won't be useful as a UI font (dmenu et al.).

The bottom line

Meslo is a good font, although a bit idiosyncratic (see the line height). It has its limitations which restrict its usability. However, in certain applications it can be a right choice. I'm rather selective when it comes to packaging font forks, but as there's no better free alternative to Menlo (which would be definitely the best choice), and DejaVu Sans Mono flaws can't be easily fixed, it may be a right option for some.

And now let me know what you think. :-)

GordonGR · 2014-11-06 13:58:28

Looks good here; there is Extended Greek, which isn't the case with all good mono fonts (alas…). And the underscore works in Geany :-) So I say go for it.

Thanks, Boohomil, you're the font wizard :-)

xorgx3 · 2014-11-06 22:09:57

Hi,
Can I still set something like decribed here: http://www.webupd8.org/2013/06/better-f … -with.html
I mean these styles:

DEFAULT - A compromise that should please most people;
OSX - Simulate OSX rendering;
IPAD - Simulate iPad rendering;
UBUNTU - Simulate Ubuntu rendering;
LINUX - Generic "Linux" style - no snapping or certain other tweaks;
WINDOWS - Simulate Windows rendering;
WINDOWS7 - Simulate Windows rendering with normal glyphs;
WINDOWS7LIGHT- Simulate Windows 7 rendering with lighter glyphs;
WINDOWS - Simulate Windows rendering;
VANILLA - Just subpixel hinting;
CUSTOM - Your own choice;

or only i can do

# fc-presets set

and this is enough?

and another question:
this is the right arial look: http://imgur.com/nb7YVN8 ?
imo is too big and just ugly compare to other fonts.

Last edited by xorgx3 (2014-11-06 23:01:05)

bohoomil · 2014-11-07 00:13:36

@xorgx3 Here is one of many available answers why Arial & Times NR are different in height. Note that the reference OS is MS Windows there, not Linux with freetype2 & Infinality. Briefly: the reason why this happens isn't the rendering back end, but structural differences between those two fonts.

Using a different freetype2/Infinality configuration file with freetype2-iu has always been possible. You just have to remember to set the 'rendering style' of your choice manually in infinality-settings.sh. Then you have to choose a font collection with fc-presets: this step will let you use your favourite fonts as main aliases (i.e. sans-serif, serif, monospace, etc.) and, when needed replace a bunch of typefaces.

Sometimes, when you use a custom infinality-settings.sh file, it may be necessary to alter rendering instructions for particular fonts: the ultimate collection simply 'pairs' font packages with freetype settings in order to get the most out of them and make them instantly ready to use. This isn't an obligatory action, though.

Last edited by bohoomil (2014-11-07 00:14:39)

aphirst · 2014-11-07 20:55:27

aphirst wrote:

Zanshi wrote:
@zainin
I'm having an issue really similar to yours. mpv crashes when watching videos with heavy use of embedded .ass fonts. I've tried using the mpv package in the community repo as well as the mpv-build-git package in the AUR. I've also tried both libass and libass-git.
mpv crashes with everything. I'm using infinality-bundle, infinality-bundle-multilib, ibfonts-meta-base and ibfonts-meta-extended.
It works just fine with the regular fontconfig packages.
Error log from playing a file that causes a crash:
[statusline] AV: 00:00:24 / 00:22:54 (1%) A-V:  0.000 Cache:  2s+37058KB
[libass] fontconfig: cannot find font 'Franklin Gothic Book', falling back to 'Noto Sans'
[statusline] AV: 00:00:32 / 00:22:54 (2%) A-V:  0.000 Cache:  2s+33553KB
[libass] Glyph bounding box too large: 33554442x33554454px
[libass] Glyph bounding box too large: 33554445x33554457px
I am experiencing similar behaviour to Zanshi regarding libass, except rather than crashing, mpv+libass-git simply mis-renders some characters, and printing the same sort of 'glyph bounding box too large' errors. An affected file can be found here, with a screenshot demonstrating the error here. A verbose mpv log can be found here.
I'm using:
freetype2-infinality-ultimate 2.5.3-12
fontconfig-infinality-ultimate 2.11.1-20
libass-git 0.11.2.37.gcad1cae-1
mpv 0.5.4-1
Since this only occurred in freetype2-infinality -10 and later according to some people in Freenode #libass (I myself simply didn't encounter any affected files until after I upgraded, presumably just by coincidence), I am led to believe that the underlying issue here is with infinality; but obviously I do not know for sure.

Just thought I'd ping back on this issue, as it's still present for me.

infinality-bundle/fontconfig-infinality-ultimate 2.11.1-22 (infinality-bundle)
infinality-bundle/freetype2-infinality-ultimate 2.5.3-14 (infinality-bundle)
community/mpv 0.6.2-1
local/libass-git 0.12.0.5.ga31ea56-1

[statusline] AV: 00:00:00 / 00:01:31 (0%) A-V: -0.000
[libass] Glyph bounding box too large: 34x33554455px
[libass] Glyph bounding box too large: 33x33554455px
[libass] Glyph bounding box too large: 30x33554452px
[libass] Glyph bounding box too large: 30x33554452px

I brought this up again over in #libass, and the devs remain convinced this is the fault of infinality somehow. If there's any additional information I've neglected to mention which would be useful, please just ask.

bohoomil · 2014-11-07 21:30:36

@aphirst Would you mind opening an issue on GitHub? Here it will always get lost under a pile of new posts. Thank you.

aphirst · 2014-11-07 21:56:49

bohoomil wrote:

@aphirst Would you mind opening an issue on GitHub? Here it will always get lost under a pile of new posts. Thank you.

Done, assuming I went to the right place.

athrun · 2014-11-09 23:40:28

thanks, bohoomil.

 freetype-config --version
17.2.11

It's no 2.5.3?

Bakaookami · 2014-11-10 02:07:54

bohoomil, can you update the Noto fonts? In the new release they are renamed. (Noto Sans S Chinese -> Noto Sans CJK SC)
If I want to use the same files in Windows and Linux I always have to change the fonts around.

knightzx · 2014-11-10 04:13:16

I have a SIGSEGV when playing some file in mpv
Turn out, freetype2-iu can't render fonts in this sample file
The font is 'Moon font-PRO'
It works with freetype2 from official repos, though
It works with mplayer and freetype2-iu, does mpv somehow render things differently?

freetype2-infinality-ultimate 2.5.3-14
mpv 0.6.2-1

bohoomil · 2014-11-10 05:08:54

@athrun You're welcome. This is the version of the `freetype-config` utility, not the entire package.

@Bakaookami Done & sorry for the delay.

@knightzx I'm using only mpv from [community] and the file plays fine: the subtitles are rendered with both embedded fonts (moonp.ttf & take_out_the_garbage.ttf) and the player doesn't crash. That's odd because some people reported problems with subtitles, we have a bug report opened, and now that I'm able to test the case myself for the first time, I can't reproduce the issue… Could you please share your mpv config file? Maybe the problems affects only certain video drivers or subs settings?

hcra · 2014-11-10 05:42:48

I've used freetype2-infinality from the AUR for quite some time, and today, I came to realize what I've been missing. I installed bohoomil's infinality-bundle along with his excellent fonts (over the top of freetype2-infinality). Everything seems to be working fine, but I'm wondering:

Should I make any other changes after switching from freetype2-infinality to infinality-bundle?

Also, I use Aura as my AUR package helper. I wonder if I should remove/delete anything to keep the old packages from messing with the bundle, if the freetype packages get updated?

I did find one forum post noting to "manually delete infinality-settings.sh.pacsave as it is not needed anymore." Anything else? Thanks so much!

[Edit] After looking closely at the aura log, I discovered that installing infinality-bundle automatically removes freetype2-infinality and cleans up duplicate fonts and settings. My hat's off to bohoomil. Not only do I have a fabulous looking display, but the package code is superbly written. Nice, nice, nice! Thanks so much!!

Last edited by hcra (2014-11-13 02:41:12)

knightzx · 2014-11-10 06:11:04

bohoomil wrote:

@knightzx I'm using only mpv from [community] and the file plays fine: the subtitles are rendered with both embedded fonts (moonp.ttf & take_out_the_garbage.ttf) and the player doesn't crash. That's odd because some people reported problems with subtitles, we have a bug report opened, and now that I'm able to test the case myself for the first time, I can't reproduce the issue… Could you please share your mpv config file? Maybe the problems affects only certain video drivers or subs settings?

I notice it's only crash when using mpv with option --vo=opengl or opengl-hq. It works fine when using --vo=xv
My config file only contains

ao=alsa
vo=opengl-hq

I'm using nvidia-340xx from the repo

orschiro · 2014-11-10 07:00:54

Is the recent Noto Sans update really as that big?

Packages (4): ttf-noto-sans-ib-2014.11-1  ttf-noto-sans-multilang-ib-2014.11-1  ttf-noto-serif-ib-2014.11-1  ttf-noto-serif-multilang-ib-2014.11-1

Total Download Size:    275.45 MiB
Total Installed Size:   449.18 MiB
Net Upgrade Size:       284.44 MiB

:: Proceed with installation? [Y/n]

3xOSC · 2014-11-10 12:32:20

I've recently installed infinality bundle using the repository method and emptied out my ~/.config/fontconfig dir since I heard that that wasn't needed anymore.
I then downloaded the font "otf-titillium-ibx" and made sure fc-list and xlsfonts can see it; and they did.

However, when i tried to use this font on my terminal (termite), the font looks squished and like crooked teeth. Is hinting/aliasing turned on?

I checked the /etc/conf.avail.infinality/ and did see the titillium settings in there. Is there something I should do with those files that begin with a number?

Thanks in advance.

frabjous · 2014-11-10 13:13:35

3xOSC wrote:

I've recently installed infinality bundle using the repository method and emptied out my ~/.config/fontconfig dir since I heard that that wasn't needed anymore.
I then downloaded the font "otf-titillium-ibx" and made sure fc-list and xlsfonts can see it; and they did.
However, when i tried to use this font on my terminal (termite), the font looks squished and like crooked teeth. Is hinting/aliasing turned on?
I checked the /etc/conf.avail.infinality/ and did see the titillium settings in there. Is there something I should do with those files that begin with a number?
Thanks in advance.

Terminal emulators are designed to use monospace fonts.Titillium is not a monospace font. Most likely termite is just squishing/stretching the letters to make them all the same width. Better to use a different font.

Bakaookami · 2014-11-10 14:29:10

@bohoomil
Wow, that was fast! Thank you!

sl1pkn07 · 2014-11-10 16:23:57

bohoomil wrote:

@knightzx I'm using only mpv from [community] and the file plays fine: the subtitles are rendered with both embedded fonts (moonp.ttf & take_out_the_garbage.ttf) and the player doesn't crash. That's odd because some people reported problems with subtitles, we have a bug report opened, and now that I'm able to test the case myself for the first time, I can't reproduce the issue… Could you please share your mpv config file? Maybe the problems affects only certain video drivers or subs settings?

i have issues with mpv (git+libass-git+fribidi-git) (mpv-build-git)

when use freetype2-infinality get this coredumped

mpv: ass_rasterizer.c:451: segment_split_vert: Assertion `y > line->y_min && y < line->y_max' failed.

but if use a normal freetype2, the playback continue without any error

the file is this '[Bakari] Haikyuu!! - 01 [D3A845A9].mkv' (found in google)

failed in min 23:09.49

the line is this

Dialogue: 0,0:23:09.49,0:23:17.45,ED,BA,0,0,0,,{\fad(200,200)\blur3}De pie en un campo vacío

Last edited by sl1pkn07 (2014-11-11 00:05:03)

bohoomil · 2014-11-10 22:01:36

Thank you everyone for your feedback.

@hcra This is the 'either/or' question. If you want to use infinality-bundle, you have to remove freetype2-infinality and fontconfig-infinality. Infinality-bundle provides you with everything you need in mutually compatible and optimized packages.

foo.pacsave files are usually meant to be deleted so this one is no exception.

@knightzx, @sl1pkn07 Thanks for additional info. With sl1pkn07's file I can reproduce the crash, but switching video output to xv doesn't prevent it. I'll try to isolate the piece of code in the Infinality patchset which can be responsible for the issue. I do hope a knowledgeable C coder will use her/his skills to assist me in fixing it…

@orschiro Unfortunately, yes: all Noto fonts occupy about 450 MB of HDD space now.

@3xOSC Remember the 2014-10-05 09:05:19? ;-)

Unfortunately, we don't have an easy and obvious way to determine whether a font is monospaced or proportional. You just have to know what the purpose of fonts you're using is. You can try playing with pacman and grep using related keywords ('mono', 'code', etc.) but the results will never be 100% adequate (e.g. grep will return Junicode, which isn't a fix-sized font). In fontconfig you can assign a font to the monospace group, but you can't list all monospace fonts installed in the system with fontconfig standard search patterns (at least I don't know about such a method).

Here's a list of popular mono fonts available in the ib-fonts repo (free) and a couple of popular non-free ones I can't supply.

free

CamingoCode
Consola Mono
Courier Prime
Cousine
Droid Sans Mono (3 variants)
DejaVu Sans Mono
Fira Mono
Inconsolatazi4
Lekton
Luxi Mono
M+ 1m/1mn/2m
Meslo
NanumGothic
Nimbus Mono L
Oxygen Mono
PT Mono
Source Code Pro
TeX Gyre Cursor
Ubuntu Mono

non-free

Envy Code R
PragmataPro

Last edited by bohoomil (2014-11-10 22:43:21)

3xOSC · 2014-11-10 23:43:05

frabjous wrote:

3xOSC wrote:
I've recently installed infinality bundle using the repository method and emptied out my ~/.config/fontconfig dir since I heard that that wasn't needed anymore.
I then downloaded the font "otf-titillium-ibx" and made sure fc-list and xlsfonts can see it; and they did.
However, when i tried to use this font on my terminal (termite), the font looks squished and like crooked teeth. Is hinting/aliasing turned on?
I checked the /etc/conf.avail.infinality/ and did see the titillium settings in there. Is there something I should do with those files that begin with a number?
Thanks in advance.
Terminal emulators are designed to use monospace fonts.Titillium is not a monospace font. Most likely termite is just squishing/stretching the letters to make them all the same width. Better to use a different font.

ah, okay. i see now, thanks for your explanation!

3xOSC · 2014-11-10 23:44:05

bohoomil wrote:

Thank you everyone for your feedback.
@hcra This is the 'either/or' question. If you want to use infinality-bundle, you have to remove freetype2-infinality and fontconfig-infinality. Infinality-bundle provides you with everything you need in mutually compatible and optimized packages.
foo.pacsave files are usually meant to be deleted so this one is no exception.
@knightzx, @sl1pkn07 Thanks for additional info. With sl1pkn07's file I can reproduce the crash, but switching video output to xv doesn't prevent it. I'll try to isolate the piece of code in the Infinality patchset which can be responsible for the issue. I do hope a knowledgeable C coder will use her/his skills to assist me in fixing it…
@orschiro Unfortunately, yes: all Noto fonts occupy about 450 MB of HDD space now.
@3xOSC Remember the 2014-10-05 09:05:19? ;-)
Unfortunately, we don't have an easy and obvious way to determine whether a font is monospaced or proportional. You just have to know what the purpose of fonts you're using is. You can try playing with pacman and grep using related keywords ('mono', 'code', etc.) but the results will never be 100% adequate (e.g. grep will return Junicode, which isn't a fix-sized font). In fontconfig you can assign a font to the monospace group, but you can't list all monospace fonts installed in the system with fontconfig standard search patterns (at least I don't know about such a method).
Here's a list of popular mono fonts available in the ib-fonts repo (free) and a couple of popular non-free ones I can't supply.
free
CamingoCode
Consola Mono
Courier Prime
Cousine
Droid Sans Mono (3 variants)
DejaVu Sans Mono
Fira Mono
Inconsolatazi4
Lekton
Luxi Mono
M+ 1m/1mn/2m
Meslo
NanumGothic
Nimbus Mono L
Oxygen Mono
PT Mono
Source Code Pro
TeX Gyre Cursor
Ubuntu Mono
non-free
Envy Code R
PragmataPro

haha, oops. i remember now. i swear i have a memory of a fly. i get excited when i see a font i really like then throw all the things i read about out the window.

Arch Linux

#1451 2014-11-04 18:18:46

Re: infinality-bundle: good looking fonts made (even) easier

#1452 2014-11-05 00:14:31

Re: infinality-bundle: good looking fonts made (even) easier

#1453 2014-11-05 11:30:35

Re: infinality-bundle: good looking fonts made (even) easier

#1454 2014-11-05 19:09:39

Re: infinality-bundle: good looking fonts made (even) easier

#1455 2014-11-06 00:07:53

Re: infinality-bundle: good looking fonts made (even) easier

#1456 2014-11-06 13:58:28

Re: infinality-bundle: good looking fonts made (even) easier

#1457 2014-11-06 22:09:57

Re: infinality-bundle: good looking fonts made (even) easier

#1458 2014-11-07 00:13:36

Re: infinality-bundle: good looking fonts made (even) easier

#1459 2014-11-07 20:55:27

Re: infinality-bundle: good looking fonts made (even) easier

#1460 2014-11-07 21:30:36

Re: infinality-bundle: good looking fonts made (even) easier

#1461 2014-11-07 21:56:49

Re: infinality-bundle: good looking fonts made (even) easier

#1462 2014-11-09 23:40:28

Re: infinality-bundle: good looking fonts made (even) easier

#1463 2014-11-10 02:07:54

Re: infinality-bundle: good looking fonts made (even) easier

#1464 2014-11-10 04:13:16

Re: infinality-bundle: good looking fonts made (even) easier

#1465 2014-11-10 05:08:54

Re: infinality-bundle: good looking fonts made (even) easier

#1466 2014-11-10 05:42:48

Re: infinality-bundle: good looking fonts made (even) easier

#1467 2014-11-10 06:11:04

Re: infinality-bundle: good looking fonts made (even) easier

#1468 2014-11-10 07:00:54

Re: infinality-bundle: good looking fonts made (even) easier

#1469 2014-11-10 12:32:20

Re: infinality-bundle: good looking fonts made (even) easier

#1470 2014-11-10 13:13:35

Re: infinality-bundle: good looking fonts made (even) easier

#1471 2014-11-10 14:29:10

Re: infinality-bundle: good looking fonts made (even) easier

#1472 2014-11-10 16:23:57

Re: infinality-bundle: good looking fonts made (even) easier

#1473 2014-11-10 22:01:36

Re: infinality-bundle: good looking fonts made (even) easier

#1474 2014-11-10 23:43:05

Re: infinality-bundle: good looking fonts made (even) easier

#1475 2014-11-10 23:44:05

Re: infinality-bundle: good looking fonts made (even) easier

Board footer