[GRASS-dev] [GRASS GIS] #432: scripts/ Makefile bug in i18N string extraction

GRASS GIS trac at osgeo.org
Thu Jan 15 13:45:45 EST 2009


#432: scripts/ Makefile bug in i18N string extraction
---------------------+------------------------------------------------------
 Reporter:  neteler  |       Owner:  grass-dev at lists.osgeo.org
     Type:  defect   |      Status:  new                      
 Priority:  major    |   Milestone:  6.4.0                    
Component:  default  |     Version:  svn-develbranch6         
 Keywords:           |    Platform:  All                      
      Cpu:  All      |  
---------------------+------------------------------------------------------
 As far as I understand the scripts/Makefile process in GRASS 6, the "make
 pot" command does not take into account that the scripts have to be
 "compiled" (see g.parser part below):

 {{{
 # i.tasscap example: long lines broken for convenience
 make[2]: Leaving directory `/home/neteler/grass64/scripts/i.tasscap'
 GISRC=/home/neteler/grass64/dist.x86_64-unknown-linux-
 gnu/demolocation/.grassrc64 \
 GISBASE=/home/neteler/grass64/dist.x86_64-unknown-linux-gnu
 PATH=/home/neteler/grass64 \
 /dist.x86_64-unknown-linux-gnu/bin:$PATH \
 LD_LIBRARY_PATH="/home/neteler/grass64/dist.x86_64-unknown-linux-gnu/lib:"
 \
 g.parser -t i.tasscap | sed s/\"/\\\\\"/g | sed 's/.*/_("&")/' \
 > ../../locale/scriptstrings/i.tasscap_to_translate.c ; true
 make[1]: Leaving directory `/home/neteler/grass64/scripts/i.tasscap'
 }}}

 Typically "make pot" is run on a clean source code tarball, could the
 procedure be changed to either trap this or improve it? I am sure that
 currently many scripts/ strings are missing from the .po files
 (unverified).

 Markus

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/432>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list