[GRASS-dev] Translations and command description/options

If anyone has any other ideas, I would be happy to hear them out. here is what has been tried so far.

Hi

Panagiotis Mavrogiorgos <pmav99@gmail.com> schrieb am Fr., 8. März 2019, 21:18:

If anyone has any other ideas, I would be happy to hear them out. here is what has been tried so far.

Did you try to set this within the GRASS session?

export LANG=fr_FR.UTF-8
export LANGUAGE=fr_FR.UTF-8
export LC_MESSAGES=fr_FR.UTF-8

?

Maybe zshell still needs some extras in grass py?

Markus


grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

On Sat, Mar 9, 2019 at 4:53 PM Markus Neteler <neteler@osgeo.org> wrote:

Did you try to set this within the GRASS session?

export LANG=fr_FR.UTF-8
export LANGUAGE=fr_FR.UTF-8
export LC_MESSAGES=fr_FR.UTF-8

Thank you Markus,

Yes I did try that and it doesn’t help.

Maybe zshell still needs some extras in grass py?

zsh is certainly not well supported by GRASS (e.g. #3740). The lack of support is probably due to using “default_startup()” in “lib/init/grass.py”



> >



> 2235 if sh in [‘csh’, ‘tcsh’]:
> 2236 shell_process = csh_startup(mapset_settings.full_mapset,
> 2237 mapset_settings.location,
> 2238 mapset_settings.mapset,
> 2239 grass_env_file)
> 2240 elif sh in [‘bash’, ‘msh’, ‘cygwin’]:
> 2241 shell_process = bash_startup(mapset_settings.full_mapset,
> 2242 mapset_settings.location,
> 2243 grass_env_file)
> 2244 else:
> 2245 shell_process = default_startup(mapset_settings.full_mapset,
> 2246 mapset_settings.location)

Nevertheless, the issue we are discussing here is not related to zsh. Even with bash, the translations do not work

https://asciinema.org/a/232727

Not sure if there is any relation but just in case it proves useful:

I configure grass with:

./configure \

–with-nls \

At the end of the configuration step I get the following output:

NetCDF support: no

NLS support: yes

ODBC support: no

Nevertheless, g.version -b seems to think otherwise:

g.version -b

GRASS 7.7.svn (2019)

./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu --target=x86_64-linux-gnu --prefix=/usr/lib --sysconfdir=/etc --sharedstatedir=/var --enable-shared --enable-largefile=yes --with-x --with-wxwidgets=/usr/bin/wx-config --without-blas --without-bzlib --with-cxx --with-cairo --with-fftw --with-gdal --without-lapack --without-liblas --without-mysql --without-netcdf –without-nls --without-odbc --with-opengl --without-openmp --with-png --without-pthread --without-readline --with-regex --with-sqlite --with-tiff --disable-w11 --without-zstd --with-freetype --with-freetype-includes=/usr/include/freetype2/ --without-geos ’ ’ --without-opencl --without-postgres --without-pdal --with-proj-share=/usr/share/proj

Hi,

On Mon, Mar 11, 2019 at 6:49 PM Panagiotis Mavrogiorgos
<pmav99@gmail.com> wrote:

Not sure if there is any relation but just in case it proves useful:

I configure grass with:

./configure \
    --with-nls \
    ...

At the end of the configuration step I get the following output:

  NetCDF support: no
  NLS support: yes
  ODBC support: no

Can you please double check what's in config.log related to NLS?

Nevertheless, g.version -b seems to think otherwise:

g.version -b
GRASS 7.7.svn (2019)

./configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu --target=x86_64-linux-gnu --prefix=/usr/lib --sysconfdir=/etc --sharedstatedir=/var --enable-shared --enable-largefile=yes --with-x --with-wxwidgets=/usr/bin/wx-config --without-blas --without-bzlib --with-cxx --with-cairo --with-fftw --with-gdal --without-lapack --without-liblas --without-mysql --without-netcdf --without-nls --without-odbc --with-opengl --without-openmp --with-png --without-pthread --without-readline --with-regex --with-sqlite --with-tiff --disable-w11 --without-zstd --with-freetype --with-freetype-includes=/usr/include/freetype2/ --without-geos ' ' --without-opencl --without-postgres --without-pdal --with-proj-share=/usr/share/proj

Interesting, here it is enabled (ASCII emphasis is mine):

GRASS 7.7.svn (nc_spm_08_grass7):~ > g.version -b
GRASS 7.7.svn (2019)
./configure --with-cxx --enable-largefile --with-proj
--with-proj-share=/usr/share/proj --with-gdal=/usr/bin/gdal-config
--with-python --with-geos --with-sqlite
     --with-nls
--with-liblas --with-bzlib --with-zstd --with-cairo
--with-cairo-ldflags=-lfontconfig --with-freetype
--with-freetype-includes=/usr/include/freetype2 --with-wxwidgets
--with-fftw --with-motif --with-postgres
--with-postgres-includes=/usr/include/pgsql --with-netcdf
--without-mysql --without-odbc --without-openmp --without-ffmpeg

Funny idea:
  which grass77

Please check for conflicting installations, or files not belonging to
the user used to compile GRASS GIS (anecdote: in the past I got
trapped because I commonly do not run "make install" but run it from
bin.x86_64-pc-linux-gnu/grass77 and then I one day used "make install"
and immediately forgot the day after that it was executed from
/usr/local/...).

Best
Markus

On Mon, Mar 11, 2019 at 10:05 PM Markus Neteler <neteler@osgeo.org> wrote:

Hi,

On Mon, Mar 11, 2019 at 6:49 PM Panagiotis Mavrogiorgos
<pmav99@gmail.com> wrote:

Not sure if there is any relation but just in case it proves useful:

I configure grass with:

./configure
–with-nls

At the end of the configuration step I get the following output:

NetCDF support: no
NLS support: yes
ODBC support: no

Can you please double check what’s in config.log related to NLS?

Thank you Markus,

There is only a single line mentioning NLS:

configure:12419: checking whether to use NLS

I also attach the log file, in case it helps in debugging this.

Funny idea:
which grass77

Please check for conflicting installations, or files not belonging to
the user used to compile GRASS GIS (anecdote: in the past I got
trapped because I commonly do not run “make install” but run it from
bin.x86_64-pc-linux-gnu/grass77 and then I one day used “make install”
and immediately forgot the day after that it was executed from
/usr/local/…).

I don’t have GRASS installed. I always run it from bin.x86_64-pc-linux-gnu too.

What I do find most frustrating is that translations do work for the “text-based splash screen” (which is printed by lib/init/grass.py) and the GUI but not for the scripts directory:
https://asciinema.org/a/233110

with kind regards,
Panos

(attachments)

config.log (28 KB)
config.status.x86_64-pc-linux-gnu (25 KB)

* Panagiotis Mavrogiorgos <pmav99@gmail.com> [2019-03-12 02:39:01 +0200]:

..

I don't have GRASS installed. I always run it from bin.x86_64-pc-linux-gnu
too.

Pano,

I know you do, but just to verify again:
you do `make distclean` before each fresh compilation, right?

Nikos

On Tue, Mar 12, 2019 at 11:51 AM Nikos Alexandris <nik@nikosalexandris.net> wrote:

I don’t have GRASS installed. I always run it from bin.x86_64-pc-linux-gnu
too.

Pano,

I know you do, but just to verify again:
you do make distclean before each fresh compilation, right?

I occasionally do, but not before each compilation. But you were right. This fixed this. I expected that changes in “./configure” would somehow propagate, but I was obviously wrong.
Thank you