I’m trying to find out if this is a general issue, a Mac problem, or just a problem with my stuff.
It used to be that whenever I displayed anything with text, it would default to Romans unless I set the font to something else.
Now, displaying something with text displays NOTHING at all unless I manually set the font globally (config menu) or in a particular module.
Is anyone else seeing this? Or is it just me?
Michael
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
On Sun, November 18, 2007 06:02, Michael Barton wrote:
I'm trying to find out if this is a general issue, a Mac problem, or just
a
problem with my stuff.
It used to be that whenever I displayed anything with text, it would
default
to Romans unless I set the font to something else.
Now, displaying something with text displays NOTHING at all unless I
manually set the font globally (config menu) or in a particular module.
Is anyone else seeing this? Or is it just me?
We had the same problem in wingrass and it was due to etc/fontcap not
being correctly written during install (wrong path names). Running
g.mkfontcap in ant open grass session solved the problem.
Michael Barton wrote:
> I'm trying to find out if this is a general issue, a Mac problem, or just
> a problem with my stuff.
>
> It used to be that whenever I displayed anything with text, it would
> default to Romans unless I set the font to something else.
>
> Now, displaying something with text displays NOTHING at all unless I
> manually set the font globally (config menu) or in a particular module.
>
> Is anyone else seeing this? Or is it just me?
Moritz Lennert wrote:
We had the same problem in wingrass and it was due to etc/fontcap not
being correctly written during install (wrong path names). Running
g.mkfontcap in ant open grass session solved the problem.
this suggests a need for a fail-safe fallover to a default value (romans) on
error, instead of setting the font to "".
Hamish
____________________________________________________________________________________
Get easy, one-click access to your favorites.
Make Yahoo! your homepage. http://www.yahoo.com/r/hs
> We had the same problem in wingrass and it was due to etc/fontcap not
> being correctly written during install (wrong path names). Running
> g.mkfontcap in ant open grass session solved the problem.
this suggests a need for a fail-safe fallover to a default value (romans) on
error, instead of setting the font to "".
The problem is that the code which initialises the font doesn't work
if etc/fontcap doesn't have an entry for "romans".
In my case, fontcap is correctly produced, but nothing is selected
apparently.
Michael
On 11/18/07 4:52 AM, "Hamish" <hamish_nospam@yahoo.com> wrote:
Michael Barton wrote:
I'm trying to find out if this is a general issue, a Mac problem, or just
a problem with my stuff.
It used to be that whenever I displayed anything with text, it would
default to Romans unless I set the font to something else.
Now, displaying something with text displays NOTHING at all unless I
manually set the font globally (config menu) or in a particular module.
Is anyone else seeing this? Or is it just me?
Moritz Lennert wrote:
We had the same problem in wingrass and it was due to etc/fontcap not
being correctly written during install (wrong path names). Running
g.mkfontcap in ant open grass session solved the problem.
this suggests a need for a fail-safe fallover to a default value (romans) on
error, instead of setting the font to "".
Hamish
______________________________________________________________________________
______
Get easy, one-click access to your favorites.
Make Yahoo! your homepage. http://www.yahoo.com/r/hs
__________________________________________
Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University