Details Ticket 4905


Comment | Reply | Take | Open


Serial Number 4905
Subject gis.m: d.text.freetype does not allow spaces in text
Area grass6
Queue grass
Requestors mlennert@club.worldonline.be
Owner none
Status resolved
Last User Contact Wed May 9 19:27:08 2007 (1 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Sat May 12 12:39:20 2007 (1 yr ago)
Created Wed Jul 26 17:26:07 2006 (2 yr ago)

Transaction History Ticket 4905


Wed, Jul 26 2006 17:26:07    Request created by guest  
Subject: gis.m: d.text.freetype does not allow spaces in text

Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs_head_20060724

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.

Moritz
Wed, Jul 26 2006 19:22:58    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17607.42218.237145.467727@cerise.gclements.plus.com>
Date Wed, 26 Jul 2006 18:22:50 +0100
To Request Tracker <grass-bugs@intevation.de>
Cc grass-dev@grass.itc.it
Subject Re: [GRASS-dev] [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
In-Reply-To <20060726152607.BE638100159@lists.intevation.de>
References <20060726152607.BE638100159@lists.intevation.de>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-3.558 tagged_above=-999 required=3 tests=[AWL=1.176, BAYES_00=-5, FORGED_RCVD_HELO=0.266]
X-Spam-Level
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.

-- 
Glynn Clements <glynn@gclements.plus.com>


Wed, Jul 26 2006 22:54:13    Mail sent by michael.barton@asu.edu  
Return-Path <michael.barton@asu.edu>
Delivered-To grass-bugs@lists.intevation.de
User-Agent Microsoft-Entourage/11.2.5.060620
Date Wed, 26 Jul 2006 13:53:59 -0700
Subject Re: [GRASS-dev] [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
From Michael Barton <michael.barton@asu.edu>
To Paolo Cavallini via RT <grass-bugs@intevation.de>, <grass-dev@grass.itc.it>
Message-ID <C0ED2477.22F92%michael.barton@asu.edu>
Thread-Topic [GRASS-dev] [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
Thread-Index Acaw9Z3y3HDuMRzoEduwIQAUUSYxwg==
In-Reply-To <20060726152607.BE638100159@lists.intevation.de>
Mime-version 1.0
Content-type text/plain; charset="US-ASCII"
Content-transfer-encoding 7bit
X-Virus-Scanned by amavisd-new
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.457 tagged_above=-999 required=3 tests=[AWL=1.195, BAYES_00=-5, RCVD_NUMERIC_HELO=1.348]
X-Spam-Level
Moritz,

If you save as EPS, the postscript text will save too.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Request Tracker <grass-bugs@intevation.de>
> Reply-To: Request Tracker <grass-bugs@intevation.de>
> Date: Wed, 26 Jul 2006 17:26:07 +0200 (CEST)
> To: <grass-dev@grass.itc.it>
> Subject: [GRASS-dev] [bug #4905] (grass) gis.m: d.text.freetype does not allow
> spaces in text
> 
> this bug's URL: http://intevation.de/rt/webrt?serial_num=4905
> -------------------------------------------------------------------------
> 
> Subject: gis.m: d.text.freetype does not allow spaces in text
> 
> Platform: GNU/Linux/x86
> grass obtained from: CVS
> grass binary for platform: Compiled from Sources
> GRASS Version: cvs_head_20060724
> 
> 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.
> 
> Moritz
> 
> -------------------------------------------- Managed by Request Tracker
> 
> 


Thu, Jul 27 2006 09:42:04    Mail sent by moritz.lennert@ulb.ac.be  
Return-Path <moritz.lennert@ulb.ac.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44C86E4B.8010408@ulb.ac.be>
Date Thu, 27 Jul 2006 09:42:03 +0200
From Moritz Lennert <moritz.lennert@ulb.ac.be>
User-Agent Thunderbird 1.5.0.4 (X11/20060713)
MIME-Version 1.0
To Michael Barton <michael.barton@asu.edu>
Cc Paolo Cavallini via RT <grass-bugs@intevation.de>, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
References <C0ED2477.22F92%michael.barton@asu.edu>
In-Reply-To <C0ED2477.22F92%michael.barton@asu.edu>
Content-Type text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Michael Barton wrote:
> Moritz,
> 
> If you save as EPS, the postscript text will save too.

But then you lose transparency... :-(

Moritz

> 
> Michael
> __________________________________________
> Michael Barton, Professor of Anthropology
> School of Human Evolution & Social Change
> Center for Social Dynamics and Complexity
> Arizona State University
> 
> phone: 480-965-6213
> fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton
> 
> 
>> From: Request Tracker <grass-bugs@intevation.de>
>> Reply-To: Request Tracker <grass-bugs@intevation.de>
>> Date: Wed, 26 Jul 2006 17:26:07 +0200 (CEST)
>> To: <grass-dev@grass.itc.it>
>> Subject: [GRASS-dev] [bug #4905] (grass) gis.m: d.text.freetype does not allow
>> spaces in text
>>
>> this bug's URL: http://intevation.de/rt/webrt?serial_num=4905
>> -------------------------------------------------------------------------
>>
>> Subject: gis.m: d.text.freetype does not allow spaces in text
>>
>> Platform: GNU/Linux/x86
>> grass obtained from: CVS
>> grass binary for platform: Compiled from Sources
>> GRASS Version: cvs_head_20060724
>>
>> 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.
>>
>> Moritz
>>
>> -------------------------------------------- Managed by Request Tracker
>>
>>
> 
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev


Mon, Aug 28 2006 20:18:46    Mail sent by mbarton  
Is this fixed now? Freetype text doesn't work on a Mac so I can't tell.

Michale
Tue, Aug 29 2006 15:16:44    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44F43E4E.4030805@club.worldonline.be>
Date Tue, 29 Aug 2006 15:17:02 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version 1.0
To Michael Barton via RT <grass-bugs@intevation.de>
Cc tutey@o2.pl, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
References <20060828181846.96E3C1005C0@lists.intevation.de>
In-Reply-To <20060828181846.96E3C1005C0@lists.intevation.de>
Content-Type text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-4.544 tagged_above=-999 required=3 tests=[AWL=0.456, BAYES_00=-5]
X-Spam-Level
Michael Barton via RT wrote:
> Is this fixed now? Freetype text doesn't work on a Mac so I can't tell.


No, neither the gis.m part, nor the d.text.freetype part (for which I 
will post a separate bug report to make it more visible).

As Glynn wrote, the gis.m error can be "solved" by typing

d.text.freetype -n -b {text=Population totale}

instead of

d.text.freetype -n -b text="Population totale"

But I don't find this solution very intuitive, especially as on the 
command line the second works.

So maybe there should be some treatment in gis.m which translates the 
second version into something usable. Or at least the documentation has 
to be updated, but I would only consider this as a temporary solution.

Just for memory, the d.text.freetype part of the bug is that even when a 
space is accepted, it is not printed on the screen, making the above into:

Populationtotale

Moritz


Tue, Aug 29 2006 16:53:08    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44F454DA.8010105@club.worldonline.be>
Date Tue, 29 Aug 2006 16:53:14 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version 1.0
To Glynn Clements via RT <grass-bugs@intevation.de>
Cc Grass Developers List <grass-dev@grass.itc.it>, "barton >> Michael Barton" <michael.barton@asu.edu>
Subject Re: [bug #4905] (grass) gis.m: d.text.freetype does not
References <20060726172258.26DD81005BA@lists.intevation.de>
In-Reply-To <20060726172258.26DD81005BA@lists.intevation.de>
Content-Type text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-4.549 tagged_above=-999 required=3 tests=[AWL=0.451, BAYES_00=-5]
X-Spam-Level
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


Tue, Aug 29 2006 18:48:57    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17652.28660.435767.8095@cerise.gclements.plus.com>
Date Tue, 29 Aug 2006 17:48:52 +0100
To Moritz Lennert <mlennert@club.worldonline.be>
Cc Michael Barton via RT <grass-bugs@intevation.de>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
In-Reply-To <44F43E4E.4030805@club.worldonline.be>
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Moritz Lennert wrote:

> > Is this fixed now? Freetype text doesn't work on a Mac so I can't tell.
> 
> 
> No, neither the gis.m part, nor the d.text.freetype part (for which I 
> will post a separate bug report to make it more visible).
> 
> As Glynn wrote, the gis.m error can be "solved" by typing
> 
> d.text.freetype -n -b {text=Population totale}
> 
> instead of
> 
> d.text.freetype -n -b text="Population totale"
> 
> But I don't find this solution very intuitive, especially as on the 
> command line the second works.
> 
> So maybe there should be some treatment in gis.m which translates the 
> second version into something usable. Or at least the documentation has 
> to be updated, but I would only consider this as a temporary solution.
> 
> Just for memory, the d.text.freetype part of the bug is that even when a 
> space is accepted, it is not printed on the screen, making the above into:
> 
> Populationtotale

There are two separate issues. gis.m has previously had problems with
arguments containing spaces, but there have been some fixes in that
area. If you come across this problem in the current CVS version, file
a bug report.

The problem with spaces disappearing is that FT_Render_Glyph() returns
an error for the space glyph, causing the code to ignore that glyph
(and, significantly, not advance the rendering position).

The code should probably still advance the rendering position in the
event that FT_Render_Glyph() fails.

-- 
Glynn Clements <glynn@gclements.plus.com>


Wed, Aug 30 2006 05:29:38    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Wed, 30 Aug 2006 15:29:07 +1200
From Hamish <hamish_nospam@yahoo.com>
To Moritz Lennert <mlennert@club.worldonline.be>
Cc grass-bugs@intevation.de, grass-dev@grass.itc.it, glynn@gclements.plus.com
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not
Message-Id <20060830152907.0c94a57d.hamish_nospam@yahoo.com>
In-Reply-To <44F454DA.8010105@club.worldonline.be>
References <20060726172258.26DD81005BA@lists.intevation.de> <44F454DA.8010105@club.worldonline.be>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
Moritz Lennert wrote:

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

I see this on Debian/stable using an older version of Freetype,

$ dpkg -s libfreetype6-dev
..
Version: 2.1.7-2.5

This is a security-update package from June,
  http://www.us.debian.org/security/2006/dsa-1095


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

                               July > June  ^^^^^^^^

?????

Hamish


Wed, Aug 30 2006 11:17:46    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44F557CC.4050807@club.worldonline.be>
Date Wed, 30 Aug 2006 11:18:04 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version 1.0
To Hamish <hamish_nospam@yahoo.com>
Cc grass-bugs@intevation.de, grass-dev@grass.itc.it, glynn@gclements.plus.com
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not
References <20060726172258.26DD81005BA@lists.intevation.de> <44F454DA.8010105@club.worldonline.be> <20060830152907.0c94a57d.hamish_nospam@yahoo.com>
In-Reply-To <20060830152907.0c94a57d.hamish_nospam@yahoo.com>
Content-Type text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Hamish wrote:
> Moritz Lennert wrote:
> 
>> 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.
> 
> I see this on Debian/stable using an older version of Freetype,
> 
> $ dpkg -s libfreetype6-dev
> ..
> Version: 2.1.7-2.5
> 
> This is a security-update package from June,
>   http://www.us.debian.org/security/2006/dsa-1095
> 
> 
>> http://lists.gnu.org/archive/html/freetype/2006-07/msg00009.html
> 
>                                July > June  ^^^^^^^^

I think it is specifically a problem in 2.2.1.

Moritz


Wed, Aug 30 2006 11:49:07    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44F55F23.3050004@club.worldonline.be>
Date Wed, 30 Aug 2006 11:49:23 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version 1.0
To Glynn Clements <glynn@gclements.plus.com>
Cc Michael Barton via RT <grass-bugs@intevation.de>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be> <17652.28660.435767.8095@cerise.gclements.plus.com>
In-Reply-To <17652.28660.435767.8095@cerise.gclements.plus.com>
Content-Type text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Glynn Clements wrote:
> Moritz Lennert wrote:
> 
>>> Is this fixed now? Freetype text doesn't work on a Mac so I can't tell.
>>
>> No, neither the gis.m part, nor the d.text.freetype part (for which I 
>> will post a separate bug report to make it more visible).
>>
>> As Glynn wrote, the gis.m error can be "solved" by typing
>>
>> d.text.freetype -n -b {text=Population totale}
>>
>> instead of
>>
>> d.text.freetype -n -b text="Population totale"
>>
>> But I don't find this solution very intuitive, especially as on the 
>> command line the second works.
>>
>> So maybe there should be some treatment in gis.m which translates the 
>> second version into something usable. Or at least the documentation has 
>> to be updated, but I would only consider this as a temporary solution.
>>
>> Just for memory, the d.text.freetype part of the bug is that even when a 
>> space is accepted, it is not printed on the screen, making the above into:
>>
>> Populationtotale
> 
> There are two separate issues. gis.m has previously had problems with
> arguments containing spaces, but there have been some fixes in that
> area. If you come across this problem in the current CVS version, file
> a bug report.

That is what this bug report is actually about (what I call the "gis.m 
part of the bug") and it is still open as of CVS-head from yesterday.

> 
> The problem with spaces disappearing is that FT_Render_Glyph() returns
> an error for the space glyph, causing the code to ignore that glyph
> (and, significantly, not advance the rendering position).

But this only seems to be a problem with the current stable version of 
freetype, i.e. 2.2.1. Using latest CVS code of freetype, the problem is 
solved.

> 
> The code should probably still advance the rendering position in the
> event that FT_Render_Glyph() fails.

Is this a problem with anything else then space ?

Moritz


Wed, Aug 30 2006 15:33:32    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17653.37799.661695.757065@cerise.gclements.plus.com>
Date Wed, 30 Aug 2006 14:33:27 +0100
To Moritz Lennert <mlennert@club.worldonline.be>
Cc Michael Barton via RT <grass-bugs@intevation.de>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
In-Reply-To <44F55F23.3050004@club.worldonline.be>
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be> <17652.28660.435767.8095@cerise.gclements.plus.com> <44F55F23.3050004@club.worldonline.be>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Moritz Lennert wrote:

> > There are two separate issues. gis.m has previously had problems with
> > arguments containing spaces, but there have been some fixes in that
> > area. If you come across this problem in the current CVS version, file
> > a bug report.
> 
> That is what this bug report is actually about (what I call the "gis.m 
> part of the bug") and it is still open as of CVS-head from yesterday.

So the gis.m bug is still present? I.e. you can't include spaces in
the text?

> > The code should probably still advance the rendering position in the
> > event that FT_Render_Glyph() fails.
> 
> Is this a problem with anything else then space ?

Probably not (well, it probably applies to all "blank" characters,
e.g. double-width space as well as the normall ASCII space character).

-- 
Glynn Clements <glynn@gclements.plus.com>


Wed, Aug 30 2006 15:48:46    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44F59746.5010207@club.worldonline.be>
Date Wed, 30 Aug 2006 15:48:54 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version 1.0
To Glynn Clements <glynn@gclements.plus.com>
Cc Michael Barton via RT <grass-bugs@intevation.de>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be> <17652.28660.435767.8095@cerise.gclements.plus.com> <44F55F23.3050004@club.worldonline.be> <17653.37799.661695.757065@cerise.gclements.plus.com>
In-Reply-To <17653.37799.661695.757065@cerise.gclements.plus.com>
Content-Type text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Glynn Clements wrote:
> Moritz Lennert wrote:
> 
>>> There are two separate issues. gis.m has previously had problems with
>>> arguments containing spaces, but there have been some fixes in that
>>> area. If you come across this problem in the current CVS version, file
>>> a bug report.
>> That is what this bug report is actually about (what I call the "gis.m 
>> part of the bug") and it is still open as of CVS-head from yesterday.
> 
> So the gis.m bug is still present? I.e. you can't include spaces in
> the text?

Yes, unless I use the curly braces solution you suggested, i.e.:

d.text.freetype -n {text=Population totale} ...

Just to make sure we understand each other: this is when adding the 
d.text.freetype command as a command layer to gis.m (I don't know of 
another way...).

Moritz


Wed, Aug 30 2006 18:32:37    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17653.48543.844755.999699@cerise.gclements.plus.com>
Date Wed, 30 Aug 2006 17:32:31 +0100
To Moritz Lennert <mlennert@club.worldonline.be>
Cc Michael Barton via RT <grass-bugs@intevation.de>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
In-Reply-To <44F59746.5010207@club.worldonline.be>
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be> <17652.28660.435767.8095@cerise.gclements.plus.com> <44F55F23.3050004@club.worldonline.be> <17653.37799.661695.757065@cerise.gclements.plus.com> <44F59746.5010207@club.worldonline.be>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Moritz Lennert wrote:

> >>> There are two separate issues. gis.m has previously had problems with
> >>> arguments containing spaces, but there have been some fixes in that
> >>> area. If you come across this problem in the current CVS version, file
> >>> a bug report.
> >> That is what this bug report is actually about (what I call the "gis.m 
> >> part of the bug") and it is still open as of CVS-head from yesterday.
> > 
> > So the gis.m bug is still present? I.e. you can't include spaces in
> > the text?
> 
> Yes, unless I use the curly braces solution you suggested, i.e.:
> 
> d.text.freetype -n {text=Population totale} ...
> 
> Just to make sure we understand each other: this is when adding the 
> d.text.freetype command as a command layer to gis.m (I don't know of 
> another way...).

Right. If you are using a command layer, then you need to use braces
for any arguments which contain spaces. More precisely, the string for
a command layer needs to be a well-formed Tcl list, where each item in
the list constitutes a single argument. Using a backslash should also
work, i.e.:

	d.text.freetype -n text=Population\ totale ...

That isn't a bug; if you want to represent a list of strings (e.g. a
command) as a single string (i.e. the contents of a text field), and
you want list items to be able to contain the item separator, you
inevitably need some syntax to distinguish between use of the
separator as a separator and its use as a literal character.

With the Bourne shell, you need to use quotes; with Tcl, it's braces.

BTW, if an argument contains an unmatched brace, you have to use
backslashes, e.g.:

	d.text.freetype -n text=this:\ \{\ is\ a\ brace ...

as there's no way to include an unmatched brace in a brace-delimited
string.

-- 
Glynn Clements <glynn@gclements.plus.com>


Wed, Aug 30 2006 18:39:09    Mail sent by grass4u@gmail.com  
Return-Path <grass4u@gmail.com>
Delivered-To grass-bugs@lists.intevation.de
DomainKey-Signature a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=bd4xyPw17JiEYTK+SSxpfLQb4MADN0s3IhsO0abE9yuzGsa24F8Q9lwCnQpsy/q9r4PGLw9Bgf4rXEIaOgktrfJmGvqbMv1fIiPWMSqjedt7rPPCrO+iYB8GlQS+J969XCjwoSL9qNkKeut9s7+mCuPo4J+6KuFiBx2hNYTsQog=
Date Wed, 30 Aug 2006 11:38:29 -0500
From Huidae Cho <grass4u@gmail.com>
To Moritz Lennert <mlennert@club.worldonline.be>
Cc Glynn Clements <glynn@gclements.plus.com>, Michael Barton via RT <grass-bugs@intevation.de>, Grass Developers List <grass-dev@grass.itc.it>
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
Message-ID <20060830163828.GA8438@localhost.tamu.edu>
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be> <17652.28660.435767.8095@cerise.gclements.plus.com> <44F55F23.3050004@club.worldonline.be>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
In-Reply-To <44F55F23.3050004@club.worldonline.be>
User-Agent mutt-ng/devel (FreeBSD)
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-4.933 tagged_above=-999 required=3 tests=[BAYES_00=-5, RCVD_BY_IP=0.067]
X-Spam-Level
On Wed, Aug 30, 2006 at 11:49:23AM +0200, Moritz Lennert wrote:
> Glynn Clements wrote:
> >Moritz Lennert wrote:
> >>>Is this fixed now? Freetype text doesn't work on a Mac so I can't tell.
> >>No, neither the gis.m part, nor the d.text.freetype part (for which I will
> >>post a separate bug report to make it more visible).
> >>As Glynn wrote, the gis.m error can be "solved" by typing
> >>d.text.freetype -n -b {text=Population totale}
> >>instead of
> >>d.text.freetype -n -b text="Population totale"
> >>But I don't find this solution very intuitive, especially as on the command
> >>line the second works.
> >>So maybe there should be some treatment in gis.m which translates the second
> >>version into something usable. Or at least the documentation has to be 
> >>updated, but I would only consider this as a temporary solution.
> >>Just for memory, the d.text.freetype part of the bug is that even when a
> >>space is accepted, it is not printed on the screen, making the above into:
> >>Populationtotale
> >There are two separate issues. gis.m has previously had problems with
> >arguments containing spaces, but there have been some fixes in that
> >area. If you come across this problem in the current CVS version, file
> >a bug report.
> 
> That is what this bug report is actually about (what I call the "gis.m part
of 
> the bug") and it is still open as of CVS-head from yesterday.
> 
> >The problem with spaces disappearing is that FT_Render_Glyph() returns
> >an error for the space glyph, causing the code to ignore that glyph
> >(and, significantly, not advance the rendering position).
> 
> But this only seems to be a problem with the current stable version of 
> freetype, i.e. 2.2.1. Using latest CVS code of freetype, the problem is solved.
This is a related thread:
http://www.nabble.com/Error-rendering-space-character-in-mono-mode-with-FreeType-2.2.1-t1881988.html

Huidae

> 
> >The code should probably still advance the rendering position in the
> >event that FT_Render_Glyph() fails.
> 
> Is this a problem with anything else then space ?
> 
> Moritz
> 
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev


Thu, Aug 31 2006 05:02:08    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Thu, 31 Aug 2006 15:01:18 +1200
From Hamish <hamish_nospam@yahoo.com>
To Glynn Clements <glynn@gclements.plus.com>
Cc mlennert@club.worldonline.be, grass-bugs@intevation.de, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
Message-Id <20060831150118.2907cc53.hamish_nospam@yahoo.com>
In-Reply-To <17653.37799.661695.757065@cerise.gclements.plus.com>
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be> <17652.28660.435767.8095@cerise.gclements.plus.com> <44F55F23.3050004@club.worldonline.be> <17653.37799.661695.757065@cerise.gclements.plus.com>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
Glynn Clements wrote:

> > > There are two separate issues. gis.m has previously had problems
> > > with arguments containing spaces, but there have been some fixes
> > > in that area. If you come across this problem in the current CVS
> > > version, file a bug report.
> > 
> > That is what this bug report is actually about (what I call the
> > "gis.m  part of the bug") and it is still open as of CVS-head from
> > yesterday.
> 
> So the gis.m bug is still present? I.e. you can't include spaces in
> the text?


well the gis.m version obviously won't work, even with correct quoting,
while the backend C code remains broken.

??!!


Hamish


Thu, Aug 31 2006 09:53:48    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44F695A1.3080003@club.worldonline.be>
Date Thu, 31 Aug 2006 09:54:09 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version 1.0
To Glynn Clements via RT <grass-bugs@intevation.de>
Cc Maciej Sieczka <tutey@o2.pl>, Michael Barton <michael.barton@asu.edu>
Subject Re: [bug #4905] (grass) gis.m: d.text.freetype does
References <20060830163237.32FEB1006CB@lists.intevation.de>
In-Reply-To <20060830163237.32FEB1006CB@lists.intevation.de>
Content-Type text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Glynn Clements via RT wrote:
> Moritz Lennert wrote:
> 
>>>>> There are two separate issues. gis.m has previously had problems with
>>>>> arguments containing spaces, but there have been some fixes in that
>>>>> area. If you come across this problem in the current CVS version, file
>>>>> a bug report.
>>>> That is what this bug report is actually about (what I call the "gis.m 
>>>> part of the bug") and it is still open as of CVS-head from yesterday.
>>> So the gis.m bug is still present? I.e. you can't include spaces in
>>> the text?
>> Yes, unless I use the curly braces solution you suggested, i.e.:
>>
>> d.text.freetype -n {text=Population totale} ...
>>
>> Just to make sure we understand each other: this is when adding the 
>> d.text.freetype command as a command layer to gis.m (I don't know of 
>> another way...).
> 
> Right. If you are using a command layer, then you need to use braces
> for any arguments which contain spaces. More precisely, the string for
> a command layer needs to be a well-formed Tcl list, where each item in
> the list constitutes a single argument. Using a backslash should also
> work, i.e.:
> 
> 	d.text.freetype -n text=Population\ totale ...
> 
> That isn't a bug; if you want to represent a list of strings (e.g. a
> command) as a single string (i.e. the contents of a text field), and
> you want list items to be able to contain the item separator, you
> inevitably need some syntax to distinguish between use of the
> separator as a separator and its use as a literal character.
> 
> With the Bourne shell, you need to use quotes; with Tcl, it's braces.

With the difference that you do

text='Population total' in bourne shell

but

{text=Population totale}


The backslash solution works and seems more intuitive.
I'll add a hint in the gis.m description.html.

Bug can be closed.

This said: Michael, what were the problems that made you take off 
d.text.freetype from the toolbar ?

Moritz


Thu, Aug 31 2006 15:10:05    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17654.57255.638071.444562@cerise.gclements.plus.com>
Date Thu, 31 Aug 2006 14:09:59 +0100
To Hamish <hamish_nospam@yahoo.com>
Cc grass-bugs@intevation.de, mlennert@club.worldonline.be, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
In-Reply-To <20060831150118.2907cc53.hamish_nospam@yahoo.com>
References <20060828181846.96E3C1005C0@lists.intevation.de> <44F43E4E.4030805@club.worldonline.be> <17652.28660.435767.8095@cerise.gclements.plus.com> <44F55F23.3050004@club.worldonline.be> <17653.37799.661695.757065@cerise.gclements.plus.com> <20060831150118.2907cc53.hamish_nospam@yahoo.com>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Hamish wrote:

> > > > There are two separate issues. gis.m has previously had problems
> > > > with arguments containing spaces, but there have been some fixes
> > > > in that area. If you come across this problem in the current CVS
> > > > version, file a bug report.
> > > 
> > > That is what this bug report is actually about (what I call the
> > > "gis.m  part of the bug") and it is still open as of CVS-head from
> > > yesterday.
> > 
> > So the gis.m bug is still present? I.e. you can't include spaces in
> > the text?
> 
> well the gis.m version obviously won't work, even with correct quoting,
> while the backend C code remains broken.

Whether or not gis.m "works" is a question of whether commands (not
necessarily d.text.freetype commands) containing spaces are handled
correctly.

Whether or not d.text.freetype itself works is a separate issue.

-- 
Glynn Clements <glynn@gclements.plus.com>


Thu, Aug 31 2006 16:16:36    Mail sent by msieczka  
mlennert@club.worldonline.be wrote (Thu, Aug 31 2006 09:53:48):

> With the difference that you do
> 
> text='Population total' in bourne shell
> 
> but
> 
> {text=Population totale}
> 
> 
> The backslash solution works and seems more intuitive.
> I'll add a hint in the gis.m description.html.

Michael,

Do you think that d.text.freetype (and other modules that may require {} or \
for attributes to work properly from gis.m) could put {} or \ automatically
for the user?

Maciek
Thu, Aug 31 2006 18:35:56    Mail sent by michael.barton@asu.edu  
Return-Path <michael.barton@asu.edu>
Delivered-To grass-bugs@lists.intevation.de
User-Agent Microsoft-Entourage/11.2.5.060620
Date Thu, 31 Aug 2006 09:35:45 -0700
Subject Re: [bug #4905] (grass) gis.m: d.text.freetype does
From Michael Barton <michael.barton@asu.edu>
To Moritz Lennert <mlennert@club.worldonline.be>, Paolo Cavallini via RT <grass-bugs@intevation.de>
Cc Maciej Sieczka <tutey@o2.pl>
Message-ID <C11C5DF1.23FF9%michael.barton@asu.edu>
Thread-Topic [bug #4905] (grass) gis.m: d.text.freetype does
Thread-Index AcbNG4GswBXE5jkOEduBXwAUUSYxwg==
In-Reply-To <44F695A1.3080003@club.worldonline.be>
Mime-version 1.0
Content-type text/plain; charset="US-ASCII"
Content-transfer-encoding 7bit
X-Virus-Scanned by amavisd-new
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-3.752 tagged_above=-999 required=3 tests=[BAYES_00=-5, RCVD_NUMERIC_HELO=1.248]
X-Spam-Level
There was some inherent problem at the underlying Mac OS level that
prevented d.text.freetype from displaying anything on Macs. Everything
worked fine (no errors), but no text was drawn.

Lorenzo Moretti figured out the cause, but could not fix it. I replaced
d.text.freetype with a TclTk version that lets you select any font
registered on your system and draw it in text that can be rendered with
postscript on the display canvas, rather than incorporated into the raster
graphic created by a d.text.freetype command. This gives nicer looking text
with postscript. 

When the dust has settled from all the proposed changes, we should review
again how best to display text items on a GRASS map.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton


> From: Moritz Lennert <mlennert@club.worldonline.be>
> Date: Thu, 31 Aug 2006 09:54:09 +0200
> To: Glynn Clements via RT <grass-bugs@intevation.de>
> Cc: Maciej Sieczka <tutey@o2.pl>, Michael Barton <michael.barton@asu.edu>
> Subject: Re: [bug #4905] (grass) gis.m: d.text.freetype does
> 
> 
> This said: Michael, what were the problems that made you take off
> d.text.freetype from the toolbar ?
> 


Fri, Sep 1 2006 00:19:56    Mail sent by glynn@gclements.plus.com  
Return-Path <glynn@gclements.plus.com>
Delivered-To grass-bugs@lists.intevation.de
From Glynn Clements <glynn@gclements.plus.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Transfer-Encoding 7bit
Message-ID <17655.24436.422287.500971@cerise.gclements.plus.com>
Date Thu, 31 Aug 2006 23:15:16 +0100
To Maciek Sieczka via RT <grass-bugs@intevation.de>
Cc mlennert@club.worldonline.be, michael.barton@asu.edu, grass-dev@grass.itc.it
Subject Re: [GRASS-dev] [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
In-Reply-To <20060831141636.CA4271006D7@lists.intevation.de>
References <20060831141636.CA4271006D7@lists.intevation.de>
X-Mailer VM 7.07 under 21.4 (patch 15) "Security Through Obscurity" XEmacs Lucid
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Maciek Sieczka via RT wrote:

> > With the difference that you do
> > 
> > text='Population total' in bourne shell
> > 
> > but
> > 
> > {text=Population totale}
> > 
> > 
> > The backslash solution works and seems more intuitive.
> > I'll add a hint in the gis.m description.html.
> 
> Do you think that d.text.freetype (and other modules that may require {} or
\
> for attributes to work properly from gis.m) could put {} or \ automatically
> for the user?

No.

Well, gis.m *could* add braces or backslashes based upon some
arbitrary heuristics, but there's no way that it can be done reliably.

E.g. the following:

	d.text.freetype text=text color=string

can be legtimately interpreted as either:

	d.text.freetype {text=text} {color=red} ...
or:
	d.text.freetype {text=text color=red} ...

The former draws the string "text" in red, while the latter draws the
string "text color=red" in the default colour.

Computers cannot read minds; that isn't a bug, that's just how it is. 

If you want a space to be treated as a literal character rather than
as an argument separator, you have to say so.

-- 
Glynn Clements <glynn@gclements.plus.com>


Fri, Sep 1 2006 09:11:57    Mail sent by msieczka  
glynn@gclements.plus.com wrote (Fri, Sep 1 2006 00:19:56):

> Computers cannot read minds; that isn't a bug, that's just how it is. 
> 
> If you want a space to be treated as a literal character rather than
> as an argument separator, you have to say so.

OK, Moritz volunteered for documenting it.

Moritz, please send me the patch and I'll apply it.

Maciek
Fri, Sep 1 2006 10:10:07    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <44F7EAF3.4000606@club.worldonline.be>
Date Fri, 01 Sep 2006 10:10:27 +0200
From Moritz Lennert <mlennert@club.worldonline.be>
User-Agent Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version 1.0
To Maciek Sieczka via RT <grass-bugs@intevation.de>
Subject Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
References <20060901071157.95D241006DA@lists.intevation.de>
In-Reply-To <20060901071157.95D241006DA@lists.intevation.de>
Content-Type text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-5 tagged_above=-999 required=3 tests=[BAYES_00=-5]
X-Spam-Level
Maciek Sieczka via RT wrote:
> glynn@gclements.plus.com wrote (Fri, Sep 1 2006 00:19:56):
> 
> 
> 
>> Computers cannot read minds; that isn't a bug, that's just how it is. 
> 
> 
>> If you want a space to be treated as a literal character rather than
> 
>> as an argument separator, you have to say so.
> 
> 
> 
> OK, Moritz volunteered for documenting it.
> 
> 
> 
> Moritz, please send me the patch and I'll apply it.

I've already comitted it:

http://grass.itc.it/pipermail/grass-commit/2006-August/024062.html

Moritz


Mon, Sep 18 2006 04:49:58    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Mon, 18 Sep 2006 14:49:47 +1200
From Hamish <hamish_nospam@yahoo.com>
To grass-dev@grass.itc.it
Cc pkg-grass-general@lists.alioth.debian.org, grass-bugs@intevation.de
Subject Re: [GRASS-dev] Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
Message-Id <20060918144947.0255dc72.hamish_nospam@yahoo.com>
In-Reply-To <17656.36289.837856.967927@cerise.gclements.plus.com>
References <20060830151604.541d4f89.hamish_nospam@yahoo.com> <C11A743B.DDA0%michael.barton@asu.edu> <17653.37525.758455.944196@cerise.gclements.plus.com> <20060830174856.GC8438@localhost.tamu.edu> <17653.53497.833664.664895@cerise.gclements.plus.com> <20060830181307.GA43424@localhost.tamu.edu> <44F6F1CE.6080509@o2.pl> <20060831150145.GB8640@localhost.tamu.edu> <17655.512.892921.746949@cerise.gclements.plus.com> <17656.27119.705966.637113@cerise.gclements.plus.com> <20060901183040.GA6853@localhost> <17656.36289.837856.967927@cerise.gclements.plus.com>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, hits=-2.3 tagged_above=-999 required=3 tests=[BAYES_00=-5, FORGED_YAHOO_RCVD=2.7]
X-Spam-Level
https://intevation.de/rt/webrt?serial_num=4905

Hi, just an update on this bug-

(spaces in text cause d.text.freetype to segfault when
 ft_render_mode_mono was used)


The Debian/stable libfreetype6 pacakges have just been updated, and it
seems to be fixed. I think the 2.1.7-5 package was buggy.

d.text.freetype text="`g.version`" path=/var/lib/defoma/gs.d/dirs/fonts/Vera.ttf
Hamish  (I'm out of town for the next while)


Wed, May 9 2007 19:27:08    Mail sent by mneteler  
d.text and d.text.freetype have been updated in GRASS 6.3, does the problem
persist?

Markus
Thu, May 10 2007 22:19:02    Mail sent by mlennert@club.worldonline.be  
Return-Path <mlennert@club.worldonline.be>
Delivered-To grass-bugs@lists.intevation.de
Message-ID <1405.85.10.90.5.1178828541.squirrel@geog-pc40.ulb.ac.be>
In-Reply-To <20070509172708.AEFC61006D0@lists.intevation.de>
References <20070509172708.AEFC61006D0@lists.intevation.de>
Date Thu, 10 May 2007 22:22:21 +0200 (CEST)
Subject Re: [bug #4905] (grass) gis.m: d.text.freetype does not allow spaces in text
From "Moritz Lennert" <mlennert@club.worldonline.be>
To "Markus Neteler via RT" <grass-bugs@intevation.de>
Reply-To mlennert@club.worldonline.be
User-Agent SquirrelMail/1.4.9a
MIME-Version 1.0
Content-Type text/plain;charset=iso-8859-1
Content-Transfer-Encoding 8bit
X-Virus-Scanned by amavisd-new at intevation.de
X-Spam-Status No, score=-5 tagged_above=-999 required=3.5 tests=[BAYES_00=-5]
X-Spam-Score -5
X-Spam-Level
On Wed, May 9, 2007 19:27, Markus Neteler via RT wrote:
> d.text and d.text.freetype have been updated in GRASS 6.3, does the
> problem persist?

Actually as mentioned in one of the many messages, the bug can be closed.
I committed a comment to the gis.m man page:
http://grass.itc.it/pipermail/grass-commit/2006-August/024062.html.

The d.text.freetype issue (outside of gis.m) was due to the freetype
library, not GRASS.

Moritz


Sat, May 12 2007 12:39:20    Status changed to resolved by mneteler  
Comment | Reply | Take | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request