No subject
Wed Nov 14 13:37:45 EST 2007
know that none of the recent versions had been tested on the Mac (I'm
fairly sure that the "libedit" change pre-dated the libgis I18N, and
the problems with that weren't found until after the release).
> 3. Tcltkgrass and intro messages: locale is set up during install and for good,
> which is not correct because it should be determined and chosen on startup
> of GRASS.
> ---------------------------
>
> This is right but misleading. Neither tcltkgrass messages nor
> grass_into and license messages are defined on install. Actually, as
> it follows from the [locale/Gmakefile], all possible locales are
> installed into $(INST_DIR)/locale, including tcltkgrass messages and
> text files, 'only if' GRASS was configured with NLS support.
Yes; I changed it; It originally used the value of $LANG at compile
time.
However, tcltkgrass is still only consulting LANG; for consistency
with C programs which use dgettext(), it should be checking:
LC_ALL
LC_MESSAGES
LANG
in that order. Init.sh consults all three, but has the ordering wrong.
> 4. More testing is needed to find out other dangers from I18N looming,
> before such code can be included into any stable release.
>
> ---------------------------
>
> No other testing except the developer's would be possible if you do
> not include the subjects to be tested into the release.
Well, some people did actually test the various -beta and -pre
releases, and even the bleeding-edge CVS versions. It just didn't
happen enough.
Now that 5.0.0 has finally been released, I'm less concerned about the
remote possibility of any I18N-related problems. However, I would
still prefer to see 5.0.1 being a bugfix-only release, with the
critical I18N changes (libgis, startup, tcltkgrass) saved for 5.0.2.
That needn't mean a long wait. Personally, I would have liked to have
seen 5.0.1 released as soon as the initial batch of MacOSX/gcc-3.x bug
reports had been dealt with, but Bernhard didn't seem too keen on
that.
--
Glynn Clements <glynn.clements at virgin.net>
More information about the grass-dev
mailing list