<div dir="ltr">Note: I've added the Ubuntu Font License (UFL) to that list. It is SIL-OFL, modified to ensure the font stays open/free even if embedded in an application, and then extracted again. <div><br></div><div><br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jul 13, 2013 at 7:28 AM, carolina poena <span dir="ltr"><<a href="mailto:myazalea@hotmail.com" target="_blank">myazalea@hotmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">yeah it's tricky... so as long as they "allow thier usage on sites" -it doesnt have to be one of these? <br>What if theme is GPL2 and font GPL3? <br> <br>Fonts bundled with Themes submitted to the WordPress Theme directory are <b>required</b> to be licensed under one of the following font licenses:<br>
<ul><li>Arphic Public License (Arphic)</li><li>Baekmuk License (Baekmuk)</li><li>Bitstream Vera License (Bitstream Vera)</li><li>GNU GPL (with font exception) (GPL)</li><li>GUST e-Foundry Font License/LaTeX Project Public License (LPPL)</li>
<li>IPA Font License (IPA)</li><li>Liberation Font License (Liberation)</li><li>LaTeX Project Public License (LPPL)</li><li>mplus Font License (mplus)</li><li>ParaType Font License (PTFL)</li><li>SIL Open Font License (OFL)</li>
<li>STIX Fonts User License (STIX)</li><li>Wadalab Fonts License (Wadalab)</li><li>XANO Mincho Font License (XANO)<br> </li></ul> <br> <br> <br><div>> From: <a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a><br>
> Date: Sat, 13 Jul 2013 06:16:13 -0500<div><div class="h5"><br>> To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>> Subject: Re: [theme-reviewers] bundled resources<br>
> <br>> I'd say it is fine to optionally use fonts from public resources like<br>> Google Fonts and similar. However, yes, the theme needs to link to<br>> something about that font somewhere. This something should both be a<br>
> credit page, as well as stating what license the font is available<br>> under.<br>> <br>> For example, if a theme used Open Sans from Google Fonts, then I'd<br>> expect it to have a link in comments or the readme.txt file to<br>
> <a href="http://www.google.com/fonts/specimen/Open+Sans" target="_blank">http://www.google.com/fonts/specimen/Open+Sans</a> , which states where<br>> the font came from as well as the Apache License it's available under.<br>
> <br>> Font licensing can be complex and tricky, so it's important that fonts<br>> used by themes have licenses which allow their usage on sites.<br>> <br>> Additionally, note that not every web user can see fonts from<br>
> third-party sites, so appropriate fallbacks should be coded into the<br>> CSS to allow for more "default" fonts to be used as well.<br>> <br>> -Otto<br>> <br>> <br>> On Sat, Jul 13, 2013 at 5:22 AM, carolina poena <<a href="mailto:myazalea@hotmail.com" target="_blank">myazalea@hotmail.com</a>> wrote:<br>
> > A question from a recent ticket:<br>> > "the reviewer asked for including font license, but the theme doesn't bundle<br>> > or distribute the fonts?"<br>> ><br>> ><br>> > -Are enqueued fonts not to be treated the same as fonts that are actually<br>
> > included in the themes folders?<br>> ><br>> ><br>> ><br>> > ________________________________<br>> > Date: Thu, 11 Jul 2013 13:58:44 -0400<br>> > From: <a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a><br>
> > To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>> > Subject: Re: [theme-reviewers] bundled resources<br>> ><br>> ><br>> > Nope; that is sufficient. It just needs to be included in the Theme.<br>
> ><br>> ><br>> > On Thu, Jul 11, 2013 at 1:57 PM, carolina poena <<a href="mailto:myazalea@hotmail.com" target="_blank">myazalea@hotmail.com</a>><br>> > wrote:<br>> ><br>> > Is it not enough if the bundled resource (when applicable) state their<br>
> > copryright and license at the top of their file? Does it still need to be<br>> > stated in a seperate readme file?<br>> ><br>> ><br>> > _______________________________________________<br>
> > theme-reviewers mailing list<br>> > <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>> > <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
> ><br>> ><br>> ><br>> > _______________________________________________ theme-reviewers mailing list<br>> > <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
> > <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>> ><br>> > _______________________________________________<br>
> > theme-reviewers mailing list<br>> > <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>> > <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
> ><br>> _______________________________________________<br>> theme-reviewers mailing list<br>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br></div></div></div> </div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>