Hi,
Dave Crossland wrote:
> 1. TTF/OTF font files are licensed individually (or rather, each has a
> license field)
> 2. CCHost's upload form prompts the user to specify a license per typeface
> record
>
> I think 2. is actually desirable from a user point of view but 1. is what's
> in the files (and is quicker - no box to tick).
2 is desirable if we were going to modify the license metadata inside
the fonts during the upload process, overwriting with what is
specified in the form.
But since we're in no position to be doing that, at least not atm, we
must do 1.
OK, that sounds sensible. So I should
* remove the input field from the upload form
* print a list of the 1.. n licenses with their logo/s, based on what I
find in the font files
* perhaps print the license for each font file next to its name in the
download list
> I already implemented a check that blocks uploaded files with incompatible
> licenses
What are your compatibility criteria?
Fontaine supplies, and I hope will continue to supply, those criteria.
It’s useful to have this single point of reference.
Dave also wrote:
I think its better if we limit the upload form to those 3 licenses,
and to TTF/OTFs, but allow fonts with other free licenses and in other
formats to be uploaded carefully by hand by site admins.
Fair enough, although that might be awkward. I think ccHost can look in
its admins list and waive the checks.
.pfa and .pfb are probably currently enabled. Would somebody like to
roll a Type 1 and try it?
Cheers,
Ben
--
Ben Weiner | http://readingtype.org.uk/about/contact.html
