[GRASS-dev] helpful error messages

Gerald Nelson gnelson at uiuc.edu
Sun Apr 29 18:15:39 EDT 2007

I don't often get a chance to have input to hard core code development so this may be a naive request, but...

can I enter a request for error messages generally, and from the catch code being discussed in particular, that are verbose and provide some indication of the likely source of the problem. Or when the source could be a variety of things, a list of possible problems?



---- Original message ----
>Date: Sun, 29 Apr 2007 23:01:15 +0100
>From: Glynn Clements <glynn at gclements.plus.com>  
>Subject: Re: [GRASS-dev] figuring out fonts - part 2  
>To: Michael Barton <michael.barton at asu.edu>
>Cc: GRASS developers list <grass-dev at grass.itc.it>
>Michael Barton wrote:
>> It is a good thing that GRASS has a set of fonts that can be guaranteed to
>> be present, regardless of the system. These are the venerable stroke fonts.
>> But these fonts are ugly and hard to read. Romans just doesn¹t stand out
>> well in a scale or legend, for example, unless against a white background
>> and even then it is not clear at a distance for presentations.
>> So here is a question. Can GRASS ship with a better set of fonts? Can it
>> come with a minimal TrueType set, for example, that could be guaranteed
>> present regardless of the system? Or is this technically not realistically
>> feasible?
>Support for TrueType fonts requires the FreeType library, which is
>currently an optional dependency.
>That aside, most people will already have the Luxi font from the X.org
>Glynn Clements <glynn at gclements.plus.com>
>grass-dev mailing list
>grass-dev at grass.itc.it
Gerald Nelson
Professor, Dept. of Agricultural and Consumer Economics
University of Illinois, Urbana-Champaign
office: 217-333-6465 
cell: 217-390-7888
315 Mumford Hall
1301 W. Gregory
Urbana, IL 61801

More information about the grass-dev mailing list