Live data from Hacker News

Font Awesome 4 released

fontawesome.io

81–90 of 97 posts

Re: Font Awesome 4 released

#81

Is this better than http://icomoon.io/app ? I can create my own font file with icomoon so it only contains the icons that I needed for my site. Only issue I have is that there is no way to save the created font file so that I can modify later.

http://www.icnfnt.com lets you subset Font Awesome to just the icons you need. Based on v3.0.2 though.

Re: Font Awesome 4 released

#82
post #77

Earlier quoted context omitted.

Some people apparently think "open source" means "anyone can commit whatever they like to the main repository", which is odd.

- Can't do pull requests on the graphics. - Can't download the svgs. The only thing that is open source is the implementation.

Can't do pull requests on the graphics?

https://github.com/FortAwesome/Font-Awesome/pull/1823

Can't download the SVGs?

https://github.com/FortAwesome/Font-Awesome/blob/master/font...

Re: Font Awesome 4 released

#83
post #36

They renamed the icons. They don't just break apps when they do that, they break users. At some point things like the names of icons should be frozen. I love Font Awesome of course. But please!

My favorite rename is push-pin -> thumb-tack :-)

I'm sure that really improves performance.

Re: Font Awesome 4 released

#84
post #59

Anyone else having trouble with using the new 4.0 fonts from the Bootstrap CDN? http://stackoverflow.com/questions/19549881/cdn-for-font-awe...

https://github.com/FortAwesome/Font-Awesome/issues/2193

Url should be /fonts, not /font.

In variables.less, change @fa-font-path to: "//netdna.bootstrapcdn.com/font-awesome/4.0.0/fonts"

Re: Font Awesome 4 released

#85
post #79

What I see on that page: one hell of a lot of unicode placeholders and not much else. We don't all agree with a site's font choices. And at least img made an attempt at semantic meaning and accessibility with alt= attributes. The failure modes for img are actually quite good. There's no such concern in the minds of those who gave birth to icon fonts.

Ligature symbols actually addresses this. there just aren't enough of them for my needs.

http://kudakurage.com/ligature_symbols/

Re: Font Awesome 4 released

#86
post #79

What I see on that page: one hell of a lot of unicode placeholders and not much else. We don't all agree with a site's font choices. And at least img made an attempt at semantic meaning and accessibility with alt= attributes. The failure modes for img are actually quite good. There's no such concern in the minds of those who gave birth to icon fonts.

Ligature symbols actually addresses this. there just aren't enough of them for my needs. http://kudakurage.com/ligature_symbols/

They also aren't supported very well by browsers. IE8, in particular.

Re: Font Awesome 4 released

#87
post #36

Earlier quoted context omitted.

My favorite rename is push-pin -> thumb-tack :-)

I'm sure that really improves performance.

Actually, it's because I originally matched the Glyphicons names. I was never crazy about them and they weren't terribly consistent. Tried to solve much of that in this version.

Re: Font Awesome 4 released

#90
post #2

Oh for heaven's sake, why is icon-* being deprecated? I stopped using Glyphicons because they switched to glyphion-* .

I can't tell you how happy I am they changed this. No more icon-* conflicts. I've had issues with duplicates with bootstrap's built-in when I only want certain icons to be glyphs, or if I want to create my own. I actually had to do an override where only objects with icon-* and a css class of font-icon would render from the font.

It'll take a little bit of work to update, but I definitely think it's better for compatibility-sake.

Post reply on HN