[GRASS-dev] Re: [GRASS GIS] #692: computational region in grasswxpy.po file

[GRASS GIS]

#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 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)

 Replying to [comment:5 neteler]:
 > The underlying question is how to translate the currently
 > chosen term (into other languages like Italian).

 Hopefully this discussion better elucidates what the perhaps imperfect
 english wording is trying to say?


 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/692#comment:6>
GRASS GIS <http://grass.osgeo.org>