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

topyli · 2014-04-01 15:52:12

ooo wrote:

I consider this is issue with the browser and not infinality patches or your bundle. As said I'll try to figure it out if this is stil the case in 3.12.

I upgraded to GNOME 3.12, and sadly Epiphany's font rendering did not improve. Which is a shame because otherwise the browser is better than ever!

r2b2 · 2014-04-01 22:34:15

hokasch wrote:

debug: checking signature for /var/lib/pacman/sync/infinality-bundle.db
debug: 1 signatures returned
debug: fingerprint: AE6866C7962DDE58
Sorry, this is indeed the wrong signature, or at least it seems to be only part of it, however the repo URL is correct. Shot in the dark, but try to remove /var/lib/pacman/sync/infinality-bundle.db* and run -Syy again? Here is how a -Syy looks in my log:
debug: checking signature for /var/lib/pacman/sync/infinality-bundle.db
debug: 1 signatures returned
debug: fingerprint: A9244FB5E93F11F0E975337FAE6866C7962DDE58

Thanks - that didn't work but then I started thinking and wondered if somehow the transfer of the file wasn't quite working properly. So I did a bit of testing with 'gpg --verify' and tried downloading the db & db.sig files with and without HTTPS. What I've found is that the .db.sig file is coming down fine with both HTTP and HTTPS but the .db file comes down differently depending on HTTP or HTTPS.

With HTTPS I'm getting the file as a gzipped file but HTTP is giving me a TAR file. Checking the signature against the gzip file is working fine but obviously doesn't with the TAR file as thats not what was signed.

I'm wondering if someone else does a wget/curl on http://bohoomil.com/repo/x86_64/infinality-bundle.db whether they get a gzipped file or tar file back. If its the former, I'm guessing that my ISPs transparent proxy is breaking things along the way.

progandy · 2014-04-01 22:42:24

I get the compressed file. I guess your proxy decompresses the file in order to perform virus detection or something like that. Maybe the server should send different headers.
This is what you get:

Content-Type: application/x-tar
Content-Encoding: x-gzip

This is what I think could prevent automatic decompression (no Content-Encoding header)

Content-Type: application/x-gzip

Last edited by progandy (2014-04-01 22:42:37)

bohoomil · 2014-04-02 00:49:16

progandy wrote:

This is what I think could prevent automatic decompression (no Content-Encoding header)
Content-Type: application/x-gzip

Thank you for the suggestion (always helpful!): I added application type for .db files. r2b2, please check if this helps.

@ooo & topyli This is just a very wild guess: is it possible that there is something wrong with WebKitGtk3? Unlike dwb, both Midori and Epiphany use it. Maybe here is the problem and that is why I could not reproduce it with my browser?

Last edited by bohoomil (2014-04-02 00:50:27)

r2b2 · 2014-04-02 01:24:24

bohoomil wrote:

progandy wrote:
This is what I think could prevent automatic decompression (no Content-Encoding header)
Content-Type: application/x-gzip
Thank you for the suggestion (always helpful!): I added application type for .db files. r2b2, please check if this helps.

Your server change seems to have fixed the issue although the transparent proxy still is holding an outdated copy with the old content-type so I'll need to work around that until you next update your database I guess. (Not sure if you can force an update or whether that will need to wait until your next updates?)

Thanks everyone for all your help and the prompt responses!

Hspasta · 2014-04-03 05:38:51

Do you know if there's a way to have Korean fonts render better? It's always looked like garbage on Linux... It's never sharp and it always seems to be a bit smaller than it should be.

Screeny

my fonts

$ pqs ttf                                                       ~
local/source-code-pro-fonts 1.017-1
    A set of monospaced fonts (TTF & OTF) designed for coding environments
local/ttf-alee 12-1
    A set of free Hangul TrueType fonts made by A Lee
local/ttf-baekmuk 2.2-7
    Korean fonts
local/ttf-dejavu 2.34-1
    Font family based on the Bitstream Vera Fonts with a wider range of
    characters
local/ttf-indic-otf 0.2-6
    Indic Opentype Fonts collection
local/ttf-nanum 3.1-2
    Nanum series TrueType fonts
local/ttf-nanumgothic_coding 2.0-1
    Nanum series fixed width TrueType fonts
local/ttf-symbola 7.12-1
    Font for unicode symbols (part of Unicode Fonts for Ancient Scripts).
local/ttf-unfonts-core 1.0.2-6
    This is a set of Korean TrueType fonts. These fonts were made from the
    HLaTeX's PostScript fonts and modified slightly.

Last edited by Hspasta (2014-04-03 05:39:25)

bohoomil · 2014-04-03 16:17:50

@Hspasta Yes. I have been looking for a set of truly decent fonts for a few Eastern scripts. The one for Korean, which eventually will become the new ib's default, is Nanum Gothic (there is also a serif version, Nanum Myeongjo, which I am going to add to the repository soon). With this one, the Korean picture looks like this: ArchWiki.

The package is called ttf-nanum-gothic-ibx. Since we still have to use the 93-final-lang-spec-foo.conf ifiles, go to /etc/fonts/conf.d and

comment this line:

      <string>UnDotum</string> <!-- ko -->

and add this (right after Koruri):

      <string>NanumGothic</string> <!-- ko -->

Hspasta · 2014-04-03 22:54:06

Thanks Bohoomil! They look much better.

edit: actually, the fonts for some reason are still offset (up a few pixels).

I'm using the ms preset too.

screeny. The top seems to get clipped.

Last edited by Hspasta (2014-04-04 02:10:26)

FreeAsInGimme · 2014-04-09 18:22:41

First of all, thank you for making this. I seem to be having trouble getting fc-presets to save my settings:

 elijah@chestnut # xrdb -load .Xresources 
 elijah@chestnut # sudo fc-presets set 
[sudo] password for elijah: 
1) combi
2) free
3) ms
4) reset
5) quit
Enter your choice... 4
 Removing current preset...
Done. Now select a new preset...
Enter your choice... 3
 [ ms ] preset chosen...
Done.
 elijah@chestnut # sudo fc-presets check
 [ combi ] is not set 
 :: Run <fc-presets help> for more information.
 [ free ] is not set 
 :: Run <fc-presets help> for more information.
 [ ms ] is not set 
 :: Run <fc-presets help> for more information.

Any ideas?

EDIT:
I think I fixed it.

sudo pacman -Rdd fontconfig-infinality-ultimate

Then removed all symlinks in /etc/fonts/conf.d, then

sudo pacman -S fontconfig-infinality-ultimate

Last edited by FreeAsInGimme (2014-04-09 18:56:22)

gondsman · 2014-04-09 18:27:17

Hi! I have a REALLY bad font rendering in wine, while everything else looks just fine. I can show you a screenshot:

Can anyone help me? I already tried enabling antialiasing via regedit but it doesn't make any difference.

bohoomil · 2014-04-09 21:31:40

@Hspasta This is Noto Sans' known issue on some pages: its descenders go a tad bit too much below the descender line, which can be an issue when a <hr> tag is used right after the header without enough padding (or in some dialogue boxes: see the screenshot). If you find it disturbing, you can use Liberation Sans as your default sans face.

@gondsman Have you tried setting your default font for Wine in 'Desktop Integration' tab? Did you install 'Source Sans Pro' (t1-source-sans-pro-ibx), which provides a default alias for Wine?

gondsman · 2014-04-10 07:23:10

bohoomil wrote:

@gondsman Have you tried setting your default font for Wine in 'Desktop Integration' tab? Did you install 'Source Sans Pro' (t1-source-sans-pro-ibx), which provides a default alias for Wine?

Rendering is bad with every font (unless I set it to 20+ size), no matter which one I chose. Also, in Office 2007 (my main reason for using wine), the text is antialiased but very blurry, again with every font. For what's worth, if I use wine <1.3.33 text rendering is fine.
I don't have Source Sans Pro installed, though, I'll try it when I'm home. Thanks for the suggestion.

2carders · 2014-04-10 12:01:49

Hi! First of all, thank you, bohoomil, for providing this nice bundle.
I have one question on mixed use of ASCII and non-Latin(Japanese) fonts.
I want to use different fonts for ASCII/latin and Japanese characters,
and prefer "Koruri" for Japanese sans-serif, and "Noto Sans" for latin sans-serif.

So I set "FC_LANG=en" to pick up a latin font first and then fall back to Japanese font,
and I got "Noto Sans" for latin characters, as shown below.

$ fc-match -s sans-serif | head -20
NotoSans-Regular.ttf: "Noto Sans" "Regular"
LiberationSans-Regular.ttf: "Liberation Sans" "Regular"
DroidSansArmenian.ttf: "Droid Sans" "Regular"
DroidSansGeorgian.ttf: "Droid Sans" "Regular"
DroidSansEthiopic-Regular.ttf: "Droid Sans" "Regular"
DroidSansArabic.ttf: "Droid Sans" "Regular"
DroidSansDevanagari-Regular.ttf: "Droid Sans" "Regular"
DroidSansTamil-Regular.ttf: "Droid Sans" "Regular"
DroidSansThai.ttf: "Droid Sans" "Regular"
DroidSansJapanese.ttf: "Droid Sans" "Regular"
DroidSansFallback.ttf: "Droid Sans" "Regular"
DroidSansFallbackFull.ttf: "Droid Sans" "Regular"
DroidSansFallbackLegacy.ttf: "Droid Sans" "Regular"
DejaVuSans.pfb: "DejaVu Sans" "Regular"
DejaVuSans-Bold.pfb: "DejaVu Sans" "Bold"
DejaVuSans-Oblique.pfb: "DejaVu Sans" "Oblique"
DejaVuSans-BoldOblique.pfb: "DejaVu Sans" "Bold Oblique"
n019003l.pfb: "Nimbus Sans L" "Regular"
ipag.ttf: "IPAGothic" "Regular"
Koruri-Regular.ttf: "Koruri" "Regular"

But "fc-match sans-serif:lang=ja" returns "DroidSansJapanese.ttf"
instead of the default "IPAGothic" in 65-non-latin-free.conf,
although I had installed both ttf-ipafont-ib and ttf-droid-ib (and ttf-koruri-ibx).

$ fc-match -s sans-serif:lang=ja | head -20
DroidSansJapanese.ttf: "Droid Sans" "Regular"
ipag.ttf: "IPAGothic" "Regular"
NotoSans-Regular.ttf: "Noto Sans" "Regular"
LiberationSans-Regular.ttf: "Liberation Sans" "Regular"
DroidSansArmenian.ttf: "Droid Sans" "Regular"
DroidSansGeorgian.ttf: "Droid Sans" "Regular"
DroidSansEthiopic-Regular.ttf: "Droid Sans" "Regular"
DroidSansArabic.ttf: "Droid Sans" "Regular"
DroidSansDevanagari-Regular.ttf: "Droid Sans" "Regular"
DroidSansTamil-Regular.ttf: "Droid Sans" "Regular"
DroidSansThai.ttf: "Droid Sans" "Regular"
DroidSansFallback.ttf: "Droid Sans" "Regular"
DroidSansFallbackFull.ttf: "Droid Sans" "Regular"
DroidSansFallbackLegacy.ttf: "Droid Sans" "Regular"
DejaVuSans.pfb: "DejaVu Sans" "Regular"
DejaVuSans-Bold.pfb: "DejaVu Sans" "Bold"
DejaVuSans-Oblique.pfb: "DejaVu Sans" "Oblique"
DejaVuSans-BoldOblique.pfb: "DejaVu Sans" "Bold Oblique"
n019003l.pfb: "Nimbus Sans L" "Regular"
Koruri-Regular.ttf: "Koruri" "Regular"

It seems that "Droid Sans" in 60-latin-free.conf is concverted by 65-ttf-droid-sans.conf
to each language versions and fallback fonts, so they always precedes the settings of 65-non-latin-free.conf.

 $ fc-pattern -cd sans-serif:lang=ja family
Pattern has 1 elts (size 16)
	family: "Noto Sans"(w) "Liberation Sans"(w) "TeX Gyre Heros"(w) "Droid Sans"(w) "DejaVu Sans"(w) "Nimbus Sans L"(w) "PT Sans"(w) "NanumGothic"(w) "IPAGothic"(w) "Koruri"(w) "WenQuanYi Micro Hei"(w) "DejaVu Sans YuanTi"(w) "DDC Uchen"(w) "TharLon"(w) "MPH 2B Damase"(w) "Droid Arabic Kufi"(w) "LKLUG"(w) "Lohit Oriya"(w) "Estrangelo Edessa"(w) "Euphemia UCAS"(w) "IPAexGothic"(w) "Sawarabi Gothic"(w) "Droid Sans Japanese"(w) "Droid Sans"(w) "VL Gothic"(w) "VL PGothic"(w) "WenQuanYi Zen Hei"(w) "Gulim"(w) "Dotum"(w) "GulimChe"(w) "DotumChe"(w) "Imperial Brahmi"(w) "Myanmar3"(w) "zawgyi1"(w) "Saweri"(w) "Droid Sans Tamil"(w) "Droid Sans"(w) "Lohit Tamil"(w) "Lohit Tamil Classical"(w) "Lohit Telugu"(w) "Lohit Assamese"(w) "Lohit Bengali"(w) "Droid Sans Devanagari"(w) "Droid Sans"(w) "Mangal"(w) "Utsaah"(w) "Lohit Devanagari"(w) "Lohit Nepali"(w) "Serto Batnan"(w) "Serto Jerusalem"(w) "Serto Kharput"(w) "Serto Malankara"(w) "Serto Mardin"(w) "Serto Urhoy"(w) "Droid Sans"(w) "sans-serif"(s)

Is there a good way to set "Koruri" for Japanese sans-serif?

And another question I have is that

 fc-query /usr/share/fonts/ttf-koruri-ibx/Koruri-Regular.ttf | grep '\blang:'

does NOT include "ja".
I tried downgrading the font package and reinstalling it, but no change.
Have I broken something? ("fc-presets check" says OK for all 5 symlinks of free preset)

fontconfig-infinality-ultimate 2.11.1-4
freetype2-infinality-ultimate 2.5.3-4
cairo-infinality-ultimate 1.12.16-3
ibfonts-meta-base 1-3
ttf-droid-ib 20121017-4
ttf-ipafont-ib 003.03-1
ttf-koruri-ibx 20140319-1

julroy67 · 2014-04-10 12:41:09

Hi bohoomil,

With latest update of infinality-bundle, it seems that Chrome japanese tab title rendering is again borked. I get the same rendering as before you fix. Hope you can take a look at it

EDIT:

I also found out that the fc-presets command, when checking the config, doesn't work. I tried to set the free preset but still shows this :

initia@initia ~ % sudo fc-presets check
 [ combi ] is not set 
 :: Run <fc-presets help> for more information.
 [ free ] is not set 
 :: Run <fc-presets help> for more information.
 [ ms ] is not set 
 :: Run <fc-presets help> for more information.

Last edited by julroy67 (2014-04-10 12:46:09)

Hspasta · 2014-04-10 12:58:51

With a recent update, 93-final-lang-spec.conf is a broken symlink. Is this intentional?

bohoomil · 2014-04-10 13:54:12

@Hspasta Yes: click.

There have been plenty of things happening since the server upgrade so I have not probably mentioned all good news yet. Right now, if you want to catch up with the updates, you can either subscribe to

Google+

or

the RSS feed @ bohoomil.com

This way you will always have a fresh copy of the CHANGELOG as soon as anything important happens to the bundle. Stay tuned.

I will reply to the remaining questions later today.

bohoomil · 2014-04-10 22:14:13

@2carders Thanks for the feedback.

And another question I have is that
 fc-query /usr/share/fonts/ttf-koruri-ibx/Koruri-Regular.ttf | grep '\blang:' 
does NOT include "ja".

Jackpot: you won the bicycle. What's more: Koruri reproduces the same bug after M+ fonts it is based on and this way none of them can be easily set default in fontconfig. This was the reason for me to move Koruri to the extended collection and replace it with IPAGothic, which is simply more reliable.

Actually, the problems with Koruri and Droid Sans Japanese (and Fallback) initiated the whole update this time. I noticed that even if I removed the support for Droid Sans Japanese/Fallback from 65-ttf-droid-sans.conf, the font would still come up here and there even if anything that had been set default should be used instead. I do not like Droid Sans Japanese: it looks crummy, rusty and dated at smaller sizes. What I think we may do is remove it from the ttf-droid-ib package altogether, or split to a separate one so that the base Droid collection will not produce issues like yours. (Besides, we need Droid for its good looking Arabic Naskh and Kufi.) I will upload modified packages soon.

What we still need anyway is a really good looking set of modern and free Japanese and Chinese fonts. The choice is extremely narrow here, with a little exception for the Chinese script because we have DejaVu YuanTi (it integrates beautifully with the base DejaVu family and looks pretty good for the price, too). It is still far from Microsoft YaHei and the like, but from 12px up it offers acceptable results. For the Japanese script, we have only a collection of quite dated options, none of which comes close to what Meiryo can do, plus buggy M+ & Koruri that cannot be set default. Any ideas?

@julroy67 I do not think so: see the shot (fonts are from free). I think this may be related to your issue with fc-presets: did you try fixing it the hard way? I believe when this is done and your collection has been set properly, the tab nuisance will be gone, too. (BTW, I test new setups against your tricky website, so nothing critical should happen again. )

sl1pkn07 · 2014-04-11 05:37:27

~~since last update..~~

http://wstaw.org/m/2014/04/11/plasma-desktopgV7242.png
elotrolado.net

fixed, but i don't know how :S

Last edited by sl1pkn07 (2014-04-11 10:04:47)

julroy67 · 2014-04-11 08:04:37

bohoomil wrote:

@julroy67 I do not think so: see the shot (fonts are from free). I think this may be related to your issue with fc-presets: did you try fixing it the hard way? I believe when this is done and your collection has been set properly, the tab nuisance will be gone, too. (BTW, I test new setups against your tricky website, so nothing critical should happen again. )

Worked fine, thanks again ! (but I don't even know how this has broken)

sl1pkn07 · 2014-04-11 08:46:59

@gondsman

you use kde?, if yes, -> http://wstaw.org/m/2014/04/11/plasma-desktopVd7242.png

doggone · 2014-04-11 10:12:28

As always, thanks so much for making my fonts pretty bohoomil. I'm using Nimbus Sans L as my main sans-serif font at the moment.. But there's one qualm I have with it, it's a little bit too high.. Is there a way to make it correctly vertically centered?

As you can see here on these Firefox tabs for example, the text should be a little lower:

2carders · 2014-04-11 11:10:22

@bohoomil, thank you for the quick response.

too forward Drond Sans:
Droid Sans is splitted into per-lang files already now, so if I removed 65-ttf-droid-sans.ttf,
I got the right default Japanese font (IPAGothic) by "fc-match sans-serif:lang=ja".
But strangely I cannnot see plain (ASCII) "DroidSans.ttf" any more in "fc-match sans-serif".

In the previous version of this bundle, DroidSansFallback was placed at a pretty high order
in 93-final-lang-spec.conf with a "strong" binding, and blocked other non-latin fonts.
I noticed that when I found a bit strange "Kanji" glyphs that are not used in current Japanese,
looking like those in Chinese or in older Japanese,
and if I placed it at the bottom of the strong alias list for sans-serif, I could get the desired fonts.

So I'd prefer splitted DroidSans as I like to use separate fonts for latin and for Japanese characters,
although I'm not sure that kind of usage (using a latin fonts with fallback non-latin fonts) is well
supported/considered in fontconfig.

Koruri/M+ not tagged "ja":
I read that M+ is in development and adding glyphs now,
and I wonder why fontconfig checks Japanese orthography so rigidly.
I also checked "Sawarabi" which is said to be relatively young and contains less glyphs,
and it did not contain "ja" either.

Unfortunately, lots of Japanese free fonts are based on M+ or IPA (or wadalab),
and there's no free alternative to the beatiful commercial fonts like "Heisei {Kaku|Maru} Gothic" or "Hiragino",
though I understand that desigining a Japanese font is a massive work.
So I with fontconfig would accept M+ derived, in-complete Japanese fonts more.

   ∧_∧
  (´∀`)
  ( ０┳０
≡◎━Ｊ┻◎

Hspasta · 2014-04-11 12:17:48

There appears to be an issue with rendering bold Korean with the free fc-preset.

This was taken from the ArchWiki beginners' guide.

free preset

ms preset

psychoticmeow · 2014-04-11 19:06:32

gondsman wrote:

Hi! I have a REALLY bad font rendering in wine, while everything else looks just fine. I can show you a screenshot:
Can anyone help me? I already tried enabling antialiasing via regedit but it doesn't make any difference.

You can tell Wine to use the systems font rendering using this registry entry:

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]\n
"ClientSideWithRender"="N"

Or you can use this script I just wrote, which also sets the font DPI if you need it, and can be run again if you make a new WINEPREFIX.

TiZ · 2014-04-11 19:12:07

Hi there. I started using Arch Linux again, and one of the first things I did as soon as I got my DE running again was to get back on the Infinality train; I gots to have my enhanced artificial emboldening! I'm coming over from Xubuntu 13.10 and its own Infinality PPA.

With your version of the infinality set, I have noticed a few weird things. The most weird and most disconcerting thing was that in order to make my fonts look like they did on Xubuntu, I had to increase my DPI from 96 to 98. But once I did, everything did look exactly the same, save for a few little things I just resolved and describe below, due to the fonts bundle. Could you possibly explain this DPI discrepancy to me? I feel like there's some really weird stuff going on, and I'm worried that there might be some overconfiguration causing it. This bundle does seem to be a *lot* more proactive than Ubuntu's PPA.

Sadly, I am no longer using the fonts part of the bundle, because some weird things were happening with those versions of the fonts. Since I'm using this bundle and tend to like Infinality's artificial emboldening, it follows that I'm pretty anal-retentive about how my system looks and feels. So when I opened up Quod Libet and found my row height was jacked up, I got pretty unsettled. First, the Japanese characters were messed up (I have some JRock and I like to tag it with kana) with large row heights, and regular latin characters were pushed down next to them. So I started ripping out fonts until I discovered that one of Droid Sans's variations had CJK characters and a huge row height. So I removed the Droid Sans package. But the rating stars still had a huge row height. After some investigation thanks to some help from the IRC channel, I discovered it was DejaVu Sans, which made me go "wtf" since DejaVu Sans is the standard font in all of Linux-land. It turns out that your t1 version of DejaVu Sans has a really jacked-up row height, so I removed it and used the standard repo ttf version. At that point I decided it would probably be safer just to use the standard versions of all the fonts. So I just thought I'd let you know about that whle asking about the DPI thing.

Thanks for your work on the bundle!

Last edited by TiZ (2014-04-11 19:12:52)

Arch Linux

#1026 2014-04-01 15:52:12

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

#1027 2014-04-01 22:34:15

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

#1028 2014-04-01 22:42:24

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

#1029 2014-04-02 00:49:16

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

#1030 2014-04-02 01:24:24

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

#1031 2014-04-03 05:38:51

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

#1032 2014-04-03 16:17:50

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

#1033 2014-04-03 22:54:06

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

#1034 2014-04-09 18:22:41

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

#1035 2014-04-09 18:27:17

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

#1036 2014-04-09 21:31:40

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

#1037 2014-04-10 07:23:10

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

#1038 2014-04-10 12:01:49

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

#1039 2014-04-10 12:41:09

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

#1040 2014-04-10 12:58:51

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

#1041 2014-04-10 13:54:12

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

#1042 2014-04-10 22:14:13

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

#1043 2014-04-11 05:37:27

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

#1044 2014-04-11 08:04:37

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

#1045 2014-04-11 08:46:59

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

#1046 2014-04-11 10:12:28

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

#1047 2014-04-11 11:10:22

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

#1048 2014-04-11 12:17:48

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

#1049 2014-04-11 19:06:32

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

#1050 2014-04-11 19:12:07

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

Board footer