Live data from Hacker News

Brick. Webfonts that look good

github.com

31–40 of 73 posts

Re: Brick. Webfonts that look good

#31

If I understand correctly, Google Fonts may be used in commercial websites. Does the license vary between different fonts in this case?

The fonts that are also in Google Fonts should have the same license; for the ones that are not, consult the license file in each font's directory, but all of them should be usable commercially.

Re: Brick. Webfonts that look good

#32
What the heck is with the bottoms of the lowercase a, w, and t? Is it really supposed to dip below the line like that? And is the fi really supposed to join up in this font, or are they just overlapping and it's a happy accident that it looks like a ligature?

Overall it looks quite a bit heavier. I can see that working sometimes but not always.

Re: Brick. Webfonts that look good

#33
Alfred, love the project and effort. Everything looks great on my Mac.

On a current Windows 7 machine, Brick is much better than Google web font using Chrome, but both FF and IE v11 would be a show-stoppers for me, with random baseline shifts in the preview header making it look a little like a ransom note font.

Is there any browser compatibility lost by offering up only the WOFF format?

Re: Brick. Webfonts that look good

#35
post #14

As far as I can see; iOS renders it just fine in both implementations

iOS devices typically have a much higher DPI than a "normal" (though this is rapidly changing) screen.

Because of that fonts often look far better and "truer" to their original intentions, Macs/iOS have always favoured fidelity over legibility (when pushed) so it is perhaps not surprising they both look good.

Re: Brick. Webfonts that look good

#37
post #22

Earlier quoted context omitted.

I guess it depends on your setup. On Windows XP + ClearType + Chrome the difference is _huge_, it has a much better font smoothing.

I'm just interested, why are you still on Windows XP?

Inertia (aka it's still working). I'm planning to upgrade OS and hardware before support ends. I can't wait to have more than 4 GB of RAM ;)

Re: Brick. Webfonts that look good

#38
You can request all subsets to include a font's ligatures with Google fonts.

See: https://developers.google.com/fonts/docs/getting_started#Sub...

So if you add a `&subset=all` to the example page requesting from Google Fonts, they'll end up looking pretty much the same (though I think some things are missing in the example, like the swashes on the Qs).

I discovered this in reading the Lobster font's documentation.

Re: Brick. Webfonts that look good

#39

What the heck is with the bottoms of the lowercase a, w, and t? Is it really supposed to dip below the line like that? And is the fi really supposed to join up in this font, or are they just overlapping and it's a happy accident that it looks like a ligature? Overall it looks quite a bit heavier. I can see that working sometimes but not always.

Is this on Firefox? Seems to be an issue.

I'm pretty sure the fi is supposed to be joined; if you highlight it with your mouse, it highlights as one character (though on copy-and-paste it's two, as expected).

OpenType fonts usually look a bit heavier, but I don't think it's a big issue.

Re: Brick. Webfonts that look good

#40

Alfred, love the project and effort. Everything looks great on my Mac. On a current Windows 7 machine, Brick is much better than Google web font using Chrome, but both FF and IE v11 would be a show-stoppers for me, with random baseline shifts in the preview header making it look a little like a ransom note font. Is there any browser compatibility lost by offering up only the WOFF format?

Thanks!

Yes, IE http://caniuse.com/woff

Post reply on HN