Hi, Dave, On Fri, Nov 14, 2008 at 6:59 AM, Dave Crossland <[EMAIL PROTECTED]> wrote: > It seems fonts developed in sourceforge like systems may not be able > to support font linking at all, or only from their own sites. > > So, as policy, should we (via moderation) accept all Free Software licenses?
Ed Trager: Yes. Question: Are all of these licenses OSI-recognized? Maybe we could have OSI-recognized license tags in one color and non-OSI-recognized tags in some other color or something like that? > > I'd like a "show of hands" - Please reply with your name and then > "yes" or "no" - we can then debate the "no"s :-) > > Dave Crossland: Yes > > ---------- Forwarded message ---------- > From: Ben Laenen <[EMAIL PROTECTED]> > Date: 2008/11/11 > Subject: Re: [DejaVu-fonts] Open Font Library wants to host your fonts > for @font-face web > To: [EMAIL PROTECTED] > Cc: Dave Crossland <[EMAIL PROTECTED]> > > > On Tuesday 11 November 2008, Dave Crossland wrote: >> Hi! >> >> Last week, "Hendry" asked on IRC if the DejaVu TTF were on a central >> website so that they would be easily linkable via @font-face CSS. > > Nope, sourceforge doesn't allow direct linking of files (it can only go > through their file release system), so we need another location like > OFLB. > > btw, wasn't there a built-in restriction for font linking in the > browsers that support @font-face which limits font linking to the same > domain as the webpage? > > Ben > > > > > ---------- Forwarded message ---------- > From: Dave Crossland <[EMAIL PROTECTED]> > Date: 2008/11/14 > Subject: Re: [DejaVu-fonts] Open Font Library wants to host your fonts > for @font-face web > To: Ben Laenen <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > > > 2008/11/11 Ben Laenen <[EMAIL PROTECTED]>: >> >> btw, wasn't there a built-in restriction for font linking in the >> browsers that support @font-face which limits font linking to the same >> domain as the webpage? > > Firefox has this, and sites must configure their HTTPDs if they want > to allow cross-site fonts. OFLB will do this as soon as FF implements > the feature (currently its turned on and can only be turned off by > users configuring FF to not do it always, but thats because its in > development) >
