Voting on RFC 9.
steve.lime at DNR.STATE.MN.US
Tue Jan 31 13:58:31 EST 2006
The example was just to show you can change the delimeter. If I can get a comment from
someone in the know I'll make sure it works when detecting a decimal point. Heck, might be
able to do that automagically if .'s become . and .'s become ,'s.
>>> Stephen Woodbridge <woodbri at SWOODBRIDGE.COM> 01/31/06 12:32 PM >>>
Area (precision=2) w/euro-style commas: 4.608.320.923.50
probably should have a comma for the decimal point ie:
Area (precision=2) w/euro-style commas: 4.608.320.923,50
but I'm not an expert on this is. Maybe someone from Europe can comment.
Steve Lime wrote:
> Take it for what it's worth. It's certainly not the ultimate solution but it does offer
> simple formatting for numbers and text, plus a simple conditional. That covers a
> lot of ground with normal use.
> I have added a bug (1636) to track this and have committed the initial code. I've also
> updated the RFC with the bug ID and voting history.
> For example use see:
>>>>Daniel Morissette <dmorissette at dmsolutions.ca> 01/31/06 8:51 AM >>>
> Steve Lime wrote:
>>So far only one +1 (me), and one +0 (Frank). I've got this ready to go into 4.9 with one more thumbs up. Anyone?
>>I'd like to get it committed and move on to something else.
> I find that the proposed mechanism may be a bit limited in what it can
> do in the long run. I mean new properties would need to be created
> everytime we want to add formatting options for new data types, etc.
> But anyway, since the change adds some useful fonctionality, it is
> localized in a single new tag in the templates and a new/better
> mechanism could be added easily without breaking compatibility in the
> future if needed, then I'll vote +1.
More information about the mapserver-dev