Re: [Freefont-bugs] Font licensing
Hi Rick, The built binary package contains what you want. They are at http://ftp.gnu.org/gnu/freefont/ Note that for Windows you should use the TTF package, otherwise, the OTF package. The least risky approach will be to deliver the entire package contents as-is. As I said, just make sure your customer can see everything, and make it clear to them what it is. Yes, the last official release was in 2012. Sorry about that. On Sun, Sep 15, 2019 at 4:18 AM Rick Marczak via Freefont-bugs wrote: > > Do I need to include a special ReadMe file or something in the folder that I > put the font in? > > > > Sent from Mail for Windows 10 > > > > From: Steve White > Sent: Saturday, September 14, 2019 5:09 AM > To: lpdirectdraw7 > Cc: freefont-bugs@gnu.org > Subject: Re: [Freefont-bugs] Font licensing > > > > Hi, > > > > The following is my opinion on the subject: > > > > In delivering the font or any part of it, it is crucial that you make > > absolutely obvious to your customer that GNU FreeFont is a separate > > product, that it is free software available elsewhere, and that you > > provide the GNU FreeFont documents to the customer in an absolutely > > transparent way. > > > > It should be adequate to place GNU FreeFont and all its documents in > > separate folder in whatever delivery media you use, in such a way that > > the customer will easily see it and be able to read the documents. If > > your software installs or copies the GNU FreeFont software into the > > customer's system, the software should inform the customer that it is > > doing so, that GNU FreeFont is free software available elsewher, and > > where the customer can find the documents of GNU FreeFont. > > > > You must not insert GNU FreeFont or any part or modification of it > > into the binary files of your non-free product (that would be > > "embedding"). GNU FreeFont must in no way be used as "a part" of your > > product. You must not deliver GNU FreeFont or any modification of it > > without making it absolutely clear to your customer that they have > > received GNU FreeFont. You must not obscure the fact in any way that > > GNU FreeFont is free sofware available elsewhere, or obscure its > > documentation. > > > > Let us know if you have any further questions! > > > > On Fri, Sep 13, 2019 at 7:59 PM lpdirectdraw7 via Freefont-bugs > > wrote: > > > > > > I am looking to build a for profit video game. The faq says that i can > > bundle the font with my software but not embed. What is the difference > > between bundling and embedding? > > > > > > > > > > > > Sent from my Samsung Galaxy smartphone. > >
Re: [Freefont-bugs] Font licensing
Do I need to include a special ReadMe file or something in the folder that I put the font in? Sent from Mail for Windows 10 From: Steve White Sent: Saturday, September 14, 2019 5:09 AM To: lpdirectdraw7 Cc: freefont-bugs@gnu.org Subject: Re: [Freefont-bugs] Font licensing Hi, The following is my opinion on the subject: In delivering the font or any part of it, it is crucial that you make absolutely obvious to your customer that GNU FreeFont is a separate product, that it is free software available elsewhere, and that you provide the GNU FreeFont documents to the customer in an absolutely transparent way. It should be adequate to place GNU FreeFont and all its documents in separate folder in whatever delivery media you use, in such a way that the customer will easily see it and be able to read the documents. If your software installs or copies the GNU FreeFont software into the customer's system, the software should inform the customer that it is doing so, that GNU FreeFont is free software available elsewher, and where the customer can find the documents of GNU FreeFont. You must not insert GNU FreeFont or any part or modification of it into the binary files of your non-free product (that would be "embedding"). GNU FreeFont must in no way be used as "a part" of your product. You must not deliver GNU FreeFont or any modification of it without making it absolutely clear to your customer that they have received GNU FreeFont. You must not obscure the fact in any way that GNU FreeFont is free sofware available elsewhere, or obscure its documentation. Let us know if you have any further questions! On Fri, Sep 13, 2019 at 7:59 PM lpdirectdraw7 via Freefont-bugs wrote: > > I am looking to build a for profit video game. The faq says that i can bundle > the font with my software but not embed. What is the difference between > bundling and embedding? > > > > Sent from my Samsung Galaxy smartphone.
Re: [Freefont-bugs] Font licensing
Do I need to include a special ReadMe file or something in the folder that I put the font in? Sent from Mail for Windows 10 From: Steve White Sent: Saturday, September 14, 2019 5:09 AM To: lpdirectdraw7 Cc: freefont-bugs@gnu.org Subject: Re: [Freefont-bugs] Font licensing Hi, The following is my opinion on the subject: In delivering the font or any part of it, it is crucial that you make absolutely obvious to your customer that GNU FreeFont is a separate product, that it is free software available elsewhere, and that you provide the GNU FreeFont documents to the customer in an absolutely transparent way. It should be adequate to place GNU FreeFont and all its documents in separate folder in whatever delivery media you use, in such a way that the customer will easily see it and be able to read the documents. If your software installs or copies the GNU FreeFont software into the customer's system, the software should inform the customer that it is doing so, that GNU FreeFont is free software available elsewher, and where the customer can find the documents of GNU FreeFont. You must not insert GNU FreeFont or any part or modification of it into the binary files of your non-free product (that would be "embedding"). GNU FreeFont must in no way be used as "a part" of your product. You must not deliver GNU FreeFont or any modification of it without making it absolutely clear to your customer that they have received GNU FreeFont. You must not obscure the fact in any way that GNU FreeFont is free sofware available elsewhere, or obscure its documentation. Let us know if you have any further questions! On Fri, Sep 13, 2019 at 7:59 PM lpdirectdraw7 via Freefont-bugs wrote: > > I am looking to build a for profit video game. The faq says that i can bundle > the font with my software but not embed. What is the difference between > bundling and embedding? > > > > Sent from my Samsung Galaxy smartphone.
Re: [Freefont-bugs] Font licensing
Hi, The following is my opinion on the subject: In delivering the font or any part of it, it is crucial that you make absolutely obvious to your customer that GNU FreeFont is a separate product, that it is free software available elsewhere, and that you provide the GNU FreeFont documents to the customer in an absolutely transparent way. It should be adequate to place GNU FreeFont and all its documents in separate folder in whatever delivery media you use, in such a way that the customer will easily see it and be able to read the documents. If your software installs or copies the GNU FreeFont software into the customer's system, the software should inform the customer that it is doing so, that GNU FreeFont is free software available elsewher, and where the customer can find the documents of GNU FreeFont. You must not insert GNU FreeFont or any part or modification of it into the binary files of your non-free product (that would be "embedding"). GNU FreeFont must in no way be used as "a part" of your product. You must not deliver GNU FreeFont or any modification of it without making it absolutely clear to your customer that they have received GNU FreeFont. You must not obscure the fact in any way that GNU FreeFont is free sofware available elsewhere, or obscure its documentation. Let us know if you have any further questions! On Fri, Sep 13, 2019 at 7:59 PM lpdirectdraw7 via Freefont-bugs wrote: > > I am looking to build a for profit video game. The faq says that i can bundle > the font with my software but not embed. What is the difference between > bundling and embedding? > > > > Sent from my Samsung Galaxy smartphone.
