scripts/ Makefile bug in i18N string extraction
|Reported by:||neteler||Owned by:|
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: 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: 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).