[GRASS-user] GRASS, ordinal not in range(128)

[Markus Neteler]

Hi,

On Tue, Mar 21, 2017 at 3:13 PM, Andres Solarte
<e.andres.solartec at gmail.com> wrote:
> Hello,
>
> I changed the debug level as Markus suggested
>
> g.gisenv set=DEBUG=1
>
> this is the result

good, we are getting closer...:

> t.register -i type=raster input=ndvi_andres maps=`g.list raster
> pattern=MODIS* separator=comma` start="2015-09-07" increment="1 days"

...
> D1/1: G_find_raster2(): name=MODIS_2015250_h12v12_1km_NDVI mapset=prueba
> D1/1: grass.script.core.start_command(): g.message -e message=ascii,Definir
> tiempo absoluto válido para mapa <,25,26,ordinal not in range(128)
> D1/1: G_set_program_name(): g.message
> ERROR: ascii,Definir tiempo absoluto válido para mapa <,25,26,ordinal not
>        in range(128)

In the locale/po/grasslibs_es.po file there is the mention of the
corresponding source code lines:

#: ../lib/python/temporal/register.py:422
#, python-format
msgid ""
"Set absolute valid time for map <%(id)s> with layer %(layer)s to %(start)s - "
"%(end)s"
msgstr ""
"Definir tiempo absoluto válido para mapa <%(id)s> con capa %(layer)s en "
"%(start)s - %(end)s"

#: ../lib/python/temporal/register.py:427
#, python-format
msgid "Set absolute valid time for map <%s> to %s - %s"
msgstr "Definir tiempo absoluto válido para mapa <%s> en %s - %s"

Probably a Python issue there in reading the "á" of "válido"?

Markus