From: list at eworm.de (Christian Hesse)
Subject: [PATCH 1/1] css: use less blurry icon for external link
Date: Tue, 23 Feb 2016 11:14:39 +0100 [thread overview]
Message-ID: <20160223111439.02b657a7@leda.localdomain> (raw)
In-Reply-To: <20160223100707.GG1766@serenity.lan>
John Keeping <john at keeping.me.uk> on Tue, 2016/02/23 10:07:
> On Tue, Feb 23, 2016 at 10:47:25AM +0100, Christian Hesse wrote:
> > Your mileage may vary, but for me the old icon looks blurry. The new
> > one is character 0xf08e from OTF font awsome in size 10.
> > The icon color is black, gray level is adjusted via opacity.
>
> What's the licensing status of individual glyphs from Font Awesome?
> IANAL but my reading of the OFL is that it's not compatible with the
> GPL.
What we have is the icon from awesome font, no?
Probably scaled down from one of the example images?
http://fortawesome.github.io/Font-Awesome/icon/external-link/
> The nice thing about the icon from Wikipedia is that it's already
> licensed under the GPLv2 so we don't have to worry about whether it's
> compatible (although it might be a good idea to credit the source in a
> comment).
The wikipedia icon looks different.
https://commons.wikimedia.org/wiki/File:Icon_External_Link.png
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20160223/7556e876/attachment.asc>
next prev parent reply other threads:[~2016-02-23 10:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 9:47 list
2016-02-23 10:07 ` john
2016-02-23 10:14 ` list [this message]
2016-02-23 10:20 ` john
2016-02-23 14:19 ` Jason
2016-02-23 14:18 ` Jason
2016-02-23 14:44 ` list
2016-02-23 15:03 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160223111439.02b657a7@leda.localdomain \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).