Opened 9 years ago

Last modified 7 years ago

#1225 assigned enhancement

Include support for kilometres / metres (re) as unit options, alongside of kilometers/meters (er)

Reported by: voncasec Owned by: hamish
Priority: trivial Milestone: 6.5.0
Component: Ps.map Version: unspecified
Keywords: ps.map Cc: grass-dev@…
CPU: All Platform: All

Description

It would be nice if the ps.map instructions would recognize the metric spelling of kilometre / metre alongside of the imperial spelling when placing unit labels alongside of the scalebar decorations.

Change History (4)

comment:1 Changed 9 years ago by hamish

Cc: grass-dev@… added
CPU: UnspecifiedAll
Milestone: 6.4.16.5.0
Owner: changed from grass-dev@… to hamish
Platform: UnspecifiedAll
Status: newassigned

taking ownership of this one, but not sure about the best way to resolve it.

comment:2 Changed 9 years ago by hamish

The place that is set is:

source:grass/trunk/ps/ps.map/do_scalebar.c@#L192

you can edit that file by hand and recompile if you need to.

I do not like the idea of making it current-locale setting dependent, or a translated macro as many of us work in/with/for both systems and need to be able to produce for both, from both on demand. Those things being silently adjusted for me drives me batty.

It could take a cue from the spelling of UNITS in "g.proj -p", but that's rather fragile and not an option for lat/lon locations.

I am loathe to add another instruction just for this spelling.

?, Hamish

comment:3 in reply to:  2 Changed 9 years ago by hamish

Replying to hamish:

taking ownership of this one, but not sure about the best way to resolve it.

Replying to hamish:

The place that is set is:

source:grass/trunk/ps/ps.map/do_scalebar.c@#L192

you can edit that file by hand and recompile if you need to.

I do not like the idea of making it current-locale setting dependent, or a translated macro as many of us work in/with/for both systems and need to be able to produce for both, from both on demand. Those things being silently adjusted for me drives me batty.

It could take a cue from the spelling of UNITS in "g.proj -p", but that's rather fragile and not an option for lat/lon locations.

I am loathe to add another instruction just for this spelling.

?

fwiw current-locale dependent spelling was in the mean time applied to trunk with r46188.

Further strategy discussion within this report would be appreciated. (+ search ML archive for more talk about it)

Hamish

comment:4 Changed 7 years ago by hamish

many of us work in/with/for both systems and need to be able to produce for both, from both on demand. Those things being silently adjusted for me drives me batty.

For this I would suggest a new "-t" flag, to either _("") translate or not.

It is not ideal, but at least you can adjust the enviro variable if you need to. The question becomes to translate the string to the current locale or not for the default?

Hamish

Note: See TracTickets for help on using tickets.