[Slackbuilds-users] fonts from the Adobe Reader package
Greg' Ar Tourter
artourter at gmail.com
Tue May 1 22:36:44 UTC 2012
Thanks Doogster for these references, very interesting.
Indeed, after King Beowulf's response I looked closely at the eula and
concluded that one was not allowed to use the fonts (unless only for
yourself in documents you do not send around) So I gave up on the idea
of linking them on the system folder when releasing 9.5.1 (still in
As the typophile comments say, I also got the original idea from
TeX.SX where people seem to promote the idea of using the fonts
provided in Reader for documents.
On 25 April 2012 19:02, Doogster <thedoogster at gmail.com> wrote:
> Sorry for the late reply, but I actually did manage to find Adobe's
> official word on this:
> "The Adobe Reader license seems to not allow using the fonts for other
> purposes such as creating documents (unlike other Adobe licenses)."
> The author of that forum post is also the author of this blog entry:
> On Wed, Mar 21, 2012 at 9:31 PM, King Beowulf <kingbeowulf at gmail.com> wrote:
>> On Tue, Mar 20, 2012 at 10:23 AM, Greg' Ar Tourter <artourter at gmail.com>
>>> I am thinking of modifying the slackbuild script for Adobe Reader to
>>> add the fonts provided with it to the system's path, more specifically
>>> the otf fonts.
>>> The reason I wish to do this is that the Minion and myriad font are
>>> rather nice and used quite often by people in documents. The fonts
>>> have the same licence as the rest of the application and allows the
>>> user to use them and embed them in documents as they please.
>>> So my first question is: is it acceptable to do so? and the subsequent
>>> one being, if it is, should I just copy the fonts to
>>> /use/share/fonts/OTF or link them there?
>>> Thanks in advance for the feedback.
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - http://slackbuilds.org/faq/
>> I would say no. The Adobe Acrobat Reader fonts are subject to the Adobe
>> Acrobat Reader software EULA and I don't see a "do what you want clause."
>> There are some redistribution and usage issues and the EULA does not allow
>> you to do "as you please."
>> There are plenty of decent public domain, open source and creative commons
>> fonts if you are looking for document creation.
>> That said, as I am definitely not a lawyer (and I really do detest EULAs in
>> general), perhaps leave it to the user: include a switch with default of
>> "no" and link them for system wide installation.
>> You! What PLANET is this!
>> -- McCoy, "The City on the Edge of Forever", stardate 3134.0
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
More information about the SlackBuilds-users