> > o You may not pretend that you wrote this software. If you use
> > it, or only parts of it, in a program, you must acknowledge
> > somewhere in your documentation that you have used the FreeType
> > code. (`credits')
>
> Can I request a clarification of what you expect for this, both in
> terms of wording/content, and also what types of "documentation"
> need this content? (Note this is coming from the perspective of a
> Commercial product)
Mhmm, we don't have anything more specific.
> Is it enough to include relevant information in some sort of
> 'credits' file within the actual installation/distribution?
This is OK.
> Or is the end-user required to actually *see* the credit, implying
> it would need to be in the 'About' dialog, or the EULA (Assuming
> people actually read those ;) ), or something similar?
This would be even better.
> What about marketing brochures,
No. I don't consider such brochures `documentation' :-)
> websites,
Maybe.
> Or is the requirement only for _users_ (Meaning someone who has
> actually bought a copy of the Commercial software)?
Where's the difference?
> Is something like "Built using FreeType2" enough, or does it need to
> include purpose/usage, version information, URLs, FT license, etc?
The more info, the better.
Werner
_______________________________________________
Freetype mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype
