Good point. I'll get some together tonight.
Great!
(Re: license) Open one up in a text editor and have a look!
The license looks just fine, BSD-like in nature. The only limitation is carrying forward the copyright notices, which is a fair exchange. Do be sure to put the Copyright Notices somewhere approriate in the change-file or font-files (if you build and distribute as a Font-Set, the comment arena is a good place for that).
COMMENT Copyright 1984-1989, 1994 Adobe Systems Incorporated. COMMENT Copyright 1988, 1994 Digital Equipment Corporation. COMMENT COMMENT Adobe is a trademark of Adobe Systems Incorporated which may be COMMENT registered in certain jurisdictions. COMMENT Permission to use these trademarks is hereby granted only in COMMENT association with the images described in this file. COMMENT COMMENT Permission to use, copy, modify, distribute and sell this software COMMENT and its documentation for any purpose and without fee is hereby COMMENT granted, provided that the above copyright notices appear in all COMMENT copies and that both those copyright notices and this permission COMMENT notice appear in supporting documentation, and that the names of COMMENT Adobe Systems and Digital Equipment Corporation not be used in COMMENT advertising or publicity pertaining to distribution of the software COMMENT without specific, written prior permission. Adobe Systems and COMMENT Digital Equipment Corporation make no representations about the COMMENT suitability of this software for any purpose. It is provided "as COMMENT is" without express or implied warranty.
-----Original Message----- From: MIME :nop@nop.com > Sent: Monday, January 31, 2000 10:45 AM To: squeak@cs.uiuc.edu Cc: squeak@cs.uiuc.edu Subject: Re: Computer Modern Fonts/Mach 2
"Andrew C. Greenberg" werdna@gate.net wrote at Monday, > January 31, 2000
9:29 AM:
At 8:48 AM -0500 1/31/2000, Jay Carlson wrote: What's the conversion path for these---how did they get > from Metafont
source
files to StrikeFont bitmaps? I've done some Metafont > hacking (a zillion years ago), and I'd like to try doing some fixups at the > source level.
For
instance, there are left-arrow and up-arrow glyphs in the > symbol sets,
and
the prime glyph might be ok as a single quote.
I tried to do this direct from Metafont, but while Metafont makes very decent printer fonts, it generates seriously groty 72 dpi fonts that unsuitable for serious use, and too weak for a pixel-by-pixel fixup. Yeah, that's been my experience too. :-/
Then, I used bitEdit to make glyphs for programming (<, >, > leftarrow,
|, curly braces) or corresponding size, and wrote some scripts to install them into the fonts in TextConstants. I then wrote another script to adjust the FontSets, and here we are. I suppose that could be automated by stealing characters from > the symbol
fonts, but that may be a lot of work to get right, visually.
Would anyone like the fonts from X11 as FontSets? I > figured it'd be
better
to publish the tools I used for conversion rather than > pure bitmaps, but even as three doIts in a class comment it's less convenient than a
unified
changeset.
Why choose? Do it both ways. Good point. I'll get some together tonight.
One thing though: are the X11 fonts subject to GPL (which,
regrettably is incompatible with Squeak)? My primary motivation for converting these fonts was to make it possible to remove the font limitations from the Squeak license of the general > distribution. I'd hate to see us move from one license problem directly to another. X11 is not covered by the GPL; it's covered by the MIT/DEC > X11 license. The
BDF sources are text files with comments in them giving > license information as well; the licenses are not word-for-word identical but are > very similar. Open one up in a text editor and have a look! http://wuarchive.wustl.edu/packages/X11R6.3/xc/fonts/bdf/75dpi
/helvR12.bdf
Jay
squeak-dev@lists.squeakfoundation.org