[9fans] fonts in plan9port

[9fans] fonts in plan9port

[Russ Cox]

On 12/30/05, Russ Cox <rsc@swtch.com> wrote:
> I would argue that distribution of the fonts with plan9port
> counts as being with the Plan 9 Operating System, since
> that's what plan9port is, just a port of the Plan 9 Operating System
> software to Unix systems.
>
> If you pulled the fonts out and distributed them with some
> other piece of software, that wouldn't be allowed.  But I think
> distribution with plan9port is fine.

The above argument was admittedly shaky.  With help from Rob,
I have obtained explicit permission from Bigelow & Holmes to
use and distribute the bitmap fonts with plan9port and to allow
others to do the same.  This should clear up any questions of
distributability of plan9port.

As part of the agreement, I renamed the font directories to avoid
the use of the name "Lucida".  If you have run cvs up recently, you
will have already noticed this.  There are three effects worth mentioning:

  - Old acme binaries, which refer to the lucidasans directory,
    will no longer run.  To fix this, simply recompile acme.

  - The fonts may be named in your acme.dump files.  If so,
    acme -l acme.dump will fail.  To fix this, edit acme.dump and
    ,s/lucida/luc/g.

  - You may need to edit your profiles or shell scripts if you use
    the -f or -F options to acme in scripts or shell functions.

Also as part of the agreement, the PostScript versions of the fonts
are no longer part of the distribution.  As a replacement, I have imported
Luxi Sans and Deja Vu Sans, both of which were freely available.
The typeset manual pages use Luxi Sans, but Deja Vu Sans has
broader Unicode support.

All these changes have been in the distribution for two weeks.
http://swtch.com/usr/local/plan9/CHANGES has a few more details.
See the March 19, 2006 entry.

Enjoy.
Russ

Re: [9fans] fonts in plan9port

[Paul Lalonde]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just did a cvs update, but I'm not pulling the new font
directories; in particular I'm not gettin lucsans.
What am I doing wrong?

Paul

On 3-Apr-06, at 9:21 PM, Russ Cox wrote:

> On 12/30/05, Russ Cox <rsc@swtch.com> wrote:
>> I would argue that distribution of the fonts with plan9port
>> counts as being with the Plan 9 Operating System, since
>> that's what plan9port is, just a port of the Plan 9 Operating System
>> software to Unix systems.
>>
>> If you pulled the fonts out and distributed them with some
>> other piece of software, that wouldn't be allowed.  But I think
>> distribution with plan9port is fine.
>
> The above argument was admittedly shaky.  With help from Rob,
> I have obtained explicit permission from Bigelow & Holmes to
> use and distribute the bitmap fonts with plan9port and to allow
> others to do the same.  This should clear up any questions of
> distributability of plan9port.
>
> As part of the agreement, I renamed the font directories to avoid
> the use of the name "Lucida".  If you have run cvs up recently, you
> will have already noticed this.  There are three effects worth
> mentioning:
>
>   - Old acme binaries, which refer to the lucidasans directory,
>     will no longer run.  To fix this, simply recompile acme.
>
>   - The fonts may be named in your acme.dump files.  If so,
>     acme -l acme.dump will fail.  To fix this, edit acme.dump and
>     ,s/lucida/luc/g.
>
>   - You may need to edit your profiles or shell scripts if you use
>     the -f or -F options to acme in scripts or shell functions.
>
> Also as part of the agreement, the PostScript versions of the fonts
> are no longer part of the distribution.  As a replacement, I have
> imported
> Luxi Sans and Deja Vu Sans, both of which were freely available.
> The typeset manual pages use Luxi Sans, but Deja Vu Sans has
> broader Unicode support.
>
> All these changes have been in the distribution for two weeks.
> http://swtch.com/usr/local/plan9/CHANGES has a few more details.
> See the March 19, 2006 entry.
>
> Enjoy.
> Russ

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEM/rYpJeHo/Fbu1wRAvMnAJ9r1vn0MhwtcmZbitKKmTbI3tgTFgCdEuQ4
4LgnSI0XKcy3Yg4izEimmlo=
=DTrF
-----END PGP SIGNATURE-----