[GRASS-dev] font path question for Linux and Windows

Michael Barton michael.barton at asu.edu
Wed May 2 00:29:25 EDT 2007


I tried various fonts randomly on my Mac without regard to extension and (so
far) all of them worked. So I assume that they are TrueType or FreeType
compatible in some way.

Michael


On 5/1/07 7:18 PM, "Glynn Clements" <glynn at gclements.plus.com> wrote:

> 
> William Kyngesburye wrote:
> 
>> I just had a chance to check OSX 10.3 (Panther) X11 - fontconfig is
>> present.  For OSX Panther, X11 is v1.0, before that (OSX 10.2 and
>> below) it was a beta and is not available for download any more, as
>> far as I can tell.  I think the betas must be where fontconfig wasn't
>> a part of Apple's X11 package (and I'm sure it wasn't at first).
>> 
>> So, using fc-list on OSX, if it's available, for mkftcap is
>> reasonable, for now.
> 
> Is it possible to filter any non-TrueType fonts from the output? Or
> are there not enough TrueType fonts to worry about?
> 
> We can probably tolerate a few bogus entries in an auto-generated
> freetypecap file; the user can always remove entries which don't work.
> However, on my system, "fc-list :outline file" generates 102 entries;
> 51 are .ttf files and 51 are .pfa/.pfb files, which is too high a
> signal-to-noise ratio.
> 
> That doesn't matter on Linux, as I can just ignore anything which
> doesn't have a .ttf extension. For OSX, we'll need to find some other
> way unless the number of false positives in the original fc-list
> output is low.

__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton





More information about the grass-dev mailing list