[GRASS-user] Freetype fonts in gis.m
glynn at gclements.plus.com
Fri Jun 9 16:10:24 EDT 2006
> > > D.font.freetype is not supported in gis.m. It became increasingly
> > > problematic on Mac (and Windows?) platforms.
> > It should still be possible to use it in a command layer.
> > The real issue is that the way that the command string is being
> > handled causes problems for arguments which contain spaces. I haven't
> > looked into why this is the case; with the "obvious" implementation,
> > it should be possible to use braces to prevent an argument being
> > split.
> are d.font.freetype and d.text.freetype getting confused here?
Yes. However, the problem with d.text.freetype is real.
> d.font.freetype usually won't have spaces unless the TTF directory has
> spaces in it.
> Do all the modules that can take SQL queries (with spaces) fail?
The issue is with the way that the command string is handled for
Glynn Clements <glynn at gclements.plus.com>
More information about the grass-user