[GRASS-dev] Re: [GRASS GIS] #692: computational region in
grasswxpy.po file
GRASS GIS
trac at osgeo.org
Sun Jul 19 04:45:28 EDT 2009
#692: computational region in grasswxpy.po file
---------------------------+------------------------------------------------
Reporter: lucadelu | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: new
Priority: normal | Milestone: 6.4.0
Component: Translations | Version: svn-trunk
Resolution: | Keywords: computational po
Platform: All | Cpu: All
---------------------------+------------------------------------------------
Comment (by mmetz):
Replying to [comment:6 hamish]:
> Replying to [comment:5 mmetz]:
> > g.region and all modules use "current region"; it would help
> > to avoid confusion if the same term is used throughout for
> > the same thing. Terms for the different regions (or windows)
> > are defined in the manual of g.region. So I would vote for
> > either "current region" or "computational region" but not
> > the one in module man pages and the other in the GUI.
>
> The dichotomy, and so the need for modifying distinctions, is only
present from the GUI. Adding redundant modifiers into the back-end modules
just adds to the confusion IMO. I am all for improved clarity and
consistency, but am wary that it is very easy to go over the top on such
crusades.
>
> (here using the term for the child to describe the parent)
>
OK. I guess there will always be some confusion with all the different
regions when displaying a raster map (default region, current
computational region, current display region, the raster's region). In
cases like this ticket, a short citation from the wxGUI manual may clarify
the meaning. It would be nice if the wording is clear without reading too
many manuals (don't say RTFM too often). Unfortunately this needs to be
sorted out for every language separately.
Markus M
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/692#comment:7>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list