<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=US-ASCII" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18939"></HEAD>
<BODY style="FONT-FAMILY: Arial; COLOR: #000000; FONT-SIZE: 10pt" id=role_body
bottomMargin=7 leftMargin=7 rightMargin=7 topMargin=7><FONT id=role_document
color=#000000 size=2 face=Arial>
<DIV>>There is now a WOFF entry:<BR>><BR>>- - - 8< - -
-<BR>><BR>>Question: 2.2 Can I make and use WOFF (Web Open Font Format)
versions<BR>>of OFL fonts?<BR>><BR>>Answer: Yes, but you need to be
careful. A change in font format<BR>>normally is considered modification, and
Reserved Font Names (RFNs)<BR>>cannot be used. Because of the design of the
WOFF format, however, it<BR>>is possible to create a WOFF version that is not
considered<BR>>modification, and so would not require a name change. You are
allowed<BR>>to create, use and distribute a WOFF version of an OFL font
without<BR>>changing the font name, but only if:<BR>><BR>>the original
font data remains unchanged except for WOFF compression,
and<BR>>WOFF-specific metadata is either omitted altogether or present
and<BR>>includes, unaltered, the contents of all equivalent metadata in
the<BR>>original font.<BR>>If the original font data or metadata is
changed, or the WOFF-specific<BR>>metadata is incomplete, the font must be
considered a Modified<BR>>Version, the OFL restrictions would apply and the
name of the font<BR>>must be changed: any RFNs cannot be used and copyright
notices and<BR>>licensing information must be included and cannot be deleted
or<BR>>modified. You must come up with a unique name - we recommend
one<BR>>corresponding to your domain or your particular web application.
Be<BR>>aware that only the original author(s) can use RFNs. This is
to<BR>>prevent collisions between a derivative tuned to your audience and
the<BR>>original upstream version and so to reduce
confusion.<BR>><BR>>Please note that most WOFF conversion tools and online
services do not<BR>>meet the two requirements listed above, and so their
output must be<BR>>considered a Modified Version. So be very careful and
check to be sure<BR>>that the tool or service you're using is compressing
unchanged data<BR>>and completely and accurately reflecting the original font
metadata.<BR>><BR>>Question: 2.3 What about other webfont formats such as
EOT/EOTLite/CWT/etc.?<BR>><BR>>Answer: In most cases these formats alter
the original font data more<BR>>than WOFF, and do not completely support
appropriate metadata, so<BR>>their use must be considered modification and
RFNs may not be used.<BR>><BR>>- - - 8< - - -<BR>><BR>>Thanks to
Nicolas Spalinger for all his great work on the SIL OFL
:-)<BR>><BR>>Cheers<BR>>Dave</DIV>
<DIV> </DIV>
<DIV>This gives me a website (and project) idea:</DIV>
<DIV> </DIV>
<DIV>Someone should make a website which has all the open fonts from the
openfontlibrary in woff and eot and svg files (one for each individual
glyph).</DIV>
<DIV> </DIV>
<DIV>It would be a big batch conversion project, and you would have to follow
the requirements outlined for the SIL OFL fonts (but not the public
domain fonts) but it would be worth doing. You should follow SIL's
requirements even when working with the public domain fonts as to not create
confusion or two different ways of doing the same thing. One key thing to do:
Make sure the font's license is embedded in the new file in the other format. I
assert that any distribution of a SIL OFL font by anyone without that
license embedded in the newly converted file would be a violation of
the SIL OFL, *IF* that file's format is capable of having a
license entry.</DIV>
<DIV>Likewise, The text of the Creative Commons Public Domain Dedication needs
to be embedded in the converted fonts which are dedicated to the Public Domain.
DO NOT distribute any without it.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Eric Way</DIV></FONT></BODY></HTML>