33 Beautiful Open-Source Icon Sets
blog.usepastel.com
33 Beautiful Open-Source Icon Sets
1–10 of 16 posts
Re: 33 Beautiful Open-Source Icon Sets
#2Seems like the meaning of "beautiful" is a little bit too specific today.
Re: 33 Beautiful Open-Source Icon Sets
#3Seems like the meaning of "beautiful" is a little bit too specific today.
Agreed. If you're looking for a different style of icons to use in your application, Tango/GNOME and Breeze are large, complete icon themes.
Tango/GNOME Icons Wikipedia pages (previews many but not all icons): https://commons.wikimedia.org/wiki/Tango_icons https://commons.wikimedia.org/wiki/GNOME_Desktop_icons
Breeze is a bit more 'modern' and would also work well on HiDPI: https://github.com/KDE/breeze-icons ; you would probably want to clone the repo and browse the files manually since GitHub isn't great for previewing images.
KDE created/used the Oxygen icon theme before Breeze, its style is between Tango/GNOME and Breeze: https://github.com/pasnox/oxygen-icons-png
Re: 33 Beautiful Open-Source Icon Sets
#4I'm tired of modern web design. These icons are even not intended to be used on toolbar buttons, but for silly landing page lists. Landings that are all the same on every website.
I miss silk icons that were ubiquitous in late 2000s: http://www.famfamfam.com/lab/icons/silk/. I miss Tango Project icons, although Gnome went off-the-rails in their UI design. I miss small UI elements, like on freaking Windows 95 desktop, not optimized for pressing with finger, despite being shown on desktop.
Re: 33 Beautiful Open-Source Icon Sets
#5also, just remember unicode is packed with icons though I find you do have to check if they render correctly.... but mostly they just work though you may need to make your font a bit bigger or it may look like
UPDATE: apparently.... HN Isn't unicode friendly...https://pasteboard.co/IpxYWjH.png
Re: 33 Beautiful Open-Source Icon Sets
#6also, just remember unicode is packed with icons though I find you do have to check if they render correctly.... but mostly they just work though you may need to make your font a bit bigger or it may look like UPDATE: apparently.... HN Isn't unicode friendly... https://pasteboard.co/IpxYWjH.png
> you do have to check if they render correctly
In general, avoid using font-based icons to avoid the problem you run into in your post above. :) SVGs are better in the vast majority of cases where you have control of markup.
Fonts are unreliable (esp on mobile) -- not enough that you should avoid them, but enough that you should avoid them for anything you need to look correct. I've seen websites and apps where not only do the unicode symbols not display, they get flat out replaced with different images, since some fonts organize themselves differently. And if they don't display, Unicode doesn't gracefully degrade, it just shows nothing.
It's always weirded me out and slightly annoyed me that emoji are associated with Unicode at all, it's a terrible format for accessibility. The more robust, markdown-ish way to do this would be to abandon attaching them to Unicode characters entirely and wholesale switch to the Slack/Twitter convention of spelling things out.
:smile: :thumbsup: :cookie:
Plus, spelling them out allows you to use emoji like :squirtle_squad_robbing_bank: or :children_standing_in_cornfield: even though they haven't technically made it into the standard yet. On an unrelated note, for some reason the standards body has stopped responding to any of my emails.
Re: 33 Beautiful Open-Source Icon Sets
#7also, just remember unicode is packed with icons though I find you do have to check if they render correctly.... but mostly they just work though you may need to make your font a bit bigger or it may look like UPDATE: apparently.... HN Isn't unicode friendly... https://pasteboard.co/IpxYWjH.png
> you do have to check if they render correctly In general, avoid using font-based icons to avoid the problem you run into in your post above. :) SVGs are better in the vast majority of cases where you have control of markup. Fonts are unreliable (esp on mobile) -- not enough that you should avoid them, but enough that you should avoid them for anything you need to look correct. I've seen websites and apps where not…
iconfonts and unicode icons are two different things. unicode icons are the built in icons that renders correctly (but with slight variations) on any modern device, iconfonts are basically your own icons set as a font, hopefully using Private Use Areas for the codepoints.
Re: 33 Beautiful Open-Source Icon Sets
#8also, just remember unicode is packed with icons though I find you do have to check if they render correctly.... but mostly they just work though you may need to make your font a bit bigger or it may look like UPDATE: apparently.... HN Isn't unicode friendly... https://pasteboard.co/IpxYWjH.png
> you do have to check if they render correctly In general, avoid using font-based icons to avoid the problem you run into in your post above. :) SVGs are better in the vast majority of cases where you have control of markup. Fonts are unreliable (esp on mobile) -- not enough that you should avoid them, but enough that you should avoid them for anything you need to look correct. I've seen websites and apps where not…
the problem above is purely how HN have done the site, I'm guessing they don't save unicode text ( possibly ascii ) as when you load up the text again all the unicode is stripped from the message
Re: 33 Beautiful Open-Source Icon Sets
#9Earlier quoted context omitted.
> you do have to check if they render correctly In general, avoid using font-based icons to avoid the problem you run into in your post above. :) SVGs are better in the vast majority of cases where you have control of markup. Fonts are unreliable (esp on mobile) -- not enough that you should avoid them, but enough that you should avoid them for anything you need to look correct. I've seen websites and apps where not…
the problem above is purely how HN have done the site, I'm guessing they don't save unicode text ( possibly ascii ) as when you load up the text again all the unicode is stripped from the message
You're right, but that's also kind of the point I'm making -- that your emoji can get stripped or broken purely because a random site or step in your display process decides not to handle the full Unicode.
Unicode emoji relies on sites/platforms:
A) choosing to support the full Unicode set
B) Being up-to-date on the current spec and having glyphs to display for the entire set
Regardless of whether or not it's easy to support -- many, many sites and platforms in the real world don't. When they don't support the full spec, you get invisible characters that can't degrade gracefully, can't be read by screen readers, and that break copy-paste.
I still run into garbled text online that's the result of people copying and pasting smart quotes between platforms that won't render them. Platforms are never gonna catch up to a living spec that is regularly extended, so it's preferable to avoid "novel" Unicode characters and use something that degrades gracefully instead.
Re: 33 Beautiful Open-Source Icon Sets
#10Earlier quoted context omitted.
> you do have to check if they render correctly In general, avoid using font-based icons to avoid the problem you run into in your post above. :) SVGs are better in the vast majority of cases where you have control of markup. Fonts are unreliable (esp on mobile) -- not enough that you should avoid them, but enough that you should avoid them for anything you need to look correct. I've seen websites and apps where not…
iconfonts and unicode icons are two different things. unicode icons are the built in icons that renders correctly (but with slight variations) on any modern device, iconfonts are basically your own icons set as a font, hopefully using Private Use Areas for the codepoints.
> on any modern device
This qualifier is why Unicode icons should be avoided where possible.
You're correct that Unicode icons are different from icon fonts in the sense that they're standardized -- but the standard doesn't matter unless everyone implements it; and as we can see on HN, plenty of platforms don't.
In practice, there are just too many platforms/devices that implement only part of the Unicode standard, or that implement it incorrectly, or that extend it with their own stuff.