>>>>> Maris Nartiss <[EMAIL PROTECTED]> writes:
> Hi Markus, Carlos. Sorry for not understanding problem at first.
> This problem was laughting in our face all time - that string is
> incorrect and thus can not be extracted from source. Attached patch
> fixes problem.
It seems that there's a few more occurences of this bug
(assuming GNU grep):
$ grep -rE --context=1 --include=\*.tcl 'G_msg[[:blank:]]+\"[^"]*\$[^"]*' .
./gui/tcltk/d.m/d.m.tcl- wm withdraw .
./gui/tcltk/d.m/d.m.tcl: wm title . [G_msg "GRASS $GRASSVERSION GIS Manager
- $location_name"]
./gui/tcltk/d.m/d.m.tcl-
--
./gui/tcltk/d.m/print.tcl- set PW [toplevel .printwin]
./gui/tcltk/d.m/print.tcl: wm title $PW [G_msg "Print / Plot (Display
Manager - GRASS $GRASSVERSION)"]
./gui/tcltk/d.m/print.tcl-
--
./gui/tcltk/gis.m/georect.tcl- set drawprog 0
./gui/tcltk/gis.m/georect.tcl: set GRMap::msg [G_msg "Georectifying maps in
$xygroup group"]
./gui/tcltk/gis.m/georect.tcl-
--
./gui/tcltk/gis.m/georect.tcl- # reset status display to normal
./gui/tcltk/gis.m/georect.tcl: set GRMap::msg [G_msg "Georectifying maps in
$xygroup group"]
./gui/tcltk/gis.m/georect.tcl-
--
./gui/tcltk/gis.m/profile.tcl-
./gui/tcltk/gis.m/profile.tcl: set GmProfile::status [G_msg "Profile for
$pmap"]
./gui/tcltk/gis.m/profile.tcl-
--
./gui/tcltk/gis.m/profile.tcl-
./gui/tcltk/gis.m/profile.tcl: set GmProfile::status [G_msg "Profile for
$pmap"]
./gui/tcltk/gis.m/profile.tcl- $profilemf showstatusbar status
--
./gui/tcltk/gis.m/profile.tcl- #vwait elevrange
./gui/tcltk/gis.m/profile.tcl: #set GmProfile::status [G_msg "Profile for
$pmap"]
./gui/tcltk/gis.m/profile.tcl-
--
./gui/tcltk/gis.m/profile.tcl- # put map name back in status bar
./gui/tcltk/gis.m/profile.tcl: set GmProfile::status [G_msg "Profile for
$pmap"]
./gui/tcltk/gis.m/profile.tcl-
--
./gui/tcltk/gis.m/profile.tcl- $pcan create text $center $titlebottom \
./gui/tcltk/gis.m/profile.tcl: -text [G_msg "Profile for $pmap"] \
./gui/tcltk/gis.m/profile.tcl- -font {-size 14 -weight bold} \
--
./gui/tcltk/gis.m/profile.tcl- $pcan create text $center $xscaletop \
./gui/tcltk/gis.m/profile.tcl: -text [G_msg "distance along transect
($mapunits)"] \
./gui/tcltk/gis.m/profile.tcl- -anchor n \
--
./gui/tcltk/gis.m/rules.tcl- set row [ frame $rules_win.input ]
./gui/tcltk/gis.m/rules.tcl: Label $row.a -text [G_msg "$label2"]
./gui/tcltk/gis.m/rules.tcl- Button $row.b -image [image create photo -file
"$iconpath/$btn_icon"] \
--
./gui/tcltk/gis.m/rules.tcl- set row [ frame $rules_win.output ]
./gui/tcltk/gis.m/rules.tcl: LabelEntry $row.a -label [G_msg "$label3"] \
./gui/tcltk/gis.m/rules.tcl- -textvariable GmRules::outmap
-width 30
--
./gui/tcltk/gis.m/runandoutput.tcl- tk_messageBox -type ok -icon
error -title [G_msg "Error"] \
./gui/tcltk/gis.m/runandoutput.tcl: -message [G_msg "d.mon
error: problem launching xmon, $error"]
./gui/tcltk/gis.m/runandoutput.tcl- return
--
./lib/init/epsg_option.tcl- set titlefr [frame $epsgfr.top -relief groove
-bd 2 -bg white]
./lib/init/epsg_option.tcl: label $titlefr.title1 -text [G_msg "EPSG CODES
(from file: $epsgOpt::browsedepsg)"] \
./lib/init/epsg_option.tcl- -fg mediumblue -bg white
--
./lib/init/file_option.tcl- tk_messageBox -type ok -icon error \
./lib/init/file_option.tcl: -message [G_msg "WARNING: The
location '$fileLocation'\nalready exists, please try another name"]
./lib/init/file_option.tcl- set fileLocation ""
--
./lib/init/gis_set.tcl- .frame0.intro.msg insert end [G_msg "Welcome to
GRASS GIS Version"]
./lib/init/gis_set.tcl: .frame0.intro.msg insert end [G_msg "
$GRASSVERSION\n"]
./lib/init/gis_set.tcl- .frame0.intro.msg insert end [G_msg "The world's
leading open source GIS\n\n"]
--
./vector/v.digit/cats.tcl-
./vector/v.digit/cats.tcl: Label $row.field -anchor w -width 10 -text [G_msg
"Layer: $field"]
./vector/v.digit/cats.tcl: Label $row.cat -anchor w -width 10 -text [G_msg
"Category: $cat"]
./vector/v.digit/cats.tcl- Button $row.del -anchor w -text [G_msg "Delete"]
-borderwidth 1 -width 6 \
$
BTW, shouldn't the REs like the above be collected to form a
kind of Lintian tool for the GRASS source?
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
