OFL.txt doesn't include copyright notice

[Dave Crossland]

The OFL.txt in the News Cycle BZR tree has this template text at the top:

  Copyright (c) <dates>, <Copyright Holder> (<URL|email>),
  with Reserved Font Name <Reserved Font Name>.
  Copyright (c) <dates>, <additional Copyright Holder> (<URL|email>),
  with Reserved Font Name <additional Reserved Font Name>.
  Copyright (c) <dates>, <additional Copyright Holder> (<URL|email>).

I kindly suggest that it be:

  Copyright (c) 2010, 2011 Nathan Willis (<email address hidden>),
  with Reserved Font Name "News Cycle".

[Dave Crossland (davelab6)]

Or, if you intend this to be a community project, to not use a RFN :)

[Nathan Willis (n8)]

Kinda surprised that FontForge doesn't populate those fields with the info already in Font Info (PS Names / TTF Names etc.)....

[Nathan Willis (n8)]

Fixed in trunk/revision/9

[Nicolas Spalinger (yosch)]

Dave, saying that font projects using RFN(s) are not community-friendly is rather disingenuous.

Even if you'd prefer to ignore it a huge number of prominent FLOSS projects have naming and branding restrictions.

Even if you'd like to deny it or make it disappear, RFNs are a key feature of the OFL licensing model and are being used successfully in the vast majority of open font projects. Authors can choose not to use them but saying that it would be more community-friendly is seriously misleading.

See section 5 of the OFL FAQ for all the details.

[Dave Crossland (davelab6)]

The vast majority of open font projects are not collaborative.

For a 'wiki style' collaboration, I don't see how a RFN can be used,
since all the different branches of development would use the RFN
stem?