[GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text

[Huidae Cho]

On Fri, Sep 01, 2006 at 10:25:23PM +0100, Glynn Clements wrote:
> 
> Huidae Cho wrote:
> 
> > Removing the font_hold variable from lib/driver affects the behaviour of
> > freetype fonts.  All modules with font= option still assume "romans" as
> > default font and it keeps the user from using freetype fonts with them.
> > 
> > d.font font=luximr
> > d.vect map=vector_map
> > 
> > will use "romans" not "luximr". Maybe we need to use GRASS_FT_*
> > GRASS_FONT varibles to let d.* modules know the default font the user
> > wants.
> 
> That's a bug in the module. If the user doesn't explicitly specify a
> font, the module should use the current font, not some arbitrary
> default. Especially as any setting which the module makes will persist
> for subsequent modules.
> 
> If you can identify specific modules which behave this way, I'll fix
> them (starting with d.vect).
> 
> > Adding R_get_font_list() would be great. Its code can be simply cut and
> > pasted from d.font.
> 
> I'm not sure that's a good idea. If we were to replace freetype with a
> font path, the list could become huge (my WinXP system has 120 .ttf
> files in C:/WINDOWS/Fonts, and that's just what comes with the OS or
> with other packages which I've installed; I haven't explicitly
> installed any additional fonts).

I didn't mean to list all fonts in the system. Instead, showing the list
of freetypecap fonts and stroke fonts will be enough like d.font does.

> 
> Instead, I'd suggest just removing the ->options field.

Yes, it's sometimes annoying, sometimes useful. Having separate font=
and path= options looks ugly.

Huidae