This bit of CSS from flickr.css:

@media screen {
  @font-face {
    font-family: 'CC-ICONS';
    font-style: normal;
    font-weight: normal;
    src: url('http://mirrors.creativecommons.org/presskit/cc-icons.ttf') format('truetype');
  }

Results in this request from IE 8:

GET /presskit/cc-icons.ttf')%20format('truetype HTTP/1.1
Accept: */*
Referer: http://zero1.org/
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; PTST 2.375)
Accept-Encoding: gzip, deflate
Host: mirrors.creativecommons.org
Connection: Keep-Alive

Obviously that's a 404.

Not sure if IE 8 is something the maintainers care about, but it seems like an inadvertent mini-ddos on creativecommons.org. :-)

Ironically, the creative commons license font isn't GNU, so it can't be packaged directly in a Drupal module. http://creativecommons.org/about/downloads

Comments

lolandese’s picture

Version: 7.x-1.x-dev » 7.x-1.3

Ironically, the creative commons license font isn't GNU, so it can't be packaged directly in a Drupal module.

Oops! Just packaged the font two weeks ago (only in the dev version for now), mainly to avoid using creativecommons.org's resources.

I could make a request to extend/change the license to GNU, on the other hand I don't want to poke the bear.

Any suggestions?

Thanks.

mile23’s picture

I think the constraints come from drupal.org, where everything is assumed to be GNU. I would assume that the Creative Commons icons are licensed as Creative Commons. :-) Not sure if these two things are compatible.

lolandese’s picture

Status: Active » Postponed
Related issues: +#2176433: Add optionally license info
StatusFileSize
new5.46 KB

Formally only CC0 is compatible with the GNU GPL. That means that the font can't be hosted on D.O. until it is licensed under GNU GPL. See https://drupal.org/node/422996. Attached patch removes the font and uses the mirror on creativecommons.org instead. Committed. See http://drupalcode.org/project/flickr.git/commitdiff/6372b10.

I have made a request at metadata@creativecommons.org to change the license to allow inclusion of the font on D.O. (the only reliable and user friendly solution). Postponed until we get an answer. Meanwhile solve the IE8 problem by including the font manually from http://creativecommons.org/about/downloads.

A similar post: https://drupal.org/node/907520.

Some info about CC0 - GNU compatibility:
http://creativecommons.org/tag/gpl
http://www.gnu.org/licenses/license-list.html#CC0

Thanks.

mile23’s picture

Thanks, lolandese!

lolandese’s picture

I wrote an additional mail to creativecommons.org with the request to at least release the cc-icons font under CC-0 which is GPL compatible (see http://www.gnu.org/licenses/license-list.html#CC0). Now it is licensed CC-4.0 as mentioned in the site footer.

Compatible licenses should be allowed on Drupal.org's repository (see https://drupal.org/licensing/faq#q7). I guess it's in the same boat as the MIT licensed Symfony code that is included in Drupal 8.

If the license of the cc-icons font is not changed within the coming weeks, I will add a note to the project page and/or documentation describing:

  • in what circumstances a local copy of the cc-icons font is needed
  • where the font can be downloaded
  • in what folder it should be placed
  • how the module code should be altered to make use of the local copy.

Additionally a custom drush command could be built to include in the module.
Meanwhile feel free to submit a patch for this and/or add/edit documentation.

Thanks.

lolandese’s picture

Please note #2308099: Conflict with respond.js on IE8 that points to the font being inside the media query as the culprit when using respond.js. See if the patch there helps.

We had an answer 4 months ago from Creative Commons that they intend to release the font under CC-0 (GPL compatible). The tech people there had to convince the legal people. Tried to remind them a couple of times but never had another answer.

lolandese’s picture

Status: Postponed » Closed (duplicate)
Related issues: +#2308099: Conflict with respond.js on IE8

Likely a duplicate of #2308099: Conflict with respond.js on IE8.

Although this issue is older, the other one contains a patch that might solve this issue.

Please review it there.

Thanks.