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

[Moritz Lennert]

Glynn Clements via RT wrote:
> Request Tracker wrote:
> 
>> this bug's URL: http://intevation.de/rt/webrt?serial_num=4905
> 
>> Subject: gis.m: d.text.freetype does not allow spaces in text
> 
>> As the postscript text layers do not survive saving the map display
>> to a graphics file, I am trying to use d.text.freetype as a command.
>>
>> This works perfectly until the text I want to display contains
>> spaces. When I use the following command line:
>>
>> d.text.freetype -n -b text="Population totale" east_north=2,95 size=3 col=black path=/usr/share/fonts/truetype/ttf-bitstream-vera/Vera.ttf
>>
>> I get:
>>
>> Sorry <totale"> is not a valid option
>>
>> I have tried with single quotes and brackets, but I get the same error.
> 
> Using braces works, i.e.
> 
> 	d.text.freetype -n -b {text=Population totale} ...
> 
> There doesn't appear to actually be a space, but the same problem
> occurs when running d.text.freetype from the command line, i.e. it's a
> problem with d.text.freetype.

Actually, the fact that the space is missing it is a problem with 
freetype 2.2.1:

http://lists.gnu.org/archive/html/freetype/2006-07/msg00009.html

So apparently not much we can do about it, just have to wait for the fix 
to propagate to distributions or tell people to compile the cvs version ...

Unless we can use ft_render_mode_normal, instead of ft_render_mode_mono, 
but trying that I just get completely garbled output on the screen, and 
I don't have the time now to look into this any further.

Moritz