Live data from Hacker News

Symbolset - symbol font using clever opentype ligature hack

symbolset.com

21–30 of 63 posts

Re: Symbolset - symbol font using clever opentype ligature hack

#21
post #18

This appears to be the current list of keywords: info subtract delete heart alert checkmark replay cart dropdown navigateup navigatedown twitter globe view user creditcard desktop cell search link reply

We're using a subset of the font that only includes the icons we're using on the site. The distributed font contains much more. :)

Re: Symbolset - symbol font using clever opentype ligature hack

#23
post #17
post #16

Earlier quoted context omitted.

Zapfino is actually much more complex than what this is doing. Zapfino has glyph variants - that is, it can display the same set of glyphs multiple ways. Ligatures just combine specific successive glyphs into a new glyph.

Yes, but the word "Zapfino" in Zapfino is one long ligature. That's what the GP was talking about.

I understood that - I wanted to dispel the idea of anything more complex than a ligature.

Re: Symbolset - symbol font using clever opentype ligature hack

#25

> On the web, Symbolsets are supported in all major browsers. ...They work in modern browsers..." Does anybody know exactly what browsers and operating systems? IE6 on XP, for example? There's no chart, which makes me hesitant.

If by "work" you mean do something interesting when one of the suggested words are typed, I can report it doesn't work on my up-to-date Ubuntu.

Re: Symbolset - symbol font using clever opentype ligature hack

#28

Having trouble figuring out the license ( http://symbolset.com/license/ ), specifically: "You may not under any circumstances embed the licensed fonts into software or hardware products in which the fonts will be used by the purchasers of such products." By that are they only restricting adding the font as a selectable font for writing (i.e. WYSIWYG editors) or can you not use the font in your own software in any cas…

Thanks for your comment, we'll clarify that in the license.

In short, the license covers your use in the software, websites, mobile apps, etc you create. The limitation is to prevent distribution to your software's users. For example, if your product was a CMS, you could embed SS in your app's UI, but you couldn't give it to your users to embed in their own websites without an extended license.

Re: Symbolset - symbol font using clever opentype ligature hack

#29

Having trouble figuring out the license ( http://symbolset.com/license/ ), specifically: "You may not under any circumstances embed the licensed fonts into software or hardware products in which the fonts will be used by the purchasers of such products." By that are they only restricting adding the font as a selectable font for writing (i.e. WYSIWYG editors) or can you not use the font in your own software in any cas…

Most font licenses get this badly wrong.

It LOOKS like they're trying to prevent WYSIWYG editors from using this font, but it also looks like they'd prevent me from adding it to an app I was shipping, by virtue of only allowing it to be embedded in a DOCUMENT.

Even most free font licenses get this wrong; they seem to WANT me to use it and redistribute it, but the way it's worded I can't. Sigh.

At least most new free fonts are using OFL now [1].

[1] http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&#38...

Re: Symbolset - symbol font using clever opentype ligature hack

#30
post #28

Having trouble figuring out the license ( http://symbolset.com/license/ ), specifically: "You may not under any circumstances embed the licensed fonts into software or hardware products in which the fonts will be used by the purchasers of such products." By that are they only restricting adding the font as a selectable font for writing (i.e. WYSIWYG editors) or can you not use the font in your own software in any cas…

Thanks for your comment, we'll clarify that in the license. In short, the license covers your use in the software, websites, mobile apps, etc you create. The limitation is to prevent distribution to your software's users. For example, if your product was a CMS, you could embed SS in your app's UI, but you couldn't give it to your users to embed in their own websites without an extended license.

The limitation is to prevent distribution to your software's users.

Isn't that an inherent requirement of using the font in software/websites/etc? If I have, say, an open source CMS, I'd have to ship the font somewhere with the code to be able to use it in the UI, no?

Post reply on HN