[GRASS-user] Freetype fonts in gis.m

[Hamish]

> > 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?

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?



Hamish