[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-bugs] Error with placeholder $<gender_mapper>$

From: Jim Busser
Subject: Re: [Gnumed-bugs] Error with placeholder $<gender_mapper>$
Date: Sun, 14 Aug 2011 11:45:35 -0700

On 2011-08-14, at 10:53 AM, Karsten Hilbert wrote:

> On Sat, Aug 13, 2011 at 12:45:02PM -0700, Jim Busser wrote:
>> The following tex code
>> re: $<lastname>$, $<title>$ $<firstname>$  ($<gender_mapper>$, born 
>> $<date_of_birth::%Y %B %d>$)\\
>>    $<adr_number::home>$ $<adr_street::home>$\\
>>       $<adr_location::home>$ $<adr_postcode::home>$
>> results (in the PDF) in
>>      re: Kirk, Capt. James Tiberius (error with placeholder [< gendermapper 
>> >], born 1931 March 22)
>>      3366 Chandler Rd
>>      Windsor N8W 4B3
> Of course. That placeholder needs to be used as per
> definition (which can possibly be improved upon):
>       # those [placeholders] must satisfy the pattern "$<name::args::optional 
> length>$" when used
>       ...
>       u'gender_mapper',                       # "args" holds: <value for 
> male> // <value for female> // <value for other>

Ah, I did not realize it would do anything other than pass-through actual 
existing database values, I though the above was simply informative and/or 

Is it reasonable that the lack of arguments should be supported (where the user 
does not wish to override what may exist) to simply pass through what exists? 
Or is there an issue of limitation of language recognition and therefore the 
need to "map" values?

-- Jim

reply via email to

[Prev in Thread] Current Thread [Next in Thread]